Hello everyone. Hi. So thank you for being here. My name is Harshita Sharma. I'm a developer advocate, kind of a newbie in that area, and a software engineer also. So a little bit about me, I work at a company which is called Maya Data. Our company has an open source product which is called OpenEBS and it's a containerized storage solution for Kubernetes applications. So we also work on the area of data agility. So when we also, another product is Data Migration as a service where we leverage Heptio Valero to backup and restore the Kubernetes resources along with the persistent volumes. Or you can see the data. So the things which we'll cover today in our lightning talk is what is Valero, why is it different, how it works and where can you use it. So Valero is an open source backup tool to backup the Kubernetes resources and persistent volume. It can be used in case you want your cluster migration or in case of disaster recovery.  So your data is lost. So you don't want to be stuck in those cases. You want your resources and data to be saved somewhere and mostly remotely. So how Valero helps in it is, in case of Kubernetes resources, when it comes to Kubernetes resources, it communicates with the API server, Kubernetes API server instead of communicating with the ATCD database. So it has two components mainly, which is, first is server, which runs for the cluster where your applications are running. Second is command line tool, which you can run anywhere, mostly locally. And yeah, it can be run on premises or on cloud. And yeah, but for in the thing to be noted here is it doesn't provide any solution to backup your persistent volume. What it does it, it provides support for cloud snapshot features. So basically it communicates with the cloud provider snapshot feature to take the backup of your persistent volume. And any storage solution which wants to add a plugin to the same thing, to the Valero, so they can also add a plugin. It provides support to adding a plugin. For example, for our product, we have created a C store plugin. C store is our storage engine. So now it also supports the backup and restore of our persistent volumes for our storage engine. So why is it different? As I mentioned that it doesn't communicate directly with the ATCD database and it basically communicates with the Kubernetes API server to fetch the Kubernetes resources state. And how it helps is it lets you filter out the resources what you want to backup and restore. For example, you only want some namespace to be backed up or you only want a particular type of resource to be back up.  So you can filter out a mention in the command line, your command. Just I want my namespace, for example, your application is running MySQL. So I just want my MySQL namespace to be backed up. So all the resources which are in that particular namespace will be backed up. And if you mention the type of resource is pod. So all the pods will be backed up. Or if you have connected your resources using labels, then you can also provide a label selector. And you can also mention using label selector that, for example, if you use a combination of it, you want the namespace to be backed up. But you don't want a particular resource to be backed up from that namespace. So you will use a combination of mentioning include namespace, which is MySQL, but excluding a particular resource may be service account using your label selector. And the second thing is you don't need to have direct access to the ATCD. And in most cases, because of security reasons, you don't have this access also. So how it works? For Valero, every operation which is basically on demand backup, schedule and restore. So every operation is a custom resource which is defined by a custom resource definition, CRDs, and which is stored in ATCD. So Valero also have controllers which who process these custom resources and lets you backup, restore and the related operations. So what you do? If you see the whole process is, I have deployed the Valero command line tool. I will run, before that, before running, you just need to set up your snapshot and backup locations and you set up your Valero server on your Kubernetes cluster. So snapshot and backup location is just simply a remote cloud place or object storage where you want your snapshot files and your custom resources configs to be stored and to be restored from.   And in case you want to snapshot your volumes, you have to mention for which location you want the snapshots to be stored in. So for example, if you want AWS snapshot feature to be used to snapshot your volumes, you will just create a snapshot location and then you will, there you will mention the access and the URL of it. And then when you mention in the command line, I want to, I want you to use this snapshot location. It will automatically store the snapshot files there and also use, will use the S3 or the AWS snapshot features to backup your snapshot. And yeah, then when you mention, okay the URL in the command Valero backup, now Kubernetes client or CubeCity, sorry, Cubelet will communicate with the Kubernetes API server and Kubernetes API server will validate your custom resource and if it everything is fine, then your custom resource will be created and backup controller will run a watcher. And if it finds any new backup object is created, then it will again query the Kubernetes API server for the Kubernetes state of your, of the Kubernetes resources, which you have requested to be backed up. And when the whole backup is complete, it creates a tar ball and it uploads the tar ball to the cloud provider. The cloud provider is the same where, which you mentioned in your backup and snapshot location. And you can have a different backup snapshot location. For example, you want your snapshot files to be saved in different place and your resources, Kubernetes resources to be saved in different place. You can do that, but preferred that you put it in the same place for like, for example, in case of cluster migration, everything will be at the same place and you can restore from the same place. Okay, so yeah, after that, when it comes to use cases where and when you can use the Valero. So, first is disaster recovery, second is cluster migration and third is whenever you want, suppose you want your setup or your application to be tested in a different or replicated cluster, then or testing cluster, you can say development clusters. You can replicate the production cluster to development and testing cluster and the next thing is disaster recovery. Okay, so I just mentioned that you, the Kubernetes as you can see is a volatile system and service outage can happen at any time or a pod or a namespace is deleted accidentally maybe or a node can go to an unrecoverable state. So in that cases, what you should do is, you can create a schedule and that interval is on your choice. You can create a daily backup schedule and so when you create a schedule or triggering intervals, if anything happens or any disaster happens, before that you will have your backed up resources and your data at the remote location. So and at the time of, suppose you have already created the schedule and your resources already there. So if in case some disaster happens, you know, okay, now I need to go back to the same state. So what you will do is, you will help, you will use the Valero client and you will run Valero restore these resources for me and at the time of restore also you can filter out. Okay, I do not want these three namespaces to be backed up. I just want one of them or I want to, do not want this particular resource. So you can use a label selector for that and for restore also it uses the same snapshot location which you can mention in the command which is Valero restore and yeah. So also at the time of restore what you can do is, you can put your location, the storage location, the cloud object storage location to a read-only state so that a new backup or restore is not, sorry, a backup, new backup is not created at the time when you are restoring your resources. Next is cluster migration. Okay, you can decide, you want to migrate your Kubernetes resources and your data to a different cluster, maybe a different, maybe in case you want to replicate your cluster for the testing and development reasons. So what you can do that for the, in that case of destination cluster which is a different cluster, you have to set up your Valero server then you have to create the backup and storage location, the snapshot location and as soon as you create the storage locations there, which is the same location you, where you, which you use to do the backup in your source cluster. So as soon as you create the location, Valero server keeps on syncing the resources which are there on the cloud. Okay, so when it comes to Valero, the, our object storage location is a source of truth so it will keep on checking, okay, these resources, these backups are there so I need to sync them down and if in case a backup resource is created on your cluster but it's not on your backup object storage location then it will delete it from your cluster. So, yeah, as soon as you create your location every backup resource, every single one of them will be synced from your object location, object storage location and when you see, okay, now this is the backup name which I used to backup my resources and then you can restore your, your resources using the same backup name by mentioning it in the Valero restore command. And yeah, open to questions. Yeah. Sorry, do you stop once before the backup one? Stop what? Pots. Pots. Pots. Pots. No, no, no. You don't need to stop any application before backup. It will, the application will keep on running as it is running but because the Valero communicates with the API server so it will just do the query and keep on checking the Kubernetes resource state. Can Valero stop? Can Valero stop? Before the backup. Yeah, if you want it to be stopped you can use a pre-hook for that. Valero provides support of pre-hooks and post-hooks. Like for example in case of databases if you want to flush in the, your data then you can use a pre-hook in that case.  Can you do incremental backups? Yeah, if the Valero does the incremental backups only. Okay, thank you guys.


What do we got here it's a classic first-person perspective body and then You have It kind of out Facing the world And then you have all these ideas Let's show up And all these ideas are Bing Bing Bing Bing Bing Bing Bing Bing Bing and all those govern your existence Like a heads-up display of a hologram and so what's said is well what if Actually this had nothing in its heads-up display It was totally empty Like this No name time location identity information whatsoever, but you were able to access your zip code or whatever Social when you needed to but not that those things identified you So then you could feel what the nature is of this Empty space like the sky, you know basically like this Open empty no no identifiers and then on earth You could feel all of those different different cheaters and identifiers when you need them But you weren't identified With them and you see like this fish-eye perspective is also really important because if you're living kind of on this perspective Very zoomed in you're very zoomed in and focused And it's very difficult to get You to zoom out When you zoom out you can focus more More on like the bigger picture on the open space instead of just on the single object So it's like that and that This is like your name And your personality and all your attributes and identifiers and features And this is the feature less without any identifiers or attributes the open space that everything shares


In the last section, you review the environmental factors that influence fire behavior. We looked at some of the resources available to you when you're analyzing your fuel, weather, and terrain conditions. But even with those resources, predicting fire behavior is difficult. In today's environment, we hear more and more experienced firefighters saying that they are seeing fire behavior that's more intense than anything they've ever seen before. New terms are being thrown around such as area ignition, wildland flash overs, simultaneous ignition, and explosive fire behavior. If this is true, if conditions are really changing on the fire ground, how does that affect your ability to predict fire behavior? Let's listen to some professionals from both the wildland and structural world talk about fire behavior at the high end of intensity. Bob Kittridge specializes in teaching wildland firefighting to many structural firefighters. One of the things I've been looking at is how, in my teaching, is how to get structure firefighters. Because when we looked at some of the structure firefighters, the majority of their training is in structure. So what I looked at is how do I get them to understand what's happened in the wildland arena? One of the comparisons that I've seen is the fly-shover compared to what's happening in the wildland arena with whatever we call it simultaneous ignition, area ignition. Something where the fuels in that given area are igniting at the same time. It's not a rate of spread. It's not fire progression. It's a simultaneously ignition. Is that an option? I don't know, but there's something there that's really key in me into something's happened that's catching people off guard. You know, this summer started out, or I should say this spring, ended up on the Ham Lake Fire in Minnesota. And, you know, Minnesota early season fire didn't expect much. Incredible fire behavior. I mean, spotting, this is observed spotting up to six, seven miles. Rates of spread that were just, you know, running behavior. I couldn't get the behavior model to predict what was going to happen on the ground. It just, it would reach its wind limits. It would top out. It wouldn't go any further. And then that recurred all summer long. And I kept talking to firefighters, you know.   And then it was this exponential growth because then you'd have four or five trees torch off thousands of spot fires. And just things happening so quickly, I think, was the, you know, fires are getting bigger, faster. And then these conditions for that area ignition, which I saw this summer, you just, you could see a whole hillside that would suddenly become this carpet of fire. Rates of spread, you know, for instance on the wine cup complex, we had in the afternoon it was, the conditions were light, light winds, you know, moderate temperatures, relatively speaking. But we had spread rates in the sagebrush of 22 miles per hour clocked by a vehicle. And there wasn't a wind pushing this, you know, this was something else altogether. Atmospheric instability, not quite sure what happened, but you just basically saw a whole hillside light up. And being able to model something that's so dynamic and these factors, you know, it just, it's a tremendous challenge. And I don't see how it can be done. I'm sure there are some scientists that know a lot more about the building of the models, but just, I don't see how it can be done. Maybe it is a flash over, not in a contained vessel as a structure, but somehow in the wildland arena, we've got a flash over happening, whether it's terrain driven, whether there's some weather factors, whether it's, if you look at some of the common denominators, light flashy fuels, the dry dead fuels we're having, the calmness of the wind which allows maybe the heat to build up and raise the temperature of that fuel. I don't know, I think it's just a theory and something that we should start looking at. To take a closer look at this phenomenon, we went back to the Missoula Fire Lab to talk to Brett Butler. I'd often wondered what is it about fire that in many cases the people with a lot of experience say they see a whole hillside seemingly explode into or ignite all at once. From a physics standpoint, an engineering standpoint, that's difficult to imagine how that occurs. And I think that from a human factor standpoint, we could say, well, we have a difficult time keeping track of more than two or three variables. So maybe there's multiple variables occurring at the same time and once it seems like the whole thing comes on fire when it's a whole bunch of different factors coming into play. As to why a whole hillside would explode, seemingly explode all at once, I think it has to do more with the interaction between the dead fuels burning and igniting, maybe the surface fuels and putting off enough energy that the live fuels, the live vegetation in the crowns, then participates in the fire. And then you get this seemingly broad area ignition. From a scientist standpoint, it's always important to listen to those kind of whisperings from the field, from the people that are actually on a fire. And one experience that I relate back to are the crown fire experiments we did in northwestern territories of Canada in the late 90s. And the video footage that we have of the cameras in the stand and the fire burns up to and past the camera. And you see as the fire is coming, you see it's getting brighter and brighter and closer and closer. And then all of a sudden you kind of see this vapor, this kind of smoke coming off over a broad area and then it almost ignites the whole area all at once and the fires past the camera. And it may be that what we're seeing is this type of behavior, if we assume that fuels maybe are drier, climate's a little bit drier now, so you have drier fuels over a broader area that that's impacting how the fire spreads. And the other thing that we saw in those in-stand videos in the crown fire experiments was the spotting, the ember shower that occurred ahead of the fire, actually was a major part of the spread.  And the interesting thing from a fire physics standpoint is you have a point ignition, the fire will accelerate. Even the experiments we do here in our wind tunnel, we have a fuel bed that's 3 feet wide and 30 feet long. We ignite one side, one end of that fuel bed and let it burn down the 30 or 40 feet. The first 10 feet, the fire just burns like crazy. It just goes almost instantly and then it kind of slows down to a steady rate of spread the last 20 feet. So let's extrapolate to a real fire now in the forest. Let's assume we do have very dry conditions and you get these embers that are coming out of the plume spotting ahead of the fire and so you get a point ignition. You could have that similar behavior at kind of a small scale where the fire burns very rapidly just at the point of that ember till it reaches a steady state and then kind of chugs along, but then it's putting out more embers that spot ahead. And so this may be its convoluted way of saying that it may be kind of a mechanism to figure out how fires seem to accelerate and cover a broad area and what we would, from an observational standpoint, seem to be instantaneous. Kelly Close started his career as a wildland firefighter and later moved to the structural world in Fort Collins, Colorado. He is currently an F-band and a member of the NWCG Fire Behavior Committee. Here are his thoughts on what might be happening. You know, I keep hearing this term, flash over on wildland fires.  And in that enclosed container full of combustible materials, the temperature rises and rises and rises until the temperature everywhere in the room, the air, all the fuels, everything is at the ignition temperature and everything in that room truly does ignite all at once. That's flash over. In a wildland fire environment, we don't have the same sort of physical properties as we would in an enclosed room in a structure. It's a much more open environment. We might have some constrainments by terrain, but it's generally a much more open environment. We don't have the same physical conditions that would predispose an area what's considered to be a flash over. What we do have, what appears to be happening more and more with the drier conditions, with the volatile burning conditions, is what appears to be a very rapid ignition and fire spread over a large area that's so rapid that it almost appears to be happening simultaneously across a very large area. Extreme fire behavior is a term that I hear batted around a lot. A lot of people use it as becoming a further common term to describe things that we didn't expect. We hadn't seen before that are unprecedented. There's a lot of words I think you can attach to it. Really, whether extreme fire behavior is an appropriate term or not, I'm not sure. I think what we're really seeing, if you think of fire behavior, is kind of a bell curve. And in the middle of that bell curve were traditionally we've seen a certain type of fire behavior. That was a fire behavior that was behind the fire behavior prediction systems that we used, behave plus the fuel models that were developed for that. That's the fire behavior that we've been seeing up until recent years. What we're starting to see now is fire behavior that's getting more and more towards that right-hand end of that bell curve. We're seeing that kind of upper end of fire behavior. If we're dealing with fire behavior at the upper end of the bell curve, how can we begin to understand and predict it when it is outside our current modeling capabilities? Well, at this time, there are some research efforts, both here in the U.S. and other parts of the world, to improve our predictive abilities. There's some other work by Professor Villegas in Portugal looking at how fire spreads up slopes and in the presence of chimneys. And that work is based on a relatively small set of experiments I think like 10 or 20 experiments with a field bed about the size of a sheet of plywood and they just vary the slope and the angle between this two sheets of plywood and then watch how the fire burns up that. And that's important. It's pointing some of the directions we need to go in understanding how fire spreads but it's not to the point yet that we probably should be using it operationally. There's important physics and understanding there but once again we need to keep working on this and as well as the scientist's responsibility to keep working on it, all of us trying to understand what's happening with fire. But in dealing with that upper end of the bell curve, we're closer from the very get-go, we're closer to that transition point. So we might go out in the morning and things may seem to be exactly what we'd expect given the conditions. The fire behavior we're experiencing that we're seeing that we're observing given the conditions they may be exactly within what we would consider normal but we're much closer to that threshold than we ever were before. So by afternoon we could be crossing over into that and getting into some very extreme fire behavior or I shouldn't use that term but by getting into some very intense fire behavior some things that we haven't seen before and that we're now calling extreme fire behavior and I think that's the danger is that we're starting out much closer to that transition point and so we're not quite as clue and we don't expect things to change that quickly and that dramatically even just over the course of one day. While research continues to improve our understanding of this upper end fire behavior there is one concept that poses significant threat to the ground firefighters and that is the concept of a steady rate of spread versus an accelerating rate of spread. The work that the Vegas has done with accelerating fire spread in working on developing a model I think has really helped if nothing else to increase our understanding of what's going on that to demonstrate to us that fires are actually accelerating that rate of spread is not always steady state but what it's demonstrating to us is that we've always been taught even at the very basic fire behavior level that given a certain set of conditions in the fire environment you're going to have a set rate of spread and a set flame length but now what's happening is you put fire in a different set of circumstances you get fire that is established at the base of a very steep V-shaped canyon it's a whole different set of conditions now and what seems to be happening is that fire starts accelerating moving up to some new higher rate of spread some new higher intensity level and probably at some point it would accelerate, accelerate and then flatten out when it reached the new steady state rate of spread or flame length we're not seeing that because the fire usually blows out the top of the drainage before it actually has a chance to hit whatever that new steady state value is this rapid acceleration of fire spread obviously occurs when a fire moves from flat terrain to the base of a steep slope but this is not the only precursor a sudden wind increase, numerous spot fires with a high probability of ignition or even slight variations in the fuel type can result in exponential increases in rates of spread this was seen many times last year on flat terrain in Texas and in many parts of the southeast the lesson here is to understand how an accelerating rate of spread can occur and how it can compromise the effectiveness of your escape routes and safety zones I think it's important also for us to recognize that in terms of situational awareness we need to be aware of what's going on but we're very poor at keeping track of multiple variables and we kind of assume well the fire is just marching along when let's say the fire is marching along it reaches a point where it can involve live fuels in a few shrubs well that increase in intensity could cause a rapid acceleration in the fire spread rate much like an example of a fire trying to cross the street a car is coming towards you if it's moving at a constant rate of spread well you look, you gauge how much time you have, you walk across if it's accelerating from, if it's a Porsche accelerating from 40 to 80 then it's much more difficult for you to gauge how much time you have to get across that street we need to use a similar analogy in terms of gauging the effectiveness of our escape routes if there's a potential for fire behavior to change forecast for a wind change that terrain change, fires at the base of a canyon that could move on to a slope perhaps then we need to think about the effectiveness of that escape route in terms of a much faster spreading fire and much higher intensity when people seem to be caught off guard when things were fine a minute ago and now things have changed and suddenly they're in a very dangerous place or they've been overcome by hot gases or a fire front that's changed quickly we didn't expect that change to happen we didn't expect it to happen so fast I don't know how well we really can predict that because again we're getting out of the realm of what we know we're getting out of the realm of what's normal fire behavior we're getting into that up around, we're crossing that threshold much sooner in the day, much sooner in the season much more quickly so a lot of times things will happen like a fire accelerating up a canyon like a hot air mass moving through a canyon through terrain features that we didn't expect our current fire behavior models don't predict but I think the one thing we can do is look at just the changing conditions the last eight or ten years and know that again the live fuels are going to be contributing much more than they have in the past to fire behavior, to fire spread and especially live fuels that have volatile compounds that with a little bit of heat and preheating can actually put some of those volatile gases into the surrounding air in those fuel beds I think the one thing we can do is just expect that things are going to change a lot more quickly than we had planned and be constantly aware we talk about situational awareness be constantly aware especially if we're working in complex terrain that any or all these things can develop in a very short time and be honest before we expect it so in terms of that we need to be absolutely sure we know where our safety zone is how long it takes to get there and continue to reassess that during the day because we may not have as much time as we think to get to a safety zone we may have to be able to get there in half the time a quarter of the time and I think we're going to need to readjust our assessment of what's an adequate escape route because what was adequate ten years ago is proving to not be adequate now another aspect of fire behavior that we need to talk about is the dangers of moving hot air masses in and around burning convection columns let's go back to Dr. Butler and listen to his observations on the Neola fire this last season in Utah where three civilians died trying to protect their alfalfa field we wanted to go down there after that occurred and do some wind simulations but then it looked at the pitchers and you see that green alfalfa field and one spot where that came out right where they were standing it would have been 100 feet to the left or right it would have been fine probably and one spot where you probably had this big turbulent eddy just kind of reach out and move across just bump out into that alfalfa field and move back in it and just caught them there and we're so sensitive as humans to hot air to injury from hot air that it only takes a matter of seconds and you're unconscious that's the scary thing about fire is that we can't predict everything and if you get too close there's certainly a chance possibility that you get caught in that bad location what the old timers tell you is good to know listen to them but don't bet your life on it because we're seeing things now that they haven't seen we're seeing a whole different game now so learn from people that have had a lot of experience but also be ready to to change your perspective based on what you're actually seeing expect the unexpected something that I heard years ago that I really liked was this term called preoccupation with failure look at the situation to determine what is the worst that can happen here and if it does happen am I ready for it?


Subscribe and press the bell icon to never miss an update from Sistweep. There are many things running inside your Mac, but they are not revealed completely with Mac's own temperature monitor. Additional tip if your Mac is facing performance problems, we recommend you to download this clean Pro by Sistweep. You can use the link given in the description below. By using this clean Pro, you can avoid any kind of heating issues due to storage full on your Mac. It also cleans up the junk and manages the disk storage for Mac. Here are the top 5 best temperature monitor apps. On number 1 we have TG Pro. TG Pro is capable of providing the information of Mac's health in detail. Interestingly, its clean interface is very appealing while providing all the vitals. You get to check CPU, GPU, logic board or hard drive temperatures, battery health and other hardware details. Though you can manually boost the power of fans, TG Pro is capable of doing so automatically. So keep your Mac clean, cool and use this powerful Mac temperature monitor. On number 2 we have Menu Bar Stats 3. Mac's CPU monitor is different level experience with Menu Bar Stats 3 that visually appeals to the user and gives swift access to all the information. You can even drag and drop all the required modules to expand the window. And in case, the window is full, automatic scrolling of the page begins. How cool it is to monitor CPU temperature on Mac? On number 3 we have Fanny App. With Fanny App you can get quick information on current speed, target speed, minimum speed, maximum speed, number of fans and of course temperature. All you need to do is open the notification center and find the status of fans. On number 4 we have Tamp Monitor. This app alerts you when your CPU temperature gets too high and your system is prone to any danger. It also has a fan control feature that calms down Mac during the time of overheating. For your ease, languages like English, French, German, Spanish and Vietnamese are supported. On number 5 we have Smart Utility. This tool not only indicates the individual attributes of the information but also uses an internal algorithm to detect the drive's health. It displays information in the menu bar and more details are provided in the separate windows. Overall it is another one-stop solution for the Mac temperature monitor. If you are willing to keep your eyes on MacBook for various purposes, these Mac temperature monitor apps are a good source. So that's it for today's video. If you like this video then don't forget to like, share and subscribe to our channel.


How are you? I don't even care about red skittles or dude. Hey run run Hey, we'll come back to our personal movie feuds this week 21 Jump Street, right? We're doing 21 We're filming that one or no. We're doing a view. No, we're doing that. Okay The camera did not pick up the opening. We're cool. We how hard is that though? I mean really? Snack table should always we are on we need to start looking at this more often 21 Jump Street Why do we jump across the car like that? It looks cool.   I'm not a big Channing Tatum fan. Not even really a big Jonah Hill fan I kind of liked him super bad, but he's the same character every that's true Channing Tatum though typically your romantic comedy slash kind of you know high school teen movies It doesn't do anything. It doesn't do anything worth its salt as the kids say so I'm just gonna tell you right now. I liked it Wow You want real world? Yeah, let's do it man. Come on.  What do we report down on Jump Street 21 Jump Street? I was skeptical as well, but I thought that they did a pretty good job giving a nod to the old 21 Jump Street I liked how it was self-referential to just making fun of the fact that it's a remake and it knows it They had the boss on there from Parks and Rec who does a great rant about how they're reintroducing an old police policy of undercover cops because the police department's out of ideas Obviously, you know mocking Hollywood for We're reviving a canceled undercover police program from the 80s and revamping it for modern times one of these programs Involves the use of young immature seeming officers.  So you brought up Channy Tatum earlier I think he was kind of the surprise steal of the show I thought he was actually better than Jonah Hill Jonah Hill falls into that category of comedians where he looks funny He looks the part so it's easy to follow his role on film Possibly why I thought he was less funny in this because he lost 40 pounds for the role Travis Are you gonna eat all the pretzels or put some on the snack table? Just let it go wait till after the show You will be going undercover as high school students You are here simply because you look young You some Justin Bieber Lookin mother's It's not forget about ice cube who plays a stereotype version of himself.   He was in I was R. O. F. L As the kids say they actually do say that just first time through through sexting Let's take a step back and talk about the story a little bit Channing Tatum and Jonah Hill's undercover cops go inside the school to investigate a drug ring Which leads to great comedic hijinks my favorite part? They're in the bathroom stalls making each other throw up trying to find each other Drunk There's an opening couple of scenes when we look at Jonah Hill and Channing Tatum as police officers when my cops Channing Tatum doesn't know the Miranda rights, but then they make their first arrest So there it is 21 Jump Street both pleasantly surprised. I'm willing to say this is the best comedy I've seen in the last ten years. Wow really ten years. Well, when did Zoolander come out earlier than that? But bridesmaids the hangover super bad hangover overrated a super bad Funny to start bridesmaids a good chick flick Well to the next week as we do bridesmaids because clearly that's our next that's happening He's really like that. All right. Well, there you go Well, I thought you know the movie critics the real ones anyway had this kind of right on the spot You know right on the 70 75% mm-hmm. I'm gonna go ahead and give this eight Peter Pan hats out of ten though Okay, well, I think that that's a little low for what it deserves, which is 15 ice cubes out of 17 Which is actually pretty consistent with what I said, but you know, I thought this job would have more car changes Explosions and shit. We're just reviews. This is movie feuds Okay, I already see red skittles. So don't even bother going to the trade I don't even bother putting it on the tray on the table. Put turn around You're fired.  Not a huge tanning tandem fan. Not ready to take him. What was his name? Channing Tatum? It's not a weird I didn't name him right off the tee as the kids say. I don't know what that means like on the golf course like off a tee Just like right off of tea time like an England Travis, are you gonna eat all the pretzels or put someone on the snack table? Just let it go wait until after the show He needs to let it go and put it on the snack table


Yeah, think tech tech talks at 3 p.m. on a given Tuesday Wednesday Wednesday Wednesday, thank you Attila. That's it. That's Attila. So as he runs a salanda and he's going to talk to us today about Reval our capital R capital E capital V I L making its mark here on think tech tech talks So interesting. So let me give you my impressions and then you can tell me the reality, right? First of all, these guys are very creative. They, you know, expanded the operation to support for the service. They give you Technical support, they take a piece of the action. It's like a regular business. Really creative. And then, you know, in order to avoid the, you know, the option that other victim would have of Encrypting data and the like they and having a backup they they take they take your data also and offer it to the public on auction. In order to undermine your business and your brand as well as locking it up. So it's like a two port approach.  And then, of course, we need to talk about You know, what's going on with Mr. Putin, who seems to have some sort of loose connection with re evil, re evil. So tell us this is a major, major attack. That was reported and then and then they went out of business just as best.  And it makes the rest of us more scared than we have ever been. Let's talk about it. Well, there's a lot of moving parts here. So you're right, Jay. This, this is something that is scary. It does involve data exfiltration.  They take the data and send it out. And that's pretty common, believe it or not. So most of the times bad actors are sitting inside of networks. And they're just waiting for instructions or they're selling access to the network or they're just waiting for the right time, such as what happened with our reval. I'm not sure how to best pronounce that. Maybe you'll have to help me. R. E. V. I. Reval, maybe. Anyways, I'm probably short for real, real evil. I would say reval, reval myself. In speaking with different members of Homeland Security, they all seem to pronounce it differently. So I don't know who to trust on that. So I guess if we get hung up on the pronouncement, that's, that's okay. But So this is a supply chain attack. And this is why it's so important. It's because the victims didn't necessarily do anything wrong. Right. And as a supply chain attack, unfortunately, they targeted what is called the managed services community, the MSP community. And these guys use tools to service computers for their customers. And that tool was, was unfortunately what was the part of the supply chain attack. And if we want to kind of go back to a series of events, it might help you understand what's going on here and why this does fall into the profile of a rebel and what, you know, which is why it made perfect sense for them to pursue this avenue. So probably about a month ago, a, a security researcher out of Europe somewhere discovered a zero day exploit with Microsoft windows, involved the print spooler. It was called the print nightmare. And the security researcher said, Hey, you know, I found something. Let me just put it on GitHub. And GitHub, as you know, is an open source community where you can post code and bad actors at rebel said, This is just what we needed. And what they instead did was they used that vulnerability to infect Right. The, the RMM tool, RMM is short for remote monitoring and management. And Kaseya is one of the more prevalent vendors that does this. As such, they have MSPs, right? So their clients are IT companies who are highly technical and are very offended by this, by the way. So this is this is big news in the IT community. Right. And then they took me the worst of it being offended. You know what I mean? Yeah. Well, and, and, and that, and that that became a real problem because there's a lot of trust between the IT right who essentially has these, you know, godlike overlord powers over your network and the customer, right?  Everything all the way up to Fortune 500. And defense contractors included. Yes, that they are in there as well. And unfortunately, this is unlike the SolarWinds attack, which was very similar. It was a supply chain attack. But in SolarWinds's case, their product Orion was specifically installed and marketed towards defense industry contractors. So that, that, that was the big problem there is because it did involve a lot of monitoring for a long period of time. They knew about the issue for quite a while. Now, of course, no one's talking about SolarWinds anymore, but what are you going to do, right? Everyone's now moved on to Kaseya. Now Kaseya, their Hatch Management servers were then infected by this zero day exploit. And the guys at Rebel made a very smart update. All the Kaseya clients, all the ones out there, and they pushed out this update and they deployed it on a very small number. Now, when I say a very small number, that was over a million computers on hundreds of businesses. And they said, if you want your machines back, we want a ransom of $70 million. So seven zero. So that was the largest ransomware demand to date. So everything happened to these poor managed services companies that were stuck in the middle, right? They built up trust with these, these companies and all these offices. And they, they went out and had to try to mitigate this bug, which they had introduced to these, to these networks in the first place. And so there's a major uproar on that. There was a well over a million devices encrypted and demanding a ransom and it infected 70 million was for one or for the whole lot of them. Yeah, they were demanding that Kaseya. Now, luckily, IT people are pretty resourceful. So I believe that many of those systems were, you know, emergency patched, or should I say emergency recovered. And in the meanwhile, those that were not encrypted were emergency patched with Microsoft's CVE so that Microsoft did release, I believe, was for security updates. And unfortunately, we're discovering that some of those updates are breaking computers, they're disabling or destroying the ability for that computer to print. So machines are having to be re-imaged. There's a lot going on in the IT world in the background to try to scramble and get machines patched that are, you know, to keep them from, you know, continuing to be, you know, exploitable. And this really highlights how a supply chain attack and a zero-day put together can really mess up the community. Now, you know, the print nightmare bug, as it's been called, has been something that IT departments have been scrambling all week long to try to patch on, like, pretty much every window system has this bug out there. And they're discovering now that there's problems with specific print manufacturers, such as, like, say, like Zebra receipt printers or barcode readers, these kind of things break, sometimes when the print subsystem gets replaced in a rushed and emergency fashion is what Microsoft's been having to do. But that zero-day exploit, unfortunately, does give root backdoor access to the system, and it's not good. And that security researcher who messed this all up for everyone should not have published their findings on GitHub, and it wouldn't have spawned all these problems from happening. Now, let me unpack some of that before we go in further. So, how does this get processed as ransomware? How does this bugged vulnerability turn into a ransomware scenario? Well, once you have backdoor access to a system, you've got lots of choices. Ransomware is kind of the quick, dirty, and simplest way to get that malicious payload out there and make some money. Revol, evidently, does not have nation state ties. Evidently, you know, obviously is in Russia, but they're a for-profit organization, and that's fine. But they moved very quickly to take advantage of this exploit. They knew that the highest impact would be from Kaseya, and unfortunately, the news now, and this is probably, I think, the bigger problem, Jay, and I think we should really focus on this. Is that several whistleblowers have come forth from Kaseya over the past year-plus, well-documented, and either after they wrote up a very long and extensive brief indicating that there's a security vulnerability with the company, or that there's not best practices being performed with these companies, they are either fired or they're silenced. So, the same thing happened with SolarWinds, they knew well in advance that there was a security problem at their organization, they did nothing about it. So, that's a real problem, because that's what can prevent this from happening next time. Because, you know, I guess the best analogy to this entire incident is that it's a storm, much like what we have to deal with here in Hawaii. We have storms, you cannot stop the storm from coming, but you can improve your resiliency against that storm when it inevitably comes. And that's what we should really be focusing on, is how, as individual business owners or business operators or IT departments, how do we maximize our company's resiliency to the next supply chain, to the next whatever attack that's going to inevitably come. Well, this is so much here to talk about, I can tell you. So, what kind of, you know, warnings, early warnings that they have, you know, to sort of foretell of this fellow who revealed the vulnerability only a few days ago. How do they know that, so that they should have been, so they wrote their warning memoranda to their companies, and for the companies could have done anything about it. What did they find? What was the weakness they found? Look, people don't take cybersecurity seriously until there's an incident. You know this, I know this, right? When do people buy a security system for their home or for their business? After there's been a break-in, right? And in the same way, there's not a lot that's considered beforehand. And Kaseya, and I hate to say it, you know, we've had to deal with them on different occasions for different products. They're printing software companies, but they are what? I would call them more like a pac-man of the managed services world. They buy up companies that they think might fill a need or are generating revenue and they just add it to their portfolio. SolarWinds is no different, by the way. And that's a pretty common trait in big corporate America, right?  You know, it's been like that for a long time. That's not going to change. But what really should change is how seriously they take their own cybersecurity, knowing that they are so responsible for so many businesses and lives. I don't look at a company as, you know, this money machine or a vet's office or a dentist's office. I look at it as someone's livelihood that then supports the community, which then pays for schools and pays for roads and everything that we depend upon. So when you attack a business like that due to gross negligence from a big corporate entity that's just more interested in, you know, policies and procedures rather than protecting the community or for which they are responsible for. Then that's really what is upsetting to a lot of those, such as myself, who are in the IT space, who have to try to mitigate some of the fallout. Now, luckily. What could the executives, what could the executives in that company, those companies do if they read the memorandum? If they hook the warning, what could they have done to prevent against this? Well, as in most things, there's always a solution, right? You don't have just a problem with no solution. Nobody knew about the Microsoft vulnerability until recently. You know, it only came to light short time ago. You're talking about memorandum that were written a year ago or whatever. Well, it was clear that they were following poor security policies, right? I mean, they had to get inside the server somehow. There were some issues with, there were some issues with how they were maintaining their existing staff. It's all kind of laid out, and the specifics haven't been revealed, but what they are saying is that there have been several whistleblowers came out and said, look, guys, we really need to do something about this. There is a real security risk. We are responsible for a lot of people's livelihoods. I'm going to say a lot. I mean, in the millions. And our product is vulnerable. We need to do something about this. Now, in SolarWinds, it was really obvious, right? Their password to their main server was SolarWinds123. Kind of easy to guess. Oh, jeez.  You know, so, okay, so yeah, really, so you have this and, you know, the newspaper would suggest there was an awful lot of, a lot of, a lot of companies hide up in ransomware scenarios. And are we out of the woods on that? You know, unless we forget that Joe Biden had a telephone call about this large ransomware attack by Revol or Revol or Revol a few days ago, only a week ago or so. And, you know, of course, Vladimir Putin did not admit that he knew about it or it was his fault or anything.  Putin has connections. It's a capital concentration or intellectual concentration or certainly a computer nastiness like this. He knows. And so remarkably, less than a week after that, their website came down. And now they're not available for hacking as a service anymore. And their whole business is like disappeared, although we all know it'll probably reappear soon enough. But what about the guys whose beta was kidnapped? What about the guys who were suffered? If the site went down, if Revol isn't in business anymore, who do they call to get their data back? So data exfiltration is one piece of the puzzle. And the second is decryption. Data exfiltration, as far as I know, there's been no evidence of data exfiltration. I could be incorrect on that. Probably worth googling that. But data exfiltration is when they actually take the customer's data and they either publish it or hold it for ransom outside of the customer's network. And that could be independent of ransomware being deployed. And so it can go both ways. In this circumstance, I believe it was just a smash and grab, quick ransomware, sloppy deployment. Luckily, since most managed services companies already have a good disaster recovery plan in place for their customers, those that were affected were able to be brought back online. Or if they weren't, then a great expense to the managed services company, the man in the middle, they had to do what they could to get that business back up. But like I said, this is just magnifies the problem that already exists in our world. This is not unique. We see it a lot.  It's not great.  You got to have a good successful business disaster recovery plan, business continuity plan, and that's going to allow you to weather any storm that comes your way. So if I have a little company, or a medium-sized company, and I was attacked by something coming from Rival or Rebel, then if I had backed up, then I could get back online. And the problem with the printer software really wouldn't make too much difference to me, because I'd use the Microsoft patches. I'd get my data back, because I have it encrypted somewhere safe, end of the story. Am I right about that, or are there people left high and dry on this? It's a little bit of both. Hard to tell at this point, because there's just so many victims. But those that took advantage of cloud services most likely have their data. Those that outsourced certain parts of their operation for specific things. So, for example, they subscribe to a software as a service like Adobe, instead of purchasing an individual license copy and then losing that installation file. That's really easy to restore. If they're a subscriber of Office 365 and they are in a plan, which includes the software, it's very easy to just wipe the system or re-image it and then bring it back online and download the software and you're back up and running very quickly. So the good news is that part of COVID has forced us to be more nimble and cloud-dependent. And so when something like this does happen, it's a lot easier to then recover versus having extended downtime. So it just really depends. Well, conceptually, as long as I keep my data safe in a backup, I'd say an encrypted backup probably best, then I can come back again. I would not be affected by this. This is really awful what happened, but the prepared companies will have survived. Others maybe not because it's not like you can pick up the phone and negotiate with somebody who went offline and disappeared into the Ukraine somewhere. So the other thing I wanted to ask you about is this.  And in the process, they're gathering information as to prosecute, arrest and prosecute. And in this case, what's happened here is really a step forward. Tell me if I'm wrong. These guys are very creative. Now they're offering it as a service. You can go on the website, at least recently. You can bring the software down. You can be a criminal in a matter of seconds. You can go be a criminal overnight. And I'm sure that some kids in this country, an adult too, would have done that. And then of course, you have to share your ill-gotten gains with them. There's a lot of contact. I mean, there's a lot of contact interaction between the customer, so to speak, who gets the criminal software and the one who gives them the criminal software reval. And so that leaves a lot of opportunity for the FBI or somebody who would engage in this kind of, entrap is the right word, the wrong word, because entrapment itself is illegal. But some kind of situation where they stuck them in, deceive them, and then nail them. Is it easier with the software as the service model to bring the criminal in and nail them? Well, to be fair, the reval is just one of many. In fact, I believe it was April of last year, there was another shutdown, let's see, of another large-scale software to grant somewhere as a service and cybercrime as a service-type organization. And they just pop right back up. This is not going away. These are like mushrooms. You just chop them down, and then they pop right back up again. It's because it is political. Yes, but they're more advanced every time you look. Each generation of mushrooms has new and creative tricks, like this thing about taking your data also and auctioning it. And the other thing I wanted to ask you about, you said before, you didn't think that Putin had any connection with them, don't you? I mean, doesn't it seem like he may? I mean, there's a remarkable coincidence here, a week after this contentious conversation between Biden and Putin, the thing goes offline. Now, I guess some commentators would say, well, it was subjective. Riegel decided that there was too much heat, heat coming from, obviously, the US, but also from Putin himself. And they decided the better part of valor he would be to disappear like a mushroom and come up later. What do you think happened there? And is there any issue at all about them coming up later? They'll be back a few days or a week. They'll be back and they'll be even more creative, am I right? You're right. And the one I referenced earlier was Trickbot. So if you want to Google Trickbot, you'll see it's the same thing. It's ransomware as a service. It's business email compromises service. They make a product, people pay for it, they use it, they infiltrate. And when Microsoft shut down their networks back in back back last year, April, I believe, well, what happened? It was later they came back stronger than never. So there's going to be Trickbot. There's going to be another rebuild 2.0. They just come, they just go, I wouldn't count on these folks going away. And yet to answer your question about whether there's any sort of politics involved, perhaps, I mean, I don't think I'm qualified to say yes or no. I'm not even sure anyone in law enforcement or FBI or Homeland Security may have the answers to that either. It's hard to tell. But you must think about where they are. There must be telltale signs about where they are, about how well, for example, they write and speak the language. You think they're in Russia, you think they're in Eastern Europe, you think they're in Asia. I always felt that Siberia was a good place for them. Vladivostok and all that could be anywhere. But two guys, and I say you guys, people in the industry must have some idea, even by way of rumor, about where these guys are and who they are. Well, post incident response and evaluation, sometimes you do discover who's in there. And for instance, in the case of SolarWinds, which wasn't that long ago. I know everyone thinks it's ancient history, but that was just like six months tops. They were inside, but everyone was pointing the finger at Russia. But then it turns out that once China got wind of it, they were in there too watching what was going on. So who knows how many advanced persistent threat actors that could be in nation states that are out there looking in all these networks and finding vulnerabilities and taking their time. That's the other thing about this Kasey attack. There could still be infected machines out there. And they could do a second wave. I mean, this was just over the July 4th weekend, right? They deployed it on a Friday morning before. I mean, it could very easily happen later. This is not over. And I don't think it's going to be over anytime soon. So what about the success of the FBI for recovering half of what was paid in the colonial pipeline a month ago? They seem to be successful in getting half of it back. Did anything that they learned or demonstrate that they found in that case helped the community deal with this going forward? Did they discover a new way of dealing with ransomware? I really do like the fact that they chose to spend $800,000 more than they had to to pay with Bitcoin versus Ethereum. So Bitcoin has a better, what's the best word, paper trail along the blockchain. So they were able to work with the FBI and get some of that back, which was good. Ethereum is less so. And I believe, if I remember right, their operational cost was something like $400 million a day. So a few million bucks here or there was a lot less impactful to the pocketbook than having the whole system shut down. Is that lesson that we learned with the FBI and colonial pipeline going to be useful? Or is it just run off the hacker's backs and it doesn't affect their ability to do this, in fact, do it better at all? Did that change things? Did it reach some sort of tipping point? Absolutely. You're asking the right question. What can we learn from a colonial pipeline attack and how does it apply here? Well, guess what? Colonial pipeline attack, they paid the ransom. What happened? They got a decryption. You haven't had to deal with post ransomware and decryption software, but it's not like nice production value software. It's really garbage. And it doesn't work very well to decrypt stuff. So what did the colonial pipeline do? They said, heck with it, we're going back to our backups. And they had a good business continuity plan in place. So even though they did the negotiation, they went through all the rigmarole, they paid the ransom, it still didn't help them. Having that business continuity plan, getting everything back up and running was the saving grace. That's what saved their hide. And so we can all learn from that, especially with this latest supply chain attack. Well, it seems to me that this is a soft target because you can be anywhere. Even if you don't have any skills in coding, you can take it off one of these acting as a service website. But as you said, there are others. And Rivo will be back. And you can do this. And every time they have this big number type of ransomware news headline, the price goes up. And you can make more extravagant demands every time. And more people can get involved. There's like no limit because nobody got arrested in a colonial pipeline. Nobody was actually identified. They got they got a half of it back, but that doesn't really float my boat because these guys are still impugned that wherever they are, they're completely impugned. Nobody ever got caught, prosecuted, convicted or punished in any way. So it just seems to me there's a global process here. This is just it's set to expand and expand and expand until there are sanctions, until there's accountability. And so far, no accountability. So my question to you, of course, business has got to, you know, business has got to take steps. And you know, companies like yours can help them. But there'll be more business involved, more damage involved, presumably more destruction of the economy if somebody wants to do that. And nobody is stopping them. What's the future of this? Well, the future for sure is right now. The problems that you're describing out of control ransom, ransomware, you know, bad actors out there destroying networks, that's happening today as we speak back probably during our conversation. Probably a bunch of networks got taken out. So you got to, like you mentioned, you got to hire the right people to come in and help you be resilient against these kind of things. Do you have a clientele here in Hawai'inae who were victims of this? I'm sorry. Hawai'intel is being picked up? No, you have clientele here in the state of Hawai'i who were victims. Well, I'm not a liberty to name names, but I can tell you for sure, we are not immune here in Hawai'i. I knew you'd say that. And to me, it sounds reasonable. There are no barriers, no borders. You know, why not? You know, it actually would be fun. There is a sense of humor involved, which leads me to believe these guys are not only creative but young. I mean, for example, I thought it was really cute that in the latest version of the ransomware software as available then from Reveal the website, there was a trial period where they would take your data or lock it up. And then if you were in the trial period, I signed up for it, in the trial period, you could unlock it just so that it would be demonstrated to you that the unlocked aspect of the ransomware worked. That's so cute. They got that from all these trial versions of software that we see all day long. It's like business.   If you get a million dollars, there's some kind of oddball deal where they get a part of that. That is the Reveal types. They get a part of what you recover. I'll tell you, put me on the jury, Attila. Put me on the jury. I will do what has to be done. But we haven't seen any juries. We haven't seen any prosecutions. So my question, my last question to you is, with all the knowledge that we have, that you have about the vulnerabilities and the way these guys conduct their intrusion into the networks, do we have a way, some way to identify them and go out there and arrest them? They could be doing this from Moili-Ili, not Ukraine. Let's assume for this discussion, they are doing it from Moili-Ili. They're a little one-bedroom apartment. So can we identify them? Can we bring them to justice or is it just impossible and leaving us as the globally vulnerable? Well, hopefully our friends at the FBI are not listening because they are very interested to find out if there's any bad actors here on Island because it is criminal, of course. So I would venture to say that you're right. We don't know who they are. And I'm also going to say that you're right. You got to do something about this. So everyone knows what to do. Everyone knows how to lose weight, but it's the action that makes the difference. Everyone knows how to keep their business secure, but it's the action. It's the decisions that matter. So until you change people's behavior, we're going to keep having overweight people. We're going to keep having cybersecurity incidents, unless you hire a professional. Last question. There are other professionals who might be interested in this conversation, namely lawyers. So if I'm damaged by this and there's a you know, a smoking gun kind of whistleblower memo out there, and I find it, doesn't it seem clear that the company who ignored the whistleblower, the company who knew or should have known about a vulnerability and did nothing as enormous, even total liability to me for failing to protect me? Well, that brings us up a good point. And it reminds me of GM's gross negligence back in the early 2000s with their safety belts, I believe. I'm not sure. They had something. It reminds me of pharmaceuticals that have had this numerous times. It reminds me of food manufacturers that have had E. coli and they knew about it. This is not a unique circumstance. It just happens to affect computers. You're right. You're right. But we have to we have to think along those lines, though, because as a community, we can't let this happen. So what are your closing suggestions to the public who may say in response to this conversation, I'm too small. I don't care. They're never going to care about me. Well, this is systematized, so no one is immune. And if any indicator on the news gives you any sort of direction, just know it's not a matter of if but when. Just like living here in Hawaii, we can expect storms. This is a way of life and it's part of the risks that we take on deciding to live in the most isolated landmass on the planet. You're going to have storms, you're going to have weather. And the best thing that you can do is prepare and be resilient. And there's lots of resources to do this. There's many community resources now being pushed out by the SBA. In fact, we have some good friends and relationships there at the SBA. They have some good cyber resources there. More and more IT professionals are becoming cyber aware and security aware, you know, speak with your cyber professional, or should I say your IT professional will see what the limits of their knowledge are on these kind of things. We work pretty extensively with in-house IT teams to help augment their capability and make them look good because sometimes there's just too much to be covered by a single IT person. You do need a professional. Now, who would have ever thought that this becomes so important in our world and important for coverage here at Think Tech? So I feel confident and hopeful that you and I will be speaking again because there'll be some other prices along a similar lines going forward. I look forward to a continuing relationship with you. I'm glad to help. I think the last time we talked about something was just a few weeks ago. So, you know, just a matter of time. Exactly what you're looking at. Yeah, it fell as a rest. Ilanda really appreciate it. Thanks guys. Stay safe out there.


Hi, I'm Rafael Ramirez. I'm a professor in the University of Pompeo Fabra and I will be teaching the course on music and neuroscience. We'll be talking about neuroscience, in particular We are going to learn the functionality and the organization of the brain. We are going to see correlations between the music, listening, music playing and brain activity. We are going to go and also learn about neuroimaging techniques such as fMRI, EEG, and we also have hands-on activities to try to apply these techniques, especially EEG, to gain insights into music. Also, we are going to be talking about the benefits of music in conditions such as Parkinson's disease, autism, emotional disorders and stroke rehabilitation and how to use music in the best way to alleviate or improve these kinds of conditions.


So, if you have Eris Morn's Gold Shell, this is not for you, but if you don't, this is definitely for you. There are certain Gold Shells in the game which reward you 10% increased XP. How's it going guys? My name's DPJ and I'd like to thank you for stopping by and checking out my video. If you do enjoy it, leaving a like truly helps me out and subscribe if you want to see more Destiny 2 videos. Okay, so with XP being a major part of the new grind with Shadowkeep, learning of ways to earn more is pretty important. Today I will bring you a said few Gold Shells which help you earn extra XP. So firstly you can see on screen now that Eris Morn's Gold Shell has a perk called Guiding Light which grants an additional 10% XP. If you don't have this Gold Shell then no worries, there are others you can get in the game, mainly from your collections. But if you do have Bright Dust Spare, at the moment there is one for sale which has this perk, it's this Shell right here called the Kitbass Shell. This will however cost you 2850 Bright Dust. But if you don't have the Bright Dust Spare, you can grab a certain few from your collections as long as you've had them in the past. And there are these. From Season 2 we have the Cosmos Shell. From Season 5 we have the Neon Helix Shell and the Hard Pact Shell. And from Season 8 the ones to look it out for are the Lunar Shell, the Orphi Eaches Shell, I believe that's pronounced, I'm probably wrong I normally am, and the Lion Garden Shell. All of these Shells stated reward up 10% additional XP from all sources. So if you don't have one, what are you waiting for? Get on that shoes. So yeah guys just a quick tip for anybody out there not aware of this. I thought it's quite important and I think you should know it. 10% additional XP is quite a lot. Especially if you are farming it as it adds up over the hours it really does. So yeah guys on that note we have come to the end of the video. Just a quick one informing you of these Gold Shells which you should be having and using. But on that note we've come to the end, I hope you enjoyed the video. If you did leave a like really helps out. If you're new around here and want to see more Destiny 2 videos be sure to subscribe. And if you never want to miss a video I upload you can turn notifications on by hitting that bell button. But guys thanks as always for stopping by. Hopefully you enjoyed the video and hopefully I'll see you on that next one.


All right Good afternoon. Thank you for coming after the almost the end of the conference. You got like what two more talks So I'm here to talk to you about forking. How many of you have ever forked software before? Okay, how many of you have maybe used forked software before? Okay How many of you like forking software? Okay, so I have some experience with forking software I I forked my SQL when we founded MariaDB server But that's not the only experience I have with forking software Because open office eventually also end up having a fork called Libre office and actually that fork was kind of an easy fork Because there was something called old build for Linux users So there's a lot of experience around forking A rough quick agenda around what I will be talking about Because folks mean different things to different people. Does everybody use github? Who doesn't use github? How about that? Okay? So That's a picture of a fork So it in software engineering a fork is basically you take an existing code base it's a very weighty decision and you can definitely You know force many parties that are reliant on the software to choose between one or the other And this is very true in many things like you know today my SQL And MariaDB. It's also very true from a Libre office Open office standpoint and so forth But the github generation forking means something else completely For one when you start something people people the maintainers they sort of appreciate that you've done some good work It's kind of like a bookmark Then they also encourage you to fork software But that is not a typical software fork that I'm going to talk about Forking software is basically you making a repository making changes and then Asking is submitting a pull request. So this is more a workflow and get up. Just calls it a fork The first open-source fork that I could actually track is actually postgres It's when Michael Stonebreaker decided he wanted something after ingress and today Postgres is what is probably what you're familiar with called postgresql So the first probably known fork was in the open-source wall was a database But maybe probably one of the better known forks is Gnu emacs and xemacs anybody here use emacs Okay This one really actually split an open-source community It also touched end users. So when I went postgres forked from ingress It really wasn't a you know, very end user end usable stuff But emacs had a nice UI and stuff and it had many many code branches And this is just a snapshot of those code branches This comes from a guy called Jamie Zawinski who made a lucid emacs and It's it's so big it can't even fit on a slide and he's actually made emacs timeline So if you Google JW that emacs timeline, you get Jamie Zawinski Zawinski's emacs timeline and Generally speaking forks take a really long time to play out in the case of emacs and xemacs It played out from 1991 all the way up to 2015 Timelines here 24 years before One one over the other When it comes to copyright assignment as well as contributor license agreements many open-source projects have them the free software foundation Definitely sees this as important And necessary for them to defend the code against gpl violations Whereas the xemacs developers for a long time argued that the lack of a copyright assignment Was what allowed major companies to get involved hence the you know formation of lucid and so forth And it allowed sometimes companies to license code back and so one of the major reasons to fork had to be around copyright assignment and Maybe if you contribute to open-source projects today, you may also end up Occasionally having to sign a contributor agreement, which many people do but many corporations find it maybe hard to do So the last table release of xemacs came out January of 2009 They always thought there would be a need for compatibility at the lisp level so lisp is a language that you get inside of emacs and There are a whole bunch of third-party packages like people use emacs to read email and they just move directly back into the emacs tree Then it turns out the reason Forks sort of disappears that you end up getting feature parity So once ex once emacs had feature parity to pretty much everything xemacs had as has an Enhancement they realized they were at a crossroads and there's probably not much reason for xemacs to continue development So that sort of stopped in December of 2015 And I think if you go and try to go to the xemacs of arm today even that domain does not even resolve any longer My SQL is definitely the world's most popular open source database There's another track downstairs. I think in the on the second floor. It's where we've been it started in May 1995 It's now many many years old. It has a huge history My SQL didn't start off as GPL software. It was not really licensed. It was sort of in the public domain but you had to pay for Save binaries on Solaris And on Windows since the idea was a you already paid for the OS you might as well pay for the software but my skill then became GPL in 2000 and dual licensing was definitely popularized by my SQL because the Libraries were also made GPLs and you get a copyright assignment sent to the company So the company actually owned the code But it wasn't it was definitely not invented there because a ghost script had it before as well In a DB Friday happened in 2005 Oracle grabbed the IP of the most important storage engine for my SQL the engine that made my SQL transactional and not a toy database so the first ever Maria project started actually back in my SQL days itself in late 2005 and The reason was because in a base had already been acquired. The idea was let's make another storage engine called Maria to Basically be a transactional my ISM. Is everybody who used my SQL before who has not used my SQL before? Okay, so you're familiar with storage engines my eyes. I'm in a DB and so forth So Maria was actually started off as as a project to be an engine so we we fast forward a little bit and There were other forks inside of My SQL as well. So this is a good example of one that started while my SQL was acquired by Sun Called Drizzle Drizzle doesn't exist anymore Well, then there are many other branches as well So to give you an idea of how long it takes for a fork to get started the first beta release of a server started in October of 2009 and many of us Were already working on the Maria project. So back then we used to use we went from bitkeeper to Bazaar and launchpad and now we use git and and github. So It took a fairly long time before we could sort of make a fork just just ready Because we already had a tree a base tree that we could use so The one thing that Maria DB sort of wanted to do right afterwards was to ensure that there was a foundation formed So and this would mean that if the corporation ever got acquired probably will have to get acquired This would mean that at least the software code remains open source So you don't make the same mistakes my SQL again Sky SQL was what was a company that has totally raised nearly a hundred million in VC funding So we fully expect that the company Maria DB cooperation has to get acquired because they bought Maria DB and they renamed the company to become Maria DB If you're gonna fork you want to make sure you have a story This is the story that managed to get people to use Maria DB From my SQL we would go to trade shows and tell people hey if you've used if you've heard of my SQL You must hear about Maria DB. Hey, we're the new emin lamp Even though maybe people don't use a lamp stack anymore and this was this was the original goal for the project And of course it didn't hurt that the competitors from Maria DB the project overlords were Oracle people for some absurd reason have an aversion to Oracle they have Bad memories for some reason or perceived memories, but Oracle has been great So make sure it's community developed right participate in Google Summer of Code Take stuff from other people because smart people are everywhere, but but in one one place And that's something that my SQL has never really managed to do so much My skill used to do this before the Sun acquisition, but never after We also want to make sure it was available everywhere So our logic was look if our fork is going to be Utilized we must replace my SQL in Linux distributions So we worked really hard to replace my SQL in every links distribution possible Because we were at that point in time backwards compatible But today when Maria DB is completely a fork and they're two different competing features I guess Linux distribution sort of realized that you have to offer both my SQL and Maria DB because the two different products But when we started we would just a drop in replacement This is also you can take a page on the cloud providers when you go to Amazon RDS You actually get to install my SQL or Maria DB. You don't get to you don't get to say hey, it's Maria DB That's actually my skill We also care about usage right usage really matters and OpenStack every six months runs the survey and it tells you What kind of usage? Patterns you're getting and if you're making a fork and you're not getting users then you're then you're probably forking for the Wrong reason for forking without users is kind of useless Of course in the my SQL world There are a whole bunch of branches and forks and people want to maybe migrate between them now If you could compare this to other things like say LibreOffice It may be a bit easier because the file format at least stays the same between LibreOffice and OpenOffice But it's not necessarily true when it comes to database features So So when you come to a fork in the road, maybe you should take it Sometimes you can backboard fixes So when you when you fork something you may think I can do I can do a merge and add features or sometimes you cherry pick features The merge and add features way is way easier and way Maintainable over a long period of time compared to the whole let's cherry pick because you'll miss stuff out during a cherry pick That's guaranteed So generally speaking From an engineering standpoint, I highly recommend that you you think more of a branch Than a than a hard fork But forking is forking becomes very expensive from an engineering standpoint as well Of course This also means that you've got to get rid of the not invented here syndrome that people tend to have When they wanted to do a fork They say, you know, you shouldn't look at you shouldn't look at something and say, oh, you know They've written that feature and it looks kind of odd. I can do it, you know, five percent better Because the reality is if you even if you write infrastructure software and you can get five percent better performance How many people run the infrastructure? How many people would benefit from that if you're looking for a user base? Probably not as many as you think also When you fork something like in the case of drizzle, there are two things one could learn from them One is you know when you make a fork you don't be aggressive you make it easy for people to migrate to your fork Because if you make it such that you can't even migrate say a wordpress a fairly simple schema database schema like wordpress To run from my SQL to say drizzle You can't you don't even allow wordpress to just be ported over directly because you've decided to be standards Compliant and remove features like a medium int for example Because the standard doesn't include things like a medium int and you want to be on csql compliant That turns users away because if you're not if you're not easy to use people are like we don't want to touch you Also drizzle think we'll teach you something else about making a fork If you all work in one company and you're the only people contributing to send fork if that company changes its ideas like in the Case of drizzle they said hey, you should go work on open stack rack space is not interested in a database anymore Then but then the project dies So this is something else you need to think about when you when you decide to go out there and choose software that you're going to use so Libre office They forked in late 2010 It's it you know it started its life as staff is Sun Sun purchased that and then had an open office project around around it But the fork was actually made very possible by the fact that there was something called OO build Which started by Michael Meeks of then Zimion and novel now collaborate and the goal was to make it easy to build a Linux OO build was a way to make open office build easily across all next distributions And that's how red hat managed to contribute to it Of course the Zimion folk did and whole bunch Other Sun even made commercial agreements with people like IBM so IBM's lot of symphony was actually based on Open office. How did how did that manage to happen when you make a commercial agreement? That's because every time you contributed to open office as a community member you signed a contributor license agreement And that's probably one of those bonuses of having a CLA However open office the Lord languished while it was at Oracle So LibreOffice sort of just took over and by the time it was too late I think Oracle decided to give it to the Apache foundation and by the end of by the end of maybe third quarter of 2016 The Apache project realized that were just lack of active developers or contributors that it didn't make much more sense to continue open office And today if you start needing to use software you probably just use LibreOffice But there's so many others When it came to Nagios and Icinga Nagios decided to take a more commercial path. There's a monitoring software and it took ten years for a fork to appear called Icinga It started first off as a hobby Nagios I love as a hobby like most open-source projects Then they maybe decide to make money obviously then people say hey Maybe we should in get investor money and then investors usually say look we were happy to give you money But within ten years you got to give us like ten times back the money Very hard to do with open source Nagios was serious about trademarks Slowed very very slow development on the open source project led to the creation of Icinga both now have active communities Though Google trends of course suggest that if you use that that Icinga probably needs to work harder at marketing OpenSSL and LibreSSL Maybe a few years ago some of you may remember the Ability and that they aimed to actually start refactoring code to make a more secure implementation OpenSSL at that stage and probably even now still needs better funding But it's a critical piece of internet infrastructure and the Linux Foundation decided to found a core infrastructure initiative to make that happen The whole Node.js and IOJS fork was was very short lived Largely because it was a governance issue. They needed an open foundation to help with more development No, no one in the community wanted just one single company to actually control active development at that point in time Joint was actually pushing Node.js fairly heavily joint was then acquired by Samsung So the Node.js foundation and love being part of Linux Foundation umbrella organization Everything's good. No no reason to fork Probably today you don't even hear about IOJS any longer Hudson and Jenkins so again not to pick on Oracle, but they seem to actually generate good forks Oracle basically said there's a trademark assertion on Hudson so the community decides to vote change the name to Jenkins and Oracle basically said Jenkins is now a fork. They will continue developing Hudson and but Jenkins today I guess is probably way way way more famous There's no security patches that we see that are being pushed to Hudson Hudson eventually got donated to the Eclipse Foundation probably to rest in peace just like open office So again not to pick on Oracle they're doing an excellent job with MySQL In fact, they're probably running most of the office in the track downstairs and my skill keeps on getting better own cloud and next cloud this one just bizarre The corporation basically received investment then one day the creditors cut them Off next cloud is a new thing with the next cloud foundation There's probably a much better story that one could tell if one went out for a beverage with the people behind this Sugar CRM and sweet CRM If you decide to quit doing open source and people depend on you they will fork Sugar CRM basically said we like to make money We're gonna stop developing the open source version and I know lots of you depend on it because it's a great alternative sales force People said no, we're not going to pay you money. We're just gonna fork and we call it sweet CRM Open BSD and net BSD open BSD is a very focused fork to your direct decided He wanted to make a much more secure net BSD. So he forked From a redhead standpoint I'm sure they they love that Oracle Enterprise Linux basically rebuild sent to us Sent to us is basically rel for people without subscriptions that even Red Hat is quite happy for you to use OEL is the hostile rebuild of of sent to us. I presume there are many people here with an Android phone Maybe not everybody is using a pixel phone Or or maybe to be fair. There's a Nokia also apparently now ships Android that's pure but however most of you probably use Android that's unpeel and They're basically forked androids Your user experience is affected the upgrade cycle varies And that's fragmentation in the market And I'm sure if you're all following the whole Cambridge Analytica fiasco You're also realizing that if you're using older versions of Android the messenger app probably uploaded all your phone calls to the cloud Bitcoin how many of you came in for the cryptocurrency aspect of things? Okay, good. There's another track for that however Bitcoin and And other cryptocurrencies they can they can do a hard fork They can basically think of a permanent divergence in a blockchain and it can occur with upgraded nodes and non-upgraded nodes And then the non-upgraded nodes will not be able to validate nodes for the future And then they use a consensus mechanism to say hey, okay, we've moved to this new standard maybe and You can have a regular hard fork and also a soft fork in the cryptocurrency world and If you Google forks, it turns out it's a great way of printing money So every if you decide today to create Bitcoin for seizure you could If you decide to create like coin for seizure you could in fact The holders of the existing Bitcoin will get access to other things So Bitcoin and Bitcoin cash or something that something has something like this happened And you actually you virtually start printing money, but you don't actually print like Derek derivative money, right? You print forked money And again, it's a how do you pick a winning fork? Those who can't obviously remember the past will probably repeat it. So one thing's for sure Why are you forking? The mere existence of a fork isn't what hurts a project rather. It is the loss of developers and users So if everybody decided to switch to Bitcoin cash and stop Bitcoin Bitcoin would die This is an extract that I've taken from Carl Fogel's book producing OSS. You can get it online for free as well Your real aim really is to minimize the harmful effects of a fork So generally speaking a branch is definitely better for development to continue in both directions Whereas forks generally slow development in one side. So if you look at the e-max axiomax example Pick a good name that focuses on in values Hence the whole new admin lamps scenario Takeaways if you're going to pick a winning fork the community matters your developers matter never ever annoy your community Work with them harness them Don't irritate them No matter what you plan to do your developers are really king They're gonna they're gonna push you if you're gonna choose a cryptocurrency to back Make sure they've got good developers behind it. Otherwise It's probably one of those scams You want to limit end-user friction make it easy for people to get on board You also want to make sure you're fairly well funded because that's part of the sustainable development method Methodology right it's getting much harder for you to get say if you decide to start a foundation get tax exam status in the US Any longer Go with another organization like the links foundation or something an umbrella organization think if you need a contributor license agreement as well and Hate to tell you You only fork after all other options are exhausted. You don't fork because you think I'm going to print money That's a really bad idea to fork forking for the sake of forking is very very silly Have a clear fork focus as a user of When you're choosing a bunch you got to think about the innovation that's happening today You definitely have to think about vendor locking because it turns out that even in open source You could be vendor locked in without you really really realizing it Think about the features you need today as well as tomorrow look at the support ecosystem around it as well No point using a fork that nobody supports or just one company supports And you can be smart about these things right look at website changes if they've taken money to fork You can obviously look at the web.arca.org to see they're spending money developing software or the developing websites unless that was the purpose of the fork and Remember venture funding as pitfalls as well. Sometimes things fail so with that Never like x386 or xOg and a myriad other folks that even exist so But maybe the best takeaway is is a branch better than a fork Probably yes But if you're gonna do something make sure you have a really clear fork focus If your focus of a fork is ego ego is a really bad motivator to do anything Ego is truly an enemy for if you're gonna fork software Okay, I think I'm out of time, right? well listening and I'm open to questions at the back outside The next be curious here, okay, so


really the matter is much more simpler than that. It's really much more simpler than that. There's injustice that was committed, and people just need that right back. It's really not complicated. We don't need to philosophize any of this, make it a big case of where we need academia, or you don't need a PhD or anything like that. What's wrong is wrong, and it's obvious. Killing children is wrong. Killing children is wrong. I don't care what their reason is. When you say this is because of the hands of Hamas, this is not the case. Okay. Thank you. I'll know that you're right. It's very simple. The path is simple. If Hamas surrender tomorrow, Hamas surrender tomorrow, the fighting would be over. If they release the hostages, the fighting would be over. Tomorrow, it would be over. It is very simple.