So what is going to be the final product? Will it still be OpenShift and you will just merge the technology technologies or there'll be a new product line? Yeah. So we're going to have, from a Kubernetes perspective, we will have one brand, the brand will be OpenShift. Okay. So let's start with the host level. So we'll start with CoreOS. So what we did is we said what became Container Linux, originally CoreOS Container Linux, what that did incredibly well was all of the automated operations over the year updates. The one thing that it didn't necessarily have was it was built on a kernel, like a Gen2 kernel, which didn't necessarily have the breadth of applications certified against it that REL has had in the past. So what we did was we are taking the work that the previous atomic team had done around miniaturizing the REL kernel for an immutable container bringing over the automated updates and over the year work, and that repackaging will be called Red Hat CoreOS. Oh, interesting. So the atomic brand will sunset over time. Red Hat CoreOS will be our container-centric immutable. So that will replace the project atomic host? Yes. Okay. Yes. And that will be mostly, is it rebranded Container Linux or Container Linux plus what you explained, bringing all those capabilities to that? So really, the way we look at it is there's two really important pieces. We want to have the best of the operations over the year, and then we want to make sure that every ISV that's ever certified against the REL kernel can continue to just work. So we get the best of certifications. Customers don't have to go through any process, but they get brand new operational model if that's what they choose to have. So that's the first step. We're going to, our offerings will be still available on REL if customers want that, but also now on Red Hat CoreOS. Excellent. So that's the host level. Okay. The second thing is at the platform level, the Kubernetes platform level, and what we really found was when we talked to tectonic customers, what tectonic delivered was a really great operation centric, Kubernetes cluster centric viewpoint, right? What it didn't do was anything that was sort of really developer centric, application centric, DevOps centric. So no pipelines, no middleware, no service catalogs and so forth. So what we're going to do is we're going to bring over the tectonic console. So a richer set of operation level viewpoints, we're going to bring that into OpenShift. So the brand that will continue there will be OpenShift. OpenShift's had a much richer enterprise footprint for deployments for Kubernetes. And so what we'll end up having is if you are an application centric person logging into the platform, you will see what you used to see with OpenShift. Very application centric, very robust in terms of building applications. If you log in as an administrator, you're going to see what's going to look and feel like the tectonic console, all the Prometheus work. So our belief is that we're going to now have a richer, we're going to have as rich an experience for the application developer, we're going to have a richer experience for the operator. And then the third immediate piece that we'll do is we're going to take the tectonic platform operator and make it infinitely simpler to manage and update that platform because we're getting Kubernetes updates every quarter. That's interesting because I don't know how I put it, but depending on who you talk to, sometimes OpenShift is seen as a redhead, not for, but distribution of Kubernetes, but quite kind of far from upstream communities, but tectonic was always seen as kind of always upstream. So is that correct? So not 100%. So tectonic was always just upstream. That was the claim was just upstream. And then obviously they integrated Prometheus, they integrate Flannel and SD. So just taking upstream, tectonic or Kubernetes never gives you enough to do everything. You still have to have network storage monitor, right? So that was tectonic. OpenShift was always, it still is, everything from upstream Kubernetes. And then there are some additional things that we have done that we will get back into mainstream Kubernetes, but that we had done ahead of the community. The community just didn't have the ability to accept them. So there's some more advanced routing capabilities we have in there, one or two little things, but from purely a Kubernetes perspective, any customer who wants to grab any Kubernetes tool from the community, Cube CTL, Cube anything, everything works exactly as you would expect in OpenShift and always has. Right, okay, so how challenging is this integration? Because as you said, operators will see tectonics if I'm not wrong and then we will see OpenShift. So how long will it take to integrate it? So we've already got some baseline integration done. So three months we've got that done.  The next release of OpenShift, which will be 3.10, which aligns to Kubernetes 1.10 will be out sort of the end of June. So that will be the first time customers will see sort of tech preview of these early integrations. So roughly four month window pretty good for two teams. And then we'll see further things in 3.11 and 3.12. So for the second half of the year you're going to start to see a lot of these things come out. The other really big thing that we're doing as part of this is that operator framework that CoreOS had initiated probably 18 months ago, they had delivered a Prometheus operator, an SCD operator and a Vault operator. Last week at KubeCon we open sourced that to the entire Kubernetes community, which was great. We saw a lot of interest in it. We've actually, and then this week we talked about it as something that will be fully integrated, fully supported by the OpenShift platform. And we got 60 or 70 ISVs who signed up and said we're fully behind this. We actually saw five or six database vendors in the last week who have built working functional operators. So our belief is that's going to be the new way that ISVs are going to package their software. They're consistently telling us Kubernetes is going to be sort of the new unit of compute that they're going to build against. And people love this idea that I'm going to use an operator to basically build an on-demand service that will run anywhere, sort of self-driving. It's got life cycle management built in. It's got an SDK to allow you to have all the knowledge about your application. It'll do some basic metering so you know what's going on. So that's for us really, really exciting.


Hello everyone, today we will be discussing about internet connectivity principles in IoT. Here is the learning outcome, by the end of this session, students will be able to critic the trade-offs between various internet connectivity options for a given IoT application in their own words. So these are the things that we'll be covering up in our video. First I'll be taking you through an example where we will discuss the basic needs and why exactly we're learning all these things and why it is very important to understand the network capabilities and the types of options that we currently have in the market for Internet of Things. Then we'll discuss about the types of network connectivity, then we will try to segment the given options into certain groups just within the scope of this video. And finally we will be trying to set up a balance depending upon an IoT application and then proceed ahead. So before proceeding ahead, it's a good moment here for the students to pause the video and think on which entity of this diagram that you're able to see on the screen belongs to which exact content of the cloud architecture that we have seen earlier. What you're able to see on the screen here is we have a couple of sensors, just imagine that we have some networks connected in a star topology like this, where we may also have some mesh topologies available. So these yellow dots, whichever you're able to see here, can be considered as sensors. This entire thing which is shown with the help of these yellow squares is a type of sensor and there are various configurations of the networking topologies available in the sensors. So as we are already aware that in a given computer network, there are multiple possibilities like we have a star topology, we have a ring topology and then we also have a mesh topology. So depending upon what kind of topology we are implementing in the given example, for instance let us imagine like these are the sensors like 1, 2, 3 and 4, these are trying to sense temperature for instance and these are trying to sense humidity and these are trying to sense maybe the smoke across some industrial plant. So at this moment it is very important to note that the available protocols that we have so that the entire data that is being sensed by these sensors will be transferred to some gateway. So here as we can see we are having again multiple options like what kind of internet we will be using. So ultimately when we think about the types of connectivity options that we have so that the data being sensed by these sensors needs to be pushed forward to the cloud. As the diagram shows here we have a cloud storage available somewhere on the internet maybe it would be something like Amazon web service based content or it would be based on Microsoft Azure or it would be based on IBM's blue cloud. So irrespective of what kind of cloud storage we are having we need to first of all think like how to transfer the data that our sensors are sensing to this particular cloud. So for that we may have multiple options like we may opt for Bluetooth, we may opt for ZigBee, we may opt for Wi-Fi or we may opt for an NFC that stands for Near Field Communication. Depending upon the available situation and depending upon the type of scenario that is present where these sensors are deployed we can decide like if the distance from the gateway for instance let us consider that we have a small gateway over here and this gateway is compatible to understand the protocols of Bluetooth, ZigBee, Wi-Fi as well as NFC. Then I can say like yes I have the following possibilities so that I can I can actually force this particular start topology. So when I say like I have a gateway which is capable of understanding all these four protocols that is Bluetooth, ZigBee, Wi-Fi and NFC then I can consider these group of sensors which is currently following the start topology can use Wi-Fi to transmit the data from this group of sensors to directly to the gateway. So the next group of sensors that we are having here is a ring topology which we have in the form of a ring. So I can follow Bluetooth over here and here I am having a mesh so I would force these group of sensors to follow ZigBee. So as you can see depending upon the need of my own IoT application whether I need a mesh kind of network or depending upon the topology that I am making my sensors to be deployed I can actually go for the selection of the protocol. So here what we have is the protocols. So I can literally force any of the sensors and their deployment depending upon the application to use a specific type of protocols. So whenever we have a gateway which is capable to understand all these protocol stacks it is whole and so responsibility of the gateway to forward the data further to the cloud. So it would be either through a cellular data like what I am showing you now or it would be through a router which may further be connected through an ISP or any other sort of network provider and then further data is pumped to the cloud. So on the other hand we also have some sort of user applications like it would be browsing some sort of applications on your cell phone or it would be direct consumer where you are sitting in a net cafe or maybe in your computer labs in your organization or industry and then you are trying to access the internet. So it would generally happen through this particular channel. So your traffic is actually transferred to the internet over the router and then this router is responsible for setting a proper connection to your cloud. And on the other hand we also have some sort of home automation examples like you want to automate some of the appliances like your rate conditioning units or maybe the light bulbs or whatever you have at your home. And then again you can set up your own IoT gateway in between your internet. So all these devices are somehow connected all let us imagine that these are smart devices and these smart devices are connected to your smart IoT gateway and then that will be holding the responsibility of connecting that to your home router or it will be directly connected to your satellite depending upon the application. And then furthermore the control or the data that is being sensed by these home automation devices is transferred to the cloud through this router. So if you could recall the cloud architecture for Internet of Things that was discussed in our earlier videos it becomes very prominent that the general architecture that we have on the screen now is always following a certain structure which is very important for considering the type of networks that we have and what protocol needs to be utilized. So let us move ahead and so now let us discuss about the types of network connectivity available in our hand. So internet connectivity generally possesses seemingly overwhelming number of options in today's market and one of the most widely used internet connectivity options for IoT based devices is cellular network and very rarely we may use the satellite kind of internet where imagine that we are trying to send some sort of industrial parameters over a ship where you are in the middle of an ocean and you do not have any other means of internet connectivity except you need to directly access the internet from the satellite. The third one is which we are widely using in today's market is the Wi-Fi connectivity and the Bluetooth one. Apart from this we also have numerous number of applications like NFC, RFID, LB band and all the things. So here we have high power consumption, high range and high bandwidth. So here are very good comparison of the trade-offs between the connectivity options we are going to lay down. That is here we can consider a smartphone which is trying to transmit a live video definitely requires a high power consumption. So by saying high power what do we mean is it needs frequent charging. So if you consider your cell phone definitely we need to charge it oftenly for every one or two days as of the current scenario what we are having in the market. And definitely it has a very high range since it is having a cellular connectivity and also it has a very high bandwidth. Since we are having 3G and 4G available in today's smartphones we can say that the bandwidth being used is very high and also the capacity of these devices to use this high bandwidth is also possible. So the next type of category is wherever we are using Bluetooth and where we have Wi-Fi and we may use that Ethernet connection sometimes. So whenever we are talking about Ethernet connectivity especially we can say like the power consumption is going to be really low and of course since we have limit over the length of the Ethernet cable the range is also very low. So here we can definitely gain higher bandwidth, low range and low power applications wherever we have embedded devices or any sort of other computers which are opting Ethernet connectivity. And the last option is low power, a very high range and a very low bandwidth. So this is something very tricky combination. So the most important protocol that we will be discussing in our further videos is LP VAN which stands for Low Power Wide Area Network again which offers its variants if we try to explore this protocol further. So this is an application where the power consumed and the bandwidth being consumed is very low but what it is offering is a very high range. So as a summary what we have is every IoT system combines the four basic components like sensors, connectivity, data processing and user interface. But what matters is ultimately it comes down to your specific application and the organization needs to choose a right component for connectivity and the available options for connecting your sensors to the internet. Here are the differences used, thank you.


Uh, let's see where I've got to find it though, because there's lots of stuff in here. There's, we have lots of Tonys, but listen, uh, Tony reminds us. But again, with quick tips, if you don't know, then it's not a reminder. You get to learn a new thing, which is amazing. In iOS, uh, Tony says, I never realized I could trash from mail just by holding my finger on the archive button a moment longer. And what he means is if you have it so that the default button in mail, when you're reading a message is archive, now you could have the default button to be trash, you can choose between the two, whether it's, you know, the, the button is archived or the button is trash, whichever one it is, if you hold down on it, it will give you a little menu and you can choose the other one. So if it's archive, you can, as Tony says, you can hold it down and it changes and it'll let you choose trash. And of course, if it's trash, you can hold it down and choose archive. And that's a super handy feature. I love that about, um, mail. I love being, it's like iOS mail for triaging mail. It's not as efficient as doing it with a mouse and a keyboard on my Mac for sure. But it's not bad. Like it's doable with, especially with swiping and you can swipe left to delete and swipe right to, to archive or vice versa. Again, depending on how you have those options set up, but, um, but yeah, it's, it's pretty good.


Hi, I'm Greg. I can do a whole talk and just icons. So last year, I've been giving a talk about what happened with Spectra and Meltdown. And this year, I'm actually talking about what's happened in the past year. It wasn't as publicized, but it's just as important and just as nasty in a way. So I gave this disclaimer last year. I'll give it again. This is a vastly oversimplifying all of this. I don't actually have code in this talk anymore. There's a whole bunch of really, really good details, links to technical papers, links to the academic papers that are written about this, links to everything else in the presentation, links that are in here, too, as well. So go download the presentation. So let's talk about this. So MDS. MDS was announced beginning of this year as yet another type of Spectra Meltdown issues. These are, again, hardware bugs. These are bugs in the CPUs themselves that the kernel is then responsible for fixing. Because it's hard to fix hardware, you have to buy it. The CPU life cycles are years long. It'll take a while. All these issues exploit how processors see in the future.   And it turns out a lot of CPUs don't really unwind everything. If they did something and it affected the system and when that happens, you can take advantage of it in a side channel and get some information. There's a whole bunch of different variants. A lot of them got lumped under this name of MDS. And like I said last year, this is gonna happen for a very long time. I've been giving this talk already for a number of months and I'll talk another issue just was publicly released two weeks ago, I'll talk about, and there will be more. This is not going away. So again, all these are hardware issues. MDS really only affects Intel chips. No other processors are affected, no other hardware companies are affected. Spectra Meltdown did hit all the other companies, PowerPC, AMD was only half affected. But all of these are for Intel. And there's all again the variant of the same problem about going ahead in the future unwinding.  So you have to update your BIOS. We have to work hand in hand. They have to do things in the processor to fix this. And if you don't update your BIOS, you are still at risk. So please update your BIOS. It'll ask you to do so. Don't ignore that. You have to do that.  So push back on your vendor. They have to have this. So MDS is again the same type of thing as they're not a really extreme security issue. You can't write something to somebody else. You can't cause something else to happen in the machine. All you can do is read what somebody else did. But the interesting thing about this is it'll cross the virtual machine boundary and in cloud computing, you're running untrusted things in different virtual machines. You don't know who else is running on your machine. So this can be a real issue. I can read a data of somebody else. Somebody else can read your data. And that's not a good thing. It can also cross in the user space. You can run web browser and read other web browser tabs and things like that. So that's exploited ways as well. The big thing about these MDS issues is it exploits hyperthreading. Hyperthreading is when you put multiple cores and they share a CPU cache. So you share some caches and there's a way that Intel and a number of other processor companies have gotten to give you a fake second CPU. But when you start sharing resources, it turns out you can see the resources that the other people are using. Again, you share the TLBs and they level one cache, sometimes level two cache, depends on your chip. These are the problems that are issues here. I wanna call this out. OpenBSD was right. When Spectrum Meltdown first came out, they told people, disable hyperthreading. We think there's gonna be more issues than here. They were right for the wrong reasons. They didn't guess what was really gonna happen, but they knew something could happen here. And they took the heat. They took the heat from a lot of people because when you disable a hyperthread CPU, you are now removing a processor from your machine and it can affect performance big time. OpenBSD again repeated it in August. Please disable hyperthreading because people weren't doing it. And because of that, they were not vulnerable, almost not vulnerable. They had a little bit of vulnerability, but they took away almost all the vulnerability because you disabled hyperthreading. They chose security over performance and you have to give them credit for that. They were ahead of the curve that way. Now, all the Linux distros say disable hyperthreading. All the other operating systems say disable hyperthreading, preBSD, NetBSD, even Windows. You have to do that, but openBSD was first. Gotta give them credit for that. So that was MDS. Here's the specifics of them. One was called RIDAL. It was rogue in-flight data load. There's a cool research paper about this. Inside CPUs, there's something called line fill buffers and load ports. CPUs do, there's a whole nother machine way down underneath there that does all sorts of other complex things that I'm learning way too much about. I never wanted to know. And these again, you can steal the data across an application, across the virtual machine and out of a secure enclave. And this is really unique. Intel processors have this thing called a secure enclave that it was supposed to be trusted. Nothing can ever get out of this at all. It turns out everything can get out of these. They were totally and completely broken. We fixed this by flushing some buffers in the CPU when you do some context switch and again, a bias fix. So we flush buffers and it fixes it. There's another paper that came out called Fallout. This one had a cool logo. Again, the CPU store buffers, not load buffers. Same idea. This one, from user space, you can read what the kernel is doing. And normally that's not a big deal if you own your machine, but sometimes you can read secrets like if you're in a container from somebody else's container. Or you can read secrets in the kernel where they have keys, other issues like that. Not good at all. It totally and completely broke the random kernel addressing. And a nice side effect of meltdown is it made it much easier to exploit this. Side effects, it is bad. So we fixed this by flushing the buffers in the CPU on every context switch and a bias fix. Zombieland, best logo ever. These guys have a really, really cool demo. A nice little demo in the browser. You can read another browser's tab. Good at marketing. These academic people are really cool. Just like Rital, again, steal data across applications out of virtual machines, out of secure enclaves. Another little different variant. We fixed it by flushing the buffers on the context switch. That's fun. And then there's a number of other ones. All of these got announced at the same time. Store to leak, meltdown to UC. They all, again, reading data across security boundaries. Places that you should not be able to break. You can read data across them. We, again, fixed it by flushing the buffers on the context switch. No fun. And then two weeks ago, another one came out. Swap to yes. This one's a little bit different. It's more like Spectra was in the beginning. And the best thing about this is Intel has documented all of this stuff in their patents. Security researchers and academics there's a great tweet of one of the academics who I think published this one showing all the patents they printed out from Intel and how they're finding these issues. It's really funny. So now you have all these professors out there reading patents. There's going to be more. Again, they found it reading patents. So this is public knowledge. One to 5% performance hit depending on your workload. And we fixed it by flushing the buffers. Fun stuff. So all this flushing buffers is slow. So all of a sudden, the kernel has to do a whole bunch of more work that it used to never have to do that. We can't do anything about this. There's a way in theory that we could do something by scheduling things in different ways and different processes and whatnot. It's a wonderful academic theory. There's nobody actually been able to do this in a way that works. We have some cool patches out there for it if people want to try it and work on it. But so far it is not a viable solution. The best way to do it is disable hyperthreading. And then almost all these issues go away. So all the distros, all the processor company, all the Linux, all the operating system companies are saying disable hyperthreading. Do it. And that's the only way to solve this issue. So if you're worried about this, you have to do this. Not good. But that's the only way to do this. But how slow is this really? And it all depends on your workload. So when I do things, I do two things all the time besides read email. I build kernels and then I make a kernel and ship it off somewhere else. When I build a kernel, highly OS or highly IO and CPU bound, huge issues, it is a 15% decrease on my workload. That's noticeable. That's real. If I leave hyperthreading on with some of the performance issues, we're still flushing some buffers, there's still a little bit of security issues. It's only 2% down. But that's not very good. But when I create a kernel, it's all one thread. It's all IO bound, no impact on my performance at all. So it all depends on your workload, whether you'll see this or not. Run your workload. Everybody has a different workload. Run it and test it. Because now the problem in the kernel using Linux is syscalls actually matter. Before, Linux syscalls were the fastest thing out there. Now they're slow. And now you need to worry about that. Depending on which syscalls you're doing, if you're doing an IO syscall, now it's not as slow because you're doing IO and that's the slowest thing in the world. But if you're doing other syscalls, they can be slow. And that's a real problem. Everybody's workload is going to be different. There's nothing we can do about it. So test your workload. It's all different. So now you have a choice. You have a choice whether you want to go for performance or whether you want to go for security. And everybody's choosing differently. My cloud provider shows performance. I don't know if they're going to be my cloud provider much longer. The cool thing about the kernel is we export all this information. And you can see below you what is happening in the virtual machine and on the physical machine whether it has these updates, whether the bias has been updated, whether the patches have been made lower than you in your virtual machine. Your kernel will report that information to you. Look at that and make your own decision what you want to do. And tongue in cheek, make Linux fast again, shows you the command line you can give to the kernel to disable all this stuff. All my kernels go back to 15%. This actually, all my numbers, my performance numbers were before swap Gs. So add another 5% to my workload. So now my kernels can be 20% faster back to what they were two years ago. The kernel, all new releases are usually faster. Now we're actually having to go slower to fix hardware bugs. It's not fun. But look at what your cloud provider did. Everybody did something differently. Hopefully everybody will make the right decision for cloud providers at least if you're running untrusted virtual machine to be secure, I hope. So I talked about before, Spectrum meltdown with Linux was a total and complete nightmare the way it was handled and whatnot. So for this, we were much better. We've gotten a lot better. We had kernel fixes for everybody available on the announcement date. Intel did talk to us and we let us work together in a nice way. It was much, much better. We worked with the other OS vendors, we worked with the BSDs, we worked with Windows, worked with Xen, we worked really well together. Much, much better. It still needs some work. I will call out Debian was only notified two days in advance. That was not acceptable. For SwapGS, Debian wasn't notified at all. So Intel actually regressed there. They've since fixed that and they are now knowing what's coming up next.  I gotta call out a very good job. Because it turns out 80% of the cloud systems out there are either running a kernel.org kernel or Debian. And companies don't realize that anymore. They think that the old model of the enterprise distros, which their market has grown and they're still important, but that's not the majority anymore. The majority is Debian and kernel.org-based kernels. So AWS has a kernel.org-based kernel that they use on their systems, things like that. You cannot ignore Debian. That is not acceptable until it's getting better. But it's doing that. The thing is we release these things now a larger amount of kernel people can see it and we fix another thing a week later. And again, keep updating. We're still doing fixes. We're still finding problems. We're still fixing other issues. It is not a matter of patch once and you're done. You have to take these kernel updates every week. Always update your kernel and always update your bias. That's the best way to do this. And along these lines, talk about security fixes overall for Linux. You have to do this. We update and push out a security fix at least once a week. If we know it or not. We're doing about 22 patches a day in the stable kernel releases. Those are all known bug fixes. You need to take those. Sometimes we don't know if a bug fix is a security fix or not until years later. Infamously there was a bug in code that I wrote and then fixed that wasn't figured out till three years later that it was a security fix. I didn't even know it. So take these fixes and do it. The kernel, community, mantra is a bug is a bug is a bug. We fix it, we push it out and we go. And we don't get CBEs. CBEs for the kernel mean nothing. We don't assign them. We don't do anything about them. You cannot rely on a CBE to say, oh, I got the CBE fix, I'm okay for the kernel. It doesn't matter because only a small fraction of the fixes for the kernel get a CBE at all. I will never reply for one. There's issues with trying to revoke them when they're invalid. It's just a nightmare. For the kernel, it doesn't matter. It does not work well because we have fixes like spectrum meltdown had one CBE number, but we had 80 patches and they were fixed by Gustavo more spectra patches last week. So he's been fixing spectra patches for about two years now. You can't say it's one CBE every, here's the 200 patches. It does not work that well. Somebody, so there's a link. You can look at my talk, how the kernel security team works and why this matters and how we do this type of stuff. Read that document. It's a big long white paper I wrote a long time ago. It's really, really relevant. And another thing is we've looked at what CBEs are actually issued for the kernel. Case Cook did this research. We looked at 12 years of the kernel CBEs. The best is negative fixed date. Average fixed date of negative 100 days. Think about that for a second. Somebody says, I wanted a CBE for this bug fixed. So I go, okay, great. They assign a CBE. He's like, what was it fixed? It was fixed four months ago. What? People are abusing CBEs to get around management problems with their companies. They assign a CBE because as the CBEs are there they have to get the fix in instantly, right now. Engineers are routing around the crazy policies that management has put in place. That's what this is proof of. I mean, look at the negative 3000 days. I don't even know why that CBE was assigned. The standard deviation is what? 400 is over a year. This data is all over the place. It means nothing. CBEs and the kernel do not work. I've sat down with the Mitra people. We're trying to figure out what to do. They've said the CBEs and the kernel does not matter at all. Open source and CBEs for a lot of projects are not relevant. That's not what CBEs were created for. We're trying to come up with a way to have a better type of thing. I talked about it with earlier at a conference this week here and we're talking about it in Paris and another conference in a couple of weeks. We're coming up with some ways to handle this. For now, do not handle this for CBEs. There is a better way to do this. And Google actually has documented this stuff. They've proven this. We always said the kernel, the stable kernel releases, they have all these fixes in it before you need it. And Google's like, yeah, yeah, we don't believe you. So we didn't track the numbers. The kernel security team at Google goes around and finds all the problems that were reported, that are found, that are told to them, that are announced to them with their bug bounty program and then they tell Android, hey, go take these fixes. For all of 2018, 92 over 201 of all the problems were already fixed before they knew about it. Every single one of them was already fixed. The only ones that were not fixed were ones in the code that they had added to their kernel that was not upstream or that was there because they back ported features incorrectly and they got it wrong. So every single fix, every single problem that they found that they were reported or they dug up was already fixed before they knew it. And because of this, Google is now mandating for Android devices, you take the LTS releases. Pixel phones, they update to the LTS release. I'll call out Sony. Sony's been doing this for the past year and a half, at least. Update the kernel every two months or so with all the latest LTS, they are safe and they're good. Essential, another phone company, really good about this. They're doing the right work. I've seen the numbers so far from Google, it's not public yet. The numbers so far were over halfway, they're already in the 200s. So they're actually finding more and more problems. And again, we're on track record to be the same percentage again. So it is, take LTS releases, it'll be fine. So I will say this, I've said this is other conferences, please get this through your head. If you're not using a distro kernel that you trust, some distros trust more than others or stable a long-term kernel, you have an insecure system. That is the facts. If you can't update your kernel on a device, it's insecure. I'll say that right about the time. So I gave this talk, somebody in this room told me this quote, somebody else had said this needs to be the title of my talk. It's sad, and you should feel bad. We feel bad. The goal of a kernel is to paper over the bugs in hardware and make it look like a unified system to upper user space. You can run any kernel, run any hardware. That's the job of Linux. We do that really well. We've been doing that for 20 years. The problem is when the hardware has bugs that breaks the model of how we thought they worked. And you can't really fix it. And we have to do things to work around those problems that directly impact you. That's the only way we can fix this stuff. Hardware has bugs. We've always known about it, but now we have to fix this and we're fixing this before you know about it. Spectrum meltdown, zombie land, MDS, they're all issues. They're not as important as the whole security instance. We push out fixes that can cause your machine to crash, that can handle nasty network packets that do bad things. We fix those bugs every single week and we push them out to the world and people take them. Update your kernel. Disable your hyperthreading. Have to do that. We are now on board with OpenBSD. Again, they were right. Fully give them credit. Disable hyperthreading. That's the only way you can have a secure system. And update your kernel and update your bias. And yeah, it's sad. I'm sorry. Thank you very much.


So pull downs rows there's different variations like I can row from down here from here from up here And then as soon as I come up here now It's more of a pull down and I've got different and the part that makes it different for the back is not really the Position of the wrist as much as the position of the elbow Understanding that you can grab all these cool variation handles and that helps dictate where the elbow That's right So if I'm in supinated look where my elbow drives versus where if I'm in a wide grip look where the elbow drives So when you're creating variety for the pull down and the row Think less about the handle think more about where the elbows are driving down and back and how different and it is from the last exercise


A tear in the knee meniscus can cause this shock-absorbing structure to shift from its normal position. A new study on pygmies suggests that even a small degree of meniscal displacement can have a big impact on meniscal load transmission, increasing stress to the knee joint. The findings are published in the American Journal of Sports Medicine. Tears of the lateral meniscus, or LM, are common sports injuries. Associated meniscal displacement is sometimes visible on MRI, which can aid in diagnosis of a tear. However, it's not clear how the amount of displacement is related to the severity of the tear, or to the degree of load transmission impairment. To help clarify these relationships, researchers used a robotic system to assess eight pygmies before and after radial LM tears were created. The system applied a 300-Newton axial load to each knee at 30° and 60° of flexion. A sensor attached to the tibia measured the three-dimensional forces on the knee, while cameras tracked LM displacement according to the relative positions of reflective markers. Each knee was tested under a series of four LM conditions, with an intact LM, and with a 30%, 60%, and 90% radial tear. The LM was then removed, and the robotic system measured the knee forces over the same exact trajectories from the previous conditions, but without the meniscus present. The resultant force through the LM was calculated based on the forces in all of the tested conditions. This resultant force was used to evaluate the effect of each degree of tear on the load transmission function of the LM. The 30% and 60% tears did not cause meniscal displacement, or affect the force through the LM under axial loading. However, the 90% tear caused significant anteroposterior displacement under loading at both knee flexion angles due to tear separation. Because of this displacement, the resultant force on the LM was markedly reduced, indicating that load transmission through the LM was impaired. Importantly, the LM dynamics inside the joint and the potential effects on the medial meniscus weren't evaluated, and acute versus chronic effects weren't considered. In addition, the robot was only able to apply a standing force, running and jumping forces weren't tested. There may also have been tissue or sensor differences between trials, since the same knees were tested repeatedly. Although more work is needed to translate the findings to humans, the study indicates that even one millimeter of displacement after a radial LM tear can significantly reduce load transmission, suggesting that repair surgery is worth considering for human patients with displaced torn LMs.


This was listed as the UNICEF Summit. Really, it's more of like a game type act as a blockchain team. Fun fact, UNICEF has a blockchain team. But we are part, yeah. My name is Chris. And my name is Maren. So if you don't know, UNICEF is the UN Children's Foundation, or Children's Fund, I should say. And we are part of the innovation team. As I mentioned, we explore emerging and frontier technologies for UNICEF and kind of use spaces for the broader UN connectivity and the importance of designing with constraints in mind. So at UNICEF, we are focused on certain program countries. So these are countries that are low resource, have high resource constraints, meaning that they don't have access to all the same resources as developed countries. And so today, we will be doing, because in the immersive game, which are all these tables are for, to help you think about when you're designing your dApps or your different programs, what it may be like to have internet connectivity constraints. Cool. Thank you. So the basic agenda is that I'm going to talk for 12 minutes or so, and then we get to try out this game. But before we do that, if you have a phone, can you hold up your phone? If you have one phone, if you have two phones, can you hold up two phones? Yeah. Two phones. OK. If you've got a Nokia 1100, anybody have a Nokia? This is the best phone ever made. Remember this, with the charring last seven days and I have one game, which is that one? Our team looks a lot at how we can design solutions for people who may be using a phone that's closer to this than to the computer, the super computer apples that we all have in our pockets and hands. And so we wanted just to spend that first 10 minutes to talk about why this is important to everybody in this room and to the world that we live in. As Arianna said, UNICEF is this really old organization. It's 70 years old. It works in every country in the world in some way or another. And it has a $7 billion a year budget, which is stuff that I don't think we knew when we joined the organization. But it's a big market-shaping organization as well. So when it starts to buy things like pencils, well, more importantly, like vaccines, it begins to also shape global markets, which is kind of interesting. It uses that huge amount of money to influence the way that companies produce products and goods. And this is really important because our world is faced with a huge number of issues now that we weren't faced with 10 years ago. And one of the examples is the outbreak of Ebola that we're finding moving quickly through the DR Congo and elsewhere in sort of the region, although still not a ton of cases have appeared around Congo. But Ebola is a disease that spreads quite quickly. And it spreads particularly where there isn't a lot of information around it. And we want to just give two examples. We'll talk about Ebola. We'll talk about schools. One of these is happier than the other. The Ebola one is the less happy. So as we look at how we as an organization work with governments to predict where a disease like Ebola is going to spread, you can do it really easily in a well-connected city. If you remember the Google Flu trend stuff from about five, 10 years ago, as you get a lot of data points from all the stuff that we're generating on our rich phones, it's pretty easy to track where an epidemic is spreading. But if you're out in Eastern DR Congo there and I ask you, where's Ebola going to spread? It's pretty hard to tell me as an epidemiologist or a data scientist.  And we're gathering, like Facebook's gathering all the creepy information about us that we don't want it to and network operators are also. But that provides a web of connectivity that allows us to know where people are in the connected world. But in the world of the Nokia 1100 or less it's really hard to figure out what kind of data is being generated and it's really hard to figure out where people are moving. Where people are moving is where diseases move. So if you're an epidemiologist, you wanna track a disease, you look at where people move because where a person moves, a disease goes. But this is the type of tool that we often use to track diseases. And so when our team was in Liberia during the last people outbreak in 2014, this was a map that we used. This was updated, the refresh rate of this was like every two days and you couldn't zoom in on it very well. And so that was the type of map that we were using to figure out where Ebola was moving in Liberia. However, the type of stuff that we're able to do with data scientists and with a team of pretty smart people is to look at how you can take the type of thin data that comes out of a mobile phone like this, aggregate it and turn it into intuitions about where a disease is spreading. And in fact, we've done this in the art combo and you can see some of the results of our work here which is that we're able to predict where populations are moving by de-biasing mobile phone data. And that's really important because those diseases affect all of us. They affect us in this room here, they affect people in Geneva and Stockholm and New York because we're suddenly a connected world. But we're not an evenly connected world. If you look at a country like Mauritania, this is a map of Mauritania as seen through data science and the white triangles here are roads. Those are roads which have mobile phone towers on them. That's what those triangles are, so it's a cell tower. The dots are schools. The schools in blue are schools that have 2G. The schools in yellow have 3G connectivity. So in the 2G schools, you can send a text message. It's kind of neat. In the schools that are gold or yellow, you can do something more sophisticated. The schools that are red, those dots there, have no connectivity at all. That's where there's no signal. There's no way to get to a teacher and make a call to understand whether a disease is going to spread. And if you ask a doctor and epidemiologist, they'll tell you that if the bullet starts here, it'll spread along this corridor. And again, that's an intuition that we have in a connected world very easily. We can gather that data. But it's really hard to do if we don't have good connectivity. Obviously, if you have connectivity, you also have tons of opportunities for businesses, for building apps, for looking at the next generation of users. But the user experience has to be very different because if you're using something like this, it's really hard to think about all the stuff that we sometimes take into account when we're designing for a smartphone. And so we wanted to talk a little bit about that with you today. And we've all come to a hotel where you have a Wi-Fi that's the most important thing, more important than being into your room. So we're all kind of familiar with that Maslow's hierarchy of getting connected. But we wanted to actually put ourselves in a position for the next 20 minutes or so, 30 minutes, where we run ourselves through a game about connectivity. And we'll explain why later on. Connectivity is a global problem. We've been mapping connectivity in countries like Brazil and Colombia. These are the same maps that we showed you as in Mauritania and in Kyrgyzstan. And the number of schools, all those dots, the red dots, without connectivity is huge. There's no way to solve that with traditional money. There's not enough dollars to put into solving that problem right now. And we need to think about other sources of value, other ways that we can inject capital into the system to connect people, to generate the data that we need to be safe, but also to ensure that people all over the world have access to the opportunities that can be taken for granted in a connected world. And so this question of access to information is what we're gonna spend the next 30 minutes or so of doing with some layouts. We're gonna look at what it means to be connected. We're gonna challenge you to do something very frustrating, which is solve a challenge where you don't have access to your phones for the whole time. The test group that we did this with, so you're gonna cut your phone for a little bit, put it away for a little bit, it'll all become clear in the instruction. The test group that we did this with almost revolted against us, because they found it so frustrating to do simple things like figure out a song lyric without access to the Google, which is tough. But we're gonna try to do it together and you may be frustrated at the end, you'll feel a sigh of relief as you get your device back and you're not gonna lose it at any point, but you are able to be connected again. But the reason we're gonna challenge you to that is because we believe we'd like to propose a solution to this. We'd like to propose a set of thinking around how we could create some of this connectivity and use all of your brains in the room to do that. So the end of this is reductive in a way, even if you do stage a revolt, because we're gonna look at some solutions for how we prepare for the jobs of the future, how we start to get in front of some of these pandemics that are spreading, how we monitor things like climate change where they're not happening in urban environments, and how we start to deal with people who are stateless, who are disconnected, who are immediately out of the whole informational context that we're working on. So I wanted to pause there, we're gonna go into the next round, but again to say thank you to all of our team and to Yas, where are you in the back of the room, who's joined us from Tokyo from the UNICEF office there and you better where are you, who's joined us from UNICEF France as well. So there are a few other colleagues of ours who are here and very excited to see how angry and frustrated we can get as we become disconnected for the next half hour and how we can work together to build something pretty exciting. Thank you. Game time. So what we're going to do with you up that we'll begin with instructions and so we're gonna ask you for the next 40 minutes to put on your role playing hat. The game is a spy and having to solve different challenges and puzzles so channel your inner James Bond and get ready to solve some challenges through being disconnected. So you will see on the video and we'll have the mic, the sound system is a bit off so we will have the mic next to the speaker on the laptop but there will be sound queues so for some parts of the game you'll be able to use your phone for other parts of the game you won't be able to use your phone. As Chris said it's gonna seem confusing there's instructions also in the bags on the table but we're gonna take a few minutes and allow you to self organize around the table. So ideally there are about 20 to 30 people at each table and then we'll give you time to get adjusted and then we will queue the game. So we'll take a couple minutes down, you can stand up. You can bring your phone with you. Yeah, so instructions. So there's gonna be a narrator who is giving instructions. They do go kind of fast which is why we've included a printed version of the instructions and then we're gonna play the video for 40 minutes and it has the time queues for the game. So the video will be playing for the next 40 minutes and here we go. Hello spies, welcome to your training session. An notorious thief has stolen several rare and expensive items and has hidden them in different locations. Your task will be to figure out what has been stolen, where it has been hidden and collect further instructions from one of our agents by giving them the top secret go code. For the location you'll find a series of cards on the table with this icon. For the image you'll find cards with this icon. You'll definitely need the internet for this one. For the go code, you'll find cards with this icon and the Legos. A go code has a series of numbers that will translate to a phrase such as the eagle has landed. Separate yourselves into groups according to which task you'd like to do. Would you like to find an image? Or would you like to find an image? Or maybe you'd like to work on a go code. Then, one of the spies will shuffle the deck and deal cards to each spy, including themselves. Throughout the session, you'll see a great sign which means you can use your phones and show your cards to other spies. You'll also see a red sign which means to put your phones down and to take your cards back into your area. Do not show them to other people. Remember, even when there isn't internet, there is always something to do. Once you've managed to get the image, you're created by drawing it on a key card. Once you've managed to go code, show it to the facilitator. If you get it right, they will give you further instructions in an envelope. If you get it wrong, well, better luck next time at another spy academy. Oh, yes. Go, go, go. So, within the deck of cards that you have, there are actually three sets within that. So once it has, or once you've completed that cast, just wait for the video. Just make sure everyone has a card. Does this happen? The dance team over here. Some people may have to have two cards, just to have them. I'm gonna fast forward because you guys are so good at it. Cool, okay. Okay. If you refresh around the instructions, they're on your table. Oh, yeah.


Everyone and welcome, this is Melissa Armo with the stock swishing and reviewing Delmo. Delmo, Delmo, Delmo, Delmo. Delmo is, well, I mean, this is totally flip for the day, but if you look at the market, you can't wonder why. But this is again, why you must take profits and stocks. This was in a really nice call this morning. So let's go back out of the game. Two o'clock on a Friday, no one should still be in a trade anyways. So anyways, we shorted this today, boom. Got it, drop, boom, out. Beautiful move. In fact, where did this go? I did say the possibility of 25, 25, 12, 12 cents from the dream target for this, but this was in big move. Beautiful call in here and out. That's how fast day trades can work. Fast, fast, fast, that's the way that I like to do it. I said this morning, that's gonna fast trade and out, it's Friday, it's summer, it's the best thing to do. Now I did call a second trade if anyone wanted to do it here into the drop and this did almost get to 25. I think a couple people missed the first trade to the second trade, some did the first trade and the second trade. Again, if you're going to listen for the day, I suggest people just cut it. Do one trade and stop. I'm a firm believer in that, okay, which I followed those rules today to the letter, but going up here and looking at this, I will just show you this picture here. This does not have a lot of data, which I normally, I'm kind of like, you know, when I see something like this we'll add a lot of data, but I really do like the app today and I was right, great call, nice call. A media call. Really so happy this worked out so well today. A lot of people want to buy a stock, so 200 per move an average and it's not a strategy and it's the wrong thing to do on a regular basis. Even though sometimes it works, that's not what you should be looking at. If it was that easy to go long, every trade of the 200 per move an average, then everyone would make money and no one lose money. You know what I'm saying? So it's very important to get the directional bias correct in a stock when you trade it. You have to get the directional bias correct. Oops, sorry. So in this case here with Delmo, Delmo was a short. It was an aggressive short out of the gate because I rated the gap and the gap rated per my golden gap rating system good enough to short. In fact, what was the rating on this? What's going on? Delmo, Delmo was 22 points. Yeah. So this was good. So out of the Delmo, we'll see what happens for the next week of June, watching very closely and very focused, but nice, nice close to the week. Big move in Delmo. And congratulations to everyone at the Stock Swish Show Live Trading Room that did it. If you would like more information, you can always reach out to me. If you want to sign up for the golden gap course, email me. I did the class once a month. You can email me at melissathestockswish.com. But normally what I'm looking to do on any given day is turn over your money. So if you risk one amount, you make one amount. If you risk one amount and make two amounts, it's fabulous. And today was one of those days where this was almost two amounts of risk and profit, which is fantastic. So the risk is the difference between the stop and the entry. And in this case here, I just wanna show you, this had, boom, more than a dollar drop where we hit it and got it. And that was a beautiful, beautiful, beautiful call. And so for example, if you're risking $500, your goal every day is to make $500. If you are taking a stock and say you take a stock and you short this and you short it with 1,000 shares and the stock drops a dollar, what's your profit? $1,000. So you see how it goes.  And this was more than a dollar. Boom. And actually this went way farther if you held it. But again, I think the fast trade is very, very important in the morning. Anyways, congratulations to everyone. Nice, solid week here. We'll see what happens next week with the market and everything else. If you're interested, email me at melissathestalkschwisch.com. Have a great day.


Hi and welcome to the session. Today we will learn about transpose of A matrix. If A given by aij bn m by n matrix then the matrix by interchanging the rows and columns of matrix A is called transpose of matrix A and the transpose of matrix A is denoted by, so symbolically if A is a matrix given by aij of order m by n then A transpose will be the matrix given by aji of order n by m. For example, for the given matrix A, A transpose will be 351-1. Now let's move on to the properties of transpose of the matrices. A matrices A and B of suitable order, the following properties are true. So first property is transpose of A transpose is equal to A itself. Second property is k into A whole transpose is equal to k into A transpose where k is any constant. A plus B whole transpose is equal to A transpose plus B transpose and the last that is for this A into B transpose is equal to B transpose into A transpose. Now our next topic is symmetric to symmetric matrices. So first of all let us see what is a symmetric matrix? A square matrix given by aij is said to be symmetric A transpose is equal to A. Symbolically we can say that the matrix A is symmetric if the matrix given by aij is equal to the matrix given by aji for all possible values of i and j. Now let's move on to skew symmetric matrix our square matrix A given by aij is said to be symmetric if A transpose is equal to minus A. Symbolically we have A is a skew symmetric matrix if the matrix given by aji is equal to the minus of the matrix given by aij for all possible values of i and j. Also all the diagonal elements of a skew symmetric matrix 0. Now let's see some results.  The second result is a square matrix can be expressed as the sum of a symmetric and a skew symmetric matrix. Let's take one example. Here we are given a matrix A and we need to express it as a sum of symmetric and skew symmetric matrix.   So let us suppose this is equal to P and this is equal to Q.  So for this first of all we need to find A transpose and this will be equal to 351 minus 1.  Now P equal to half of A plus A transpose will be equal to 333 minus 1. Now A minus A transpose will be equal to 315 minus 1 minus 351 minus 1 which is equal to 0 minus 440. So Q equal to half of A minus A transpose is equal to 0 minus 220. So let us express A as a sum of symmetric and skew symmetric matrix that is P plus Q. So this will be equal to 333 minus 1 plus 0 minus 220 where this is a skew symmetric matrix and this is a skew symmetric matrix. Now here this is a skew symmetric matrix and as we can notice that the diagonal elements of this skew symmetric matrix are all 0. With this we finish this session. Hope you must have understood all the concepts. Goodbye, take care and keep smiling.


News Update. Welcome folks. We're the Dow Industrial Straighten down now 660 Nasdaq is off for 17 S&Ps off 121 gold. Gold contract up $17.40 trading at 1908. We have silver at $22.98. Light suede crude flat $104.63 a barrel. Notes and bonds. The 10-year note down 76 trading excuse me. $119.04. 30 is off 19 at $140.20 and $King dollar. $King dollars down 647 ticks at 102.976. Euro is at 105, yen is at 129.46 and the British pound is out here trading at a price point of 129 to 125 to 1 US dollar. We can open and take a look at the S&Ps folks. Bottom line, you're going to finish out the month. Bad you haven't broken the gone after the low yet. Now this is the real danger pot. So you get an ABC structure down the spy to 410. 410 happens to be you're laying that high volume low and you're going to go over a weekend. So my take is you're going to jump the creek again this coming Monday. The NDX100, you take a look at the three cues that you have with the three cues. Bottom line, you are under the same break that we're talking about. And the three cues, the number is 318.26. Now we're 316. The very possibly can close at that. My take is that it's not going to that we're going to sell right into the close. But the bottom line is that that brings you down to a whole nother level inside of the NDX100. The NDX100 is just driving this market. So when you take a look at it, the next stop inside of the NDX is basically 303. And right now you're at 316. And there's not going to be much support at 303. The real support unfortunately comes down to 219, which would be insane. I get it, but guess what? That's where it is. We take a look at the gold contract. We finally got some juice on the gold contract. We need more volume. It's still 156,000 contracts, not a lot of contract volume. It's a stop. Okay, we came down to the breakout area rejected, lower price as it came down yesterday into that 10, 1870. 1882 is the number closed above it. That's saying guess what? It wants higher price. And finally the dollar won one day. It tested the high and it failed on the high. And what we are going to have is a failure at a monthly, but it's very close. I mean, because the bottom line, this has been a one way route on the way up. Stay right there, folks. Come right back.


Hey everybody, welcome to your mart. Hi, I'm Matt. Yeah, I'm well, thank you. How's things for you? We're going to talk about it when we get to what we've been up to this week, but I've been having a Linux week. It's not very good. Other than that, it's... Paying the Linux tax lawyer. Yeah. Well, actually what I'm paying is the ADD tax because really, I did not... Alright, so let's just jump into it. Normally, I let you go first when we talk about what we've been doing in Linux, but just let me get this off my track. I'm in a ranting mood, so you're just going to have to deal with me. So I've been using Oracle Linux for the last six months. It's my longest stay on a distro ever. I mean, it was... I actually had to go through and upgrade the kernel because I actually sat through a kernel and told us end of life. I'd never done that before. Usually, I hop every two or three months. And I was having some compositor problems, and I was like, well, you know what, maybe if I switch to a different distro, I'll get rid of the compositor problems. So I did. I started off with ArchLabs. That did not work. And then I said, you know what, screw this. I'm going to go back to Arco. I got that installed, but I couldn't get it to boot into the boot manager. Not the boot manager, but the display manager. And then you can tell I'm desperate because I installed the boot too. It only would have been worse if I had installed Mint, you know? I was on there for about four hours before I had serious AUR withdrawals because snaps are not good. I don't know if you know this, Martin, but when you open up a snap, it takes like 30 seconds for it to load. The loading time is so bad. Yeah. It's all decompression. It's essentially unzipping it, I think, in the background. Come on, man. I can understand them being a little slower, but that's just downright ridiculous. I thought maybe I'll try Flatpak the next time, but I just couldn't, you know, whatever. I'm just going to try Manjaro. I did end up getting Manjaro installed. That's what I'm using now. And I've had some experiences with Manjaro in the past. I just expect this to fail eventually after an update. Every time I install Manjaro after an update, it always fails. So I'm expecting within the next two or three days for this install to just completely not restart or something after an update. Add on top of that because, I mean, you remember when I first got this microphone set up, I spent, like, what, two or three weeks trying to get it to work?   And audio on Linux is just not good. It's still, it's so bad. I mean, it's been 30 years. Alright, so I first used Linux in 2000, probably 2001. It was open SUSE. I'm like a CDRW. And audio was bad then. It is now 20 years later and it's still bad. Alright, that's enough of my rant. So what about you? What have you done this week in Linux? I'll be delving into further customisation on my KDE desktop. I'm installing the Larte dock and various other widgets and icon sets. Obviously, I got the desktop looking terrible and it just broke during my journey down that rabbit hole. So, yeah, that was my story really. I had fun though. That was the main thing. When I first started using KDE, I broke it a lot too. It's one of those things where you just kind of have to break it in order to put it back together, I think. To be fair, it's because I was on the KDE Plasma distro, which is quite high in the rankings. But I think KDE even say, well, it's not really good enough for a daily driver. So I just went back on to FurnoS, which is fine. Nice and easy setup really. Audio is working perfectly as you can hear. Bragged that up, yeah, yeah, alright.  It's horrible, man. Come on, don't rub that in. Alright, so if you want to get in contact with us, you can do so. On Twitter at TheLinuxCast, you can follow me on Twitter. I'm at mtwbmartinsmartintwit2u. You can subscribe to all of our stuff at thelinuxcast.org. You can contact us via email at thelinuxcast.gmail.com, or like us on Facebook at facebook.com. And don't forget to subscribe to us on YouTube, where you'll see Foss and Linux related videos coming out every single day of the week, because I'm an insane person and decided to find a new hobby. It's going well and some of the stuff, some of the videos are horrible and some of them are less horrible, but they're pretty good. Anyways, make sure you do all that stuff. You can also support us on Patreon at patreon.com. TheLinuxcast. So each and every week, each of us come up with a one-on-one link each for like news-ish kind of stuff. So Martin, what link did you find for us this week? Yeah, it was Mozilla, love them or hate them recently. So they set up their VP, well they haven't set it up, they set it back up in July. The VPN service made it available for Android, iOS and Windows. And now they've released it to Linux and macOS users. They reckon it's low price. I don't know about your VPN prices on there, but I've got five books a month. Does that sit about well, about right? I think I saw one for $40 a year. Yeah, I think I pay about £32 a year with private internet access, which I do quite right. So product details, blah, blah, blah, connect five devices with one subscription. That should just be a given to be fair, if not more. So 280 plus service, 30 countries and 40 plus cities. I don't know whether you cap your VPNs over there, but I've got no bandwidth restrictions. Interestingly enough, no logging of your network activity. Fours easy to use, can be quite fast, but obviously depending where you live, if you're in cities and Trusted Mozilla name. So for a question mark by that, but there you go. A couple of against I've got is it doesn't...  Doesn't unblock US Netflix, Amazon Prime Video or Disney Plus. It's got few features, barely only custom configuration options. Encryption and IP address obfuscation. Mozilla VPN uses wire guard even and zero network activity is logged to service. So if speed and security approaches to you, the five books a month may be reasonable. My biggest problem with it is that it's not through Mozilla. They're just rebranding someone else's stuff, right? Yeah, basically, yeah. It bothers me a bit, because I mean, not only do you have to trust Mozilla, which is, you know, iffy these days, but you also trust the small bad company or whatever to... I mean, they say they don't log any network activity, but I mean, how do you really know? Well, let's wait till someone's rather naughty and they get subpoenaed for the information. We'll see exactly. I'm guessing the company's in some... based in some random country like that, but I'm guessing if they're operating services on US soil and things like that. We can only see, I mean, different places. I don't know their name any. They've said they don't log it and things like that and they've soon coughed up information to the authorities.  How about yourself? What news caught your eye this week? All right, so I've never actually used Tails before, but basically what Tails is for anybody who doesn't know is that it's a Linux distribution that lives on a USB stick and it's completely focused on security. It's kind of like the Tor browser version of Linux. It's completely... it doesn't remember any of your safe states. It's all containerized and stuff. It's very interesting, but this week it came out that they're looking to migrate their entire stack over to Wayland instead of Xorg to improve app security. And I just thought that it was interesting because I think more and more this year we're going to see Wayland kind of come to the front. Now I know Disturtube did a video today where he was poo-pooing Wayland, but I know like Steam has gone through and done a whole bunch of work to get Wayland, like Wayland gaming working, and I know that Nvidia just signed on to make Nvidia graphics drivers work better with Wayland and I know that the AMD open source drivers work fairly well with Wayland. I mean, we're seeing this kind of... It's taken 10 years, but finally we're getting some momentum into the point where Wayland seems to be kind of finally coming to the point where maybe we might be seeing it in some more mainstream distributions. It'd be interesting to see if we see something... I mean, I complain about Linux Mint being not unique enough for Ubuntu. It'd be very interesting to see them say, we're going to make Wayland default. And then all of a sudden, Linux Mint has a reason to not focus on the Debian edition. I know Debian itself has been focusing a lot on Wayland as well, so it would be interesting to see how that goes down as well. I want to try Tales because I think Tales would be kind of interesting to... Literally, it's just a Linux distribution you carry around in your pocket. You go to the library and you don't want to use Windows 98 computer or something that's at the library. You pop this in and you have a full Linux distribution that's completely containerized, so it's really interesting. I doubt Wayland... I'm sorry, carry on. I was going to say, and you saved the £5 for the VPN off of Mozilla if you're just using this. Very true. You don't have to worry about anything else. It looks very fascinating. I'm going to give it a try. Obviously, in these days and age, that scenario is not realistic because nobody goes anywhere anymore. Eventually, maybe we'll be able to go out to the library and do that kind of stuff. Yeah, but it's nice as well if you literally... some people obviously just stick to the one browser and things like that, but it may well be a case that you don't want to see these adverts popping up or anything. They're ad blockers and everything like that. Or use Brave for whatever. But yeah, at the end of the day, if you just want to go shopping and do the odd thing online without just looking over your shoulder, whether it's obviously for the correct reasons, I mean, everyone's got that right, really. Yeah, it does look good. I must admit, I've never used it really, I've used something similar. Obviously, if you do go on the tour network, obviously your internet is a lot slower because you're hopping, you're basically bridges and hopping from internet to internet.  Yeah, like you say, it's ideal. Just pop it in your pocket. And if you're on the PCs, it's not your own. You know, it's secure in it. It's volatile as soon as you pull it out or leave it behind. Yeah, it's just one of those things. I know there's other alternatives out there, something like, I think there's something called like CubesOS or something that's kind of similar to this. I know, I listened to a podcast about that before. Anyway, so let's move on to the main topic. So the main topic this week is something that we've covered before, I think, back when Ricky and I were doing the podcast. But I just thought we'd kind of do it and talk about it a little bit. GTK versus QT. Now, recently, GTK 4.0 was, I believe it was either finalized or went into beta or something. So we're looking at a kind of a re-emergence of the GTK versus QT because QT6 is also going to be coming up in the next year or so. So when you're installing a desktop environment, a lot of times, really what you're choosing between is GTK and QT.  And I've always been a big KDE guy. So I was wondering if there's a reason why you and I seem to kind of go towards the design language of QT instead of something like GTK, which is about the gnome and, you know, budgie and all those different design environments we rely on. So what are your thoughts on this? Well, it's simple, really, in my mind. So I mean, you've just got to name a couple of the desktops. KDE, Plasma, Deepin, Ubuntu, Kylin. Use GTK. Sorry, use QT. Obviously, KDE does use, I think, a bit of GTK also. But I've got that totally the wrong way. No, that's right, isn't it? Yeah, QT. Yeah, KDE, Plasma. Yeah, there's some GTK stuff in there, yeah. Yeah, I mean, KDE uses a bit of both, obviously. But, yeah, just straight out of the box. It just looks fine, I mean. As you know, you can theme stuff to all you want. I mean, Covantum as well, you can use QT to get it themed and stuff like that. I'm sure you could do it with GTK, but I mean, GTK, I mean, some of the desktop environments use that, so we've got like Budgie, Cinnamon, Mate, XFCE, Pantheon doesn't look too bad, but then again, they're still quite heavily themed anyway, but yeah, I'm quite happy with QT. I mean, there was talk of memory, one's more memory, one's less memory, but I'd like to think that, but they're probably owning all the creases out there as we advance on through. So my takeaway is kind of similar in that QT seems to be much easier to theme. Maybe that's just more of a KDE thing, that they've just kind of built that into their desktop environment, but it seems that they, but because of the way the framework is built or whatever, KDE's been allowed to go through and build in theming, which is something that GNOME and all these other things kind of have to hack on to the top of the framework in order to get it to work. So I mean, like if you're using GNOME, and we talked about this, I think it was even last week where we're talking about theming. If you use GNOME, the theming is kind of like set on top of it and it's kind of really hacky, and GNOME has gone through and said, you know, it's not that great and we're going to tear it out and all this stuff, whereas the cute guys and KDE specifically have kind of built it in stuff, so really it's kind of really all about theming, but from a, if you look at it from like a developer standpoint, now I get to remember I'm not a developer or a designer, like even like a minuscule a little bit. Like negative. If it was possible to be an anti-developer, that would be me. But from everything that I've read, GTK seems to be easier to code for, mostly because the framework is more, I guess I'm going to say simple, like the tools that they use to design their apps and to deal with outputting the appearance of their apps seem to be more refined and simplistic than what you find on the cute end. Whether or not that's true, like I said, I don't know, I'm not, I have any experience with those things, it's just things that I've read on the internet, so of course it's going to be true. Oh, of course. Yeah, yeah, right. So, really when I use a desktop environment, I always preferred the KDE that uses cute, mostly because of the things and things, but I've also noticed that a lot of the times KDE and the cute stuff is faster and uses less resources than GTK. Now, I know a lot of people say it's the other way around. And I also know that a lot of people say that it's GNOME that gives GTK a bad name because there's a lot of GTK desktop environments where Mate uses it and it's fast. The Pantheon uses it and it's fast and Cinnamon uses it and it's fast. So maybe it's just GNOME that gives it a bad name, but every time I use it, it seems like it's a little bit slower than what I experienced on the KDE side. Whether or not that's quantifiable and you can go say, you know, this uses 200 megs of RAMs less or whatever, I don't know about all that. It's just feel-wise, it feels that the cute stuff is quicker. Yeah, well, I mean, QT with the desktop environments like UKUI, LXQT, I mean, that's one of the lightest ones you can get, I think, if you're not going to go for stuff like OpenBox and things like that. LXQT definitely went up on my old laptop from 2009 to get that up and running. I mean, I didn't put anything much heavier on it, but like I say, I mean, QT's supposed to have the least memory, but I think as we go down the line and the years that the amount of processing speed that we're getting, I don't think... it's probably going to be marginal. No, with the RAM comparisons. I mean, obviously, things like that we've all pulled up an app that we've got used to in a different history on it, whether it's GTK or QT and I opened it up and just thought, oh my God, that looks absolutely horrible. It's usually QT. I pulled something else up and I thought, oh my God, what's going on here? Before I even knew about all the theming and different things like that, it's just a case of, well, that didn't look like that before. Is it an old version? But obviously it was GTK or QT, whichever and I just didn't have it set up.  It's infinite, isn't it? What you can do with theming and stuff like that. Well, and it's not as if you're on GNOME, you can't install a Qt program or go the other way around. Yeah. That's the good thing about Linux, although they use competing frameworks or whatever. You can still install a GTK app on KDE and it works just fine because KDE has gone through and done the work to make that stuff kind of look... Yeah, it looks like you followed it up, haven't it? Yeah. And that's gotten way better in the last few years because it used to be the case. I mean, you could still use them. They didn't have all the features that you would experience if you used a GTK app on a GTK supported desktop environment. We don't have to really get into this, but it always just seems to me, and this is just me beating on GNOME again, but it always seems like if you want to go to a forward-leaning desktop environment, it's always going to be KDE because they're always developing stuff, they're always coming through and refining things and making things better. GNOME just seems to stay the same.  That may not even be true anymore because the GNOME 40s looks like it's finally going to get a design refresh, which is good. I don't know, maybe we're coming to a point where the Linux desktop is going to be exciting again or you could just use a window manager like I do. All right, let's jump into the apps of the week. You have an app of the week for us. Yeah, so I've got quite RSS, quite RSS, so it's written in C++ and QT. It's a great little RSS feed reader. It's clean, easy to use interface with all the usual features including tags, ad block, share button if you want to send it to Twitter, Reddit, or Facebook if that's your jam if people bother with Facebook nowadays. But yes, really good. It's just, I mean, it's been a while since I've done an RSS feeder and I forgot how actual good they are just for condensing your news down into literally a readable format instead of just opening up a folder with your various news or open up your tabs or just flick through one. But yeah, it's really nice little RSS feed reader with all the main features that you need and it's quite recommended. How about yourself? What have you got on us for us this week? All right, so as everybody knows, Mozilla came out and pretty much pissed off everybody by saying they wanted to determine truth on the internet or whatever. I mean, I did a video on it. I think everybody, every Linux YouTuber did a video on it. So I've been looking for something to switch to. I'm still using Firefox as my main one because it's like the only alternative unless you want to use Chrome. I looked at Brave. I haven't been impressed with Brave. It would probably be the one that I'll end up switching to. But if you're into keyboard-centric navigation, Qt browser probably is the one that you might want to go with. Especially if you don't do syncing between your phone and your desktop. I happen to do those things, so Qt browsers might not be the one that I switched to. But I've been using it quite a bit. And basically what this is, is just a frame with a web page in it. And you do all of your navigation with your keyboard, the VIM keys and key bindings and stuff like that. You're not supposed to use your mouse at all.  It's of the one of the browsers that work like this. So there's a few of them. There's like surf and there's the min browser. And there's the, I think there's one called the Vi browser, VIM browser or something. Those are all fairly slow. Q browser, it's not as fast as Firefox or Chrome, but it's not something where you'll say, like five minutes later, YouTube still has not loaded. This one was really fairly snappy. It loads faster than snaps, I'm just saying. So yeah, Q browser is mine. And it's still being developed, unlike some of the other ones that I just listed. So yeah, that is mine. So that was a really short episode, but it was really good. I think most people, Martin, really don't care about GTK versus Q, but it's kind of like a nerdy little topic that we just talked about. Yeah. I mean, should we pad it out a bit and just talk about browsers or Brave mode as well? Is that what you use as Brave? What browser do you use? I'm just curious. Well, to be fair, it's going to give you Q-dust. I'm not giving us a command line app this week. Oh, Q browser. It seems an absolute nightmare. It's going through your feed or your YouTube subscriptions with your keyboard shortcuts clicking on it. To me, it seems a torture. See, I go through on every browser that I do and install something called Vemkeys and it allows me to navigate my browser with a keyboard. So I do that anyway. So I'm just used to it. I think it comes down to the using of a window manager. Once you switch to a window manager, you're kind of prodded into using your keyboard to navigate everywhere. And you've got them all in your memory. Yeah. And while I still do, I still have a problem where sometimes I use my mouse, like the muscle memory. Every once in a while, but most of the time I'm just using my keyboard and while I wouldn't say it's faster, it's just different. It's kind of like the difference between a controller and a keyboard in a game. One's not necessarily better than the other. It's just which one you're more used to. Because I'm not a gamer at all. I'm more of a developer than I am a gamer. I'm just saying that. And we know how much of a developer I am, which is negative. But I can play with both. It doesn't bother me at all because I'm not a good gamer. Every once in a while I'll play. Like yesterday I subscribed to Google Stadia and tried to play in Firefox, did you? Like Google Stadia doesn't play in Firefox, so I had to download Chromium for like five seconds. Chromium. Yeah. Yeah. And that did not last long because at least on Arch, or on ArchBase distros, and on whatever subsystem Manjaro uses to manage preferred applications, I'm assuming it's probably like Xfce or something. I downloaded Chromium and it automatically set itself as the default browser. Like, come on man, that's horrible. Every day it goes by I hit Google a little bit more. And I can explain to you really quickly. I don't know if you watched this video but I did one of the videos I did. I said the word Google at the end of it and the Google home I have in my room and my phone started listening. And guess what? About 30 seconds ago I said the word Google, my phone's sitting here listening to me. Like right now.  So yeah, I've been... Yeah, I've turned that off on my phone. The OK Google... Oh, sorry, if anyone's got it on. OK, geez. But the problem is, I think, with the Stadia and the actual controllers, I've saw a couple of videos on how to actually turn the microphone off. And I think it consists of using a Dremel to actually get in. Because I think it is on by default. Much like your device is anyway. But it's a case of you want just a switch, whether it's hardware or software, just to flick it across just to not listen. It's not that you're going up to anything, you just don't want stuff like this being transferred across. Just on the other side of Brave, I mean, I use Brave as quite happy.  So I'd went on and I thought, let's get this into cryptocurrency and get these bat tokens. I'll get this and I'll get that. I think after about two weeks, I've made about $2. And I just thought, sod that for the amount of time. Yes, I'll give it its props. It is good at blocking ads, I must admit. I've got ad blockers on Firefox and silly things like eBay. You've always got the odd silly ad down the bottom unless you delve a bit further and maybe get a couple more. But Brave just takes everything away. I think there's been talk sometimes of replacing the odd ad, maybe I'm making that up. But from my experience, in terms of blocking ads and stuff like that, just so you can actually read a webpage without having copious amounts of clutter to scroll past. Yeah, I would thumbs up to Brave till I find something else. There's that many out there and yeah, I think a lot of people have just had enough of, I think there's a bit of an exodus from Firefox. Yeah, I know there definitely is.  Firefox is completely open source. Way more open source than Chromium is because Chromium, I mean, sure Chromium is open source but it still relies on a whole bunch of stuff from Google. And while there is a version of Firefox or Chromium out there that's apparently un-Googled or whatever, they still had to go through and do that process. I wonder why there's not more forks of Firefox out there. I found two. I mean, I know there's Pale Moon but Pale Moon looks like it was developed for Windows 3.1.  I'm not using this. But the two that I've tried or tried to try, I guess, is LibreWolf and WaterFox. And the WaterFox one, I couldn't get to build at all. I don't know if it's not being developed or maybe it's just some weird quirk of the way Arch Linux tries to build things. I don't know. And LibreFox will not remember cookies at all. So I understand that cookies are bad and evil and all this stuff and that they use trying to make sure everybody knows they're being tracked and stuff. And I'm one of those people like, I don't want to have to re-sign into Google every time I want to go to YouTube. I also don't want to re-sign into Facebook or Twitter or any of those things. I want to remember once I've signed in that I've signed in. I know that's probably, that's not the most secure, false way to do things. I want that to happen because it's convenient. I use these long complicated passwords. I don't want to have to type it in every time I go through and go to a website, whether it's a good website or a bad website, it doesn't matter. So that was, I usually read well for about, I don't know, two hours. And I just got completely sick of it not remembering anything because it didn't even remember like zoom level.  And because their text or whatever is like five point, and you navigate away and you come back later to read another article or something, it should remember that you've zoomed in. I mean, that's just, but LibreWolf doesn't because it doesn't want to, it doesn't want to store that data because it's completely privacy focused.  So I'm still using Firefox. Yeah. And me, I've been exporting my, exported all my bookmarks last night and transferred them over to Brave. It's quite easy. Did that to be fair. I think the problem with your Firefox for, because these are security updates and things like that. Because I mean, obviously Mozilla though people are forking it and things like that.  So I mean, the main thing is the security updates. I mean, it depends on your value, your security really.  And if you're having two, well, one month, two months out of date security settings. It's not very good really.  Brilliant sync, things like that to your phone. I mean, I'm currently looking where I've got Brave. Vivaldi's quite good. I quite enjoy that. That's got to, have you ever used Vivaldi at all? I have used Vivaldi and I would probably switch to Vivaldi because I like their user interface. I would switch to them if they were open source. And I know it's stupid just not to use something that's, you know, because it's not open source, but I just kind of want my browser to be open source, completely open source. I'll probably give it another try because I do like the way their interface, at least on the desktop. Do you know if their mobile app now will sync tabs? Because the last time I tried it, I couldn't sync tabs between the desktop and the mobile. And that's really the one feature I need is something where I can switch because I always do that. It's like every all time. Yeah. I mean, it was working perfect for me. Whether I'd cleared my remote data on my computer and it kept on my phone. So I mean, I've got to look at it a bit deeper in that, but I mean, interested you enjoyed Vivaldi because I mean, obviously you like to do things a hard way because when I started Vivaldi, I was like, oh my God, this is so busy and there's that amount of options.  I've updated since. So I mean, Vivaldi is a heavy browser. Let's face it. It is. I mean, it's got so many features to it. I mean, I don't know about in the States, but over here, if you get your shopping delivered, you literally have to sit there and just watch your screen and wait for a slot to appear with Vivaldi. Let me just pull Vivaldi up. This is great radio, isn't it? I just want to get the proper name of it. You see, Internet Vivaldi. What is it called? So I mean, you can pin essentially mobile tabs to the left of your screen. So you can have your main page that you're looking at. And on the left is essentially your mobile screen. So you can leave things running on there. You can stick YouTube on there while you're doing a work. Yeah. I know you can have picture-in-picture. I've tried it with Plex, just having it running in there. Or if you're keeping an eye on sports course while you're working away.  There's untold features. If you go in there. But that was a really good feature. I did like just pin in my a web-based version of a mobile web page just on your screen. And you could just carry on and just have that to the left or right or up or down, whichever way you want it. But yeah, I did quite like the Vivaldi.  I mean, I'd like to stick the probably fixer now and that was possibly more user error.  But yeah, give it a spin. Yeah, this is going to seem superficial, but I liked it because I could put the tabs on the bottom. I like customizing the... When I'm going to use a GUI interface, I want to be able to customize it. That's the reason why I like Firefox because I can go through and change the whole thing because it's all controlled through CSS. Anyways, that was a nice little chat about browsers. We should definitely talk about that a little bit more. But I think we should call this a day. All the contact information there was at the front, but just remember to subscribe to the YouTube channel. We really do appreciate any of those support where you give us there. Our podcast is available on YouTube. It's also available on Spotify and Apple iTunes and Pocket Casts and pretty much... I think we're available on like 10 or 12 different places where you can subscribe. We are also... There's an open source podcast player. I don't remember what the name of it is, but we are in there as well. I also saw that we were featured on the Spotify app the other day. So, there you go. Worth Linux Cast ever. Yeah. Hey, you want to know what? It helps setting the mint users. That's what it is. Well, hey, you want to know what?  It's okay. Exactly. I don't care if you hate me, as long as you're watching my videos and listening to my podcasts. That's all that matters. Anyways, our next topic, just real quick, is going to be... I can never remember this if I had this up. We're going to talk about firewalls and security. Do you need them? Do you want them? That's what we're going to talk about. We'll see you next week with that topic. See you next week, guys.