The following is a creep I passed that never appeared on Slash X Slash. YouTube user creep I passed it to bulkloaded the whole tape after having it sent to him. But it was taken down for an unknown reason. Howdy. One of my favorite formats, being one of the highest quality ones. The sheer thought on it makes me excited. Okay, maybe that's not true, but when I'm choosing my video format to make movies and, this is what I will always pick. Spongebob is a great cartoon, but sometimes it's a little childish. But half the time, it's funny. My friends always criticize me for enjoying such a childish cartoon, but who cares what they think? They may not like it, but they can't stop me from watching it. Something occurred two years ago that lowered my trust for any point out of formats, and stopped me from enjoying Spongebob Square Opens as much. This is my complete story. What you are about to read is not made up in any way, and there are no extra things added into this that never happened. This is it. I was at a garage sale one day, when someone lost selling a box of old EHS tapes. I thought this seemed interesting, so I dotted four pounds ten. I asked the man if I could have an old trolley or something to carry the box in, and sure enough, he was prepared. Suddenly, he looked as if he had remembered something, and asked if I would like a EHS player and some old cassettes for free. This was clearly an offer I could not refuse, so being myself, I took the lot. He seemed rather relieved to have got rid of them. I popped the boxes in my car, put the trolley next to the parking lot entrance, and drove off home through the rain. When I got home, my friend was waiting at the door for me. He asked where I'd been and I simply told him that I'd been to a car boot sale. I allowed him inside, and put the boxes in the living room. My friend said he was going to put them in the attic, but I stopped him and told him only to put the cassettes in the attic. While he was sorting things out, I made some popcorn. I found a simple tape that was peculiar with marker and on the front that read Mercy Point Heavy. I plugged in the EHS player, popped in the tape and we both started to watch. The videos started off with pure static. I couldn't help but notice that this could not be an anti-format due to the terrible quality, but still, it was easy to make out the image. For around a second, the words Mercy Point Heavy appeared in scream. I turned around to look at my friend. He looked back in terror. It went back to another few seconds of static. Then the opening credits played, but it a threshold effect. This was getting very disturbing. A second of the end of the credits was cut by some more static. Then a segment of the credits was played at the same effect, but in reverse. I wanted to stop, but somehow I felt that I had to keep watching. Then a shot of Squidward, but his eyes were bloody. A strange effect appeared in his face. His face seemed more realistic to say the least, but I can't describe it any better. The screen cut to black for a split second, before a satanic walk cycle of a happy SpongeBob appeared. A normal walk cycle now appeared in scream, but SpongeBob lost cost, but still smiling. Then a demonic angry Squidward appeared. He was in his home. I turned around to my friend. Tears were falling from his eyes. I felt sorry for him, having to watch his. The words help appeared in the screen for a split second, before the episode cutting to a horrifying image of Squidward's eyes. Everything else seeming blacked out. This stayed in the screen for a while. After that, Squidward seemed to be walking. I may be wrong, but it looked a bit like walking. You couldn't make out his face. It was just white. That in our dot i dot b message appeared in screen for a split second of a split second. It reared that Squidward had committed suicide. Could this be because of SpongeBob? I don't know. My friend was sobbing. A quick lightened hip-hopper flashed up. Then another image of Squidward. Next up, something flashed on screen that made my eyes widen. A message appeared in screen. It reared. Nickelodeon SpongeBob Square opened episode minus 0.000 Mercy. Then the worst sound. The worst sound that could possibly occur. Screaming. It cut to black. Then finally, screaming. I looked at the EHS player. Only 1 minute and 48 seconds. This experience has haunted me forever, and I will bring more information as soon as possible. Thank you. I have copied the EHS file into a low-quality video file in my computer, and I will send it off to a scary channel on YouTube so they can publish the video. Thanks. August 28, 2011, I sent the tape to a YouTube user creep I passed a tube. The bad news is that for some reason the tape was taken down due to copyright reasons. I'll try finding a way around it like uploading it on Vimeo.


Clay is mud, natural mud from the earth. It's not made with flour and it's not made with oil. It's just mud, a very special mud. What makes clay special is it's sticky. It sticks together, it sticks to itself. When you move it around, it stays where you put it. And when it dries, it gets very hard. Clay is often fired, meaning it's put in a kiln or an oven made just for cooking clay. And it's taken to temperatures as hot as a volcano. When it comes out of the kiln, it's no longer mud but has turned to stone, mud to stone or clay to pottery. Ancient man used clay for pottery and art. We still use clay today. Cups and bowls and plates are still made from clay. My coffee cup is made from clay. Your dinner plate is most likely made from clay. Pieces of art are still sculpted from clay. Clay is a common thread that ties man together from his earliest beginnings to now. People have been using clay and making pottery since we've been people. All over the world, ancient civilizations used clay. Pottery played an important role in many cultures. China, Africa, Peru and Greece, just name a few, all had pottery as a major part of their history. At the same time they were making pottery, the people wanted to use clay for art. They used the same process they used to make the pottery to make decorative pieces or sculptures. If it's functional like cups and bowls and plates, it's pottery. If it's decorative, it's sculpture.


We're here in Shamar Sheikh in Egypt and with the Radio Communication Assembly prior to the World Radio Communication Conference. I'm very pleased to be joining the studio today, Mr Walid Sami, who is a Senior Project Manager for Technology and Innovation for EBU. Walid, welcome to the studio. Thank you. Now, I wanted to start off by talking to you a little bit about these two events, the Radio Communication Assembly and the World Radio Communication Conference. It's actually going over a period of five weeks here in Shamar Sheikh. Why are these conferences important? Well, the EBU first of all is partner of the ITU since the creation of the ITU sector, the ITU Radio Communication sector. And the engineers of the EBU participate actively in the study groups of the ITUR. We contribute to the work of the study groups and we also are involved in the management of some of the groups. We occupy some positions like a chairman of study groups or chairman of working parties or sub-working parties and sub-working groups and so on. So this is an ongoing work since several years. So we are naturally concerned and interested in these two events. Now, these two events have different objectives, of course. So the RA deals with the structure and the working methods of the study groups. And the WRC is about updating and revising the radio regulations. Radio regulations about spectrum and broadcasters are concerned also with spectrum. We use spectrum for broadcasting on terrestrial. We are concerned with spectrum on satellite as well for either our services for distribution or for contribution as well. So spectrum is a major subject for us. So these are the obvious reasons for which we are interested in participating and contributing to these two events. And what do you hope will be the outcomes of these two events? Okay, the RA as I said is about working methods. So we would like to be sure and make sure that the study group 6 which is the broadcasting, let's say group where the community of broadcasters gather and contribute will still have the good conditions to continue working and contributing to the development of the broadcasting industry worldwide. For the WRC, although we don't have an agenda item specifically related to the spectrum of broadcasters, however we have one important subject which is the preparation of the next World Radio Communication Conference where we know that already an agenda item is foreseen for the spectrum used by broadcasters. And we want to make sure that all the options are still open for the discussion at this next WRC in order to be sure that spectrum is secured for the usage by the broadcasters and the development of the broadcasting systems and services. Members that you represent of course. And I just wanted to ask you mentioned study groups. How important is the work of ITU study groups in terms of the resolutions and the studies and the reports etc. for the broadcasting industry? Well, we have two main areas of work. We have the production side and we have the distribution side. And in both areas the work and the outcome of the study groups is important. For the production side we have recommendations which are really respected by the manufacturers. They are followed by the manufacturers and they are followed by the broadcasters as well. So I can mention the recommendations, some historical recommendations about the high definition television and recently about the new generation audio enhanced audio systems. So these recommendations have really very good weight in the industry. So this is one example. For the distribution part, the new systems for distribution like the digital systems, they are described in the ITU recommendations and reports. And this gives them sort of let's say weight in the whole world. So not necessarily in Europe, although we are European broadcasting union, but the outcome will be used by all broadcasters in the world. So these are a few examples, but definitely one big outcome is the radio regulations of course. So it's not only the recommendations and reports, but also the impact of these recommendations and reports on the decisions of allocating frequencies. Very briefly, we were talking about before the length of the process of these conferences all amalgamated. We're talking about approximately six weeks in total at the end of the meeting. For all intents and purposes, of course, this is a very, very important decision being taken here, but for people on the outside, they might think this is an extremely lengthy process. Why does it take so long? Why is it so long? Well, this is a question that I had from my relatives saying that what is that conference that lasts for six weeks or something. But when I explain that thousands of delegates come and the work and the outcome is a revision of usage of frequencies worldwide with interests and sometimes completely conflictual interests between countries, between administrations, that requires first of all four years of preparation with, as I said, positions that could be completely conflictual. And then in these four weeks, let's talk about the WRC itself. The aim is to really get the positions close enough to get a consensus because the work of the ITU is based on the consensus, not on voting, whatever. So if it was voting, I think it would take much less time, much shorter time. But because of the principle of work at the ITU, it needs this time and sometimes it's not enough. And I know, I remember in some WRCs, that some nights are used fully, so 24-hour work on some subjects when they are really, really difficult to solve. Let's hope that there's consensus on every degree and on every point and that you have a very good set of few weeks here. But thank you very much for joining us in the studio and very good luck for the rest of the conference. It's my pleasure. Thank you very much. Thank you.


Hey stampers, welcome to another week of Watch It Weekly Wednesday. I'm Aubrey, part of the Stampin' Jill creative team. And today I'm excited to share with you a stamp set and punch from the mini catalog. This is the stamp set that I'm working with. The Hello Ladybug set, as well as the Ladybug punch. These are so fun and they coordinate and go together so well. The Ladybug stamp set is so cute and I love it used as a Ladybug. Let me show you some samples with that that we've come up with. So cute. So here's one just with the stamping. The punch isn't used there. This one is just with that cute daisy flower. So cute. Here's one with the punches. So you can see it just lines up and is so cute. And this one actually I used the wings as leaves as well. Another one. Here's one she's taking off and flying. And a shaker card. It's so much fun to be used as a Ladybug obviously because that's what it's meant to be used as. But I wanted to come up with some other ways that you could use this punch and stamp set in more ways than just the Ladybug. So I wanted to show you some ideas doing that. First I'm going to stamp with you. So we're going to make a card all together. We're going to start with our piece of basic white here. And these are the polka dots that normally would go on our Ladybug. But I'm going to use them to create a background on this card. Because I think when you can have a stamp that does multiple things for you, you just can't go wrong. So I'm just going to take this and just stamp all over the back of this card stock. And just kind of create a cute little polka dot background. I like to kind of move my stamp all around so I'm getting all the different ways that it can go just like that. Kind of cute. It kind of looks like a little Dalmatian a little bit. And then I'm going to stamp my saying, we'll get this little bit of stamping done. You can bug me any time. The nice thing about this one is that it's photo polymer.  You can bug me any time. OK, now I want to create something that's not a Ladybug. So we're going to make a bumblebee. So I have some black card stock and just a little strip of yellow card stock. And we're just going to take some stamp and seal and adhere this strip just along this black card stock in three straight lines. And then snip off the extra. So one there, one here. I don't want them too far apart. And then one more, just like that. OK, and then we're going to take our Ladybug punch and I'm going to, well, you can see it's not going to go this way. I want to punch it this way. So I'm just going to trim my black piece here down so that it'll fit in there. It all works out. OK, just like that.   OK. And then our bumblebee needs some wings. So I'm going to use some of our supple shimmer paper, the glimmer paper that's in the mini catalog, the blue piece. And I'm just going to punch out some little bumblebee wings just like that. OK, now let's put our card together. So we're going to adhere down our white background piece that we created just in the center of our card. And then we're going to adhere our saying onto a piece of pool party as well. And then I've already cut out a circle from our circle's dies in the pale papaya. And we'll just put that on top of there. And let me bring in the finished card here. You can see how cute that's going to turn out. So much fun. And you have a cute little bumblebee instead of a ladybug. So let me show you two other card ideas that I've made using different designs using the ladybug punch. OK, so here's one with a butterfly. You can see I just used the wings and created butterfly wings. And I still used the little antenna in the back. And then we have some flowers.  So cute. The Hello Ladybug stamp set and the Ladybug punch are so versatile. And there's so many different options of things you can make with it. I've had so much fun playing with this, and I hope that you do too. We've shared on our blog stampinjill.com some of these other ideas. So if you want to go and check them out there, you should do that. If you have any questions, let us know. Thanks so much for watching, and we'll see you next week for another Watch It Weekly Wednesday.


Hello and welcome to the NPTEL course on an Introduction to Programming through C++. I am Abhiram Ranade and in today's lecture sequence I am going to be talking about structures. So let us take a look at where we are in the course. So you have really learned enough to write essentially any program. So you have learned basic control statements, you have learned functions, you have learned arrays and in this lecture we are going to learn language features that will make writing programs more convenient, safer and modular. These terms may not mean anything to you right now but they will become clearer as we proceed. So let me begin with a difficulty. So if you are writing a large program then it will have lots of variables and just managing all the variables is often a bit tiring. It is like you have lots of papers strewn over the table and you do not know how many papers you have which is what you called which variable, all such things and on a table we can bring some neatness by putting related papers into files. So that way we have groups and we know what we can sort of roughly know what is in which group and that helps us figure out what all we have. So an interesting question is could we do something like that with variables and that in fact is the solution that structures gives us and that is the main topic of this lecture. So here are the high level ideas. Most entities we deal with in programming have lots of attributes. If your program is about simulating movement of stars then each star has a position, capacity, mass, if our program is about managing books in a library then each book has an author, library number, who has borrowed it of course the title and the key idea in structures is to collect together all information about an entity into a group or you might even think of it as a super variable. And a super variable is called a structure. So here is the outline for this lecture. So we are going to start by talking about structures. So we will talk about the basic facilities that C++ provides to define structures and by the way the structures are inherited from the C language. We will also talk about operations that can be performed on structures and also lots of examples. So a very high level overview, a structure is nothing but a collection of variables and the term member is also used. The members of a structure are the variables in the collection. So a structure can be thought of as a super variable and it denotes all the memory used for all the members. Each structure has a name, the name refers to the super variable or in other words the name refers to the region of memory in which all the members are present. So it refers to the entire collection. Each structure also has a type and the type defines what variables there will be in the collection. So let us talk about structure types first. You can define a structure type for each type of entity that you want to represent on the computer and these types are what might be called programmer defined types. For example to represent books you can define a book structure type. When you define a structure type you must say what variables each structure of that type will contain. So continuing the example, if you define a structure or structure type to represent books you may wish to have variables to store the name of the book, its price and other attributes. So here is how you define a structure type. The general form is the keyword struct followed by the name of the structure type that you are defining. Then it consists of several variables or members. So for each member you first have to specify the type, the type of that member and then you have to give it a name and that is it. So it ends with a brace and usually braces do not have semicolons as we have seen them so far but here there is a semicolon. And here is an example of a specific structure type that we might define consistent with this general form. So here is a type for storing data about books. So we are going to call that structure type book capital B and then it will have members. One member is a title which is a character array. So members can be arrays or members can be just plain variables. And then there is another member which is price and it is of type double. You could have more but let us say we just have these two. So as I said earlier a structure type is a user defined data type and it is really similar to int, char, double which are the primitive data types. And the structure type and member names can be any identifiers. So how do you create a structure of a type that you have defined earlier? So we just defined a structure type book. So if you want to create a structure of that type we just simply write book PQ. So this creates two structures PQ of type book. Each created structure has all members defined in the structure type definition. So at this point we have actually allocated memory. When we defined a structure type we did not allocate memory. We just said that look here is sort of the format using which you can create structures and the structures actually cause variables to be created and memory to be allocated. Now member x of structure y can be accessed by writing y dot x. So since we have a structure P and on the last slide we said that structure type book has members title and price. We can get to the price member of P by writing P dot price. And this statement is storing 399 into that member. Now we can print it if you wish. So if we write C out P dot title or C out P dot price whatever the contents of these members or these member variables are will be printed. So P dot title is presumably the name of the book represented by the structure P and so that will get printed. Of course we will have to assign it first and so once it is assigned we can print it out in this manner. So what have we discussed? We have discussed how to create structure types and then we discussed creating variables and instances of an already created structure type. Next we are going to discuss operations on structures but let us take a quick break.


Right then. Thank you very much. Okay, so I'm Richard Brown from the OpenSUSA project. This is actually my second talk of the day on this topic, which is kind of fun. I was really looking forward to coming to the first session in this room because it was meant to be, you know, our distribution is still relevant in the container world, but I was too busy in the container track telling them how distributions are still relevant in the container world. So this is kind of the follow-on from that of what we're doing with OpenSUSA, what we're doing with containers, why we're doing it. But, you know, at the beginning, you know, starting really from the basis level, as distributions, you know, we are here to distribute software, and it doesn't necessarily matter how. You know, people might call it an app, we might call it a package, it might be a service, it might be a container. You know, when I started, you know, software was distributed on one of these on a cassette tape. And, you know, I'm getting a bit older, and I'm realizing, you know, a heck of a lot of the assumptions that I carry with my open source stuff come from the fact that this is where I started. You know, playing with this, learning how to code basic, learning, you know, then having an IBM PC, learning how all these little bits and pieces work. But that's not the world we're living in these days. You know, everybody has, and might have started on all of these interconnected devices. If we're lucky, they might know about these things called servers. But, you know, there's an entire generation of developers these days who have just been born with this cloud thing of the internet where, you know, they can go to some web page and start doing stuff. And, you know, that's not necessarily a bad thing. They don't necessarily need to know all of that stuff going on underneath. You know, but ultimately everything's getting more interconnected. It also means everything's getting more and more complicated. So actually that stuff down in the deep plumbing actually matters even more than it ever did before. Just nobody wants to worry about it. And when you get all these nice complicated interconnected messes, you know, what's the first thing we as developers all do? We make the whole thing modular, which then causes more connections because we've made everything modular. But this isn't necessarily a new thing.  But, you know, this is something we were doing back in the day when we started packaging.   And Kubernetes is releasing every three months. And SaltSnack is releasing every three to six months.  You know, there's no release schedule. It's just something new whenever it's ready. And so, you know, as a Linux distribution, we're trying to take all of this stuff, condense it down to something that someone can actually use because we're not expecting everybody to just pull down Git repos and build them themselves and, you know, run it themselves. And it has to be, you know, coherent, consistent, and, you know, operational for the purposes it was built for. And when you start looking at the container world and the cloud world, you know, not just on that one machine in your room, you know, or even that couple of servers, you know, it needs to work at scale for large systems, for large deployments, with thousands of users. And it needs to be totally and utterly stable. But it needs to have the latest of everything because that's also what users are expecting. You know, they've got used to having new software delivered quickly with new features. Not just us Geeks at Fastem where, you know, we like all this upstream stuff, but, you know, the expectation is something isn't going to necessarily be the same as it was for 10 years.  And so the way people are working with their computers is also different. You know, my Commodore 64 was my pet. My first IBM PC was a pet. I cared for it. I packaged everything on there, you know, I installed my packages on there really carefully. And there's nothing wrong with that. That use case is still valid. People are still thinking in that way and using it that way.  They don't know how to deal with this. They've never been exposed to it in the same way that some of us have. And this is where sort of the pet versus the cat in the hatch you really come from.   But when you actually extrapolate it and think about it more, you know, which is more important for the world at large? You know, which one has a bigger impact on the most people?   So the OS that is running your cattle servers is more important than the old OS that was running your little one server.    You know, they just want their web service to work. They just want to deploy their microservice and move on and have the OS do its thing out of the way so they don't have to worry about it.  They shouldn't need to worry about the OS. But they want everything even faster. A lot of these themes, I was here years ago talking about in a slightly different context. Because, you know, in OpenSUSE we have tumbleweed and tumbleweed does try to address many of these issues by being sort of the traditional Linux distribution iterating incredibly quickly with good testing and good building. But it's only part of the story. It works really, really well for, you know, effectively people thinking like we think. But it doesn't really solve the problems that you see if you're doing everything with containers, with, you know, on clouds and working that way.  Yeah. So, you know, I've started looking at this problem and trying to figure out, you know, yeah, what is the root to the solution? And despite the fact that, you know, fundamentally deep in my heart I still know as a distro guy they're wrong. They are not built correctly. You know, containers do bring a huge amount of opportunity to actually solving this problem.  They may have their flaws because, you know, the way they're bundling things together, the way they're isolating things, you know, aren't necessarily well engineered as a traditional distribution package, but they do give a huge amount of freedom to users to just be able to install what they want to developers to just be able to deploy what they want without having to have to engage quite so much with distributions.   Maybe we have a chance to actually lower the scope of the distribution to something that's more manageable rather than trying to please everybody with everything and come up with a solution that can just, you know, deal with what we need to deal with and basically leave everything else to be everybody else's problem, you know, just leave it to the container framework, leave it to the application framework to, you know, deal with the user space stuff and we're just dealing with the plumbing which is our core competence. It's our main strength. So, you know, looking at building the community distro for this new age. Inside OpenSUSA we started looking at this problem, kind of, yeah, pretty much the route I've just taken you in the cubic project. I started in 2017 it's a sub project of OpenSUSA, yeah, looking at all this stuff. We then, you know, because we have tumbleweed because we know how to do all of this stuff, we've based all of our efforts on the tumbleweed codebase and effectively built a new distribution derived from that focused on this problem. We're using kubeadm for Kubernetes. We're using the podman cryo family of container tools. We have transactional atomic operating system updates and really heavily customized installation routine because, you know, we're a bunch of geeks and we still want to do like 500 things differently rather than just deploying the same thing all the time. But it's a community project. You know, that's list of what we've been looking at right now. We will look at anything else that anybody else wants. And in fact, there's some examples of stuff that's changed lately that I honestly had no idea was happening until suddenly I had a release announcement for this really cool new feature. And that's, yeah, it's an OpenSUSA project it's how we do everything. The base layer of cubic we call microOS and that's sort of the aiming to be the perfect container host. It has a read-only root FS using butter FS. For reasons I'll explain later. Like I said, using podman and cryo is its container runtime based on tumbleweed. And the kind of the general use cases for microOS on its own without something like Kubernetes on top is like as a single container, a single server, a single machine container host. So your typical sort of developers machine for running containers, testing containers, building containers, stuff like that. Using the features of like being completely automatically automated for updates. So patches itself, reboots itself, takes care of itself, rolls back if something goes wrong. We're currently using cloud in it. I'm probably moving to Ignition soon for actually handling things like bootstrapping the machine initially. Adding things like SSH keys and the like so there's even less effort. And the general idea conceptually is to have all services provided by containers. Of course, that's a lie. You need to have a bunch of services there so the containers can do stuff. But in terms of story, that's the story. And also we've started looking at other architectures. So this is one of those features that I had no idea was coming until I had the blog post. But we have a fully working AR64 port now with all of this stuff rolling, moving forward on AR64. Is it true? Generally speaking, sysadmins never want to touch a running system and yet almost every distribution we do forces them to touch their running system. We apply updates, binaries change, libraries change, conflicts, files change, and the machine starts changing its behavior immediately after the point of that patching. This ends up being a huge problem. It's a dangerous problem. Services are running, users are doing things, and users are half the problem most of the time. It's what they've done ends up breaking what we've upgraded and what we've patched. Software changes things, sometimes on purpose. And as packages, we don't necessarily always get it right. And that's really bad when you've just done an update and some RPM postcripts accidentally deleted the database or something like that. Rolling releases make it even more complicated. This is what we've learned with Tumbleweed. It's changing from system D to system D. It's a huge big change. If you're just pushing out the updates in a rolling fashion, suddenly sysv in it not being there because system D replaced it, that's going to have really weird side effects on your machine while it's running. Major versions of update stacks do it. What can users do if their system suddenly breaks? If they're literally in the middle of doing work and suddenly isn't there anymore, most things stop working. It's even worse when you start looking at the enterprise side of things. On critical mission systems where you've got large cloud systems, high availability, some kind of service moving things around, no one wants to have their service interrupted, but in reality they normally have enough redundancy that they don't care if the system is interrupted. The server itself can turn off because there's three other servers doing that job as well. But still, at the moment, just push everything out and break all of them at the same time. You need to make sure that everything is upgraded in one consistent change. If you have a bunch of new packages, are they all applied the same way? RPM Postscripts are the enemy number one to that idea. It could very easily leave a system in a very undefined state. It might be working. It might not. It might have done the same thing on every system. It might not have. How do you deal with that in a safe and sane way? We were looking at the solution to the problem, the transactional update as in database transaction. Wanting to have a system update that is atomic. Either it fully gets applied or none of it gets applied at all. We didn't want to touch the running system in any way, manner or form. Once it does touch the system, once you have applied the update, we also needed to be able to roll back that entire change in its entirety just in case something went wrong. With Sousa and OpenSousa, we've been trying to tackle this problem at one level for 15 years with all of the work we do with ButterFS and Snapper. On any Sousa distribution by default, we install ButterFS. Our package manager is applied to a snapshotting tool called Snapper. Whenever you patch the system, which of course is touching the running system, we do take a snapshot before and after. Have a snapshot before. Exactly what the state was before the changes were applied. You have the snapshot after. Which is cool for being able to roll back. That part of the problem gets solved. It isn't atomic. Those RPM post-scripts do change the running system. The system changes in flux. It solves only half of the problem. With transactional update, basically what we did was realize that we kind of over-engineered the solution in some respects. The ButterFS, Zipper and Snapshots were, because the system was running, we were patching the running system, we were in some respects doing twice as much work as we needed to. What we do instead is we have the running system and that is actually a read-only root file system. No package manager can make any change to that system even if it wanted to. Then with BTRFS, we make a sub-volume. That snapshot is therefore overlaying over the root file system. But that snapshot is read-write. We then effectively just redirect the output of the package manager to that snapshot. The snapshot gets patched, not the running system. The running system is running and every binary is untouched, and everything is clean, clear and pristine. But all of the changes, no matter what they are with RPM postscripts and what have you, all get redirected into that snapshot, which then when the update is finished, we close and we set that to be the next boot target. When your system then reboots, you're moving in one single jump to the new state of the system. It's kind of effectively a hybrid model of where with embedded devices you have all these images going out and you deploy the image on the next boot. The really nice thing with this is of course it's way more space efficient because BTRFS snapshots are only covering the diff of what's changed. We don't have to carry a whole second image of the OS and flipping partitions or anything like that. We can do duplication over the whole thing. There's also potential for over-the-air updates of sending the snapshot to a different machine so you make sure everything is getting exactly the same update. From an RPM point of view, packaging point of view, it also means we haven't had to reinvent the packaging wheel. We don't have to use some ornate new format.  We can use the existing packages, the existing way with minimal modifications if hopefully not at all. So we don't have to learn new tools. We don't have to learn new processes. We can basically take all of the skills we've had and all the benefits we've learned from doing this stuff for decades and apply it to this new world where people just want to have a system that moves immutably from one state to another. Doing it this way means of course you also have the benefit of a normal boot time. There isn't handling things like processing OS trees where you're figuring out what am I booting to. And you have the benefit of an incredibly quick rollback. When you boot up, if that snapshot does not work the way it's meant to, you just throw the snapshot away and you boot again and you're back to exactly where you were. So it's a very nice clean way of doing things. Does anybody want to see a demo of this working? Or I can move on. Okay, fine. Let's see if this works. This is fun, doing it backwards over my head. There we go. Nope. Thank you, Libra Office. Oh, come on. I love this. Demo effect in full force. Sorry. There we go. Does that look okay? Yeah, kind of. All right, so this is a standard cubic machine installed with micro OS. So we've got things like Podman installed on there for running containers. But we've got Vi on there as well, which is what I was not expecting. Fun. More than I thought. But we don't have Htop. So we want to install a package for whatever reason to have Htop to monitor the system. If I try and do an old fashioned zipper install of Htop, it's not going to work. It's a transactional server, which unfortunately you can't really see it. It's a nice big red message there, faded at the bottom. Not really, because this is a VM and this is a really dumb shell and I haven't installed anything that can increase the font because it's kind of a very minimal OS. But, hmm? Yeah, I tell you, that's not going to work. There we go. So yeah, Htop's not found. I can't install it because it's a transactional server. So instead, I run our transactional update and hope the Wi-Fi is working well enough. So this is just downloading, creating the snapshot, preparing the update, and so now I'm getting the output from zipper, so it's running our usual package manager, saying do I want to install Htop? Indeed I do. It's installed Htop and now I type Htop and Htop isn't there because it hasn't touched the running system. The running system is exactly the same state it was before I ran any of these commands, which is kind of the point. The only way now of getting Htop on this machine is actually rebooting. Normally we have a service called RebootManager, which literally has a schedule. It also can be set up to do stuff like checking for maintenance windows, so your nodes only reboot when you want them to. In this case though, I'm just going to reboot. Reboot after every action is horrible. Yeah, well, not every action because you're going to get stuff from your container apps that aren't applied to this, so it's only when you're changing the OS beneath. Yeah, so for the recording the question was, congratulations you've repeated the windows experience. My point was not really because it is scoped with focus of just being for the OS, with your applications coming from some other layer, like containers. On that level it's different, and then on the second one of course, Windows isn't atomic. Your API runs, screws your current system up, and then you reboot. At least this way, your current system is fine, and you reboot whenever it suits you. So it's a better model for that. And there we go. Now we have Htop. So that's transactional updates in a nutshell. Let's see if the poor video guys can do with that. And as you saw then, the boot time was, ah, sorry, completely. There we go. So if you're interested in using it, the commands you need to are all there. Very close to what we're used to in a typical zipper environment, so things like zipper up, zipper up, updates the entire package, yeah, transactional update, up and update the entire system. There's also really nifty debug style features like transactional update shell, where it will create the snapshot, and then transactional update will just dump you into a shell in there so you can do whatever the heck you want, then you exit it, and that's your single atomic update. So it's a nice flexible way of doing it, and then like rolling back, just transactional update rollback. This isn't an exclusively cubic thing, so it's used also in SUSE-CAUSE platform for updating their Enterprise Kubernetes distribution. We use it of course in cubic, and it's also available in the traditional open SUSE distributions. So both Tumbleweed and Leap have transactional server as an option, so you can kind of get everything in the standard open SUSE distributions, but with that mechanism for updating. And also coming soon in the SLEE-15 Service Pack 1 as a tech preview as a module in there. With some kind of known issues, because there are some packages which do stuff that's just a little bit unfriendly. Not like PHP might admin writing to SRV where that of course isn't necessarily going to be directed because that's read-write, that's going to change in real time. So it'll work, it just might change something that it shouldn't change. So those will have the caveat of and avoid those couple of packages. Cool features and cool ways of delivering software kind of part of the story. In open SUSE we're trying to talk a lot more about the bit that's really important is actually how we build it. Because it doesn't necessarily matter how cool it is today, it matters how well is it going to work 10 days, 10 years from now, whatever. With rolling releases, we've learned this rule which I kind of try to summarize here as if you're trying to move a complicated software stack the traditional option is you build your thing, you freeze your thing, and then you spend ages backporting stuff on top of it. Which works, but it's a lot of work and that work gets bigger and bigger over time. When you're looking at doing something in a rolling release, your goal should be to be able to effectively throw away your entire software distribution at will if you need it. If that one library requires you to change 100 libraries, which requires you to change 400 other things, you need to have a process that can actually scale to that kind of change so you can just move the entire universe to get that new thing you want in there. And yet still deliver it in a way that's built properly and tested properly and works properly for your users. With Open Susie, we've got a few tricks up our sleeve. We've had our build service now for well over a decade. It's what we use to build all of our stuff. It also can be building packages for anybody else. It's used by more and more people, not just the Linux foundation and VLC, but also now within the container world. Anybody here used Cata containers for anything on any distribution? Shame. I got way more hands in the other room when I asked that question. All of the Cata container packages for every distribution are all built on our service as part of the Qubic project. And now, of course, we're also using it for building containers because it's pretty much, in many respects, a lot of the problems OBS solves of making sure if this dependency over here changes, the entire dependency chain gets rebuilt so you have a consistent offering. The container solutions don't do that, so you end up with all these containers looking around with stale packages inside them. With the build service, we now have to do that with RPMs, so we also have to do it with containers. You can build a container, have whatever packages you want in there, and when OBS notices those packages have changed, it will actually rebuild the container for you and you have nice fresh containers all of the time. Registry.OpenSusie.org, literally any container you build will start using it to play around with that kind of thing. Building's cool, but what doesn't matter unless it works, so we're using OpenQA, we started it.  It can see the screen, it can see the UI, it's aware of which areas of the UI it's interested in, it can move the mouse, it can click everything. So with OpenQA, what we basically do is test hundreds of different scenarios and digging down into those scenarios, actually making sure that the user experience of using the distribution, using the tools on that distribution is acting the way it's meant to work, and the slightest deviation, like for example someone changing the background on Grubb will get caught, will stop the test, so you can actually make sure was this an intentional change or not. With these tools tied together, we basically built what now would be trendily called a CI pipeline for building distributions. And this rough workflow is what we use for cubic, this is what we use for tumbleweed, this is what we use for leap, this is what we use for sleigh, in some form, where any submission gets sent in, gets automatically checked by a whole bunch of scripts and linters in OBS, we then do sort of one tier of OpenQA testing, making sure basically like is this submission putting the entire code base at risk, is it just going to destroy everything and block us from testing anything in the future. Then at that point humans get involved and there's a manual view of the usual kind of checks making sure is this change sane, is it solving the issues we wanted to solve. If assuming that gets accepted it then gets put into what we call factory, where basically it's the prototype for the next release of the distribution, where we then build all of that stuff consistently and we test all of that stuff as an individual distribution. In the case of tumbleweed and cubic, we basically do tumbleweed and cubic in absolute lock, step and parallel, so we then take the isos and the images and the FTP trees that get produced by factory and we test them in parallel in OpenQA because they're all based on the same code base ultimately. Assuming all of the OpenQA tests pass that means everything from KDE and GNOME to Kubernetes and Podman, when they're all sufficiently green, they get shipped automatically to users. It's sort of devops for distributions. And then I've talked about all this testing and all this building and then people say, well yeah, but I run Arch. I just want everything now. I don't want to wait for this building and testing stuff. Looking at upstream projects, I'd say we've got kind of a bit of evidence that we can keep up. So with Kubernetes, they released version 113 December the 3rd. We shipped just over a week later with Cryo, shipping three days afterwards and with Podman I made a mistake and shipped it before they announced it. The process really can keep up. We can build this stuff, test it, ship it, it moves at the pace of contribution just like everything else in OpenSUSA. Now I've managed to go through this entire presentation by only mentioning the D word once, Docker. I'm not a huge fan of Docker and we're not huge fans of Docker inside the Kubik project. For a whole host of reasons which I haven't got time to go into, the simple and short ones are just architecturally speaking, looking at this container stuff from a distribution person's perspective, it's this massive monolithic demon which if it goes wrong, you're completely screwed when it comes to all of your containers running on top of it. You can't manage your containers. If it gets breached, all of your containers are exposed. It's just a huge nasty clutch of solving the problems they were trying to solve. Luckily though, Docker isn't the only answer to really solving those problems. In the Kubernetes land, there is an alternative runtime called Cryo running the same kind of containers. So it's still OCI containers doing the normal container stuff but built for Kubernetes, focused on Kubernetes, with ridiculously more lightweighting comparisons. Not having huge demons running on every machine, but just Kubernetes spawning the Cryo process. The container is a child of that process, good old fashioned Unix philosophy, keeping it simple. That also then makes it easier to tie it up with the other tooling and techniques we've been using to secure our systems for years. Things like SE Linux and App Armor. With Docker, if you want to try and wrap App Armor around it, it's a complete nightmare because you basically just end up poking holes for every single container that you possibly have, just so it can get hold of the resources it needs on the base operating system. With Cryo and Cryo like runtimes, it's just a single process. Each container can have their own App Armor profile which gives that container just the access it needs to just the bits on the system it wants. When you think of a typical container being some binary running some service and despite the dream of everything being stateless, that's never true. There's always some data somewhere that needs to have some access. With this model, it's quite easy to have an App Armor profile that just gives access to the bits of the OS the container needs to see and that one storage location so the container can get to a storage and everything else the container can't see. Life is nice and safe. But like I say, Cryo is very much Kubernetes centric. So if you're running a Kubernetes cluster, Cryo is underneath that thing but it's sort of abstracted away from really interacting with it. You're not going to see anything interesting. For those of us just messing around with containers like on our workstations or on like a standalone server to replace Docker, we're using Podman. It's basically a drop-in replacement for the command line for Docker. It's using the same containers, like I say, just like Cryo. It shares a lot of the same concepts in libraries with Cryo and in fact at some point they're going to be aligned more and probably merge together in at least some form. The syntax is practically the same. Podman run is the same as Docker run. Podman pull is the same as Docker pull. So in fact on my systems I just alias it and haven't run Docker for a year. There is kind of one big difference is Podman has no equivalent to Docker compose because being sort of a child of the ideas behind Cryo, you've got Kubernetes. In Kubernetes land when you have a complex container service instead of having like a Docker compose file where you're defining all the different containers in some YAML, you have a Kubernetes kube YAML which defines all of the containers for your pods for Kubernetes. So basically the same concept but more people are using Kubernetes these days. So that's where Podman gets its name. It's the manager for pods. So it has additional functionality for running or creating pods by hand if you want to. So you can literally start a couple of containers, create a pod without having to write any YAML which is kind of nice. You can then have Podman generate that YAML for you which is really nice because I don't like writing that much. Or you can take existing YAML templates for existing Kubernetes clusters. Thanks. And running it on your Podman machine instead. So Docker compose is missing but to be honest it's kind of not really needed. There's also some extra nice features that people working with Docker kind of really wish they could have things like deleting all of your containers or deleting all of your images. That's kind of another reason why these tools have my heart. Full requests for that have been lurking in Docker's GitHub history for years. In Podman it's there, it works. The downside of all this really cool upstream and open source stuff is when I moan to Podman they tell me just to fix it because that'll accept my full requests which in the past I could just make everything Docker's problem. It's a nice problem to have. And being more lightweight, being a simple process, running on a machine, starting a container, it means you can also do very interesting orchestration kind of things like tying it up with system D so having like system D starting a container, stopping them using socket activation so the container only starts when a user is trying to access it. Which nice features that kind of potential I don't think has been fully realized yet but we can see where we go with that one. Building containers. Podman build basically emulates exactly the same way Docker build works but there's more ways of building containers. So builder actually does all of that in a million different ways so building from scratch, building from images, existing images, using a Docker file, it can do the standard compliant OCI format or it can do the Docker format and you can also do really cool stuff like just taking existing container, mount it make your changes in a shell, unmount it and then actually creating a new container from that changed instance which is just a far nicer way of doing things and trying to manually inject it with other tools like a lot of other places trying to do it. Then once your container is built you've got to put it somewhere, you need some registry or you need to handle that and we have Scorpio for handling, uploading, controlling, deleting the content of a container registry. Outside of all that sort of standalone container stuff, we have Cube ADM which is the upstream Kubernetes cluster so you have the issue of you need to have at least three or four nodes or working in conjunction to run your containers, how do you get those three or four nodes to talk to each other. Lots and lots of people have tried home brewing their own solutions and it kind of got so messy to the point where like Kubernetes upstream started like okay we're just going to build one tool that at least does the basics so everybody does the basics right. We've really embraced that and we're wanting to use that as much as possible the issues we bump into, we're working with upstream to extend it and then if people come up with additional third party additions which don't work upstream we'll look at using them. It was GA in Kubernetes in version 113 just before Christmas and from a cubic point of view it's incredibly nice because it's completely decoupled from the operating system so it creates your Kubernetes cluster in containers so those containers can have their own life cycle can be replaced when you want to replace your containers and the operating system can just happily patch, reboot whenever it wants so it kind of fits in perfectly with our way of thinking of what an operating system should do and what the containers should be doing on top. Setting up a cube ADM cluster is nice and easy. We have all the instructions on our wiki basically you take the cubic ISO, start it up, say you're going to run cube ADM it doesn't matter if it's going to be a master or a slave because it's always actually going to install exactly the same binaries and then the difference will be handled by the containers.  It basically downloads the control plane, sets up Kubernetes properly, configures everything the right way at the moment you have to actually declare the fact that you're using cryo that part of the string will disappear in 114 because we need it to disappear in 114 so you can auto detect which run time you're using and then at the end of that you get a nice text output of your cluster is basically built and done and you have this string here which is the string you run on the other machines so they can join your cluster. It basically includes the discovery key. You need to have some tool to manage that cluster now you've initialized it so there's a couple of commands you need to run to basically extract the key so your machine can be trusted to run the cluster so basically set up the admin console so normally you do that, well you can very easily do that on the machine you're currently working on but if you want to handle it remotely you just take those files and deploy them wherever the hell you like you need a network. In Kubernetes land there are tons and tons of different network layers or using CNI. In the case of Cubic we're testing Flannel mostly at the moment from CoreOS so once your cluster's got to that point you just deploy your Flannel containers or your CNI containers of choice and that set up the network so the other nodes can actually join something. They need some network to actually work together and then once that's configured you go to the other nodes and you run that string and you have a working Kubernetes cluster and you can start actually running your containers on a highly available fabric so things move along between the different machines. It looks something like that. I was going to try and do a demo but I don't quite have enough RAM on this laptop to run like three nodes at the same time. The moment we're working very closely with upstream Kubernetes so using their stuff, filing most of our issues upstream first is not really carrying any patches for any of this stuff in Cubic and it's working out quite nicely because as of two weeks ago Cubic actually became the first open source community distribution certified by the CNCF so it's certified Kubernetes following all of their standards, passing all of their test suites commonly on 113 which is the latest upstream release. I'm hoping with 114 to actually use that whole process of ours of building and testing so it will actually be the first distribution even faster than all the enterprise ones to have 114 in there should work at least all three as close as we can and when it comes to everything we're doing right now when it comes to what next, whatever the community wants. This is working really nicely now the container world is moving incredibly quickly so if anybody has any bright ideas now would be a good time for the ideas or for questions. Thank you. Yes sir? Will there also be like a container version that is more long-term support? So the question was this is is this a container version of tumbleweed? The answer for that is yes and given that is there going to be a sort of a longer supported version of Cubic? I'm not going to say no because when I started working on Cubic literally the first thing I did was change a lot of the structure we were doing to kind of make room for that possibility so like inside the build service we call it tumbleweed Cubic so you know there could be a leap Cubic if somebody wanted one but the more I look at this stuff and the more I'm packaging this stuff a rolling release solves so many problems like I dread to think out of work someone would have to do to get Kubernetes 113 or 14 running on Leap. Podman is actually being quite portable so like I can see some of that stuff translating along like we did with transactional updates but generally speaking for container oriented OS I think the challenge is to actually keep up with upstreams, keep up with where everyone's going but do it in a way that's still stable. I don't see an LTS actually solving any problems but yeah. Are you planning on putting that into Zipper so that sometimes we just run the Zipper command and it will know the right thing to do? So the question was are we planning on putting the transactional updates stuff into Zipper? Ignace are we still planning on doing that? Yeah. He's working on it. Yes. Release date? Tomorrow.  Okay so the question was when you're using transactional updates is Zipper running on the base OS or running in like some container? Yeah. Yeah. No. So with this we're basically a cut down traditional style OS so that is typical Zipper, typical packages running on a typical disk of choice and then we kind of make the container problem something higher up the stack so we do the OS part fine we didn't see the benefit of trying to containerize everything. There has to be some line where in our minds at least as a distribution we're responsible for providing an OS. It has to be built properly and done properly and containers aren't the right way for doing an OS. Okay. So yeah. To repeat the question sort of running something in a transactional update like what if like a postscript was trying to get hold of system like yeah accessing system D. We wouldn't allow that in open users so I don't think it's ever come up. We try and build stuff in a way that that would never be necessary but yeah. That would be fun. Yeah. It would fail and to be honest I'd be glad that would fail rather not have that package installed in that way. Yes. How do we deal with incompatible configuration files? We do our best to do a 3-way merge and have snapshots of the we doubly snapshot all the ETC stuff so you know you fix that. Okay. Yeah. Yeah. Fill up. Fill up templates exactly. There's a mechanism fill up templates which will just transform configuration files from old versions to newer versions if the configuration files itself was modified. Yeah. That's what I meant. Yes. Yeah. Yeah. If you want to update if you want to snapshot your data so the question was yeah what if could you snapshot your data also if you want to snapshot your data that's something you can already do in every open source of distribution snapper for anything outside the root file system so it's kind of out of scope for the OS because in the same sense of like we don't want to mess with user data like we don't want to presume what snapshotting policy you want for your data but the tool is there so you could say you know okay this folder snapshot it this often you know and you could potentially hook it into our tooling too. Yeah. So the argument there was you know distributions could know that they're changing data in open source we have a philosophy of like don't mess with user data like so like you know when like MySQL is a perfect example you know when we're updating MySQL you know we expect the user to run the appropriate update scripts we don't run them for them because you know that doesn't seem like our place it seems presumptuous I'd rather you know I'd rather the next boot to have MySQL not work and then the user have to fix it there it's different philosophies I think I'm done for time thank you very much.


In the U.S., we tend to get less than 20 grams of fiber a day, only about half the minimum recommended intake. But in populations where many of our deadliest diseases are practically unknown, rural China, rural Africa, they're eating huge amounts of whole plant foods, up to 100 grams of fiber a day or more, which is what it's estimated our paleolithic ancestors were getting, based on dietary analyses of modern-day primitive hunter-gatherer tribes, and by analyzing coprolites, human-fossilized feces. In other words, paleo-poop, these most intimate of ancient human artifacts were often ignored or discarded during many previous archaeological excavations, but careful study of materials painstakingly recovered from human paleo-feces says a lot about what ancient human dietary practices were like, given their incredibly high content of fiber. Undigested plant remains, strongly suggesting that for over 99% of our existence as a distinct species, our gastrointestinal tract has been exposed to the selective pressures exerted by a fiber-filled diet of whole plant foods. So for millions of years before the first stone tools and evidence of butchering our ancestors were eating plants. But what kind of plants? One way you can tell if animals are natural folivores or frugivores, meaning leaf-eaters or fruit-eaters, is to map the area of absorptive mucocin, our gut, versus their functional body size. Folivores are those meant to eat mostly foliage leaves. While frugivores are better designed to eat fruit, the phonivores eat the fauna, another name for carnivore. If you chart animals out this way, they fall along distinct lines. So where do humans land? Here's our functional body size, and here's our absorptive area. So while eating our greens is important, it appears the natural dietary status of the human species is primarily that of a fruit-eater. Why does it matter how much fiber we used to eat? Well, one theory for the rising levels of obesity in Western populations is that the body's mechanisms for controlling appetite evolve to match how many plants we used to eat. Our ancestors ate so many plant foods, we were getting like 100 grams of fiber a day. So for millions of years, food equaled fiber. So no surprise, one of the physiological mechanisms our body evolved to suppress our appetite involved this fiber. For example, fiber is metabolized by our gut flora into short chain fatty acids which bind to and activate receptors on the surfaces of our cells that alter our metabolism. For example, activating receptors on fat cells to increase the expression of the weight-reducing hormone leptin. Other hormones are affected as well. Since until recently, food meant fiber. An increase in food intake meant an increase in fiber intake, which made our gut bacteria so happy that it made lots of short chain fatty acids.  So we eat less, but if we eat less, there's less fiber in our gut, so less of these hormones are released, which boosts our appetite. We get hungry and we want to eat. But what if food doesn't equal fiber like on the standard American diet? Then we keep just getting those signals to eat, eat, eat. We're always hungry. If we haven't eaten our 100 grams of fiber for the day, our body may be like, what are we starving here? Discovering this mechanism makes the food and pharmaceutical industries very excited. They figure they can now come up with the new drugs in the fight against the current obesity onslaught, or we could just eat as nature intended.


Good morning, cyber traders. Welcome on this holy Thursday. Good morning, Brad. Good to see you, Lawrence. It's nice to be back. Let me tell you, I was shocked.  It was there for over the week.   My wife had a little husband and wife getaway. Thank God for after, you know, now the kids getting old and so on. But we had a good time. Met a lot of the great partners out there that we do events with. A lot of great speakers that some of you very familiar with. You know, Andrew Keem was down there. You know, Rob Booker was down there. I mean, but just a ton of people, great speakers and gurus in the trading room. They all said hi, you know, but I'm nice to be back. Let me tell you, I took the red eye and I was shocked.  Well, I heard you guys had a lot of good fun with certain stocks. I know the staff to see to carry you had some really good stocks. We'll talk a little bit about them. Listen, we got a really packed schedule today that's going on. A lot of big things that are going on today. Just to remind you at 11 o'clock this morning, we are going to have trade station, one of the senior reps there, are going to go over the execution system. You know, we do that in a cybergroup room. If you're watching YouTube, Facebook Live, you want to join us, you're more than happy to do that. Just, you know, once again, just click on, if you got your phone, you got a QR code on the top left hand corner, just scan that little QR code and we'll be able to get you in that free workshop. But yeah, so we got, yeah, it's 11 o'clock today, that's right Jeff. So we got a lot that's going to go on this morning at that time. And then obviously also today at 12 o'clock, I'm going to do an open house for everybody here every week, we do it here every week. And we're going to talk about how to find these stocks and all that good stuff and everything that's going on. But anyway, regarding really about that stocks really quick, thank God, CFRX, holy crap, this thing is making a huge run, we're up almost a dollar since this morning, eight o'clock this morning, even at 220, we're at almost 250, 30 cent move. Are you kidding me? Does that sound like a lot? Of course it is, 30 cents and a thousand shares, 300 bucks. What is that, 50 grand a year? Who doesn't want that? So of course you definitely want to look at. We're going to talk a little bit about that, a couple of other stocks. And then also I got some great, great news that I also want to share with you. I have finally was able to launch my new Faustal Home Living channel, how to make authentic Italian sauce. I'm going to give you guys the link. I did post it in there. I know everyone's been waiting for it for a long time. There's two videos, just to let you know. There's one on Instagram, which is a 60 second video. We're going to try to get it on YouTube. And then there's a second one, the really lengthy one that you want to watch that's in detail, that's the one you want to watch on YouTube. But we'll give you that link. And don't forget everyone, you got to share it. You got to like it. Please get as many views that you can for us on it. You know, it's the only thing I always ask for all of you to kind of go out there, share it on your YouTube, your Facebook, you know, any channel you're on here, any social media, but it's only a favor I would always ask everybody. All right. I teach you how to make money. You better like my videos. All right. So anyway, let's talk about what happened yesterday because you guys had a couple of good things I heard that you were trading yesterday. But anyway, this FRC, this is one of those California stocks that we were talking about, the ones that banking stocks, this thing did not come back. I saw the alerts coming on, you know, you know, we have the alert service at CTU, but that thing just took a huge dive. But it had a really nice bounce. You could see it here. You know, when it got that, it took that big crush this morning, I could see it right here.  I think everyone should have probably found it. What we taught you right around here, a 580 thing ran only to $7. But my God, that thing just like, and you know what? The crazy thing is I thought that was going to be a swing trade. And I had second thoughts on it, but you could see it right around this price. I mean, the stock was a $125 stock. I'm like, you know, it's holding it for a while, but it never really kind of came back. It wasn't like somebody other ones, like Wall did come back, WAL. Somebody other ones, he'd ever came back. This one did come back a little bit, PACW, but that FRC doesn't look like it's doing too well. And I know everyone here was trading the PACW, which was trading very close. And you can now start seeing as a trader, they trade very similar to each other. Now, LUNR, that one actually did a really, really nice move. You could see it right there. Nice great push, $7 stock, $750 to $9. You know, once again, follow the mousepad. Oh, just to let you know, regarding about the mousepad, first of all, it was a big hit from all the gurus. They were all dying for it. We just kind of shipment in. So we'll put the link in there. If you guys are looking to get the mousepad, best times to trade, we'll get it out there. I know that some of you have been harassing me, like where's my mousepad? But, you know, the clock, so we got that that's coming out. We just got a shipment in. So we'll be able to get that sent out. Getting back to the stocks also we're trading the CAX. That was a really nice CAX AI, one of the AI stocks. That was the one that we were trading back in a couple of weeks ago, $1.50 to $20 share. Listen, in regards to the whole AI news, these things don't move and go up from $2 to $20. I don't think it's gonna go to 100. You know what I mean? Can that happen? Of course, just remember, the faster they go up, the faster they come down. Actually, it's twice as fast. All right, and also AI. Listen, we had a lot of fun with that stock, right? Guess what, went all the way up. By the way, anyone wanna speculate why the stock's coming down? Anybody have an idea why it's really coming down, speculating? I mean, the only thing I kind of figured out, Elon Musk came out and really bashed the company and said, we gotta put a cap on AI's and stuff like that. I know we had a meeting yesterday with Senator Schumer regarding about it. He said it was a really good meeting. He actually even tweeted about it. And I don't mean, read between the lines. That might have something to do with it. So anyway, that's what I would be careful of. Anyway, that was the past. Let's focus on the future. Let's get back to CFRX. So anyway, that is the biggest percentage gainer right now in the market. This stock last year was in the $300 price range. This thing got destroyed. Don't think it's going back to $300, okay? If we can get back to $3, I'll be happy with that. But I wanna go hop on and bring on and see what's going on level four. Now this is what I see here, okay? Now you can see when I zoom in and zoom out, you can see the iceberg where we're starting to show up. 27,000, you can see the ladder effect. This is actually pretty cool. You got a three level tier, you know, which is also kind of brings it up. I'm not seeing any sellers out there. You can see the buyers when they show up here around $60, 65. Once again, we're gonna talk a lot about this in the afternoon meeting. We're gonna talk about it with Trade Station. We're also gonna talk about it in my 12 o'clock open house. So once again, if you just log in in late on YouTube, take your phone and you got that QR code right there on the left, just scan it and we'll be able to get you logged in. And by the way, if you're watching this as a video later, you could always watch the recording, okay? So anyway, that stock is moving pretty nice. That is obviously is going on the watch list. I just wanna post up the pre-market watch list and on the tags and there you go. So that was actually the, we post that, what time we post that? At 746. What was on the first one of the stock? So 746, what time is that? When you got the alert, oh, right around here, $2.  Anyway, no sellers out there read between the lines. All right, another stock that came up on my watch list was Atom. Now, I don't know, Atom, it had a really big move yesterday after hours. So obviously you could see it was more of an earnings play and it went and shot up over at 850. Nice little move. It's not really going anywhere. And you know what? When I look at level four, I'm not seeing anything going on. So I'm not really completely sold on it, but it's not a really good morning. I'm not seeing that much. Even though the market's up 140 points right now, CFRX, that's all we really need right now. But, you know, listen, some of us already missed it. Well, I don't know, did you really miss it? The market didn't even open up yet. So I will probably be too much concerned about it. We'll see what happens. The big news right now, obviously what's going on too, which I probably have never seen this in a long, long time. MetaStock is doing great. Their earnings came out great yesterday. And you could see I think pop from 210 all the way to 235. She's moving pretty well. The stock got a lot of scrutiny. The stock was in the $100 price range. Stock's already doubled. You know we're not going to trade it because it's too expensive. I mean, let me tell you, level four though looks amazing. I mean, let me show you what's going on.  Anyone else out there? Not really seeing any big sellers out there, but I do see a little bit of a ladder effect that happened early in the morning. But so you can use the style we train you here at Cyber Trading, how to shadow big iceberg orders, you know, even with brand name stocks. Hey, we did really good with that with Tesla, you know, last week, if you remember. But anyway, they're all in the big percentage gainers. Amazon, you could see that Meta's in there. Intel's obviously take a little bit hit. Tesla really taking a big hit right here. But obviously, you know, that's not our real forte. We like to trade stocks a little bit more, less brand name and more volatility on it. So other than that, as I was watching, I mean, with some of those stocks that we found in pre-market, I'm not completely sold on it regarding what's out there, but they're, you know, they're okay. I mean, this stock I saw too was moving up at the bottom of those little light 38,000 shares of 50% TWOU, this stock took a very big hit. It was okay. And New York stock, you change stocks. And this is up 12%. It's a very, it's a very cheap little stock. Nova, I mean, not that much out there. Really, really not that much. Losers, Wolves taking a big hit.  I mean, this is trying to make a little bit of a comeback. Yeah, this is not really that much out there. This one's taking a big hit. This one might be a short $33 stock, but the spread is ugly. Remember the big thing we always teach you at Cybertrain University. We always talk about the three T's, tradable, trend and trap. And you know what, if the stock is not tradable, you gotta be very careful because you can really get beat up on it. But you could see most of the stocks here and the most active are brand name stocks. And remember, we need good volatility on it. So not really seeing that much out there. We've got about three, four stocks. We'll throw that back in there. We'll see what happens. It looks like a lot of the stocks that we found early this morning are basically pretty, pretty much that. All right, so now regarding about the big news. So about the sauce video, all right? Because I know everyone's been harassing me for that sauce video. Where is that sauce video? Oh, here we go. So to give you guys the link, just wanna hit me with commercials. Let me give you the link right here. All right, so here's the link if you guys wanna register. You wanna be able to watch that video on YouTube. This is the link. There it is right there. And a lot of good videos. Just wanna post that up there for all of you here on YouTube. There you go. Thanks a lot, Rich. Rich is sharing that on our trading room. So if you wanna finally get to learn how to make authentic Italian sauce, here's your chance to kinda watch it. There's a short one on Instagram, 60 second, but this is actually the more detailed version of it, all right? And by the way, I got three big ones that'll also come out after this one. This is supposed to be the most popular one. All right, anything else before we go to Cyber Traders? Anything else? All good? So let's get ready for the market open up. Don't forget today, we got Trade Station at 11, we got the open house at 12, you got the link on the top left hand hot tide. If you're in a cyber group room, once again, you're gonna have a little busy day today. You know, you had Traders Talk on Tuesday, Thursday's always our popular day to bring out some of our VP, some of those big gurus and some of the big, well-named brokerage firms and gurus into the industry to come talk to you. So we'll see you until then. So you got a busy day. All right, guys, good luck today, happy trading. And for everybody else, we'll see you back here. Midday, and remember, we are live every morning, 9 a.m. to 2.30. Happy trading, everyone.


I'm Zach Kobel, the Systems and Emerging Technologies Librarian at Gettysburg College. I hope to gain a better understanding of the direction that the DPLA is going in, and mainly just to get a better idea of the status of the project. I hear a lot about it and follow some of the developments online, but to see the people who are active and involved in it, and learn about what they're doing. That's a great question. There's a lot to do as far as funding and then copyright, and which collections to include, and there's just a whole slew of things to consider when putting this together. So as far as one next step, it's hard to exactly say. Still keeping my vision fairly broad at the moment. I think this is a really interesting project that has a lot of potential, just the grand scale of it. So trying not to get bogged down by all the technical difficulties and small details like that that can get in the way. So I don't have an exact answer for that at the moment.


Good morning, my little sasquatches, sasquatches.  I'm deliriously tired, clearly. I was supposed to film, I'm thinking very slowly right now, so bear with me. I was supposed to go over with AHF to their OTC, which is out of the closet, it's a thrift store and we're gonna do our little thing today, but Avery told me that she had a lot of stuff pop up from other people putting workload on her, so we're gonna push that till tomorrow. So the only thing I really have going is my barber appointment at 11. Two daily vlogs ago, I talked about Eugene and having stick my old barber shop and how he was there when I needed a new barber and now he's awesome. And right now I'm just gonna go do some cardio really quick and head over and get my haircut. Which as you can see is a hot mess right now. Yeah, it's a hot mess. So we're gonna tame the beast. This is awkward. I'm here in the little gym in the apartment building. Yesterday my coach said he wants me to up my cardio, so I'm gonna be doing 55 minutes today and then actually if I can come back later tonight since I don't have anything going on, I'll probably do a second round either here or when I do my actual workout at crunch. I usually do my workout in the morning, but I don't have time since I'm going to the barber after this, so I'll just do a little cardio to start. I was just responding to a Snapchat message from Gabriel Lewis. Just wrote me a really sweet message supporting me in my competition prep. I guess he's coached some people, some fitness models into prepping for competition before so he knows like how exhausting and draining overwhelming it can be. And I was just saying that I've had such an amazing outpouring of support and love from so many of you guys that like it really has become my fuel in a lot of ways for when I'm feeling tired or hungry and I just wanna cheat or I'm like so sore that I'm just miserable. I'm really, you guys pop into my head now every time and it really is helping fuel me a lot towards staying on track and consistent and pushing even harder than I would if it was just for me. I feel like this time around competing has, because I've shared it with everybody, it has become something bigger than it ever was for me in the past before. You know, it was a big deal to me but I was really just doing it for me because I wanted to, which is still true this time but I also feel now like I'm also doing it for you guys, I'm accountable to you guys.  Just the amount of support. I even have some people who watch my video and like I have some extra cash I could help you out. I can throw out your way to help you with competition fees and stuff like that. And like it's just really nice and I don't wanna take anybody's money. I just wanna be able to do this and do it well. So I'm trying to figure it out and I know I will. It's just the gesture alone and the sentiments means a lot to me. So thank you guys. I really do appreciate it. I feel like getting emotional in morning cardio. So typically on any day when I go to the gym, usually I'm at crunch.  So I'll post my selfie and then I'll work on my daily motivation for the post and then I'll just go through probably some DMs and then usually for the majority of the cardio I turn on Gary Vaynerchuk's latest video and I just sit there and watch that and get super motivated and inspired by his videos. That's my treadmill routine. So now I'm on five minute cool down and then I'll be done. All right, so I'm just parked. It's like two minutes to 11. That's when my appointment is and I'm gonna go in and some fiber down. So that's all camera shy now. Camera loves me. I can't help you. You never know what you can do until you try it best. Yeah. All these other ones. Affirm it, visualize it, believe it and it will actualize itself in bed. But what the fortune is, you add in bed and give them in? Perfect. Because your hair lays this way right here. All right, yeah, I'll shorten the time limit but I just have to make sure I add that and it'll give me a little more time. Okay. I got you a ticket, come with me. Oh, stop. Yeah, you down or what? Slow down. All right, good. I just figured if you could for you this whole at a time. I'm excited. Send that to yourself or I don't know if there's any information. So I just, I made a hundred bucks for two tickets. They're the same tickets that you would get for a hundred dollars a piece.  I don't know. Maybe you can make a little vlog about that. Yeah. Because it means all the way to go. You're gonna record it this whole time? Yeah. Oh lord. You got an iPhone. You know Mario Kart is now available. Yes, I haven't got it yet. You already got it? It's free. Really? Gary, you literally just put this on. I know, that's why I knew about it. Yeah, he's like, I knew about it too. He's like, good job, Nintendo.  White faces. He's so mean. I was so much like he wanted me to do this. Get a lamp and you can tell me. Yeah. What friends are? Mek team. Mek team. You're very spread. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. Mek team. FC than. Mek team.Jason. Mek team. MSRC. There it is, it's all white faces. OK. Give me another guy for me. Oh, man. Oh bitter, no. Oh bitter, yes it's okay. OK, thank you. Oh bitter. Right, you mean. Your stickers, dude! You are awesome. You are impressive. I'll keep all the stickers on you guys. Like pencil just. They just like, put that back on yourself. So I just got here to the restaurant where I actually used to work. It's closed down now, at least down here there's events going on upstairs. So I asked my GM if I could shoot some stuff here for a new show that my buddy Carl, I've mentioned him several times before, we've done a vlog together. He created a show called Plus Life and it's going to be based online on social media and it's around having discussions around HIV and also love sex relationships dating, navigating life as someone who is HIV positive or technically other STIs and really cool things like that. So just a really cool and socially conscious show obviously has a lot to do with what I talk about when I'm interested in. So they asked, one of his producers actually reached out to me a few nights ago and asked me if I could create a little video of like a cocktail of the week that you might see on different shows. They want to do that concept so I'm coming up with a cocktail right now. I'm going to shoot it, try to make it look pretty and then get it ready for them by tomorrow. So that's what I'm going to be working on. Okay so it is 12.30 am and I just finished editing the video that I needed to edit for Carl's new show Plus Life. I sent a clip of it to the producer earlier and he liked it a lot so that's a good sign.  And I just finished editing my vlog for September 24th so that is now uploading to YouTube. It says it's going to take a couple of hours to upload so I'm definitely not staying up for that. So I'm going to hit the hay and then wake up early and hopefully be able to post that right away. I'm obviously now I'm like three days behind on my daily vlogs so I'm going to have to figure out a way that I can edit these and get them done in a faster way which probably means like less editing of them, actually less cutting and adding music and effects and all that.  I want you guys to be interested in it and not bored.  Alright, good night.