Dette sesjon skal være en generelt update på staten av Dora Verkstationen, og også hva vi har gjort så farlig. Det er vort å nøte til, at jeg tenkte at min sesjon var skadet for et halvt år, men jeg vet ikke om det er 50 minutter. Så jeg vil tøye til å spille på de slikene litt, så jeg kan gå til dem. Min namen er Christian Schallert. Jeg er manager for Desktop at Red Hat. Så dette talet vil faktisk cover everything we did since we sort of launched the Dora Verkstation effort five years ago, and sort of what our next steps are. I the first start we'll talk a little bit about our goals, and then of course how we've progressed so far in terms of achieving those goals, and then what the next steps are. So, what is our goal, is actually correct here. For the Dora Verkstation, we had an explicit goal of targeting developers, and that is still true. Our plan forward is still targeting developers, but I think we have sort of widened the definition of it. So we include things like Gisadmin, graphic artist, and I would say sort of makers in general. Anyone who uses their computer for creating content is sort of part of our target audience. While I guess sort of, let's say a productivity worker, or someone who's just using it for email and so on, is of course more than welcome, but they're not like someone we prioritize in terms of choosing over development priorities going forward. So, progress so far. So these slides I actually was planning to rush through when I have half an hour, but I will talk a little bit more on each item since we have more time. I think we have quite a few major achievements that we achieved the last five years. I guess most of you know the Linux Vendor firmware service, was the thing we kicked off to make sure that people actually could install and get firmware on their laptops, or on any basically Linux system. I mean, before we had the Vendor firmware service, for the most part you could not actually update your firmware at all on most laptops, or at best you could download some kind of thing that would start on special DOS session to install your firmware for you. And I think today we are, we're not on par with Windows, but I think we're getting quite close. I mean, we have all the major vendors, Dell, HP, Lenovo signed up, and they're also getting more and more of their hardware partners to add up. So for instance, I think just yesterday I saw a post from Richard Hughes talking about how Lenovo had started on updating Thunderbolt firmware updates, for instance for the Thunderbolt controller, I think, for example. All in all, I think this has been one of our big achievements that we know have succeeded in getting so much firmware created, and more and more people are coming aboard continuously. And also some of the smaller things are starting to appear, like I was talking to Richard Hughes actually, and he was mentioning that Intel, for instance, is starting to upload firmware updates for their prototype hardware. So when you get sort of sample hardware from Intel for new architectures, you will actually be able to get firmware updates for them through the firmware service. Another thing that we worked on as part of this, and actually to go back a little bit. So, you know, as I said, we started focusing on developers, and we sort of did actually quite a few surveys and went out and asked people, like, what are your main concerns with Linux as a development platform, or as a, and you know, the thing that came back to us very, very often was like hardware support. The things didn't work correctly, or that, you know, the botany laptop, and most things worked, but there was one or two things that was broken. So a lot of initial effort over these last few years has been on improving hardware support. But I think as we go through these things, remember that, you know, the things we focused on was actually targeting developers, even though of course a lot of them are quite generic in their thing. And of course, Thunderbolt support was only since it came, and there is a lot of hardware support. There was basically no Thunderbolt support at all in Linux when it started out. And we've been working on this project called Bolt to make sure that we handle this kind of, you know, security levels and so on for Thunderbolt. And this is a project we still keep pushing forward to make sure we add functionality for supporting more and more things. Another thing we have been working on, and this is maybe not so visible from the community, but it's having better relationships with the hardware vendors, especially like the laptop vendors themselves. Because to some degree it doesn't scale, or that might really work if we own the problem of making sure hardware works. Because what happens then is that let's say Lenovo ships a new laptop, which has a new piece of hardware in it that nobody else has been using before. And at that point you will have a situation where, you know, Linux will have a period of time where it's simplest to support it. And of course we will then struggle with having to maybe try and reverse engineer that hardware to make it work. So we've been pushing very hard on our hardware partners to say that, you know, you need to hire people and you need to own the problem. So that they plan, so A, that they push their suppliers and that they plan to make sure, you know, that there's upstream support for their hardware in time for a new hardware to ship. And also that they let us know so that we are able to make sure that, you know, we bring it into Fedora or Elford at a good time. And I think we've been quite successful there. I mean, of course I've had their own effort for some time as part of the Reproduct Sputnik and, you know, the Express 13 and so on. So they are probably the furthest along with making sure that they plan Linux hardware support. I know that for instance Lenovo know is also ramping up quite heavily their efforts to make sure that they can properly plan hardware support for the laptop to Linux. Wayland is another big effort that, you know, we successfully brought in. You know, when we started contributing to Wayland it was mostly an Intel project at that point. I think it was a general agreement that, you know, Wayland was the way forward. And it had advantages over X in terms of improved security and so on. But it was still far from ready for disapuse. And at the same time, at that point, Ubuntu was trying to basically fork into doing MIR and doing their own proprietary setup. But I think we succeeded in A, of course making Wayland a reality. And then of course MIR ended up falling by the wayside. So I think we have succeeded there in making sure Wayland had a future standard for Linux desktop graphics. Flatpacks is another effort that has gone far and I will talk a bit about also what we are doing going forward.  First of all, you know, I think we had a talk today from Facebook for instance and also from Matthew talking about like, you know, too fast or too slow. Turning things into flatpacks will help us, you know, eliminate clear between operating system and applications so that we don't and so easily have the situations that you constantly have no that you operate update your OS and then application break because it depends on an older library or something. So by, you know, making everything into this containerized this applications, we will be able to have applications and always move at different paces. We don't constantly, you know, trigger break hazards or having applications fight over which version a certain library should be at. Very clearly developer targeting we did was that of course spending time over last few years adding improvements to the GNOME terminal and trying to make sure that it works really well. And things like, you know, you get these notifications now when the job is finished. So if you have like a big compiler running in a terminal you don't know it manually go back and check it instead you will get notified saying, hey, you know, your job has completed. GNOME software is another piece where we invested a lot of time and effort. I mean, it does, of course, the firmware updates that I mentioned earlier. It does nice and easy graphical updates of the whole operating system. I think it also has made huge strides in just making applications discoverable and easy to install. And of course it also supports multiple packaging technologies like RPMs and Debs and flat packs. Another thing, and this goes back to this hardware supporting we spent quite a bit of time some years ago making sure. We got a great HCI high DPI support and you know Fedora Workstation got a lot of good press actually over that. I mean we were the first distribution to have good high DPI support over the box. And of course at this point there are still a few applications that are still lagging a little behind in terms of adopting high DPI. But all in all I think we are in a good place and I think it was a good example where we were managed to get on it quite early so it didn't end up being this thing that you know you got your high DPI hardware but it took you a year or two before you could actually start using the functionality under Linux. LibInput is maybe not something you actually see today but as part of our valent transition we also decided to split out the input support in X into this thing called LibInput and also rewrite it a bit to make it better and more scalable. So we have seen a lot of improvements through the input stack now due to that and it also helped us you know consolidate a few things that used to be separate things like you know you had a separate input library for various things and there are all no centralized into LibInput. Another big achievement I felt that we achieved was of course solving the problem that had been for years where you had the conflict between Mesa and the open GL stack there and then Vida driver which meant that you know depending on which package got updated the latest had things over writing each other and conflicting. On a more of course a polished front the recent thing for Dora 30 got this thing called flicker free boot where you know don't see your screen sort of flickering and then you know resetting itself as it goes through the different stages during boot instead you sort of have a clear steady path. On one level this seems like a small thing but once again based on the service we found like people one of the things that often gave people impression of Dora and Linux in general was it that it felt unpolished so this is also why we sort of greenlit Hans de Gøde to work on doing this. We put a lot of effort into integrating Qt into Dora Workstation because you know Dora Workstation is based on GNOME but there's a lot of applications out there using Qt so we spent time making sure we had teaming and that supported Qt to make it look like the rest of desktop but we also created a thing called Qt GNOME platform it makes sure that when you change things like when you switch to the dark team or if you enable accessibility or change your desktop font that it applies not just for GNOME GTK but also to your Qt applications. Another thing that we used to get dinged for a lot was the lack of codecs and of course there was a lot of legal challenges around that but we spent quite a lot of time over the last years making sure that we cleared a lot of these codecs still in use for including, to be able to include them on disk. So I think we have in terms of other codecs we have all the major ones now supported and we also got impact to video recently cleared so we can support for instance if you have old files from DVDs and so on that you still have around. For H264 we made an agreement with Cisco some years ago to ship this thing that I have called Open H264. The problem with that was that it only supported the low complexity format of H264 which is useful for videoconferencing but it's not what you want to use when you have like a playback of a H264 video file in a Matroska file for instance. So what we did there was that we actually pulled money from Red Hat, Cisco, Endless to pay Centricular which is consulting company to basically make sure we got support for these more higher profiles into H264 and that actually became available only I think some months ago but that means we also finally have a full featured Open H264 decoder available for for the users out of the box. There's still some things that you might want to try to do there going forward. I mean it's all software decoder at the moment and of course it would be nice for instance get take advantage of GPUs but that's what we have but at least we can play back things now. Yes, we also spent time improving battery life. I mean it was also the recurring thing we got a lot of feedback from is that people for instance who had been using Linux for a while and ended up for instance switching to Max. The common reason we often got quoted was that like well I just wanted a laptop that had long battery life. So we spent quite a bit of time improving that having general conversations with the vendors to make sure that they start taking ownership of ensuring that their laptops have good battery life and I thank you for your reference and look at things like the XPS 13. The battery life is absolutely competitive with comparable windows or Apple systems. When you use Linux on it. We had a Google Drive support that was also something we got feedback from a lot of users for that they needed. I least said that here is done because many times it has been available for some years already in Fedora but we are actually going to take another look at that now and see if we can improve performance actually a little bit because especially for large files it's a little slow the way it currently works. And then also we put in some work to make sure that Fedora works better as a guest in a virtual box because we know that there are quite a few developers out there who are on windows or Apple systems who rely on virtual box for getting access to a Linux system. So next steps. So another effort actually kicked off recently is that we have started so Red Hat has a quite close relationship with the University of Boston at Boston University and also quite a few universities in Bernal in Czechia. So we have started trying to use that relationship to basically try to tailor our solution a bit towards computer science students. So we are now doing user interviews and surveys and so on on some of these students with the goal of basically starting to have a feedback loop so that when we do improvements and changes in Fedora we will sort of instantly get feedback from them and I guess they also at least the two universities we are currently working with are quite different in the sense that at Boston University a lot of the students there are Mac users so we sort of get feedback from people coming from Mac to try Fedora while in Bernal I think it's more of a mix of either people already on Linux or Windows so we sort of get a different kind of feedback from them and we can use them to contrast and see of course what they haven't come in and where there are different things people are looking for. So in terms of major things going forward I think over the flagship effort at the moment is this thing called Fedora Toolbox and unfortunately the talk about that happens now at the same time as my talk and this is already available today in Fedora as I call it prototype here but it's basically like a first implementation and the goal of Toolbox is to just make using pet containers as easy as possible Toolbox is basically built on top of a lot of these other tools that we have available like Podman and so on but it tries to help you make it that easy to the setup a new pet container and log into it and know that you are in it because like let's say you have 20 terminals open we are just trying to make sure that you for instance know for sure okay I'm in this container now or I know I'm on the host and I just make you know give you visual cues for instance telling you where you are and also just make it easier to find the image you want is the goal of this project or plans for instance that currently it's where you have ease access to a Fedora image we also want to make an image available or it's called UBI the universal base image that is a rail based container so that if you want to do development for deployment on rail then you can pull in this and then develop towards it and we are also working with the team inside Red Hat working on AI ML to make a special container available easily that will provide all the tools to do AI ML development like TensorFlow and so on so at the moment as I said it's available and you can do some testing with it it's currently basically a big shell script but we plan on writing it in Go and once that's done then we'll start extending the functionality of it but of course we hope people will start using it already and start providing us feedback because as I said our goal is to make this the best way to work and part of our motivation for doing it was of course that if you run on an immutable system like Silver Blue or CoreOS then you don't have the ability to just install random packages or at least not easily install random packages on the whole system but instead you should work inside your pet container but but in some sense we want to go further than that too because our goal is to make using pet containers so comfortable that you actually want to do that even on a normal Fedora system because the advantage of a pet container is that you can set up your environment exactly like you want it without risking breaking your whole system so like let's say you for whatever reason need for instance a newer or older version of Relip C you can install it in your pet container and it doesn't affect anything but the pet container but if you try to do that on your whole system you may be asking for trouble another effort that's also been done for a while but we are going to start pushing harder is Fleet Commander Oliver is actually here he just finished a new version that has support for using Active Directory because up to this point we require you to have free API available to set up Fleet Commander however we got a lot of feedback from both people in the Fedora community and reddit customers that you know due to Windows being the predominant desktop in the company overall and they did have Active Directory setup so we added support for Active Directory now directly so we do expect a lot of people who have been waiting for this to deploy it and what Fleet Commander does is that it allows you to configure your desktop session on a per user basis centrally and you can create groups because based on your directory server so if you have like different teams inside Active Directory you can assign different profiles to each of them and I think when you saw the Facebook talk today they talked about for instance how they used these Chef scripts to change the screensaver settings and yes it is possible to use Chef for that but it's also if you look at the screen it's not obvious I think for someone who doesn't spend a lot of time with living systems how to do it while using Fleet Commander it sort of will be a purely graphical environment where you can click click through the desktop UI and set the settings you want and then just save that as a profile and then deploy it to the user so you want to have that profile Fleet Commander is also not a replacement for things like for instance like satellite or Ansible but I think it always stays like a compliment to specifically deal with the complexities of configuring a desktop session while you still need to rely on these other tools for if you want to have controlled rollout of packages and these kind of things which is not part of the area of expertise or goal even for Fleet Commander to try to do or that may have the ability to do On our to-do list there is to improve support for Firefox because we know that of course most people use Firefox or a lot of our red desk customers use Firefox because it's a one browser that we can ship out to the box with always the goal there is for Fleet Commander to be able to set things like default bookmarks and so on automatically centrally so that if you want to add a new bookmark to your new travel expense application and you can just deploy that through Fleet Commander and it will show up wherever it wants to bookmark automatically another thing you can use Fleet Commander for is that if you need to deploy a new VPN setting that's another thing we support there where you can say that we are removing the VPN server address so I don't want to deploy this to every user that they automatically get the new settings for VPN so I think this will Fleet Commander will be a very powerful tool for Fedora too because it actually gives us a good story for people who want to do this for the big scale deployments of Fedora and need to have certain things managed and of course when you end up trying it and deploying it, please give us feedback for features you want to add it because that's definitely also a big part of our next step there to figure out what are the gaps people feel they have compared to for instance similar tools for Windows and Mac. Flatback Ecosystem. So I talk about course Flatbacks has been I think a major project that we succeeded in doing and what we're looking at there now is to start trying to build out the ecosystem. We have a runtime in the works based on the universal base image and what it will give us is that we will finally have a runtime available for ISV to target that sort of LTS runtime. The goal eventually will be that the life the supported lifetime of the UBI runtime will be the same as the release you can expect it to be around for around 10 years and still get secured updates during that period. So for a lot of vendors who are interested in having a Linux version you know, interested in necessarily chasing fast moving distributions like Fedora currently is they can instead target this UBI runtime and they will have a platform that is going to be stable for years to come and then they can also just switch to the next UBI version once they're ready. We're also I guess from the red side working on figuring out how to do hosting of Flatback containers we're currently looking at both the Red Hat Container Catalog and also this Quay.io for possible places to host this so the goal also once again is for a lot of these ISVs you want to basically be able to provide them a place to upload their Flatback and it becomes available to users across well first of all of course Rail and Fedora but also any other distribution that wants to support Flatbacks We have also spent a lot of time making sure you can build Flatbacks in Fedora from over RPM the RPM content there Over the latest content is that we managed to get over 60 Flatbacks built from Fedora RPMs and we actually have an interaction at the moment focusing on that effort so we expect that by the end of the summer we will have significantly grown that number so that means if you are experienced Fedora Packager you can hopefully quite easily get into making sure that your application is built to the Flatback and becomes available to people across Fedora, Rail and of course any other Flatback using distribution available Fedora Silveblu Mattje mentioned that in his talk this morning This is an effort that of course is trying to use some of these same principles that are behind CoreOS and apply them for desktop use having an immutable OS image and of course the big advantage of that for here is that you basically get hassle for upgrades because I think for anyone used Fedora or any current distribution problem especially if you bring in third party packages into your system when you do an upgrade things easily go wrong but on top of that I think you also have seen in the past that you sometimes get problems because a lot of these packages have script that tries to manually edit text files and so on and sometimes especially if you have modified the text file locally things go wrong during the upgrade and then you suddenly have a system in a uncertain state which is also of course painful for anyone to support you on because they don't necessarily understand or know exactly what went wrong and what the current state of your system is but by replying on these immutable OS images that means that when we go from version to version we just do one upgrade politically centrally and we verify that at work and then we push that out to everyone just to work for everyone to go from version to other and even in a case where something went wrong let's say for instance there has been a regression in the kernel that means that driver doesn't work properly and more for your specific system thanks to using OS 3 in here we can actually do OS rollbacks too so that you figure out that hey actually you know this update breaks my system and then you roll back while a bug and once your bug is resolved then you can of course update to the latest version which should hopefully and once again work for you and we're currently focusing on closing functionality gaps with sort of a normal for door install because once again we want this to be a positive experience, right? We don't want to have people feel that you know they in order to get the advantages of having immutable OS images and so on they on the flip side get trapped so that's why for instance we have the toolbox for making sure you have a good development experience but we're also spending a lot of time making sure we deal with things like how do we get the driver installed in these kind of setups how do we deal with third party printer drivers and these kind of things so at the moment of course Silver Blue is a separate download and we'll probably remain some for some more time but you know eventually we hope to sort of say that the workstation is Silver Blue but that's further on the road and we sort of feel that yes we are confident now that Silver Blue is ready for mainstream use another feature that we will try to be focusing on for a bit now is high dynamic range for those who know it it's basically standard for having better color representation on screens it's becoming quite popular on high end TVs which we also see that a lot of laptops and computer systems are starting to have HDR capable monitors NVIDIA and Intel and so on are looking at this from their end the overall goal here is to provide a technical leadership to ensure that we get a unified solution that works across every vendor system but it also means that you know even once we have the hardware support in place we do expect that there will be plumbing needed up to stack all the way into the desktop shell to make sure that we correctly support HDR systems Pipewire is another effort that we are pushing forward the overall vision for that project is to make Linux the first class operating system for component creators as a side or in some sense the initial target for us there and where it's already deployed is of course handling video capture and screen sharing in Fedora the reason for that for that being a priority for us to resolve was that first of all with Wayland it does provide better security I guess a lot of you probably have been to talk in the past where you talk about how easy it is to basically do keyboard capture under X but with Wayland it has in some sense improved that but it also made things like dealing with video sharing and screen sharing a lot harder to do so we basically made sure we could bring in Pipewire to provide an API and a way to do that and we've been working over the last year making sure that the browsers have support for Pipewire to basically for instance when you run things like BlueJeans or Google video Google Hangouts to the video calls that you can then under also on Wayland get that working and you know you have video capture and screen sharing and at the same time of course on the application side where we are trying to move to flat packs we needed a system to enable people to get you know secure access to the video device from inside the sandbox flat pack so Pipewire also you know answers that question for us and provides a way to securely do that and also have multiple applications sharing on video device there without getting necessarily access to each other's content so that's already deployed but our next step that we're trying to focus on is bringing in a jack compatibility layer to flat packs which I think in terms of like you know the pro audio community has for a very long time been almost like a separate sub community within the Linux community but our goal is to basically make them first class citizens and make sure that you know you don't need to install and configure jack and figure out how it interacts or interoperates with pulse audio instead Pipewire provides a jack API that's API compatible with jack and so at least in theory every jack application should just work I think in practice when I was testing this I did discover that quite a few jack applications due to the way the jack has been working so far there's a lot of weird things like you know they try to search for a jack binary in a specific binary binary location and then auto start it and then connect it and so on and of course if you do that sort of things that doesn't work but if they just implement and try to talk to a jack server running on system then Pipewire should work perfectly as a drop in replacement our final step which probably is some time out still is to also be a replacement for pulse audio at the moment the way it's going to be working is that pulse audio will probably be talking to Pipewire so the current pulse audio application will be all this operative to Pipewire and we're going to handle it that way but eventually we won't be able to shut down the separate pulse audio daemon and just have one Pipewire daemon handling video, handling pulse audio use cases and handling the jack use cases yeah, one thing this also wants a bit of smaller future but we've also been looking at making sure we have a mirrorcast support so that's available for testing today in Fedora but it's a separate little test application we hope to sort of merge it into the desktop proper but I did notice that the TV set the hotel room here actually do have mirrorcast support so if you want to test it tonight you can just download the mirrorcast test application and try it in your room tonight ok, so I think that was what I meant to cover, as I said when I wrote the slides I expected to spend half an hour and I only realized half an hour ago that they had 50 minutes so I hope there's some questions here so of course we and my team don't necessarily have resources to support every possible option out there so I think what I'm expecting to be the outcome here is that once we iron out quality kinks and the challenges of doing an image based operating system with silver blue and gnome of course as part of that process we will resolve a lot of quality nor operating system level issues so that eventually for instance the KDESIG to be able to take over and eventually may produce you know a version of silver blue but basically the same kind of system with KDG on top I think due to the nature of systems you won't be able to install another desktop on silver blue so you will have to then install a different image and use that instead that said of course being image based systems I do expect that you might get to a point that if there are multiple images available switch between them might be really easy because they will probably be parallel installable and you can say that you can actually boot into any image now or exit the image now instead and they still share the same object and so on afterwards I don't think it will be from the login manager I think it will more be from the u5 boot manual but of course our focus at the moment is simply getting the silver blue image to a level where we expect people who are using workstation play to want to use it so call it extended future use cases like alternative desktops or other more major if I think this is not something we currently have any complete transport because we are full engaged just trying to make the service of the boot mainstream and usable with the full choices we already made No, we don't I think I have been discussing with Matthew Millie a few times whether it would be nice to actually get that so we could sort of see for instance how the transition is going The challenge we have there as Matthew mentioned in his talk is that by default we are trying to respect people's privacy as much as possible but that of course comes at a price of not really knowing what they are doing either which is good from a privacy perspective it's harder for us to then make good decisions based on having such data available so we will hopefully in the future come up with good ways to add more metering to the system so we can sort of figure out at this point 99% are using valent maybe that's a good time to start deprecating the X version or for that matter if you know that hey you still see that 70% are on X so we can obviously not deprecate it no kind of trade offs but at the moment we don't really have that data as far as I know from some weeks in philosophy the current plan is for the next fedora release to have it all to the box yes that should actually doable so if you want to have an aquarium or something behind you as a talk that should be absolutely possible to do as a filter in pipe wire similar i guess what phase time I think have that functionality right but yeah it's a pipe wire have the architecture to allow you to you know even if the application doesn't necessarily support it to actually say hey bring in this filter for me and give me a neutral background or an aquarium or whatever it should be that you would like to have there any other questions yes that is the plan I mean we have a talk actually about tomorrow alright yes we have a well it is I would say like this it is a definite our goal and we want to see it happen as soon as possible but as I mentioned on the slides here I mean we don't want to commit to a certain time for doing that before we are 100% certain that we have crossed off all the boxes that needs to be there because we don't want to sort of go after until the world you know switch now you know this is a new default and then you know 60% of people come running back to us saying that hey you know Skype doesn't work or you know whatever is the particular thing that sort of then makes the system not useful for them so we are trying to to sort of organically grow syllabi at the moment by having an alternative download and then once we this is also back to the question about metrics I think we are hoping to eventually be able to also get to metrics so once we see that a lot of people are on syllabi already and that we have been able to address at least the issues we are aware of then of course that would be the time we say that okay so let's for Dora33 as an example let's make syllabi over sort of default and then of course still keep the RPM version there but switch to default but at the moment I think we're still we're still not certain we're there or I guess we're certain that we're not there today to make that switch so we want to be certain we do that because I think you know in the past I think a good example there was the original rollout of pulse audio I guess in many ways it wasn't really ready for prime time when it was rolled out and it basically lost years of bad feelings towards it afterwards and we want to avoid that and I think when we did the transition to Wayland I mean on one level we wanted to do that a lot sooner than we actually did in Fedora but at the same time we were very clear right that we don't want to start saying in Fedora now is Wayland and then have nobody be able to use it in a functional way and I think at least based on what I feel reception was when we eventually did switch to default and the general comments that I see on various news sites and so on when people discuss it is that we succeeded in making the switch at the right time not that everything was perfect but at least it wasn't like everything was broken either you know, can often be a problem so that's the approach we take with Civil Blue 2 is that we're going to switch Fedora over or Fedora Workstation over to it once it's ready but not before now I think I have a feeling that in terms of like you probably would at least want to do re-install at some point just to get rid of the old system lying there because at some point you probably don't want to use it but I think also due to the way it works one thing we have been discussing but there's no concrete plans of doing is trying to maybe have some sort of application or tool for extracting some of your configuration and then being able to restore that configuration once you re-installed that's your Civil Blue system that would probably be a very limited thing if you end up doing it at some point like maybe preserve if you have some custom macro images or things like that and some configuration data but there's not going to be I don't think we will get to a point where we can sort of guarantee that everything on your old Fedora system some will make over it because especially the home directory could probably be left untouched so any configuration has stored there we might be able to reuse but if your instance then changes to slash ETC there's no way we can preserve those especially if it's sort of in stuff outside of desktop so I think the only question is we don't currently have any concrete plans for providing any tooling there apart from reinstalling and then re-configuring for bigger installations like for your not personal system and of course Fleet Commander could actually provide that where as long as you know all this configuration is under Fleet Commander it will then re-apply it once you switch to Civil Blue any other questions thanks a lot everyone I hope it was useful there's a Civil Blue talk tomorrow and I recommend going to that there was also a toolbox talk happening at the same time as this one so I recommend people to check out the video because as I said that sort of over flagship effort going forward thank you


So, for the last two or three years, my primary terminal file manager has been Ranger. And I enjoy Ranger quite a lot. It's been a very sturdy choice for me when it comes to file managers in the terminal. But it also has a big problem when it comes to image previews. A lot of times they just don't work. And you really don't know why. Either one of the dependencies is out of date or it's just stopped working for some random reason. And one of my primary reasons for using a terminal file manager is to set my wallpaper. It's really nice to be able to open up Ranger, scroll through all my wallpapers, and then hit a keybonding to set my wallpaper. But that only really works if image previews work because otherwise how do I know what the wallpaper actually looks like. So recently, when Ranger decided it was going to stop working again when it comes to image previews, I decided it was time for a change. And someone on my Discord pointed me towards a file manager called Yazi, which claims to be a very fast terminal file manager. Now I was very skeptical about this particular claim simply because we've heard it many times before. And while we have seen fast terminal file managers before, NNN and FFF, usually the way they gain that quickness, that fast implementation of their features is that they just don't have very many features. They do the basics and that's basically it. If you want to add more stuff, you would add it externally or via plugins or environment variables or whatever. And that usually ends up slowing the terminal file manager down a bit and therefore loses its quickness. Now Yazi does things completely different in terms of that because it's fast while also being very full featured. It's very much kind of like Ranger. In that regard only it's actually fast. So I decided I was going to give Yazi a try. I've been using it now for a week and today we're going to be taking a look at Yazi and I have some thoughts on it. So let's go ahead and jump into it. But before we do, if you leave a thumbs up on this video, I'd really appreciate it. So first let's talk about installation just real quick. If you want to install Yazi, you're probably going to have to build it from source. Now it does reside in some repositories. So if you use Arch or Alpine or you use Nix, you can get it fairly easily from those places. But if you use Ubuntu or Debian or OpenSusa or Fedora, you're not going to be able to download it from your repositories. Chances are now I don't know for sure whether or not you'll be able to find this thing in like the in in copper or not. I don't use Fedora anymore. So I'm not sure. But chances are you're going to have to build this from source. It's not hard, but just know that that's the case. Also, as you can see here, even if it is in your repositories, chances are it's going to be somewhat behind now. So if you do end up having to build it from source, you can do so from cargo either downloading the Git repository or getting it from crates. And it's fairly easily. I think it's just like two lines. So it's not hard to build, but just know that going in that you'll probably have to build it from source because it's not in a lot of repositories. OK, so let's go ahead and take a look at Yazi. This right here is Yazi. And if you were to just take a kind of broad view of it, it does look a lot like Ranger, which I found very comforting because it's not it doesn't it didn't present a lot of change for me when it comes to actually look and feel it moves around like Ranger. So if you do J and K, it will move up and down. If you do H, it will go back. L will go forward and things like that. It's a very similar experience in terms of moving around to Ranger and many other file managers, which is I found really good. But it does have some variation. And this was my first hurdle because there are some things here that are just a little bit different than Ranger. So, for example, in Ranger, you would hit D to move a selected file or directory to the clipboard. Basically, it would cut it. And in Yazi, hitting D will move it to the trash. It will ask you for confirmation, which is nice because I can't tell you how many times I've hit D expecting it to cut when it really was doing is trying to move to the trash. So that's one difference that I discovered. If you want to cut, you'd use the X key. X would cut it and then you could use P to paste. So that's a little bit different. Another difference is that if I go into my downloads folder here and I want to say open up this ASCII text file. In Ranger, I would hit L and that would open it up because it's kind of going along the file tree. In Yazi, it's a little bit different. I have to enter and that would open it up in VIM and I could do the things that I want. I could then save it and then move back to Yazi.  I'm not saying any of this stuff is wrong or bad or any of that stuff. No opinion on it really whatsoever. It's just as I went along, I noticed these things that were just a little bit different and I wanted to point them out to you guys so that you don't get caught like I did. Probably the best way to find those things is to go to the configuration file. And I'm going to talk about the configuration next because I think that that's the best way to show you some of the features. So, if I go back to my main home directory here and go to .config. So, if I do like so, here we are, config and then go in here and then it's in Yazi and these are the three configuration files that you can get from the website. Now, you have to get these from their hub page and then create them yourselves. As far as I know, these don't reside anywhere on the system. I might be wrong about that, but you do have to create them. Yazi doesn't create them like Ranger does. Ranger, when you first run Ranger, we'll create the configuration file. Yazi does not do that. I believe it's getting the, it just does the defaults when you open it up. If you want to do any of the customizations, you get the configuration files yourself. And these are the three that you are going to use. Yazi.toml will control the basic functions of Yazi. Things like how it sorts, how it looks, what things open, certain types of files, all that stuff is done inside of Yazi. And to be honest with you, I've spent the least amount of time in this particular file, simply because the defaults are fairly good. I will talk about a couple of defaults that are bad here in a minute, but other than that, I've spent the least amount of time in here. And really what you're going to go in here is you're going to, again, control the sorting, control the default application opening things and how it actually looks. So that's what Yazi.toml does. Theme.toml does what it says on the tin. It controls the colors. So basically, if we were to open this up here, you'll be able to see how Yazi is configured in terms of color. You can change these things. Now, I kind of wish that it just inherited the colors from the terminal. It'd be better, but you can just create your own theme if you want, just like so. And I do believe that there are some things that you can download online and if you wanted to use something different. Now, the one that I'm going to focus the most on in this video is actually the key maps because I think that this is the best way to kind of show you how Yazi works. So if I open up key map.toml, you can actually see basically how the syntax works when it comes to key maps. Now, I will say that they've done a fairly good job of segmenting this file so that all the stuff that goes together is together. So things like all the quit commands are right there. All the movement commands and navigation commands are right there. And they do a fairly good job of like I said, keeping all that stuff together. And the syntax isn't hard to understand. So even someone who doesn't know any configuration syntax that you use traditionally use can really pick this up very easy. It's not using things like VIM script. It's not using Lua or JSON, like hardcore JSON. I believe this is actually Toml file. So it's using Toml, but Toml is actually fairly easy in terms of kind of pick up in terms of syntax. It's not so hard that you're gonna get lost is what I'm trying to say here. So if you want to say, for example, control how the cursor moves up and down for a half page, you can do so in these key bindings here and you can just tell what this is. So this is control and you or control and D. This one here is shift down, shift up. So if you wanted to change any of these it'd be very easy to do. Now, these are just the regular key bindings that you'd expect them to have. So Q and capital Q, they quit. You can use escape to also escape visual motor. You can use page up and page down to move further up and down a list of files. You can use alt K and alt J to move up five units or five down in the preview. So if you use alt K and alt J, you'll be able to see that preview move up and down. Now I can't show you that because I use alt K and alt J for other things and those key bindings are in conflict and it will actually mess the entire video up. So we're not gonna do that but you can also use things like alt page up and page down. I also can't use that because my keyboard doesn't have page up and page down. So I'm on a little pickle there but if I wanted to change those key bindings it'd be very easy if I were to use that. Usually I just open up the file and do the things there. I don't have to worry about the preview but if you wanted to see the stuff that's in the file you can use those key bindings to do so. GG and capital G will take you to the top and take you to the bottom just like you would in Vim or any of their file manager that's inspired by Vim. Space will select the files. V will get you into visual mode or capital V will get you into another version of visual mode and you can use control A and control R to select all or unselect all. So I don't actually think that Ranger has that capability to be honest with you. I don't ever remember seeing control A actually working there but I might be wrong about that. So that's really neat to have. So in addition to using enter you can actually also use O and you can also use capital O to have an interactive mode. So let me actually show you this. If I wanted to open this particular file and something else if I use shift O it would allow me to select what I want to open that file in. Now in the yazi.toml file here there is a section called opener and this right here is going to be where you would define the options in that menu we just saw.  So say like genie or VS code or whatever you would define that option here in this file and then it would show up in that particular menu when you press shift O. As it is by default it will just show you the default editor or it will show the exit data. So you have to kind of put into work if you want to have that open with menu actually working well but as an option that's really cool. So right here is where it defines how cut and paste works and again it works a little bit differently than ranger so it doesn't use D it uses X. Yank is still the same and it works basically the same way it does in ranger as well. P is also does work the same way and it does allow you to overwrite files if they already exist by using capital P which is nice. You can also create links so you can create absolute and relative links using a key binding using this and that's really nice. Again I'm sure you can do that in ranger I've just never encountered that functionality before. Usually when I want to create a link I'll just use the regular terminal like the command line. So D will again take you and remove the files to trash capital D will permanently delete the file so you'll want to make sure that you always pay attention to those little pop-ups when you press that key it's going to ask you for confirmation that's definitely something that you're going to want to pay attention to because you don't want to accidentally delete stuff. So A will allow you to create a file or directory wherever you are in the file.  If you just leave the slash off it'll create a file presumably it'll create a text file or whatever extension you're going to put onto that. So if you wanted to create a Python project you do whatever.py or whatever and that would work. Another difference between ranger and Yazi is that it doesn't seem to use any of the function keys. So in ranger when you want to edit something you press F2 with Yazi it's R. So I think phonetically that makes more sense but it was something again that I had to kind of get used to. If you want to use a run a shell command it's a little weird. So by default instead of the just colon and entering the shell command you would use semi colon and you run the shell command. Colon actually allows you to block the UI until the command finishes. That way that you can't make any other changes. With the regular shell command it'll kind of run in the background and that's another thing that Yazi does is that a lot of the stuff that you can do if you run a shell command will actually run the background and it has a jobs UI. So if I actually get out of this and I press W. Yeah it's W. So it has a tasks UI. So if you have something running the background via shell prompt that you started from inside Yazi it will show it here. Now unfortunately you'd have to be quite zoomed out a lot of times to see the entire process. Also it doesn't, as far as I can tell actually show you the output of the command that's being run as it's running. So if you were like backing up something from here you decided to run rsync from Yazi using the shell option I don't think it's gonna show you the output. I may be wrong about that. I've never actually tried anything that's like that long but the few encounters with the tasks that I've come up with usually they're so stretched out along like one line that they kind of run off into the ether and you can't kind of see all of them. That's a little bit disappointing but other than that it's cool that you can run stuff in the background if you would want to on files that you're interacting with inside of the terminal. That's not again something that Ranger does all that well. It does do some things in the background. You can use shell commands but a lot of times it just runs them and you have no indication of if they're running. Again it's possible that Ranger has that functionality you just kind of have to set it up or maybe I missed it all these years because I never run a lot of shell commands from the terminal or from the file manager so it's possible it is there and I just didn't know about it but this kind of sets it up front and center. S and capital S will search the files by name using FD. You have to have FD and rip rep in order to actually use this functionality. I believe I actually do have it set up so if I quit this and I use S it will allow me to search. You can if you want you to use slash that will also allow you to find. Find and search are slightly different things in terms of what they actually search through I believe so you'll want to if you can't find one with one you probably want to use the other I think search is the more broad tool it'll allow you to search more broadly than find will. So that search you can also cancel an ongoing search or jump to a directory if you have Zoxide or FZF installed using Z. You can also control the line mode so you can select the change the line mode side using key bindings. You can also copy the path using CC or CD which would copy the directory name or CF would copy the file name or CN would copy the name without the extension. That's all stuff that's built in and really awesome as well. You can also filter the files using F and you can also control how things are sorted. Now I think that this is a good time for me to talk about sorting because out of the box out of the box of sorting is really actually quite weird.  But for me personally out of the box the way that it sorts is they sort it by most recently used first. And that means that your file lists change all the time. This is the biggest difference that I saw between Ranger and this and it would really, this was the thing that bugged me the most out of the box because that's just not the way that I want things done. I want to be alphabetical and that's just the way that I've always used it. Now again it's easy to change but out of the box they do sort it by most recently used first. Now here's the weird thing and if we go back to Yazi so if I go to Yazi again just using the find thing and go here to the Yazi.tomophile we can actually see up here at the top that it allows you to choose what you sort it by. And that's all well and good. You can change alphabetical but if we go back to see how this works we can see it specifically in a very long directory full of files and directories. You can see that if it sorts them still kind of weird so it does take into account for whatever reason capitalization. So it puts all of the directories that are capitalized first and then it starts over again. So we got zero B then CG all this stuff. We go through the alphabet and these are all capitalized and then it starts over again with the directories that are named not with capital letters. And that means it's just a very weird sorting mechanism and while there's probably a way to change that I haven't discovered it quite yet and it does bug me a little bit because I want them all just one gigantic alphabetical list and I can go on about my day. That's the way that I want it. And it's not that way. Sorting it by most recently used first just no that's not the way that I want my files to be sorted. Again, very easy to change but it bugged me a little bit. Now if you want to dynamically change your sorting you can do that with key bindings very easily. So you can sort by directory first reverse directory first you can start by date first you can sort naturally you can sort alphabetically by size by extension by created time all that stuff you can do via key binding but that stuff's not persistent it will change back to the default when you next time you open up Yazi. So you can change it fairly easily but just know that you're gonna be messing around with the sorting probably the first time you use this because it's not going to do things the way that you probably expect them to be done. Now just like Ranger it does have tab functionality I can tell you I can count the number of times I've actually used tabs in Ranger on one hand. Now if you know me that's a little weird because I do enjoy my tabs but I never really found the need for tabs in Eternal File Manager. Maybe there's a reason good reason to use those and I just haven't discovered yet and when I do I'll become a tab fanatic in a terminal file manager but I'm not there yet. Now in like Crusader I use a ton of tabs like it's crazy these are all my tabs I have a ton of tabs open and that's all great and good but in a terminal file manager I've just never found a reason to use that. Now just like with Ranger you can set key bindings to go to certain directories and some of them are created for you. So GH will take you home. Now I have a different home directory as you saw in the last video or in one of my previous videos so I've changed it to change to my new home directory. You can also go to GC to go to your config directory you can GD to go to your downloads GT to go to the temp directory and so on and so forth. I've also created one thanks to someone to Fraggle in my Discord that helped me create disk binding right here. This is the only key binding that I've actually added myself and this will allow me to change my wallpaper. So it does do it a little bit differently than Ranger again in Ranger if you want to have a shell command affect a file that you've selected inside of the file manager you use percent F in Yazi you use traditional variable expansion to do this. I think that's what it's called, right? So you use dollar sign one and that will tell Yazi to expand that particular section to the selected file. So in this case it's going to take the image that I've selected and use SWW to actually set my wallpaper. So you can create your own key bindings and I've done so in this case and that is a good thing because it allows you to expand the use of your file manager to actually suit your needs something that I did a lot in Ranger and I'll do a lot in Yazi as I use it more often. So that's the basic functionality of Yazi going through some of the key bindings I would highly recommend you guys if you're going to use this spend some time in the key bindings file change things to suit your needs just a little bit if you need to I'm going to do that a little bit more as I go along I didn't want to change the defaults because I knew I was going to make this video so definitely change these things if you need to change them and it's actually fairly easy to do. So I will say that if you need help you can press shift and then the tilde key and that will give you all the key bindings from wherever you are inside of Yazi and then you get escape in order to get out of that. So if you don't want to spend the time in the Tomo file but you just need to see what a key binding is you can get to them very easily you can also change that so I'm more used to shift and then the question mark to get to help or you could change it to the function one key if you're more used to the VimWave getting to the documentation or the help so you can change that if you want because it's not hard coded it's directly in the key binding or the key map Tomo file you can change that very easily. So that is Yazi and it's a very good terminal file manager I'm going to be sticking with oh actually I didn't show you guys the actual image preview because it does have image preview built in so I should actually show you this if I go home and go to pictures and then go to my wallpaper directory here and if I just go through these you can see it's actually not showing you okay we got a fixed Wayland again got a Dag Navit why does it do this to me? Okay I'm leaving this in by the way so you guys can see this is right here is why I prefer XOR all right we'll go here and change select the monitor again why is it doing this? Okay here we go now I can show you the image preview okay oh all right I am definitely leaving at least one of those in so as you can see the image preview works just fine and it works way better than Wayland it works way better than Ranger inside of Wayland so if you're using Wayland like I am for however long this lasts you can see that it does work fairly well and that's really nice so if I wanted to and just to show you that keep running that I created if I do shift W I can actually change my wallpaper to this and that will then have changed my wallpaper which is really cool right so yeah that is Yazi I'm not gonna actually be able to show you guys this again because I'm gonna change back to my face here and that will mean that my screen capture has gone away for whatever reason because Wayland is just the worst it's the absolute worst anyways that is Yazi it is a very good terminal file manager and I will be using it from now on I've switched all of my key bindings over to it I've started to work through that key bindings.tomophile to change things the way that I want them to change or I will be changing those things and cause I have some ideas how to do things a little bit better I'm gonna change it so probably the D key does the thing that I want the D key thing to do I'll probably change the help so that I can get to it via the key that I'm used to using to get to the help and all that kind of stuff and it's just kind of over time I'll make this thing mine and I do really find that it is quite quick but the problem with that is that I never found range or slow so it's not that big of a deal in terms of the quickness but it is a very fast file manager and I like the tasks background thing that it allows you to do so you can run things in the background I don't know that I'll ever use it or not but I like that it's there all these things kind of add up to being a very good start for terminal file manager the fact that this thing is only like probably six months old or so I think that they said it was like three months old in December I could be misremembering that but it's not a very old project at all and the fact that they've gotten this far with this file manager in that amount of time is very very impressive and I'm very excited to see where it will go in the future because they're only gonna get better and add more features and stuff and I know I'm no longer looking at the camera because everything messed up I don't know what I'm doing with Wayland seriously but anyways that's it for this video if you have thoughts on Yazi you can leave those in the comment section below I'd love to hear from you you can follow me on Mastodon or Odyssey those links will be in the video description you can support me on Patreon at patreon.com slash TheLinuxCast you can also head on over to the store which is available at shop.thelinuxcast.org there you'll find T-shirts and hoodies and hats and desk mats and all sorts of stuff all the proceeds for that goes directly to help the channel I'd really appreciate it if you head on over there and give it a try I have a lot of awesome merch shop.thelinuxcast.org thanks to everybody who does support me on Patreon and YouTube you guys are all absolutely amazing without you the channel is not anywhere near where it is right now so thank you very much for your support truly do appreciate it you guys are awesome again thank you so very much thanks everybody for watching I hope you have a wonderful week and I'll see you next time


Give someone the gift of your time and attention or To do something that gives them more time and attention for themselves Does someone in your world need you to take some pressure off them? So that they can go to the gym or go for a walk or have a night off or have a lie in Or go for a massage or go for a pedicure or a manicure or all of the above I wonder if a gift of giving someone Some space some room that makes them feel seen the gift of feeling seen is what that would be I Wonder how many of us could do things like that. It would cost you nothing or it may cost you something I don't know. Maybe you're gonna pay for the manicure or the massage I don't know. Maybe it will cost you something, but the bigger gift is that you see that they need that from you and The sacrificial cost of that to you is your gift to them Perhaps will be a great Christmas gift idea for some of you and they'll thank you for ever be the best Christmas gift Some people have ever had from you Love you guys. Have a great Christmas. I'll speak to you before then But this is one of my Christmas musings. I thought I'll pass on to you. All right. Cheers


In recent years, digital dentistry has become increasingly popular due to advancements in technology such as CAD slash CM and medical imaging. This allows for more accurate and efficient treatment plans, as well as improved patient outcomes. Additionally, telemedicine has been found to be effective in providing remote consultation and successful treatment of patients. This article was authored by SV Kazumian, IA Degtev, Vivi Borisov, and others.


There is an internet forum called NeoGaF, one day in the NeoGaF forums. Somebody decided to make a thread about this game, Imagine Babies Fashion. This guy, his name is Kriahoga, at least that's his internet name, and he said he just innocently tried to start a thread about Imagine Babies Fashion. Dude, I like this game, it's pretty cool, does anyone else play it? Yeah, he was completely, he liked this game. It's a game where you dress up babies in different clothes. I've never played it, it could be good, it could be bad. I have no idea, I can understand how someone might like dress up. I mean like, you know, most games it's like City of Heroes, right? It's dress up when you're making your characters. They're just, the characters have no babies.  Anyway, he legitimately liked this game and he posted a thread. Now as you know on the internet, if someone said that they like a game like this, people might respond.


What's going on everyone? Sam here with LaytonSportsGuard, Trippin' 22, Peninidonis Optic Football Retail, 6-Box Break for 6 random team style. So looking at your random results as always, combine these on the website under the results tab as well as the link in chat. Good luck everybody, let's do it. Again guys, schedule is a little funky tonight. If you have any questions about breaks that are going, we're doing a little out of order tonight. We're just kind of going to break what's full so we don't inconvenience more breaks than we have to inconvenience. Good luck. Two Optic Retails, going to knock those out, Kyler Gordon. Got four to go on a Penini One full-case, 20-Box case divisional as well, Nicoby Dean. That is Cam Jordan, Rising Suns. That is Lighted Up George Pickens, rookie. Hello, Mark Ingram, Wandaille Robinson. Hello, Gabe Davis, Jaylen Colbert. Do I have a full sellout promo running tonight? That is if everything does get sold out. Legendary logos, Killa Trab. Hello, Brock Purdy, my house. Brock Purdy, rookie. Face rookie for the Niners, very nice. You guys now have just eight to go on that, Chronicles Break, Blue Stars, Buda Baker. Got to get that filled on up. Just going to keep grinding through breaks tonight, Greg Dulsic, Blue Stars, Amari Cooper. Again, Chronicles Football, PYT, those teams are on sale tonight, guys, too. Roger McCreary. Those teams are on sale. If you would like a Chronicles Football hobby, my girlfriend bought one. So, there you go. CMC, Blue Stars for the Niners. John Mechie, Texans. Leonard Williams, Blue Stars. That is a Ike Mikawanu, Blue Stars. Matt Corral. And Carson Strong, Blue Stars. So I'll do it for box one. On to box two now. Bryce End with two in Chronicles' draft picks. Thank you, Brent. That's found at 18 to go now on that second Chronicles' draft picks half-case. Again, that was inherited from this morning. Channel two. Who has it this time? Trent McDuffie. Niners is Skyler B. Skyler B Vinny is interested in the Blue Stars CMC. That's the Rookies, George Pickens. If you're in chat, Skyler, or if you're watching the video. Derek Henry, Dominators. Hello, Derwin James. That's a Sam Howell-rated Rookie. Hello, Rokwan Smith and Kenneth Walker. There's a retro series, B-Doc, Weapon X, Brian Dawkins for the Eagles. Boye Mafe. Mike Dicca. Martin Emerson, Rookie. Blue Stars, JC Horne. Snoop Conner, Rookie. Blue Stars is Zay Jones for the Jags. Zay Jones. There's a Donovan of Mab on your Blue Stars. Yes, Vito, they are guaranteed one per case, but it's a 24 box case as opposed to a 12 box case in retail. Miles Sanders, so they fall much, much less commonly in retail because the cases are bigger. But you can also pull mythicals in this one as well. That's Jake Ferguson. Blue Stars, Kyle Hamilton for the Ravens Rookie, nice. And Blue Stars, Montrell Washington. Rookie for the Broncos. Very nice. I'm getting guys down to just 8 to go on Chronicles Basketball Random Team Style. 8 to go. Let's get that filled on up. One second here, everybody. Check one thing. Drop the B with a spot in the select mixer. I found a 14 to go now. Select Chronicles 6 box mixer. Like I said, that is down to 14 spots to go. I'm going to get ripping on that. A show. Roger McCreary. Sam Howell. Dominators, Joe Burrow. James Cook, the Rookie's Cook Rook. Hello, Lageria Sneed. And a Boye Mafe. Also have Chronicles Football PYT tonight, guys. Teams are on sale. There's Warren Moot. We've got Chronicles Draft Fix. We've got a full case, 20 boxes. Ranron Division Style, Panini 1. We have that select Chronicles 6 box mixer. And we also have 2020 Bowman 4 Boxer. Antonio Gates Hollow, John Mechie. As well as a 2 box mixer of 2020 Bowman Draft Super Jumbo and 2020 Bowman Jumbo. There's Ronnie Lott and Kobe Dean. Blue Stars, Nick Bolton. Jake Ferguson. No autos in this. Either there's none, Micah Parsons, or there probably are some, but they're really hard to hit. Like I did a full case of this. Joe Namath like 2 weeks ago and they hit a single auto in 24 boxes. Tyler Algier Rookie. Didn't hit a downtown. Hit a burrow downtown, though, in that case. Trent McDuffie. Blue Stars, Fletcher Cox. He's actually scored another run. Wow. Romeo Dobbs. Let's go Yankees. Nice. Blue Stars, Purdy. Nice one there. It's a taxi. Not every spot's been sold so far. Lante, Taylor, Blue Stars. Once all the spots sell, then it's on the schedule to be ripped pizza. Anthony P with a Chronicles spots. Zeke Hill with 2 and number 14. Tyler with the Bears in 34. Jonathan B with a Prism spot. So we're down to 7 to go now in Chronicles. No problem. Pizza. You got it, buddy. Assuming that's River, potentially. I was emailing with earlier today. 7 to go in Chronicles, guys. Again, if that fills up, we'll rip that first. If not, we'll go ahead and rip Chronicles draft picks. The first half case of that. That is full now. Eric Azucanma. It's Justin Herbert, light it up. Hello, J-Mo. Jermaine Johnson. It's Eli Manning, Rising Suns. Hot House, Aaron Donald. It's a whiff from Shohei. Jay Jedis, Kyle Phillips. That is Desmond Ritter, Legendary Logos. Devin Lloyd, Rated Rookie. Blue Stars, AJ Villain. J-Mo. A Trayvon Walker. Blue Stars, DJ Moore for the Panthers. Blue Stars, Joshua Jacobs.  Him and Barclay didn't sign their franchise tags. Traylon Berks, Rookie. Stop Higgly. Ty Chammer. Tony O'Gibson. Blue Stars. Sam Williams, Rookie. Blue Stars, John Mechie. And Blue Stars, the Kobe Dean. Justin with the Chronicles spot. Justin, Matthew with some national break spots. Chris B with a national break spot. The Tigers. And Prism on Friday. We're down to six to go. Six to go, everybody, on Chronicles number 13. Six to go. Let's get that filled up, guys. We're almost there. Josh Pascal, Rising Suns, Eli. Giant. It is lighted up Herbert. Deron Payne and Traylon Berks. Hello, Jared Goff and Trayvon Walker. Rookie. Yeah, guys, six to go on Chronicles. We're looking potentially next, Aaron Donald. If not, we'll go on to the Chronicles draft picks. Six Boxer as well. Desmond Ritter, Legendary Logos. That is Ty Chammer. Rookie. Blue Stars, AJ Dillon Packers. Blue Stars, DJ Moore. Geez. They said a ground roll double. Evan Neal, that went like over the left field, like the left, like the side by like the third baseline. It went over that wall. Look. Ridiculous this is. Josh Jacobs. Oh my God. Dude, Chris Olave. Come on us, Waldo. Dude, how does that happen? You've got to lay out for that. There's Tyler Elshire, Blue Stars.  Oh, it's Waldo. Eric Azucon, my rookie. That's so tough. Antonio Gibson, I'm going to get Clown by Vaughn for that one. Kyle Phillips. I can't even imagine what the crowd was saying when that just happened.  There's Romeo Dobbs. You did get Papa Dingold on that one. Good Lord. More spots coming in. Peyton with a Chronicles spot. Kevin with two T-malls. And Alex with a Mixer spot. 13 guys. Five to go. Let's get that filled up. And we also have a full-case Pinini one, random division style of football break-in. Later tonight as well. Got to get that filled on up two. Zemir White, a Kyron Williams. James Cook, on the rookie. Sauce Gardener, Great Iron Kings. Hello, Odafe Owe, Kyle Hamilton, rookie. Full for the Ravens there. Richard Sharpe. Mike Kosicki and Jeremy Rucker. Do you see who they're potentially replacing Sharpe with on Undisputed? Who? It's awesome. Mattrell Washington. What's it called? Richard Sherman. There's White Hot Rookies kind of pick it because they hate each other. Richard Sherman hates Skip Bayless. I'm not a Skip Bayless fan. No, I'm not either. Probably not River. We're not really following a schedule tonight to Forrest Buckner. We're breaking what's full. So we still have a couple of Chronicles basketball breaks that need to be filled up. Those will go. We have a Chronicles draft picks that'll need to go tonight as well. That's already full so that'll go before it. Carson Palmer. But they will go tonight. It's a matter of probably not till a little bit later. There's Derek Henry. Oh yeah, sure. That is Skymore. For, once this breaks over, I got you River. There's Chris Godwin. Carson Strong. That is Jalen Tolbert. And Last Pack. Blue Stars. Greg Dualsich. That'll do it for the break, guys. Thanks again for the fill. Coming up next is either draft picks or Chronicles. Thanks again.


Hi everyone I'm with the winner of the 2016 NCHA 5000 novice world champion Tom Long he's from Nevada and he rode he's got to be good congratulations to you Tom. Thank you. Now this was a tight tussle coming into this this race essentially. You were in second tell us how you were feeling at the time. Well it was it was a race for quite quite a good while and coming here we there were three horses that could have got the job done and it was going to just how the chips fell was what was going to happen and I was fortunate enough that the first run to to have a good run Gavin who was leading it his little mare had just come back from being injured and wasn't really ready okay and she just didn't perform to to where she could okay well that gave me the the difference that day to go ahead and catch him okay the last day of the deal it's it's knotted up tight tight with three horses and by what happened the first day and I I was third the next day Gavin was second but the average is what made the difference on the on the whole the whole weekend Mike won the the show championship here okay but he ended up third to to man Gavin in the deal okay and it looks like your consistency paid out you had a two nineteen and a half and a two eighteen and a half so um that's probably got you over the line well it and it did you know and and that little horse is that way he's been that way all year for me you know he may not make the twenty five run but he will be right there knocking on the door and he doesn't he's a real real cow horse little guy and a guy and he doesn't make a mistake on a cow so that I think that's what carried him through this this deal here especially coming from my country we cut a lot of steers out there and they're a lot different than these little quicker heifers down here and being the fact that he reads a cow like a border collie I think that made that transition where he could stay and be consistent instead of you know if you make one mistake down there with the caliber of horses that were there you're going to be out of the cutting okay and he was able to be just head to head at all the time and that's what those guys were looking for you know a clean clean run and some physicalness was going to get you there and that's what he did so how was the whole year was it back and forth between the three of you Mike Wood and Gavin Jordan all year long all year long it would be and and Gavin has helped me all year okay and I am in his corner all year and he'd win one I'd win one he'd win one I'd win one or he'd just take off and be a genius and win for five or six days and really make me mad but he helped me all year long with this deal and and we knew coming here that it was going to be a shootout between the the deal and I guess you know if you're going to Super Bowl that's the way you want it to be you know so it's fascinating aspect of the sport that you do help each other and that even though he might have lost he can take a little bit of pride in the fact that you won because he was a small part of that and vice versa oh it he was he was fantastic this week especially in that last run because I drew deep in in that set and he was instrumental in finding the cattle that I needed to and he'd already made a lead and run okay but he was still trying his butt off for me to have a run that could beat him and I had good enough run I didn't beat him but I had a good enough run to make my average beat his okay so you got you got to take your hat off to guys like that and that that's the main thing that cutting is really about is the camaraderie that we have here because we try to make the other guy beat that's kind of crazy but you know why am I taking money out of my pocket well you've helped me so I'm going to help you you know and I don't know another sport really works that way quite honestly you know so tell us about your horse and how he got the name well he actually is the first colt be born by my stallion which his cat's got a diamond okay and he's out of a dual ray mare and when he hit the ground his next name's Benjamin okay and there was a movie that was on benjamin packer some darn thing where this guy looked mature as a baby but when this colt stood up I mean he just looked just like that stud and he looked like an older horse okay so my grandkids nicknamed him benjamin okay well he ended up with a different registered name and phyllis sorbet who owns the colt she didn't like the name and I didn't either okay so she got to talking and say hey we can change that which I didn't know you can before we show one for not very much money so she starts thinking about names and they're writing these all down and the whole deal and she's on the phone with me one day and and she said you know we've got to come up with a really good name and I said phyllis look this colt has got to be good he really does with this combination he's got to be good and she just stopped on the phone and says well that's his name and boom she just sent it in right then so that's where he came with he's got to be good so fulfilling destiny oh and you know what the nice part is that it worked you know it'd been terrible if it had been a dink you know I'm I'm riding on the horse well you wished he was got to be good but I think it's a great tribute to that little horse that he he stayed sound all year long and for that much time we were doubling on him and he just he just kept trucking kept going so he's going to get a little time off now he's earned it thank you very much for joining us Tom congratulations thank you very much for having us


It is essential that our officers are equipped with the tools, training, and technology necessary to do that job safely. If we were not willing to move forward and use technology, then you would not keep up with those who are doing harmful things to hurt New Yorkers. Friday's decision was about one thing, controlling women's lives. You have my word as mayor, the largest city in America. You will do everything in our power to fight this ruling and defend the rights of women. We needed a maestro. We needed someone that understood, had to track record, and we were fortunate that we were able to find someone right in our own backyard. Rats are the symptom of systemic issues, including sanitation, health, housing, and economic justice. You can't just deal with one part of the problem. There's a new sheriff in town. And with your help, we'll send those rats back. If we move forward, we don't really acknowledge who we are. You are fighters. You are warriors. As long as I am mayor of the city of New York, we will come into this place and acknowledge the rich history of this powerful community. As the mayor said, Broadway is the reason that so many people come to New York. I'd like to just say thank you. Thank you very, very, very much.