Russian losses in Ukraine reach 1,500 soldiers a day. NATO estimates that Russia loses 1,500 soldiers in the fight in Ukraine daily. This number includes both killed and injured members of personnel. About it informed the Guardian outlet with reference to a top NATO official who prepared to remain anonymous. Dan Sabo, correspondent of The Guardian, cites his source which states that Russians suffer most significant losses in the city of Bakhmut in Donetsk, Oblast. Ukraine loses an order of magnitude less soldiers but specific numbers were not revealed. In addition to this NATO estimates that several thousand shells are used by both sides every day. NATO cannot predict for how long the battle of Bakhmut will continue. At the moment heavy fighting is ongoing on the front line in the city along the Bakhmutka River which has turned into a killing zone. As of the beginning of March Western intelligence estimated Russia's losses in the fights for the city of Bakhmut in Donetsk, Oblast to be 20,000 to 30,000 of recruits of the Wagner group in the last few months. Killed soldiers are estimated to be about a third of this quantity. Additionally Western officials believe that the Wagner group is running out of reserves. As the number of men of draft age in Russian prisons where the Wagner mercenaries are recruited is beginning to decrease. Then NATO estimated Russia's losses in the battles for Bakhmut in Donetsk, Oblast to be five times higher than Ukraine's losses.


So, it's a great pleasure to be here, Privyet, that's about the Russian I know, sorry. You may want to get the headphones if you, because I'm obviously not going to speak in Russian, so the headphones are outside, maybe we can bring them inside or something. But thanks very much for having me, thanks to Speerbank for bringing me here, great to be part of this launch. So, I'm going to talk to you about what's happening, what the future of mobile and applications could mean. I live in Switzerland, neutral country, I also spend a lot of time in America, so if I speak too quickly, please wave. If you're Twittering, I'm G. Leonhard on Twitter, you can also ask questions, I'll try to answer them later. Most importantly, I want to start off by saying, okay, you guys may have never seen the future as before. Somebody who talks about the future, that sounds kind of crazy actually, because you really can't predict the future. My job is to share some foresight. Foresight are essentially this, listening to what's happening and trying to find conclusions of where to go. There's a great saying by a hockey player, I don't know if you're into hockey, but this guy says basically, a skate to where the puck, you know, the ball, the hockey ball, a skate to where the puck is going to be, not where it is. So we have to go into a future where we don't know what it is today. I mean, clearly you can see, for example, what's happening in the airline business, you know, in the airplane business, is many airlines are now looking to virtually transport people in five years without the airplane. So you buy a ticket to virtually go with holographic or telepresence, which is not the same than going with an airplane. So business is really changing. Here's all my clients that I work with. There's over 100 companies that we work with. There's 25 futurists. Okay, let me get into the topic. First of all, how often have you been to a bar lately? To where there's guys sitting around and talking to each other about the apps that they have on the mobile phone? You used to go to a bar to talk about football or cars or other things. Now you go to a bar and people compare what apps they have. I'm sure you've seen this. So mobile phones and mobile applications have come to be everywhere.  Basically kids are very much into the touch screen, just like old people also. So if you give your five-year-old the iPad, they figure it out in two minutes. What happens? The entire behavior change that we take a long time. Now see what happens when you give somebody something that's not an iPad, like this kid is trying to zoom the page, right? Because they're so used to a different kind of interface, right? Zoom the page from the iPad. Now this will be the customer of tomorrow. These people will grow up to expect us to do different things. They will not be business as usual. You can see, for example, the music business has basically died because of different expectations of people. They have lost 72% in revenues for the last ten years. The banking business is now in the business of disruption because all of a sudden people are saying we can pay with the mobile, we can send money directly using digital means, we can pay with Facebook credits, we can buy a ticket on Facebook, digital currencies, Bitcoin. You have all these things happening. It's disruption. But the biggest thing that's happening on the internet now in the last three years is that it has finally become really useful. It has become social. All of you, I'm sure, are a member of either Facebook or LinkedIn or Zing in Germany or basically we've all become interconnected.  The internet has become mobile. For example, in all developing countries, most of the internet access is mobile internet access. So Kleina Perkins, who is the lead investor in Facebook, has called this Solomo, Social Local Mobile, and that is the path for the future. Social Local Mobile and the cloud. The cloud means that all our music, our movies, our education, our health records is moving into the cloud and we access through the cloud. Which is very good news for a lot of things, but it's also difficult because the cloud means that we're much more powerful. I don't know if some of you may know this app called Flight Tracker. Okay, Flight Tracker, you download Flight Tracker and it tells you what's happening with your flight. So when you're standing at the gate, it doesn't work everywhere, but if you stand at the gate, you can check and you have more information about the flight than the woman at the gate. The woman who is in charge of the service, you know 10 minutes before her what's happening with the flight because better data in Flight Tracker. So it means empowerment of the consumer and basically the entire business of apps is based on this kind of idea. Now let's make no mistake about this, this is not always good for business because it means empowerment of the consumer. And as consumers, we like to be empowered, but as businesses, the more power our users have, the harder it is for us. So it's a challenge for us to create a business. I mean, if we're looking what's happening in Russia, I just look very quickly, but the internet and social, local, mobile is really taken off. You can see, for example, the biggest growth here last year in terms of online audience was in Russia, 14% of growth. And this number you can't really see down here, but it's the smallest cities in Russia that are growing the most in terms of internet access. So numbers are quite amazing and for big companies, banks, airlines, insurance companies, it's a little bit like your turtle on the skateboard. So now you have to get on very quickly. For example, Twitter. Any Twitter users here who's using Twitter? Let me see who's, okay, good. Keep Twittering. Twitter is a sign, for example, that many companies are now moving the customer service to Twitter. So you can complain about what they're doing, they will answer you on Twitter in real time. That brings up a lot of questions. But clearly, as you can see here, business and life is shifting away from the computer, from computing devices to mobile devices. We can see this here in this graph from Pingdom. In America, it's only 8% is on the mobile internet and Africa is twice as big already because they don't have regular internet. And Europe is quite a bit behind. But my prediction is this, by 2017, I think up to 50% of our entire internet activities will be on mobile devices. This is primarily because it will become a lot cheaper. So right now, I don't know what the iPhone costs here in Russia, but 800 euros, 1000 euros, very expensive. But in India, you can buy a tablet device, an Android tablet called the Aakash, for $35. You can expect devices to go in the neighborhood of 10 euros, not Apple devices, Android devices. And you can expect internet access to drop to almost free. So when we have this, mobile business is going to be 50% of how people interact and how they do stuff. Look at this charity from Kleiner Perkins, showing clearly how much we have left to go from roughly one billion smartphones to maybe in seven to eight years, 5.6 billion smartphones. This is a huge opportunity for everyone, but it requires new business models. As we can see with the movie business or the newspaper business, we can't take the old business and just put it onto an app. Because it will crash, it won't work, because people act differently when they are connected. We have to actually reinvent the business model. There's a great report that just came out from Raikou and the economist, talking about all the disruptions that are happening. I would encourage you to download, this is about 80 pages, it's free. And they're talking about all the stuff like cheap smartphones for all, business-oriented social networks, data mining, cloud computing, sounds very technical, but that is a description of what's happened in the future. The bottom line of this will be for me to tell you basically you have to disrupt something or you're going to be disrupted. You cannot just sit there and wait for somebody else to invent something and then you'll do the same, because the speed is much quicker now. In fact, I would say that you have to disrupt yourself. So I'm hoping that Spurbank will disrupt itself with its own app to reinvent how business works, because that's really what we have to do. Evernote is a great example of disrupting the process. Dropbox, you guys know Dropbox? Same example, disruption of how this works. So basically what we're seeing here is in this graph, this is the most dramatic graph, it's actually wrong because it happens earlier, is by 2014 more people will use the mobile than the computer to go on the internet. In other words, you could basically say if you're not mobile, you won't exist. If you're not actually offering your products in a mobile way, a lot of people won't see you. If I'm going to your website and your website isn't mobile on my mobile device, then I just go somewhere else. This is quite a challenge, because obviously it's different. Amazon has been very good at this disruption. Think about this, Amazon has created in five years the effect that more people buy books on the Kindle. I'm sure you have Kindle users here, even though it's not in this country, but people are still buying Kindle everywhere. They sell more books on the Kindle than they sell in print in five years. So that is real disruption, but the other thing that Amazon has done, very successfully, is this. I don't know if you have WD-40 in Russia, but they lubricate, right? They make it work. Amazon has spent hundreds of billions of dollars in creating a new business, the Kindle business, which didn't exist. So my point to you is that you have to both disrupt and you have to lubricate, you have to create a new business. You have to become a market maker. Don't be a market waiter. You can't afford to be a market waiter, especially not in Russia, because things are moving very, very quickly. And all these markets much quicker than in Germany or Switzerland. In fact, you could say all stats point in one direction, is that all of the interesting innovations on the social, local, mobile internet will not happen in developed countries, so-called developed countries like Germany or America. They will happen in emerging, even though Russia doesn't really quite fit that, they will happen in Russia, India, China, Brazil first, because of the speed. Banking, here's a quote from somebody in 2000 from Forbes magazine saying, the internet banking has failed to live up to its expectation. That was in 2000. It was too early, but sometimes change takes longer, but when it takes off, it's much bigger. That's what we're witnessing right now. It took longer, but now it's a take-off point. So it's a point of where all of a sudden it works. I mean, look at the mobile internet uses distribution in Russia. It's between 18 and 35 years old is exactly the target group you want. Those are the ones using mobile internet. And they may be the early adopters here right now, especially on the iPhone, but they are the leaders. So you may have a family like this, right? There's us reading the newspaper and our kids are over there on the device. And now around the world 50% of people who are watching television are on a second screen, you know, the mobile phone or the tablet, talking with their friends about the TV show. It's called the second screen. And there's a whole new generation of people who are talking about social television and how we talk to each other while we're watching TV. So there are big differences, but they will flatten out. Well, we can't go through this really in detail. It's very hard to see here, but I call this the app of financial banking, money, financial services is a huge opportunity for this way of connecting people through social and local. Take this example, American Express has an app that's called the Open Forum. We have thousands or tens of thousands or actually about 200,000 people talking about financial services and there's no selling whatsoever of American Express. So in a way you could say that mobile money also means social banking, whatever that could mean. Here's a good symbol for this. Social banking means that your bank is now becoming a different place. Your institution is becoming a place for conversation, which is actually quite difficult because try to have a conversation with 20 million people. The number is huge. Most importantly, this is the biggest bank in Brazil. I do quite a bit of work in Brazil. This bank has 127,000 followers on Twitter. This bank has a real conversation with all the people. Every day they have 28 people who are Twittering and doing customer service and product development through Twitter. Clearly that's gonna happen here as well. I mean, in many ways, Twitter is already referred to as being TNN, the Twitter news network. And many people are saying Twitter will be as big as CNN in terms of the reach. So I think for this kind of thing, if we think about engagement, it's much better than enslavement because especially in the financial sector and in telecom, it was all about owning the customer, locking down the customer and all these nice things. Now it's about engagement. And if apps are going to be successful, they have to engage people. They can't imprison them. So what's happening is now that because everything is starting to be a screen, if sometimes when you take a taxi in a big city, you see the driver has five screens. Navigation and Facebook and the taxi thing and all screens are everywhere. And rather than having paper and books, all of a sudden we're in a world of screens and data. And that's going to take off. And you're going to feel like minority report, okay? Constant data screens, in fact, probably too many. There's already people who have what's called screen addiction. They always have to go do something while they're having dinner. Or in America, 28% of people when they wake up at night do a Facebook update. Crazy, Americans, you know, can you say? Anyway, now every screen can become a connected TV and radio. This is a huge opportunity for companies to broadcast, to become broadcasters, to send videos, to talk to people, to have a video channel. And video is obviously the most popular on the internet. So creating video channels for companies. Because now we used to be people of the print, you know, the mailbox and the newspaper. Now we're becoming people of the cloud. And this is quite worrisome for a lot of reasons because of data protection, for example. What happens with all my data? As you can see, Facebook was not very popular in the IPO for this reason. People are not sure that Facebook will protect us in terms of the data. This is the primary reason, by view. So this data cloud is going to explode. So whoever has a business of connecting the crowd, the people, and the cloud, that's a really good business. Connecting the people with the cloud. And there's hundreds of examples for how this works now. Very powerful stuff like Netflix and Swook in Russia and Spotify. So people of the cloud now have all these options. I'm sure that there are many users, for example, e-books, Instapaper, Flipboard, all the stuff that works in the cloud. So banking in the cloud, next is education. In the cloud. Being able to study. I can add that later. Oh, it got kicked out there. Sorry. Okay, Evernote is in the cloud, too. So we're moving from a society that used to be TV centric. You can see yourself here from 20 years ago. A society of TV centric where 75% of people watched the same TV show. In most countries in America was up to 90%. Today we have a society that's becoming mobile centric. And the television is still a big part of that, too. But think about that. What would you rather not have? I mean, there's many people who sleep with their mobile right on the nightstand, right? I'm sure you guys do the blackberry in the bathroom. So they're becoming mobile centric. And television now, television is lucky. I don't know if there's any television people here. But television is very lucky because television is converging with the internet. It's becoming the same thing. If television wasn't converging with the internet, it would be useless. Now, every television is connected to the internet. As you can see right here in Russia, Cartina TV already has a direct channel that you can use in this box, right? Going on with over-the-top content. A quick word about advertising. I think this will be interesting to discuss later. Advertising, as I'm sure you're aware of, advertising is a $650 billion business globally. And then there's marketing and public relations and various kind of noise-making and data mining. It's roughly $1 trillion. So now, that $1 trillion is shifting budgets into mobile, into social, and into digital. And in some countries, it takes longer. In America, we've had newspapers declined by 41% last year because that money is going into other places, into digital places. So we're looking at roughly a wave of about 30% $300 billion shifting into mobile advertising, social advertising, interactive advertising, game-based advertising. So if you're in the advertising business, you will essentially have to reinvent advertising, which is good news because the old advertising was bad anyway. We can get rid of it. Important fact, the customer of tomorrow is this kind of customer. You may have seen this video. It's a FedEx guy who delivers a computer and throws it, doesn't even ring the bell, just throws it in the garden. Now. Huh? It was a flex screen. Yes. So security camera recorded him, of course, right? And within eight hours, he had like 850,000 views. The stock went down 4% for a day, came back then. Of course, it became a huge thing. Basically now, your customers are expecting radical transparency. Your customers are going to expect that you are going to constantly keep an eye on them. And this is something to expect. I mean, if you're going out, for example, with a mobile app or with a social engagement, you better have to clean up before you do that because everything is going to come out. It's very hard news for companies that used to be closed, especially financial services and those kind of things. And then we have nowness, so-called nowness. That means a lot of people aren't interested what was good last year. They're interested in what's good now. And Twitter is the expression of that nowness.  And this is also what people are expecting of customer service. If you launch a mobile app, they're not going to want to call a number and wait for an hour. They're going to expect immediate conversation on the app. Really changes the game. So here's some challenges for you as far as business is concerned to think about. First, radical consumer empowerment. And this is not just like an idealistic headline. This is a tough reality. Consumer empowerment is quite difficult for those providing it. For those having it, it's good. Massive competition for attention. Do you know that most apps, about 92% of apps are installed and used once and never visit again? Because there's something else. If you're going to be good at apps, you have to really, really get and keep people's attention. Real-time interactions, zero tolerance for technical problems. I mean, this is pretty tough. You should talk about that later when you talk about your app. Constant stream of added values. Quite a challenge. And here's the other challenge. Many big companies are talking about, the principle number one is to plan for ROI, return of investment. Financial planning, projections. But now because of speed and because of what's happening in digital communications, I call this return on involvement. We have to switch from the idea of getting back our money from investment to the idea of how we can involve our customers. Whether it's businesses or consumers. A Chinese saying basically said, okay, involve me and I'll understand. Confucius said that rather than advertise to me. I'll skip this because we want to get to the end so we can have our conversation. Some great things about apps. Number one, you can get data from people. But here's a piece of warning. I don't yet or use any data without explicit permission.  You get locations. You get stickiness. This is the great thing about apps. But getting user permission for data is crucial. Getting them to allow you to actually do something with the data. Another word of caution is that many of my clients are building an app because they want to have a better mousetrap. They want to do the same thing with the customer that did before which is to lock up the customer into a system where they can't leave. Telecoms like to do this. I know there's any telecoms around here. Or media companies. That will be very hard to do. We have to essentially get rid of this idea of a captive customer. There's no such thing. I would propose to change that into a loving customer. Think about what people love, what brands. Apple is a cult, right? People love Apple by whatever Apple does. People love Google still also. Maybe people like VContactor. I know they love VContactor, I'm sure. They love Twitter. When people talk about brands today, they talk about love. Not about captive. So this kind of idea, especially famous with big companies, that could very well kill you in keeping a captive customer. Great quote from Doc Searle says, in the future a free customer will prove to be more valuable than a captive one. So if you can set your customer free, you'll make a lot more money, turn them into empowered users. The other thing is today that, because today we're becoming a global society, a networked society, everything that we do is really about trust. I mean, not just in financial services, but everywhere. Who are you going to trust? Who are you going to trust for your car, for your data, for your education, for your money? Trust becomes essentially the currency. And this is really the main thing about apps. When you're using apps, you're using that app to create trust. And trust is also based on transparency because I can't trust people I don't really know. So if you want people to trust them, to trust you as a business, you have to publish more things. If I see your name on LinkedIn and it says XYZ name and then just dot, dot, dot, no other information. Maybe you're famous and I don't know you or you don't want to talk. One of the two. But it doesn't create trust if I can't look at you. Trust is something that we need to be open with. So trust is the new currency. Trust is the real money. And whatever you do on mobile apps or with technology has to reflect the trust factor because that's where the money comes from. I trust Dropbox not to delete my files. I trust Google not to publish all my emails. And I did trust Facebook for a while. Maybe I still trust them. I have to think about that. Okay, I'm coming to the end here. So Facebook is a great example. Facebook's IPO, I'm sure you've watched it. Hopefully you have not bought any Facebook stock. But I'm watching this, but basically what's happening here is that we can say some walled gardens like Facebook or Apple, they're actually quite nice. We have nice flowers and beautiful place. But in general, open platforms are the feature because to keep a close platform attractive, you have to invest a lot of energy and lock people inside the platform.  But don't bank on it. I mean, that would be very, very hard to copy. So open systems like HTML5 and here's a rule for apps that not all may agree with. If you can do it on the open mobile internet, you should. If you can't do it on the open and mobile and public internet, you can use an app. That is the reason why you use an app. For example, banking is very hard to do in a secure way on a web app, right? But that's sort of the rule. We'll talk more about that stuff later. Here's a quick summary and then we can have some questions. Otherwise I can talk until tomorrow morning and we'll still be here hungry. So the future is social, local, mobile and the cloud. And that's basically a recipe for the future. It's not about the computer. It's not about the internet. It's not about all that stuff that we had until now. This is actually a new generation of the web and of course the word open also plays in there. User control. The more user control you give your users, the more power you shift to the more success you'll have. But this is difficult. Clearly that's difficult because you're telling your consumer to tell you what the product should cost or what the next edition of the car should look like. I mean, this is quite hard to do. Disruption and lubrication. You have to disrupt something. I mean, I'm sure some of the panelists will tell us a story about what they can disrupt. But if you look at the last 10 years, the successful businesses around the world have been those that have disrupted others. Skype, eBay, Twitter, Amazon, Google, YouTube, Facebook.  It's about disruption and lubrication. Make it sticky. Keep in mind when you launch a mobile product, most people will never use it again if they don't have a reason to come back. So making it sticky is crucial. It can't just be a copy of some other boring stuff that you did before. If you're a bank, you're now in the social business. You have to get connected and open up. If you're a financial institution, that's inevitable. Even in Switzerland, the banks are doing this. Cloud intelligence, getting data from the cloud, dealing with the cloud. Transparency. If you're gonna be part of this sort of new future of getting connected, you have to become more transparent and more open and you have to get ready for that. It's very hard. Sometimes I say it's very hard to lie on the internet. It's possible, but you have to be very good at it. It's very hard to tell people stuff that it's not so because they can look it up and they can talk about it. This brings me to a very important point we'll discuss in the panel. I believe that many services that are launched on the web today have to be in some sort of form-free initially. Because consumers today really love this idea of getting something that gets them inside without a penalty. This is a recipe for the future of print, newspapers, music, media. A freemium model. Avenote, of course, is a freemium model, for example. Okay, and the trust factor. Talked about that already.  This is our future. We can choose to engage and that will be there. If we don't engage, we'll probably die. Thanks very much for listening. Thank you very much, Gert. I can't...


Welcome everybody to the weekly firefly community call. Thank you for joining. I don't have many announcements for actually I don't have any announcements for the beginning of the call today but for today's topic for the first part of the meeting. Peter Broadhurst will be speaking on event-driven programming design or event-driven application design and how this is, you know, firefly is built with this design in mind and things just work great when applications are also built in this with this event-driven mindset and Peter's going to talk through kind of how to approach building a firefly app in an event-driven way and how firefly itself handles things in an event-driven way. So thank you Peter and I'll turn it over to you now. Thanks Nico and as per normal plan to use just I guess up until 35 plus on this piece and then just have another open forum for any topics that we want to run firefly after. Okay, so we thought it would be really good to do a session on event-driven programming because there's a sort of assumption in every piece of how firefly has evolved that the wave at the system, the wave at the multi-party system will be built is in an event-driven way and it's a particular type of programming. It's definitely not a new type of programming, but it is a particular pattern and it's not a pattern that everybody's come across. So I want to talk through that pattern from ground up really in this session and build up to talking about how event-driven programming is different in a multi-party system compared to all the other types of event-driven programming that you've done in the past and then talk about how it actually works practically in firefly. So that's the journey we're going to go through here. So to start with, I want to just really try and be clear about what I mean with event-driven programming and what it's different to. And the terms I'm going to try and use consistently throughout are request, reply, and events for the two sort of ways, fundamental ways that if you've got two run times administered separately, they might be like microservice architectures in their own way, but you've got sort of, you know, the payment system and the reconciliation system, they're separate systems. There's two really fundamental ways that you can connect them together. We're not talking about wire protocols or transports here, we're just talking about fundamentals. You can either use a request, reply approach, which is synchronous, but I'm going to try not use synchronous and asynchronous because there's so many ways that those could be used. And request, reply approach, which is like a telephone, system one wants to talk to system two, so it makes a call to system two and waits, waits for that call to complete. This is the way, you know, a REST API to the internet works. It's the fundamental way that HDP works, but you can layer stuff on top of HDP.   So the outcomes are either a success, you know, a HDP 200 okay, a failure, I've got a 500 or an hour or some kind of explicit error, and most of the time with hours you kind of know what's happened, or equally likely just nothing at all it just sort of a deadline, you know, we've all been on hold to the, you know, to the, to the wireless telephone provider and you get put on hold and it's silent and it's like, are they still there? Have I been lost? What's happened? And you just sort of eventually give up and put the phone down. How do you find out if it's worked or hasn't? Well, you kind of got to retry it and make another phone call. So that's, that's request reply approach to building applications. And there's two things. One of them is that both sites have to be available and ready to talk to each other. The other way is it's really just a one to one thing. You know, you've got one system on one side and one system on the other and one's talking to the other. It's a different way of programming and it's a fundamentally different way of programming and this is to use events. To not say that I've got a request and an exactly one reply to say I'm emitting an event, might be a request, might be a broadcast, might be anything. I'm emitting an event. And just like with a text message or an email, I can choose, I can expect that I'm going to get a response pretty quickly. But I'm not like beholden to having a response really quickly.  I can, as an application, I can move on and do other things. And whenever the other parties ready and it's got through the, I don't know, 1000 things I've put people have put in front of it before that gets to that, that particular email in their inbox that particular text messages come to them that whenever they're ready and they respond, you process that response. And this is a very flexible pattern because you can have lots of different failure handling strategies, you know, you can send things multiple times and and we process them which is kind of the only way that you can do it for request reply messaging. And you can also have things like compensation logic to live out sagas later. And you can also just choose to ignore things that you can't, you can't process and maybe say no, I can't process it. Or, or just, just ignore it because you know it's a duplicate or you know, you know that there's a reason why it's safe to ignore it so it's a very flexible way of programming. As I said before, firefly and these are some of Nico's charts and Nico did a great, great introduction to firefly in a community session we had two to three weeks ago. So which is recorded so you can go and listen through the fundamentals here but but firefly supports both patterns fully. One is built on top of the other and this is quite common in enterprise systems the request reply capability is just a special type of events, use of events you're just sending one event and you're expecting exactly one reply. And we're going to talk a little bit more later about the actual interfaces here and how you build applications on top of firefly for for this. And we'll come back to this I promise, but I'm going to, I'm going to take a bit of a bit of a roundabout route here and talk a little bit about the history of events, because it's the topic gets my heart I've lived it since the very, very, very first day of my my career in enterprise it I worked on on the core of the messaging technologies and in IBM called the series. And the year I started this this book was was published and it's a pretty famous book in the enterprise space and the hub and wolf enterprise integration patterns and the, the website still there she can go read about them they're still super applicable patterns. And back back then, you know, to turn a bit. You know, this is evolved over about three decades so this is kind of like the end of the first decade of the evolution here. We have these patterns that were for integrating systems within an enterprise right you've got 20 different systems, you that they're all decoupled across the world. How do we integrate them together and there's a set of these really well established patterns that evolved into things like an enterprise service bus after this book came out, and they evolved into things like service oriented and then whole companies formed, you know, driving home this sort of concept of an event driven architecture, you know, famously companies like like tipcoe really really focused on that for the whole of their existence. You know, and that's that approach allowed very resilient, resilient systems in the core of organizations, you know, the payment wells of banks, but you know the core transaction processing systems of insurance companies and supply chains and healthcare were all built using these integration patterns and they generally were event driven. And all of this happened and then web services happened and West happened and HPP became the flavor and a lot of a lot of things moved to a sort of synchronous. You know, request reply based based approach after this. And then there was another way, there was another wave in the sort of mid, mid 2010s of a resurgence of the understanding of why event driven programming at its core is just this fantastic way of of being really sure you're going to get the right outcome out of the end of something. And, and this time the focus wasn't on multiple systems all connected together and services on today's structures it was about writing really good software. And these fantastic programming languages came out and frameworks like Erlang and Scala and then the ACA framework and the reactive manifesto. And I think that the pattern that really encompasses it and the best written about sort of description of like why does event driven programming, like create good applications I think is if you read about the ACTA model. So I'd encourage you this is a really great great like five minute read to really understand how event driven programming, even inside of an application like inside of one process can allow resilient engineering. Think of this picture here as multiple, multiple players in a network think of this as just, I've got bits of logic. I can instead of connecting together by having more call each other wait for each other. I can put these mailboxes in between them, and I can decouple them, and I can say one piece of logic updates its internal state and then drives another piece of logic. And, and I know everything that's happened. It's a sequence of events. And if you can just think about the way you're writing the end to end business logic, not not like how the system fits together the business logic. It's not to think about it as the set of state changes and in a state machine. And, and you can break all of those state changes back into being a set of inputs, a function that runs on them deterministic or non deterministic that's fine doesn't matter function that runs on them. It triggers one or more other items of processing that way of working happens to allow you to scale really nicely to a distributed system. Now, micro services then came came along. One of the most exciting things to happen to the way that we build applications over certain the whole of my, my, my career and we stopped building these monoliths. We stopped building these massive Java application server applications that just like we're all in a box and we started. We started writing things that the application itself needed to be decoupled and connected together and like some of it's written in Java and some of it's written in Node.js. And some of it's written in Go and maybe some of it's written in Erlang and Scala, but all of these bits are running independently and scaled independently, and a whole new generation of programmers came and performed some amazing integration and Chris Richardson that wrote some of the stuff on this slide is is a great innovator in the space and and we discovered a lot of the same challenges that the previous wave of integration system challenges and the enterprise integration that we discovered before and and and had to even inside of one application now so the one application because it split into lots of different runtimes have to worry about how do you do a sequence of events with reliable outcome. So if you if you follow this this link you'll you'll hear about the saga pattern, which is kind of multiple services had events from the beginning they thought about events from the beginning. And saga is kind of like the latest generation of how people think about. I've got a bit of logic. It needs to call another bit of logic. What, how do I cope when that follow on piece of logic doesn't doesn't complete what what does compensation look like in the modern in the modern world. If I've got a history of events, this is the critical thing I've got a history of events and something fails, I can look back at what happened and decide what to do. I can only do that. And that's why it's called a saga. If I've got this history, like it's an evolving story that's got a, you know, a story art that goes from from. photo in Hobbiton all the way through to photo coming coming coming back, having Jesus smorg, like that, all of the, the, the, all of those hundreds of pages of story up like that's what your transaction looks like. And if you've not got all of the pages in the book marked out in a way that you can look back at them it's really hard to know what to do when something goes wrong. So if you think about it as this sort of evolving saga with information about everything that happens, you can kind of cope with anything which is, which is beautiful it's, it's, it sort of feels like utopia from a programming perspective but it does have some challenges which is, and you do have to think in a slightly different way so I'd encourage you to read some of the things that I've linked to here because, you know, people who are much more than me have really talked through in a great way like why event driven programming in all of its forms is valuable. So here we are in in the 2020s and we're on the edge of a new way right this multi party system thing that's evolving that the fireflies trying to accelerate. And that is, you know, the thing that is enabled by enterprise blockchain and by these fantastic technologies like zero knowledge proofs and peer file sharing technologies like IPFS and trusted compute engines like this multi party systems revolution this next step in the journey is really exciting because some things haven't changed, but really important things happen. So let me talk about that right. So what hasn't changed the majority, the vast majority because it's already been written it's in place it's it's the existing core systems of processing is still going to be unique to each player in the system. We're connecting people together and previously we might have been using Western interfaces that aren't so event driven we might have been using event driven integration patterns between people in between organizations in the past. And there obviously everything was private because there was no shared state but even in a multi party system, you have to just bear in mind that most of what the business cares about. In terms of their processing the human decision making their business processes, even special, you know proprietary logic that they've got that they think is valuable is going to be unique to each member. And that's going to be the majority and like terms of line to code it's always going to be a majority. It may not be the most critical piece of pieces and that's why the blockchain could be so valuable but you know it's just so much logic that is going to be unique. And it's the same with the data the vast majority of the data in an enterprise situation and here it's like, it's the 99% case the data by volume at least the data is going to be really private and sensitive. If it wasn't private and sensitive there wouldn't be an interesting problem to solve like so those things have not changed, but some stuff has changed and stuff that's changed to me. That's why I got into blockchain. It's the reason why I went on the jet that Virginia we found a collider ways is suddenly you can do this stuff and that fundamentally different way because a few things have changed. So some logic, some logic can be executed deterministically. It's in a way that no one can argue on the outcome because every, you know, enough people executed it or they executed it with a proof, you know that there's a consensus or trusted compute and proof or zero knowledge proof that says look, there's no arguing about the fact that this particular data isn't happening. That's fantastic it enables tokens enables enables like critical sort of decision making processes that are at the heart of the most sophisticated transactions where it allows those to be executed to terminally across the organizations and that's fantastic and that's never been possible before. And it also allows you to store some data in a way that everybody has it and that's really cool. I mean it's kind of been possible but before, but, you know, it's really embraced in in if you use technologies like blockchain or blockchain if you can have references or the data itself stored in a in a place that everybody has got a copy of that data and that's fantastic but again bear in mind that's not going to be all your data because there's no challenges without an enterprise to get that in case. And then the thing that this all builds upon, particularly all of this, this determined execution logic is is the thing for this presentation in particular, that's transformative over every previous generation of this tech. Instead of just having an event bus that's local to one organization. We've now got a shared sequence of events, the sequence the order is agreed through a really resilient multi party consensus driven technology, a blockchain and distributed ledger. How cool is that that is just mind boggling the transformative to how event driven systems can work because suddenly now that sequence of events can be multi party systems of events. That wasn't true in the inventory of an integration age that wasn't true in the West web services. So, age for an SOA for connecting together organizations, microservices proved how powerful it was to have that inside of an application but microservices are, you know, that's about building one application inside of an individual application. Now we can do this in a way just can't be argued way it's not worth arguing that blockchain is wrong way that you're not going to have this where's my what sequence of things happen and where's my message kind of challenge that we've always had in the past so it's transformative. What that means from a solution development perspective is that you can now you can now build these multi party business processes and get some, maybe most, but some still massive of the benefits that you that you could just the things you could rely on. You're building a system inside of your organization, like you're building, you know, maybe previous generation business process management, you're modeling a business process maybe you're building a microservices you're building a solution that that that you know has a user interface has API's connects to your core systems that implement a business process gets a transaction done end to end. We do that inside of an organization, we can now do the same thing cross organization. And that's really where fireflies trying to make the job simpler, you connect together the super on chain logic the tokens that you know simple pinning as well but the custom on chain logic you connect that together with the off chain integration to the systems across multiple parties. And we've got the shared signals of events that we can actually like do the same kind of application and business process that you can do with a microservices architecture in one organization. And there is a couple of gotchas, a couple of things that just like the laws of physics are a little bit different in this environment to they were in, in just like microservices isolated environment to one organization. One difference to having seen lots of developers building this pattern as because you know we've been doing this for quite a while in the evolution of a far flying before it came to hyperledger. One of the things that's a little bit like the sort of squint how did that happen is the event bus when it's a blockchain backed event bus, when it's an event that's significant enough to sequence it across organizations. You can't just assume when you send the event that you know where it slots into the sequence on the sending side. Now that has not ever been true really in in in in messaging systems right. So I've got I've got a Kafka queue or or an MQ or tip curious be or an active MQ between me, you know my my system like we say payments and reconciliation where I've got my payment system is on the reconciliation system. I send message 123 I just sort of know that 123 is going to arrive on the other side they're going to process message 123 right that's just true. It's a little bit different here because the you're not the only one submitting the the the the apps. You can't just like even if you do you're doing horizontal scale in my services you can still often like know that you're the only one that's sending these events. The events are being sent from the other sides as well as like five parties involved they're all sending these events. You can't assume just because you sent that event but it's going to arrive first. So, here's the trick you as the sender also need to process that event in the order of the blockchain that everybody else is saying. So you end up with this sort of initiate confirm step on your own, your own logic. You have to sort of say look, I think the first, well, the first one isn't so interesting I think the second step, like, is, is, I know it's a bidding system right I want to I want to, I've received a request for a tenant I'm going to I'm going to submit. But like the first five submissions when I think that I've I'm going to submit and my submissions going to be number four, and I submit it. I looked and there was only three submissions before I submitted it well that's not good enough to know that you were number four. You can't trigger the bit of your logic that says to your users, I submitted it and your number four at that point you can't show that state yet to your users. You can't have that in your core systems, because until it's been ordered and then you process it and at the point that you're processing it. You look at the current state, and you say I'm still number four, number, you know, another number four didn't come in before me. You can't rely on that being true. So just because you sent it doesn't make you special and you have to process, you have to think of your own events being ordered, along with everybody else's. It's really like it sounds subtle but that really does just create an extra level of force in your applications, you have to do a send and then you have to process your own applications. Now one thing that we are doing in Firefly, and there's an issue tracking this one one two is we are going to make it so that if you want to Firefly will block. This is not a synchronous asynchronous because, but it because this is this is hard like this is, this is not changing the fact that this is nice synchronous event, but I'm sending. We can make it so that it will block until you've got the confirmation from the blockchain, and that event's been confirmed so you don't have to, you know, if you want to just sort of wait, and have a spinner. Then you can do that and that back there's just a few places where it's like particularly early on in development is super super easy to do that so we're going to add that at that end of our life. So there's now another difference. And I'm conscious on time and I've been waffling a bit. But there's another there's another difference here. And I think this one's really significant personally. If you squint of a messaging technology, if you squint. But there were very, very different shaped messaging technology to traditional message queuing streams. So if you've used, if you've used when you know one of those mq technologies or you've used the you know the latest generation of things like Kafka streaming. Either that's super reliable right they, they, they, they look after your messages they get them to you really from a to b really really quickly they batch they optimize they have your ability or persistence it's often called they, you know they coat with periods of downtime they're like they're awesome. Those technologies should still be used in these sort of modern systems. But but they're not like a complete history of time. I believe without exception, and I'm happy to be proof wrong on it, but I believe without exception they, they say it's really big anti pattern, even if they support like turning up the size of your q depth, you know or transaction ledger to infinity. They're not designed to be a replayable complete history of time. They're designed to be a buffer from a and B to be a mailbox. The mail goes into it. You know, the postman can fill it up to the top they can stick stuff on top of it maybe a bit they can stick stuff underneath, but eventually it becomes full. And when you want to read stuff you take it out of the mailbox and you open it. It's no longer in the mailbox anymore. That's different to the way a blockchain ledger works blockchain ledger is designed to allow you to look back in history and see the complete history of time. It's super fantastic that's, that means that things like late join and catching up and looking at the state of the state of things. You know, if you're new or you're catching up or you're going back in time you can see like a saga, you can see the complete history now, and you can build applications that can have that that history in an immutable way that that's, if you've read about the UTXO model that the the unspent transaction output a model of the way that blockchain like Bitcoin work that that's what they're built on like that that concept that you know for sure right now you can trust the right now but also you know you can prove the right now by looking back in time to be beginning of beginning of time so so anyway that's that I think is a really significant thing and just to weird away. For our flights built on this concept you kind of need both you need the private reliable messaging and you need the, you need the ledger.


Last November the people of South Dakota voted to legalize recreational marijuana and it was set to go into effect this summer However, a judge appointed by the state's governor who was a Trump sick of and by the way has decided to unilaterally overturn the will of the people and her reasoning is Bullshit so as Reed Wilson of the Hill reports a South Dakota judge ruled Monday that a voter approved a constitutional amendment that it would have legalized marijuana for recreational use was in itself unconstitutional Setting up a legal fight that pits governor Christie Noem against her own constituents circuit court judge Christina Klinger a normal pointee in Pierre ruled that amendment a Violated a rule that ballot measures cover only a single subject and that it does not conform to rules Governing the way the state constitution is amended South Dakota voters approved amendment a which legalized recreational marijuana by a 54% to 46% margin in November a separate ballot measure legalizing marijuana for medicinal purposes passed with almost 70% support South Dakotans for better marijuana laws the group that backed the amendment pledged to appeal Monday's court ruling We disagree with the ruling and we are preparing our appeal to the South Dakota Supreme Court The group said in a statement state Attorney General Jason Raffensburg's office, which is responsible for defending state laws Said Tuesday, it is still reviewing the judge's decision Raffensburg's attorneys had moved to throw the challenge out earlier this year Noem a first-term Republican governor who allied herself closely with former President Trump has been unusually focused on opposing the amendment Both during the campaign and after voters gave the measure their approval the lawsuit challenging the amendments validity Was brought by the head of the state highway patrol who sued at Noem's request and the sheriff of Pennington County Where amendment a to take effect in July South Dakota would be the 15th state to legalize marijuana for recreational use and the 13th state In which voters themselves approved a ballot measure to make marijuana legal So for whatever reason this imbecile decided to sabotage a law that her own constituents passed Does she want to be a one-term governor? It's not like this was close like this passed pretty solidly. I Just don't understand Why you would very explicitly go against the will of the people like they clearly want this and you lost you made the case against this It was nonsensical they saw through it and they voted to legalize recreational marijuana But you just you couldn't take it You couldn't handle them not doing what you wanted.  How is this small government? Aren't you supposed to be pro-capitalist? Having a flourishing marijuana industry in your state isn't that pretty pro-capitalist Isn't that the free market? Like I just don't get it these folks are hypocrites by their own standards But no reasonable person should be against the legalization of marijuana for recreational uses because guess what? It's been done before in other states and It's a success everywhere in my state. I literally can walk into a store and purchase pot It's simple everyone loves it and there was a lot of fear mongering at first particularly like during the campaign days When it was on the ballot, but now people who were naysayers supported Older people have tried it who were previously against it because it was stigmatized But legalizing it not only does it get rid of the stigma, but it gives people access to it Who didn't previously have access to it who have found that it helps them to sleep better or you know Decrease anxiety or hell God forbid lets them have a little bit of fun Like this is a very very stupid thing to be against It's bad politics and it's bad policy But the governor of South Dakota decided to spit in the eyes of her own citizens.  It's it's just genuinely baffling to me how anyone in 2021 can be against grown adults using pot Insane, so I hope that the group who is appealing this is successful because this cannot stand I mean, this is very clearly like it's bogus. They're trying to shoot this down on a technicality But you're just trying to overturn the will of the people So do you or do you not hate democracy? It's not like they're voting on anything That is going to harm the public or harm a particular group of people They're voting on a civil liberties issue that's been decided in states. That's not even controversial in some states So I just don't get why you go out of your way to get on the losing side of this argument like history is Going to look back at you very unkindly and see you as an obstacle to progress progress that everyone Agreed on basically.


Hi everyone. Thanks so much for joining us today. My name is Erin Griffith and I'm the Program Coordinator at Fedora. Today I'm joined by Tim Shear from the University of North Carolina at Chapel Hill and current chair-elect of our Steering Governance Group, as well as Robin Regaber from the University of Virginia and Amy Blau from Whitman College, our two pilot partner institutions from the IMLS grant that we're here to talk about today. So to get started, I'm going to pass it over to Tim who's going to give you a brief rundown of Fedora and what you can expect with the latest version of our software, Fedora 6.0. Thanks Erin. Fedora is simply a flexible modular open source repository platform with native link data support. I'd like to emphasize that it is flexible. It's agnostic about what you put in it, the relationships between those objects and the metadata used to describe it. And it's brought us since it's focused on digital preservation and file management and dissemination of digital content. It's especially suited for digital libraries and archives, both for access and preservation. Fedora's been around for quite a while now. It's one of the first repository systems, open source repository systems out there since 1997 and it's gone through some changes over that time. A couple years ago, we were stepping back and looking at the current landscape and thinking about how to build our resources to make things better and as you can see from the screen. We realized that most Fedora installations are unsupported they're on versions of three earlier at the time we were at four and five content and systems is at risk, and migrations are costly. So that let us chart a roadmap forward and our goal, both with the software and the grant that we're talking about today is to reduce barriers to migrations and to build a bridge forward. What's exciting is we've gotten a Fedora six which came out this summer, and we feel like it really did a great job of meeting some of these goals. So here are some of the features. We've adopted Oxford common file layout, which is part of a digital preservation program. It's an attempt to abstract the storage of items away from their repository systems. At the same time we were able to let go of a tool that was no longer working for us called mode shape. We were able to build as you'll hear soon some robust migration tooling and documentation. We created a metrics dashboard, which lets you monitor the, the, how your repositories doing. We built in a simple search because we found that people in the community really liked that affordance, and we made minimal API changes with the idea that if you're already plugged into Fedora you wouldn't have to do much to migrate forward. The benefits that you'll see enhance digital preservation support again through OCFL improve performance and scale.  Awesome. So thanks for that Tim. Now I just want to take a quick minute and talk about the grant itself and its purpose and goal. So in September 2020 Fedora was awarded an IMLS grant totaling approximately $250,000 to be used over 18 months with the sole purpose of providing much needed documentation and migration tooling necessary to bring older versions of Fedora forward to the most current version Fedora six like Tim just spoke about. So the community had identified the need for these migration tools and documentation as crucial resources to support Fedora three upgrades. There are hundreds of libraries and archives in the US alone that are using older versions of Fedora to preserve and deliver resources to its users. So this continued reliance on Fedora three puts the stability security and accessibility to these repositories at risk, and much more concerning than that is the potential threat that this poses to the digital preservation of the unique and valuable content that's contained within them. So the purpose of the grant was to lower barriers to migration by creating a toolkit and providing resources that will be shared with the community and users around the world, so that we can collectively prevent this content from being lost. As part of the grant we're also going to administer training programs and webinars to aid in the overall adoption of Fedora 6.0. So this is an overview of the process so our great partners were the University of Virginia who is running an older version of Fedora three with a custom front end, as well as Whitman College who was also running a version of Fedora three with an island or seven front end. We then worked with the pilot partners to identify and develop appropriate tooling and documentation to assist with the migrations. Then we began to test iterate and refine the tools that were created. Once complete they were compiled into a toolkit document which is in the final stages of iteration now. And once this is all finalized it's going to be distributed to the community for feedback before being published for general usage. So in the spring we're planning to hold a workshop slash training event that's going to be focused on helping institutions work through a migration using the tools and documents created throughout the entire grant process. So as per the grant outline the work was divided into three phases. So phase one was actually piloting the migrations themselves. So much of this work and the lessons learned during this phase are going to be spoken about in just a moment here by our partner institutions. But during this phase the teams also began to work on the creation of several components of this toolkit that we speak that we're speaking about. So phase two was focused on the toolkit itself. Much of the work has already been done and been completed throughout the process but there's still work going on right now, iterating pieces and tweaking some of the tooling that's been created. Once the final changes have been made as I was explaining we're going to be releasing it to the community for general feedback before releasing the finalized version. And the last phase which we're hoping to host in person in the spring would be the migration training workshop. So this is intended to bring users together for an intensive two and a half day workshop that's going to be free to attend, thanks to the grant, where we're going to present all of our findings and walk attendees through the migration process using everything that was created. And with that I'm going to hand it over to Robin who's going to talk about the University of Virginia is contribution to the grant process. So our initial goal for the pilot was to fold primarily we wanted to reduce risk of losing content stored in a fedora three instance on obsolete server. And I want to emphasize that we knew very little about the content, but we also understood that many community members have content fedora three repositories some with custom front ends like ours. We had experienced migration pains with migrating to the door for. So this pilot gave us a real opportunity to do something we needed, and to help the community move forward by providing a demonstrated migration and validation of content from an older fedora three to fedora six. Throughout our migration, we were able to inform feature development and performance enhancements of the migration and validation tools, such as progress reporting, which greatly helped us during the testing. Most of our infrastructure is based in Amazon web services. So we worked with lyricist to build out a doctorized fedora AWS installation process. Initially, our configuration was not perform it. And we knew this because we had existing numbers from other people testing fedora six. So we had to return to the drawing board and completely reconfigured AWS resulting in us having far more confidence in how to resource fedora six and AWS. In the end, we were able to successfully migrate several prioritized collections from fedora three to fedora six. I began this discussion by sharing that we knew little about the contents of that repository, but in the end only migrated a few collections. This is a nice place to start discussing the challenges we faced. First of all, we had no staff who had worked in recent history with fedora three, and we had no one who really knew the content due to staff turnover. We underestimated the time for ramping up work for the repository and the value of involving content owners early in the pilot. The pandemic also had an impact as it forced people to work remotely which impeded communication, but also introduced infrastructure hurdles throughout the early stages. But I would say our largest issue came from initially taking an all or nothing approach to the migration. We were able to migrate everything in that repository at every change at every step was a huge time sink. In the end, we found that identifying collections of content and prioritizing a collection on which to iterate was far more successful. Our recommendation is plan well up front, understand the content, understand what skills your staff need, understand the infrastructure requirements within your environment. And finally, divide and conquer the migration by identifying a small portion of your repository for migration and testing until you have the configuration migration and validation setup that you need. We have identified a lot from this pilot. Our staff now understand how to work with the old repository and we know a lot more about the contents. We have identified what we do not need to migrate, such as derivatives which we had already reformatted and we're storing in triple I have. So now understand the AWS configuration we want for for door six, which we, which can support the remaining digital collections, audio visual materials and scholarly content, which we need to eventually migrate from for four. And with that I'm going to pass it over to Amy Blau from Whitman College. Thanks Robin. The Whitman College Island or repository contains around 30,000 digital objects, including undergraduate honors theses other student and faculty works archival collections of digitized photographs and documents and student newspapers from 1896 to 2015, representing almost every island or a content type. So all in the grant has been to migrate all of our repository content into a new island or a site, preserving the key functionality of our island or a legacy site. The successes our team has achieved include the site development and configuration, including the creation of a new theme that would be supported in Drupal mine. Our site is hosted on Amazon Web Services, Docker as using aisle. We're using Fedora six on Amazon as three for object storage. The repository contents to the new site was accomplished via the island or a workbench tool by Mark Jordan, which uses the command line to ingest content via spreadsheet in our case Google Sheets. We had worked with born digital, who is also our repository vendor to establish all of the metadata fields that would be needed for our objects, including a number of custom fields. And to ensure that the site was configured so these fields would be appropriately viewable and brief record metadata object metadata and facets. The preparation of metadata for ingest included coordinating the spreadsheet column headers with the machine field names, ensuring that taxonomy terms and linked agents were formatted correctly, and providing URLs or file paths to bring in the objects. Open access objects were retrieved from our island or a seven site, while restricted access objects were manually put on an Amazon server and retrieved from there. We also encountered included some delays. A year ago Fedora was preparing version six for release and the timeline for Drupal eight end of life meant that island or had to be completely compatible with Drupal mine. These platform dependencies in the island or a stack delayed the site build and theming, which in turn delayed site configuration and the ingest schedule. We had a lot of iterative work to optimize the ingest process. At one point in the process we discovered some serious errors and how files were being stored and we started over from scratch. The sheer number of in size of our files for our newspaper collection in particular also meant that ingest and we ingest of these objects took a while. Alan developed and ran some cleanup scripts for ingest to handle problems like derivatives that hadn't been generated, and in particular to bring over OCR derivatives from our old site. Though the ingest process using island or workbench was very successful. The other main challenges that we face had to do with support for the broad range of content types in our collections. Page content and island or a currently uses the open C dragon viewer by default, but this viewer does not have a page turning view or use H OCR to let you highlight your search term on a page or indicate where search terms appear in the issue as a whole. We're currently using a PDF viewer for the newspaper issues. And to highlight search terms you need to enter them a second time in that PDF viewer. This is a temporary solution until a book viewer with H OCR functionality is ready to go in island or a We also miss the functionality of the oral history module in island or a seven in island or a eight, we can display VTT transcripts as captions but we can't do an entire transcript and click from one portion of the text, the corresponding audio. So these, these viewing options for certain island or content types are something that isn't quite as complete in the current system. Access control has been a significant issue for us in a couple of ways island or eight not use fedora access control and Drupal access control possibilities are less granular than the exact mole of older versions of Fedora. As a result we've changed the structure of our limited access objects so that we can display metadata openly but still restrict access to the object itself to authenticated users. We've also run into some issues with the implementation of access control at scale. After there are a certain number of objects in the repository access controlled by taxonomy terms slows down the site for unauthenticated users. So we'll need to transition to a different way of living access, which we hope will improve site performance at scale for search and browse as well. Many of the plan fixes for access control are due for implementation this month. And as soon as these are done we should be able to schedule our cut over. For people who are preparing for a migration to island or eight and truly any repository migration. We recommend preparing your metadata as much as possible ahead of the migration timeline itself. Mapping, remediating and streamlining metadata can help in making decisions about the site structure and configuration and post ingest cleanup in the new system is often more difficult than pre ingest changes. Evaluate the platform's capabilities for your needs, while island or really can support a wide range of use cases, not all of the functionality of legacy island or is completely built out yet in the new version. Depending on your migration timeline and development budget, this may mean compromising on some functionality. So repository administrators developers and vendors should be very clear about what requirements must be met immediately and where there's room for temporary solutions that can be improved on later. Communicating frequently with your team and documenting questions decisions and procedures are always wise and I sign on to all of Robin's recommendations as well. We're excited about the S3 capabilities of Fedora. And we hope that the new OCFL file layout for Fedora storage may give us more options in future migrations. We're working to prepare our site for cut over and our documentation to share with the grant toolkit and Aaron's going to talk a little bit more about that now. Perfect thank you both to Amy and Robin for sharing your, you know your work through the grant process that is some very valuable information that has come from it. I wanted to just take a moment here and highlight some of the most important resources that can be found within the migration toolkit that we've been speaking about today. We have the migration utils which is a framework to support migration of data from Fedora three to four six repositories. Then we also have a key one here which is the migration validator so this is a command line tool for validating that your migration from Fedora three has successfully moved over to Fedora six. This is like I mentioned a key tool that will be involved in the toolkit and has proven useful on numerous occasions through migrations that we've seen. There's also a metadata remediation guide. And the last link there is the migration guide so this is a link to our wiki where you can find an extensive list of resources tools, as well as all of the migration paths that you will need to move from all older versions of Fedora to Fedora 6.0. There's also a YouTube video that was done by Scott Prater from the University of Wisconsin Madison where he walks you through the migration of a small Fedora three repository to Fedora six. This has been a great resource for people looking at what that migration process will actually look like from start to finish, and the link to that video will be at the end of this slide deck so I definitely encourage you to check that out. And with that I'm going to pass it back to Tim. Thanks Aaron. We keep using the word community to describe Fedora and it is a community. We have an organizational home in lyricists lyricists did the leadership to secure the I am less funding that supported this grant. And here we wanted to acknowledge some of the Fedora members who help support through in kind software development and through finances. And I should make these the slide deck available and I wanted to leave you with some additional resources. So stepping back up from the migration toolkit to the grant project landing page back to the guide. We have monthly Bob coasts, and we are community with real people that answer questions and talk and put their brains together to solve problems and a lot of that happens on slack. So we'd welcome you to join us over in slack to learn more about the, the, the project and how to move forward. There's the migration videos the workshop videos. And we can't be a successful community without membership. So if you're interested, please feel free to reach out to any of us to talk about how you can become a member. And just a quick reminder, when we were looking several years ago at the landscape. Our goal was to see what we could do to reduce barriers to migrate repositories forward so that we did not leave objects and content at risk. And that's been the driving factor between Fedora six and this grant. And I feel like we're getting there. So we're really excited that you were able to watch this. Please, again, feel free to reach out to us. And we didn't want to leave without acknowledging some of the people that really did some of the heavy lifting with the grant, and you'll see their names on the slide. So we just wanted to thank CNI for hosting us and you for watching us. And I think we'll close now.