Item number, SCP-622. Object Class, Euclid. Special Containment Procedures. All cans and containers of SCP-622 are to be immediately transferred to Site-16. The formula for SCP-622 must be contained from the public by any means necessary. Any commercial trade of products containing SCP-622 should be documented and preferably intercepted before delivery. Any persons or organizations in possession of SCP-622 are to be taken in for questioning. Handling SCP-622 will require seal-proof gloves, hand lotion, and at least one canteen of water per personnel present. In the event of a containment breach, the immediate area affected by SCP-622 is to be quarantined for no less than 24 hours and hosed down with regular water shortly after. Addendum 622-1. In light of tests 622-1 through 622-3, all future testing of SCP-622 must take place outside of Site-16's air circulation system. Addendum 622-2. SCP-622 is not to be used outside under any circumstances. Additional containment procedures are only available to security level 4 personnel and above, as per protocol description. SCP-622 is the chemical composition data expunged, also known as developed by the chemical company under the trade name Desert in a Can. SCP-622 was originally marketed as a security aid for large businesses to incapacitate intruders in a similar vein to tear gas or pepper spray. According to f*****g chemical company, SCP-622 also doubled as a cleaning agent and insecticide, but due to its hazardous nature, chemical company was shut down in 19 f*****g before any more products of this nature could be manufactured. As of f*****g, there are at least f*****g documented cans of Desert in a Can remaining, most of which are still in possession and used by the following companies. According to the directions, one layer of SCP-622 is applied to hallways during a break-in or robbery. When applied, SCP-622 becomes odorless and colorless. On application, all moisture in the immediate area is absorbed by SCP-622, creating an easily cleanable salt-like crust over the applied areas, identified to be the compound sodium chloride, magnesium sulfate, and f*****g. When SCP-622 is exposed to organic life, the immediate effects are dehydration, dried eyes, and profuse sweating, which is quickly absorbed by SCP-622. Other effects include a significant drop in blood pressure, increase in heart rate, dizziness, and chills. For more information, see Test Log 622-3. According to the cans' warning label, SCP-622 dissipates after 12 hours, but according to Test 622-1, SCP-622 can last up to 24 to 36 hours. Tests 622 and 622-3 show that SCP-622 will only dissipate in 12 hours when security levels 3 and up refer to Test Log 622 and 622-3. Test Log 622-1 Inorganic testing of SCP-622 to determine shelf life of chemical compound data expunged in an isolated environment. Procedure SCP-622 applied in isolated hallway K1 and viewed through remote monitoring devices. Moisture measured and monitored by electronic instruments. For control, hallways K6 and K7 were also monitored for humidity content, averaging at 20% relative humidity. Results In 12 hours, relative humidity around SCP-622 remained unchanged at 0%. Despite the label's claim of dissipating in 12 hours, the area did not rise in humidity. It took until nearly 26 elapsed before the relative humidity rose to 1%. The relative humidity stayed at 1% for nearly an hour more, slowly rising to 2% after the 27th hour. SCP-622 did not completely dissipate until 35 hours and 28 minutes. The final relative humidity capped at 19%. 19.26% with significant figures for the next 4 weeks and remained there as of writing. It is undetermined if it is a result of SCP-622 removing all excess moisture from the construction phase of Site-16 or if there is a chemical component that does not dissipate. Test Log 622-2 Inorganic testing of SCP-622 to determine shelf-life of chemical compound data expunged in a controlled environment. Procedure Before SCP-622 was applied in hallway KV, 4 buckets of water, equivalent to the water content of an average human being, were placed in the aforementioned hallway. As with Test 622-1, hallway KV was isolated, applied with SCP-622 and viewed through remote monitoring devices. Procedure measured and monitored by electronic instruments. For control, always K6 and K7 were also monitored for humidity content, averaging a 20% relative humidity. Results In 12 hours, all 4 buckets of water were completely dried up. The relative humidity stood at 12% until 25 hours had passed, finally capping at around 19%, 18.87% with significant figures, after 35 hours elapsed time. When applying significant figures to the control rooms, the average relative humidity has dropped from 20.24% to 20.17%. It is unknown whether this is directly a result of SCP-622, Site-16's air system or a combination of the two. Test log, 622-3, Organic testing of SCP-622 to determine shelf life of chemical compound data expunged in a controlled environment. Procedure 2D class personnel were requested by Dr. Z. Subject D-254, Male Caucasian, 24 years old, 87 kg, 169 cm, was given a canteen of water prior to entering Hallway K-255, Male Caucasian, 46 years old, 92 kg, 172 cm, was not given any water prior to entering Hallway K-255. As with tests 622-1 and 622-2, Hallway K-255 was isolated, applied with SCP-622, and viewed through remote monitoring devices. Moisture measured and monitored by electronic instruments. For control, Hallway's K-6 and K-7 were also monitored for humidity content, averaging at 20% relative humidity. Results Almost immediately after entering the affected area, both subjects complained of exhaustion. Subject D-254 immediately began drinking from his canteen. Subject D-255 attempted to struggle with D-254 over the canteen, but found himself too weak to fight. D-255 starts visibly hyperventilating around 8 minutes elapsed time. D-255 collapses at 10 minutes elapsed time, and does not get up. Subject D-254 notices a visible mist coming off his canteen, reports his water is evaporating, and needs more. Agent P sent in to give him more water, reports on how dry the air is. Subject D-255's flesh is visibly red. At 15 minutes elapsed time, Subject D-254 runs out of water, complains about being hungry. Agent P returns with multiple bottles of brand sports drinks, a bucket of water, and several granola bars. Subject D-254 was seen dunking his head into the bucket of water, before pouring it on himself, and consuming sports drinks and granola bars. The water on D-254's hair and clothes immediately dried up. At 26 minutes elapsed time, Subject D-254 collapses from malnutrition. For the next 10 hours, the bodies of D-254 and D-255 continued finally reaching the skeletons. The clear salt-like crust from the evaporated moisture had turned to a mix of dark red and brown. The average relative humidity remained at 14% until 35 hours elapsed time, averaging at 19%, 18.56%, with significant figures. When applying significant figures to the control rooms, the average relative humidity has dropped from 20.17% to 19.96%. Note, I think it's safe to believe that SCP-622 may have some sort of chemical component that still lingers long after SCP-622 has dissolved. For future reference, let's do all testing outside of Site-16's circulation system. Dr. Z Test Log, 622-4 Organic testing of SCP-622 to determine shelf life of chemical compound in an outdoor environment. Procedure, SCP-622 will be applied to a small patch of grass on the Site-16 testing Biosphere-7 and viewed through remote monitoring devices. Moisture measured and monitored by electronic instruments. For a control, testing biosphere-2 and 1 were also monitored for humidity content, averaging at 68% and 73% relative humidity respectively. Results Data Expunged Sea Addendum 622-2 Security Levels 3 and above refer to Document 622-A and 622-B Test Log, 622-4 Organic testing of SCP-622 to determine shelf life of chemical compound in an outdoor environment. Procedure, SCP-622 will be applied to a small patch of grass on the Site-16 testing Biosphere-7 and viewed through remote monitoring devices. Moisture measured and monitored by electronic instruments. For a control, testing biosphere-2 and 1 were also monitored for humidity content, averaging at 68% and 73% relative humidity respectively. Results Within the first minute of exposure, the humidity of biosphere-7 dropped to 0%, forming a brown crust along where 622 was sprayed. Within two minutes of testing, all flora within biosphere-7 had shriveled up, turning into a salt-like compound, similar to SCP-622. All of the mud within biosphere-7 turned to dry, cracked dirt. After three minutes, security notified testing staff that the surrounding plant life of Site-16 was beginning to turn brown, outside of Biosphere-7, despite the airtight nature of the biosphere. Site-16 staff dispatched to surround the area and stop SCP-622 from spreading. After five minutes, SCP-622 was covered over 0.017 square kilometers, spreading at an estimated rate of 0.2 kilometers an hour, or roughly 3 meters per minute. Site-16 proceeded to dump water on the surrounding area to stop SCP-622 from spreading. SCP-622 quickly absorbs all water and continues spreading. Site-16 command level staff immediately requested to enact Protocol Gray. 05 approves. Protocol Gray enacted. Security Levels 3 and above refer to 622B. Security Levels 4 and 5 refer to Protocol Gray containment procedures. A message from 05 to General Staff. As many of you are undoubtedly aware, SCP-622 has broken out of containment at Site-16. While this does pose a possible threat, leading to an eventual NK-class gray goo end of the world scenario, Foundation staff are doing their best to contain the problem. Site-16 staff have enacted Protocol Gray to slow the rate of SCP-622 spreading and are currently looking into how SCP-622 was able to breach the biosphere testing facility. To help alleviate fears, here are a few facts that we would like you all to know. All of the biological SCPs at Site-16 have been secured and transferred away from the spread of SCP-622. These will be slightly more cramped, but the situation is under control and all of the SCPs are in proper containment. As of 7, 18, 12, SCP-622 has only spread a total of less than three square kilometers and the rate has slowed, thanks to Protocol Gray. At the rate it's going, it will only be able to overtake Site-16 in seven years. Even then, we still have plenty of time before it reaches any urban areas. SCP-622 can be slowed down by water, especially fluoridated water. As long as we keep pumping over water to Site-16, it will buy us extra time until we can think of a solution. We have a list of all of the known companies that are still in possession of SCP-622 and are actively seeking to contain every last canister before they can be used. Lastly, I know some of you are shaky about Protocol Gray. It may come back to bite us, but I'd much rather worry about an XK-class End of the World event in a few hundred years than an NK-class Gray Goo End of the World event in the next few weeks. We'll deal with that then, but for now, Protocol Gray is buying us time. As long as we end Protocol Gray in the next ten years, I don't think there's anything we'll need to worry about. I will notify everyone once SCP-622 has been contained, and when Site-16's staff discover why it was able to breach containment, carry on 05-12-15-12. Lesson complete. If you missed the previous orientation, go watch SCP-621, Hypno-Bulbs, right now. Or for the complete course, watch this playlist.


The American Battle Monuments Commission hosted a memorial ceremony at Rhone American Cemetery for World War II veterans who fought in Operation Dragoon. Often overshadowed by the well-known Operation Overlord, which has been cemented in the public's consciousness by numerous Hollywood blockbusters, Dragoon was the other operation, two months later, that liberated southern France from Axis occupation in August 1944. We thank you for traveling the great distance to be here and for the opportunity to walk with you as we retrace your footsteps. We give thanks and we remember the sacrifices of your comrades who did not return home. 72 years have passed and we must never forget their bravery. Gentlemen, I salute you. From Dragoon, Neon, France, I'm Petty Officer Kelby Sanders.


So this is Lucas, and well. OK, thank you. So when you ask people, is that too loud? OK, when you ask people what quality assurance is, you get answer like this. So that's not quite true. So what's really quality assurance? Sorry? Yeah, but it's funny how to blame him. So the goal of quality assurance is to improve the quality of Debian as a whole, as opposed to just working on your package. So quality assurance team is not really a team. It's more like a central place to discuss stuff. And we hang out on Debian QA and the main list of Debian QA at least, the Debian.org. So what do we do? First thing is we maintain the PTS. So the package tracking system. Everybody knows the PTS, I'm sure. DDPO, which was mentioned by Tincho. So that's the Debian Developer Package of the View. And also several other tools. So what's really important is that we aim at building tools for everybody, and not just for one team. So I find it a bit sad that Tincho built this nice tool just for the Perl team without talking to the QA team in general, because probably we could have helped him and made his life easier. So what's really important is write your tools for Debian. It's cool that you write tools that help everybody, but don't write them just for your team. We also develop tools to run archive-wide checks. And then we do the checks, and we do the mass bug filings, when it's for real issues only, most of the time. The advantage of talking to the QA people about that is that usually those people are more experienced about running such tests. So you don't start filing bugs about things that are not real issues. So that attacks the filter. One other part of what we do is that we take care of our fund and neglected packages. We are supposed to maintain our fund packages. Everybody knows what an orphan package is. And we also have a sub-team that tracks inactive maintainers. So that's the missing MIA, so missing inaction team. So when I submitted the talk, it was supposed to be above. So I'm just going to present a few new things that you might not know yet. And then the goal is really to chat about QA. So the first thing I wanted to talk about is BAPAs. The problem is that there are many package that are neglected in Debian. And it's difficult to determine which are those package amongst 10,000 packages that we have. So the idea is simply to import different informations about packages in the same script and then build a table that uses a scoring system, like a spam scoring system, to detect which package is really suspicious and should be looked into. And another part of the tool is that it allows you to say, at this time, I took this action. And for example, if you file the bug saying, this package looks neglected, should it be orphaned? Then the tool reminds you, 30 days after that, that no, you should orphan the package. So that just allows to keep track of what you are doing and to process many packages at the same time. If you have questions about that, don't hesitate to ask. So examples of searches that we have are package which are very buggy, so with many bugs or neglected and useless or found. And we use different informations such as the number, the cool stuff that is not done elsewhere, I think is the number of NMUs that the package which was already NMUs four or five times, is very likely to be totally neglected by its maintainer. Something else that's new and not totally working yet, but we are really close to getting it in production state. It's the ultimate Dibyan database or UDD. So it's a Google Summer of Code project. The student is Christian von Essen. It's a German guy. I commentate it with Stefano Zacchi-Holli or something like that, Zac. And Mark Borkschmidt. Was that right? Yeah, Zac is fine. And the goal is actually similar to what I just presented about BAPAS. The goal is to gather a lot of existing data on Dibyan in the same SQL database. So then you can run cool SQL queries combining lots of different data sources which is not at all possible at the moment. So for example, you can get a list of really critical bugs sorted by Popcon or the list of common or maintainers including co-maintenors. Rather problem? No? At least maintainers with the most bugs. So the current status is that we have a lot of data so it's already imported on a regular basis. So either using current tabs that runs frequently or the updates of the packages and the sources file triggered by SSH. So it's really fresh data. And we imported the packages and sources file for Dibyan and Ubuntu, the popularity contest for Dibyan and Ubuntu. Or why Ubuntu? Simply because you want to be able to increase such as packages which are popular in Ubuntu but are not packaged in Dibyan. We also imported testing migrations. So we know when a package last migrated how long I've been trying to migrate. The history of uploads. So we know when packages get where uploaded by womb, the bugs, everything from the BTS. I mean only the summary for each bug, not the bug log. Of the list of orphan packages, Lin Tian and Carnivore. So that's everything listed here works but it's really easy to import other stuff. Philip Kand said this morning that he will work on importing when I build. So currently this runs on UDD.Dibyan. Carnivore is a tool that is used by MIA I think. To, yeah, it allows to link different email addresses or identities to the same person. So you know that this email, that email are actually the same person. So you can access it from master.Dibyan.org using this command line. This works. And it still has to be moved to UDD.Dibyan.org machine but we work on that when everything is stable enough that it's really completely usable. You can already run queries like I will show you. And there's a wiki page with some links also. For example, one interesting query is, I blogged about this, maybe you read it. It's a popular package which are not interesting because they were removed, for example, because they were assay buggy or because they haven't migrated yet. So for this we can combine the sources table and the popcorn by source package table because popcorn usually use, not normally use binary package but we have a table with popcorn for source package using the max number of installation over all the binary package of each source package. Which I just lost my screen. So those are the results. So you can, and this kind of things it's really hard to do currently without UDD. And the query, it's the most popular orphan packages. So we have a table called orphan packages that has the list of orphan packages with a type field, which is whether the package is currently orphaned or ITAID. So someone intends to adopt it. And so again, you can link it with the popcorn source tables to get a list of popular orphan packages. So are the results. The most popular ones were ITAID but that's still, I think Imlib is going to be removed. Oh yeah. So Mark Bushmitte is not at Deppconf. Mark Bushmitte feels bored, so he wrote SQL queries. I tried to format it cleanly on the slide, but I gave up. So this gives the maintainers with the most LinkedIn errors and the winner is, so it's not the number of unique LinkedIn errors. So maybe there are just lots of duplicates, warnings or errors. So just examples, you can run lots of different stuff and if you have ideas, just talk to us. So what you can do about quality assurance first, talk to us and join Debian QA and the mailing list. Look at the list of orphan packages and adopt them if you care about them. There's a script in Dev Scripts called WNPP alat, that lists the orphan packages that you have installed on your system. So it's a good way to know if you are using something that is orphaned. You can work on improving our tools. So there's lots of bugs filed against QA.debian.org on the BTS, so just have a look at the list. File new bugs so that can fix them. And think about mass bug filings to improve the quality of Debian, but only about real issues, of course, because we don't need more useless bugs. And talk to us about them so we can help you because we are used to that. But so this is supposed to be above. So I really would like a discussion. So there's a list of topics that I would like to have your opinion about. So first, the orphan packages. We currently have more than 700 orphan packages in Debian that doesn't look really right. So what should we do about them seriously? Because I don't think that we can just continue to ignore them. Well, we could just do as if they didn't exist. Well, we could aggressively remove them. We could continue to ignore them. Or we could maybe split Debian into a main section which is supported in the universe and supported section. I don't know where I got this idea from, but... And something else that we could discuss that you might have questions about is status of MIA. So the mission and action teams that tracks inactive maintainers. And something else is making the QA team more attractive. It's a really cool team with a great atmosphere. Everybody that is in it, I think, really likes to talk with QA people. Maybe we could integrate this into NM, like Andres. So John, yes. Who's actually for you a member of the QA team? Is this a reader of the mailing list or a subscriber of the mailing list or who is... There's no, well, there's no really formal membership. You can, if you joined again QA or the mailing list, then you are a member of the QA team. So that's really, yeah, there's no... But there's a UNIX group named QA that is only used to control access to the QA website and the PTS, no, the PTS is the same group. Okay. But that's the UNIX group is just a technical thing. There's no, yeah. The usual answer to that question is that everyone is part of the QA team. Yeah. I think we all should work on QA stuff and track several things, not just in our own packages. But if we stumble upon problems in other packages, we really should get rid of that impression that there's a single maintainer for a package and do QA work in a more broader approach. Yeah. The other side of that story is, of course, that many of the tasks of the QA team are very repetitive and you have to do them on many packages, but you have to gather some experience on how to do them, but you can only do that by actually doing them. So everyone that has the courage to go to other maintainers and tell them maybe you should off on your package, it looks very bad in shape and stuff like that, is a member of the QA team, but you will notice that you have to have the courage to make errors at the beginning, errors of judgment, and you will be accused and yelled at, but you will get better at spotting which packages are probably so, yeah. So the thing is, that's the reason that everybody and nobody is a member of the QA team, because the task in itself is not, most of the tasks are not very hard. You just have to do them, but they are also very difficult on the other hand in that a lot of factors can affect the package and sometimes it's better to just leave it alone because the maintainer is working on it, even if it looks bad in the archive. I'm not sure entirely what point I'm trying to make, but I hope it was still useful. I agree that many tasks of the QA team are socially difficult because you deal with people who are already too busy and responsive, it's easy to get frustrated about that, so you have to do other things besides that not to get totally burnt out. But there are also things that are purely technical and doing them inside QA team helps you be more efficient and makes the task less predictive. For example, when I started filing my FTBF, my FTBFS bugs, I did it mostly manually and now I have scripts that make it really easy to file 60 AC bugs in one hour or half an hour. You can use it, it's written to be useful to everybody, so if you want to do mass bug filing, use those tools so that, for example, you don't have to manually copy the bug numbers to a separate list because it's just insane to do. You can just import all of them using user tags to a file and fill in the files. So, yeah, these are all small tools but really useful when doing that. It's not only talking to maintainers about when their packages might need more attention, it's also working on the infrastructure. Lucas has shown some really spectacular things that he has done in the past and has a lot of more things to do. So joining the QA team does not necessarily involve talking to other maintainers if you don't like that. It's more like you do need to talk, of course, with your fellow QA members or with whoever is working on several tools to enable maintainers for themselves to work on the packages better. If there's more tools so that maintainers can see what the state of the packages and what would be the best investments of working on their packages, that is also QA. And the point that Frank was going to make was, of course, that alcohol hurt your brain. Yeah, part of the point that Frank made was that it's really sort of repetitive work and it's getting annoying and boring at times. But I would like to really encourage new maintainers or people who try to get involved into Debian to join the QA task force because usually it's not hard work but it will get you very much visibility and a good track in the history for your new maintainer application or things like that. Yeah, I wanted to come back to the first point on the slide, the orphan packages. I really think we need to get more aggressive in removing them. I mean, we have got more aggressive over the last few years but it's still a very slow and tedious process. But I mean, there's, of course, the human side of the problem that will not go away, that people actually care about these packages. They just don't have the time or don't feel that they have the time to actually maintain them. So if you remove an orphan package, it can be that you annoy many users, some of them might even be Debian developers. But it is just an unmanageable task at the moment. So it can't continue like that. And I think the sooner people realize that, the sooner they will stop complaining when we remove packages.  I mean, you have the versions in the stable release it if it was ever released. And you have things like Snapshot, DebianNet, and hopefully at some point in the near future that will become an official Debian service that would make it easier to justify removing packages because they would still be available. At the moment we only have this Morg on FTP Master, but it's a bit difficult to get there and stuff like that. So I think having Snapshot, DebianNet being an official service would make life easier for tasks that involve removing packages because we can just say if you want to reselect it, it's all there, just download it and upload it as maintainer. But the current situation just doesn't work. What sort of threshold are we going to put on for that sort of thing? Are we just going to say that the orphan packages with the most bugs, the lowest popcorn score, just get dropped at every release? Well, the problem is that orphan packages sometimes are reversed dependencies and you can't just remove them without breaking maintained packages elsewhere. So it's really a tricky problem, but starting by not releasing all orphan packages without reverse dependencies, which have been orphaned for a long time and have low popcorn? Historically it's always been one of the maintainers of the reverse dependencies who's had to take on the orphan package. I know Thomas had to do that with NuCache. NuCache took on a long list of reverse dependencies just to maintain NuCache itself. It's a big burden for those who have to use it, but it creates an incentive to see whether there's better code that they can convince upstream to use. Yeah, someone has to do that. Someone has to maintain them. This may sound a bit a weird question, but what's the problem with having orphan packages? I mean, surely it's not a good thing to have, it's better to have a maintained package than an orphan package, but how is it better not to have it at all than having an orphaned? Well, that's the point. We could just continue to ignore them and consider that it's fine. But the problem is that we are supposed to support them. Sometimes they are buggy, but nobody knows until a user installs them and that's still a problem. I think if we are supporting them and saying, why are we releasing them? No, I'm not saying we should include them in stable releases, but just have them in stable, why not? We're not supporting them in any official way, but they're just there until someone comes up and maintains them and puts them to testing. Currently they are released. They should be removed from testing, but why should we remove them from the archive? If you remove a package from stable, you just basically remove it for the users, which means you remove it. It's not available for the user. There has been raised a valid point on ISE discussion channel about that popcorn stats shouldn't be the only criteria for these packages, especially for some corner cases like accessibility or other special areas with special impact. You won't get ever any great popcorn stats for that, but that doesn't mean that those packages aren't important. Especially with respect to accessibility, they are very important to some specific users. It's hard to get people... It's very few people really interested in those because they probably needed themselves, and it's hard to get people involved into working on those, unfortunately. So just popcorn stats shouldn't be the only criteria to keep packages out. Yeah, sure, but it's really politically incorrect to say that you can't value accessibility more than science, for example, and if people care about science and people don't care about accessibility, that's life, and maybe that's another social issue to address, and I'm not sure that the right way to address it is just to make as if those packages were maintained when they are not. Well, when talking about removing packages, I can see a problem here with this situation because also they are still available at Snapshots. People usually don't know that they were removed because of some reason, like they were found and maintained, and nothing very great with them, so they can actually get them back and restore them. So I think we need to create a list of those packages that are removed so that our users can actually see that the packages are still somewhere and they don't need to package them right from scratch. So it's basically that. Actually now, if you are subscribed to the PTS, you receive a mail when the removal of a package is requested, so if a user is subscribed to packages that he cares about, he knows about it. I think he meant that if you want to package a software, that you have an easy way to look if it was ever packaged before so that you can actually reselect it. At the moment, you have to go to... You can first check if it was ever in a stable release and you have to check whether a snapshot maybe has it from some testing or unstable version, but it's not very retrieval. Actually, I think that the PTS lists packages that were ever in Debian. No, only that are currently somewhere. Well, but sometimes there's some missing information and also another problem is that the PTS only knows about source packages. So it is not something pretty easy. I'm sorry for repeating my point, but we have unstable and the bug tracking system for that. Just leave them there, we have the bug tracking system and if someone wants to work on the package and make it to fit for a stable release, then he can look at the bug tracking system and fix the RC bugs and take care of the package. Yeah, but then you run into problems like people not caring about releasing Debian and that's another issue because lots of people are just happy with using unstable because they will never work on getting them into testing or into a stable release. In that case, what does it hurt to have it there? Well, it's usually stable, but there is a package that's orphaned. If it's removed, you wouldn't have it at all. So what's the difference? Actually, this is a bit incoherent with the release practices which says that if a package is not meant to be released, it should not be in unstable. So this is what the release manager is saying and keeping packages in unstable which are not meant to be released is a problem for release purposes because it can get in between transitions and stuff like that. What is the problem? It adds noise to the list of RC bugs so you look at the list of RC bugs and RC bugs like this package isn't stable but it's not meant to be in a stable release so you have to scheme all those bugs. Does that mean that every orphaned package is per default RC buggy? We could introduce that policy that every orphaned bug is per default RC and it looks like the only way to get people to maintain orphan packages is to threaten to remove the package. So that could be a way to fix the problem. Just to even underline that, even just keeping the packages in unstable still has a problem because you're sapping Huey people's time dealing with packages that nobody ever is going to have any interest in maintaining or at least for the foreseeable future. It may be useful to when we remove archive those packages somewhere like we currently do with snapshot.devion.net and maybe perhaps make something official for those types of packages so that if somebody later decides they want to come back and do it and the archive is just wasting people's time and again when you remove it makes people sit up and notice oh, I actually use this package maybe I should be maintaining it perhaps even announcing to users that hey, these packages are going to be removed because nobody's maintaining them they've been orphaned for N days, whatever if you want to keep them around instead of packaging yet another DNS or IP over DNS thing that you should consider taking over an orphan package. Yeah, that's... I mean, as was said before the current problem is that the whole infrastructure is targeted at so that every package should eventually go to testing. There are a few exceptions which we accept but the whole infrastructure assumes that so that's not an unsolvable problem if we want to change... if we want to change that but it is a current problem so the question would be do we want to change that and I don't think we want because even if we change the infrastructure so that those packages don't... clutter... don't... yeah need so many resources like they do at the moment in terms of that they show up in all these lists of packages that need work that Brittany tries to handle them and stuff like that I don't think even if we change all that that we want to have them in the normal archive because every package needs resources and if we just let them pile up like they will need ever more resources and I think we can spend those better and if you really care about the package then you should provide those resources and that means maintaining them and taking care of them Well I guess I guess we can agree if we aggressively remove them from unstable they should be somehow accessible and actually there is a source mark on FTP master but to my knowledge it's not yet mirrored somewhere so if this would be mirrored I didn't see it on Michael when I just looked but maybe there in the FTP tree so if the packages would be actually accessible to reintroduce them into Debian and not to redo all the work I think it would be easier to just remove them or lower the barrier instead of relying on snapshots Debian or DebianNet which is not even an official service I guess and which stopped mirroring currently So not a problem I see with keeping orphaned or in general buggy packages in Debian even only in unstable is that it lowers the quality judgment that users have of Debian if one packages even out of ten is problematic for them is buggy they see the buggy packages much more than the non-buggy ones they feel them more an impression they have of the general quality of Debian goes down very fast Well in some media another way around is to for example keep all the orphaned packages out of testing and during the release cycle one can try to adopt them or either adopt them, release them or or try to decide whether in that package release should be in stable or not but make sure and then unblock the package so it can enrich testing and be prepared for the release that way we could remove several packages reduce the workload and in the same way keep the packages around for some time so that they can still be adopted or whatever I mean nobody is suggesting that we just remove orphan packages after a month or so I mean okay I've suggested that I think but for special cases it is important to find the balance between keeping them long enough so that potential adopters can notice them and keeping them short enough so that they don't cause too much work for the QA team but it is my experience that successful ITAs are very fast and everything that is a bit slow and most of the ITAs that are just a little bit slower like more than a week or so never get anywhere I mean there are exceptions for some packages that need really much work or need a new upstream version that is completely different stuff like that but you can see if packages are often there are two general ways how it goes the one way is there is an ITA in less than 24 hours and upload in less than a week and then there is the other case where it just drags on and drags on and maybe there are ITAs from some people that aren't developers and then nothing becomes of that and stuff like that but most packages can be classified as one of those two cases so we shouldn't wait too long I think because it doesn't actually help the package to be adopted so the consensus is that we are going to remove often packages aggressively and I think the point Raphael made was that we should compile a list of packages that have been previously and Debian somewhere on QA Debian or maybe with the latest description latest version and tell people if you want to have this package back in Debian go to SnapshotsDebian.net or ask somewhat to get you the latest package from somewhere that should be easy and the list should really be useful and if it's visible so people can say it really was removed at some point and that's why and maybe even a pointer to the removal bug and that would be a nice service for QA to provide and basically that's only FTP master. This removal stock TXT is just too long and it's not readable so I really like the idea of making a policy of making an orphan package marked as RC buggy and I think that will resolve a lot of problems it will preclude from propagating to testing and if it affects the reverse dependencies then it's up to the person who is maintaining the reverse dependent packages to fix it or find an alternative solution and that actually it doesn't matter if it drags for a long time and it's sitting in unstable it will now propagate to testing until its status changes I was actually if people want to further discuss the orphan issue I was more planning to talk about UDD I think it's a very good idea what I started just thinking about it and potential uses I don't know how much of a package metadata you are importing but it seems like by importing all metadata you can come up with very exciting new checks like right now Lintian as I understand it does only static checks but you could do dynamic checks for example if you import information about what files are in the package check for duplicate files or you could check that the version which people are building the library version people are building against is actually available in unstable eliminating cases like people building in a dirty truth or something like that you could probably even do an automated check for the cases where there is a freezing effect and people wouldn't be would be warned to not upload the stuff right now linking against the particular library version and things like that so are you doing it or is it something you are planning to do currently it's a Google sum of code project that started 2 months ago so it was a bit hidden currently not really public we are going public with this no because the Google sum of code ends no if you are interested in importing more data just contribute and join the GNQA talk about us and we can give you access to work on new import scripts we are going to import a lot more data there is a goal for the Google sum of code project was to build a strong base if we can build know that we can build on it for example Raphael discussed with Raphael the idea of using the UDD for DHS the DebianWatch checking system because we could import some files from each package into the DB like DebianWatch or DebianChangeLog and then have a look at those files automatically you won't need any file backend for DHS anymore basically I have an idea when I have seen that there are 700 packages QA maintained I will not browse this list regularly but if there would be a very simple tool that just scans the list of packages which are installed on your computer or so whatever and sends you a monthly email using package ABC which are not I am very sorry it should be default because I am also using a package and I have got from the release maintainer there was no interest in this package since 2004 and this was just not true but nobody noticed sorry for repeating there was mentioned that packages that get removed will put into some snapshot archive and people have the possibility to revive it from there this hopefully will also include all the bug reports that were filed against the packages before it got removed well the bug reports are archived and could be unarchived yes but it should be linked with that information so that people will be made aware when they revive the packages it probably should reopen all the bug reports that were open at the time the package was removed and should check if it still apply I think we could just document that something like resurrecting packages in developer reference saying unarchive all the bugs look at archived bugs for this package when you resurrect the package I am not sure that we need a script to do that automatically yeah in the interest of not duplicating work we should probably talk a bit about now that we have Jeroen here how to use the stuff that he wrote in mole with the UDD because I think for some of the imports for data that requires a lot of work to import like like file contents and stuff like that it would be very useful to use the mole stuff because it is actually designed to do that and we could then import the data from mole and not directly so that we can reuse that code and me and Christopher have looked a bit at it and are getting familiar with it so that mole doesn't have a single maintainer anymore so that we can hopefully improve it in the future well I don't know what things but why don't we schedule another talk or a meeting actually so that we can continue talking about all these topics because now that we have still 5 more minutes well we won't finish anything so I don't know if we can use the other room or what not right now okay I take care of that asking for another script even if we don't choose it for one hour it doesn't matter we haven't talked about MIA maintainers yet do we think we have a problem there I'm not really familiar with MIA so I'm not sure how well it works how well incoming mail get processed I don't know well there's two sides of the issue one side is processing the known cases on the other hand I have the impression that we have lots and lots of maintainers who just maintain one single package which in some cases doesn't need another upload but in some cases could use another upload and do we have too many maintainers is that a problem do you want it like that or what's the general impression there I agree that we have quite a lot of maintainers and usually it's really painful to deal with with them because sometimes they are active they answer to emails when you mail them but they don't do anything about their package and they think that it's okay and they are not aware of Debian policies they just do it in their corner and that's really on one hand it's nice to have them participate in Debian on the other hand it's difficult to deal with so I'm not sure I'm not saying at all that it's a problem for people just maintaining a single package it's a lot harder to actually tell if they are active or not if someone has 10 packages it's very easy to tell if they are active or not just by looking at the bug count but for MIA stuff it's probably always if someone else is working on pinging maintainers and asking them what they are going to do actually maybe we could make a difference between maintainers that maintain a lot of packages and maintainers that just maintain one or two packages because if they just maintain one or two packages then we can orphan them using BAPAs for example we don't need to go through the MIA process for them because it's easier to just say okay this package looks neglected I will orphan it in 30 days if you don't fix the problems I was going to suggest that I think we need to be careful to focus on what the actual problems are and address the actual problems I think for example that we could make much more use of NMUs into the delayed queues and assertions of this is not well maintained we'll orphan it in 30 days or whatever the right threshold is because I think sometimes we have people who are actually reasonably engaged and are good people and we don't really want to drive them away from the project but we shouldn't allow their periods of inactivity or their attention to other things instead of that package to keep us from fixing the package and so we need to be a little bit careful sometimes the problem isn't necessarily that we have to maintain only one package it's that we have packages that are poorly maintained and we should not be afraid to do the things that are required to fix the packages whether we can fix the people is a whole separate issue I think we are done out of time I will take care of scheduling another slot for this I think Andrea has the notes thank you


I'm just picking up my new commons here at Mountain View Chrysler and Dodge. Can't wait. I'm excited to go home.


Thanks for checking out this movie review video. So this is for the 2019 film The Beach House And it's a shutter original film and it's gonna be available on shutter Thursday, July 9th when I'm putting this review up It's a little bit ahead of time because shutter does send me screeners Which is very nice of them so I can kind of make this stuff available to you So since I'm putting this out ahead of time, this is just hitting shutter soon No spoilers for this review, but I'm gonna give you a very small synopsis of kind of what this film is Not anything that would give anything away because I don't want to I want people to really experience this but enough to kind of peak your interest maybe Written and directed by Jeffrey A. Brown This individual actually this is his first feature length film directing and writing He had done a lot of work on other films before doing various things on film sets mainly location management which Has come into it has become handy for making the film The Beach House because the location is awesome if nothing else The scenery is very very beautiful with this film because it's at a beach house It's on the beach and they do a good job of with their cinematography and directing really kind of capturing The beauty of the beach but also capturing the ugliness of other things that kind of go on in the film There are some horrific moments There's some gross-out stuff in this film which that may be really exciting to some people and make people up be like Yeah, I don't know if I want to get into the gross-out factor There's something in this that actually grossed me out. It kind of makes my skin crawl It's something that I have a particular Issue with whenever I see it in film not issue is in I think it's bad in the film issue was in it Makes my skin crawl like it's something that that gets me going and I'm just like I literally would kind of like have my mouth open while I was watching particular parts of this film for that reason so Kudos to Jeffrey A. Brown for getting me kind of creeped out and getting my skin crawling because Since the practical effects were done. Well It elicited that response for me. So that's one of the good things about it So quick kind of synopsis few sentences about this film It's basically about these two characters Randall and Emily who are in College-age kids and well kids adults I guess young adults college-age and they're having a little bit of an issue with their relationship It seems like the two of them are kind of diverging in their past and life Maybe when they kind of want to stick together so they go away to the beach house, which is owned by Randall's father And when they get there, they're like, oh, we have this to ourselves But then there happened to be other people there another couple who were actually staying there Who were friends of his father and then things start to get weird? And that's kind of where I'm gonna cut it off because I don't want to you know lead people too much on it The opening sequence of this film is kind of calming but at the same time a little bit alarming in the sense that the music is Really kind of upping that feeling of like something wrong something Terrifying going on even though the actual images of what you're being shown isn't actually terrifying That's what I'm saying. It's like it's a calming image and had the music not been there You would just be watching it like yeah, you know, I've seen stuff like this before it looks nice It looks beautiful and it's calming, but it's an important sequence in the beginning because It comes into play later and by the end of the film you'll understand what that opening sequence actually means When I was first watching it. I'm watching the opening sequence and I'm like Okay, I'm assuming this comes into play much later in the film that there's some sort of Hidden significance at the moment, but that'll become clear in the end and it does You do end up getting it in the end one scene in particular in the end that kind of mirrors in a way this opening sequence so Without backstory to really start things off between Randall and Emily They actually do a solid job of kind of the interactions with those two making it feel like it's a real relationship that like You kind of almost know them and then through their dialogue you pick up on little pieces that kind of gradually builds Who they are as characters what their relationship has been in the past and what is currently? You just kind of get those little tidbits as things go on and then you start getting those types of little tidbits from the other Couple who's in the beach house as well so from a writing standpoint kind of having those little nibblets of Knowledge about the characters and their backstories is pretty well done It's kind of paced well in the beginning of the film until you get to you know The catalyst of it being a horror film and then from there on out like we don't need to know about backstory and anymore it's it everything's totally changed at that point and then we're looking for the horrific stuff the gross-out stuff the the Interesting like what is it all about moments? Something odd and slightly alarming happens pretty early on in the film which creates a real interest in finding out what's really going on here There is kind of like There are a few moments that actually kind of like are a little bit off and you're kind of like that's slightly a Problem, but it doesn't seem dire at the moment, but I Need to know where this is going The film does a good job at kind of like grabbing your interest and making you want to see it through want to go all the way through it and see What's the point here? Where are we going and in the end? There is a point in the end they are going somewhere and that's one of the greatest things is that there are Oftentimes films that are made and and you think oh, we're going on this journey and I'm excited to see where we go And you don't really go anywhere by the end or or where you go in the end is just like With this they made some interesting points. There's some interesting underlying themes to this film and I thought it's pretty solid The acting is good for the most part Some people better than others, but for the most part pretty solid especially for a lower budget film The gradual discovery of tensions that kind of are underlying between Randall and Emily makes the story actually feel really Realistic it builds context, which is actually really important to understand the characters themselves But also the dynamic between them and then obviously that you know What ends up happening in the film much later all the you know events the horrific events is Metaphor for things going on between the two of them. So watch it know that There are some scenes that feel a bit like they're a little bit kind of stretched out Maybe to hit more of a particular runtime. This one's not super long with credits and everything It's like an hour and 27 minutes So it's not long But there are times where it starts to feel long because some of the scenes feel a little too stretched out It's even in the end which in the end portion when things are like really going and like the story is really moving and The terrible things have already been revealed That's when you want it to just like keep moving keep going keep going and at times it kind of stagnates and you're just like You know, I'm feeling a little bit bored at this point, but it doesn't linger like that too much So it's a little bit of a criticism of the film, but it's not too bad overall. I think it is a pretty solid film I think it's definitely worth checking out at least once Because of the beach shooting or I already talked about that the location being beautiful.  It looks nice. So they got a little creative. I dig that Yeah, the gross out stuff just the gross out stuff This is a movie like those moments are hard for me just because like it Literally that feeling of like your skin crawling. It's I'd be interested to know if that happens with other people So if you've seen the film put the comment down there There are aspects of this film that make it feel like the movie color out of space with Nichols cage that Richard Stanley film That actually came out last year as well So it's interesting in that aspect, but where Where things come from in color out of space It's kind of similar in The beach house, but where it comes from is different is very different, but it feels very similar. It's not exactly the same Color out of space looks way more polished way more stylistic and artistic and You know, it has bigger names. It has, you know, higher level acting to its its bigger budget So, you know, the beach house would not be able to do that but While I was watching this film because of the way the story is and because of the interest level It made me really Think to myself. I wonder what this film would have Been and could have been had they had a much larger budget This is one of those films where you're like, this is good enough That I really wonder if someone threw more money or if they just had access to more money for this film What could it have been? What what bigger things would we have seen? What crazier stuff would they have done visually with CGI or visually with practical effects? There's so much more that could have been done with this, but I know they were just Tied up because of budget so that that kind of sucks, but I think they did a good job with kind of what they had So that's pretty good There's an aspect of dealing with change and how tough that ends up being for people but also how that can really Fracture relationships, especially when one person is changing and the other person is staying relatively the same or both people are changing And they're changing at a point where they're going on diverging paths in life And then, you know, what do you do? What decisions do you make? How do you deal with that? There's also an aspect of questioning how much we know as human beings or think we know And what happens when we have to deal with something that we never really considered something that's part of that unknown to us You know, what happens when something totally unexpected occurs and we're just not ready for it You know as humans were used to knowing a lot and being able to plan ahead and have things in place to be To feel like we got it handled whenever anything pops up But inevitably something's gonna come along that we didn't plan for we didn't even know about potentially And you have to adapt to that and and this film kind of takes a little bit of that into account and and is kind of a moment of Then what happens when you weren't planning for something you didn't know about something and then you have to react to it. So And some people Go with it. Some people succumb to it. Some people fight it. It's It's a mix There's a lot in the ocean. This is my final thought on this There's a lot in the ocean we haven't discovered and this is actually something that one of the character One of the characters talks about in the film. So it has a tie-in to the actual film really What else is out there is kind of one of these questions? And then my final thought is I pulled this from the National Ocean Service This is an actual quote on there more than 80% of our ocean is unmapped unobserved and unexplored So that kind of goes to what I was just talking about with, you know How much do we think we know and how much do we actually know and what happens when we come across something? We don't know so There you go But overall, I thought this was a pretty solid film I would really be interested to see what jeffrey a brown Can do in the future especially with a larger budget because With the way this film was done It kind of feels to me like if he's the type of person who can get a much larger budget We can get a really good film visually out of that person so Interested to see what he could do in the future. Uh pretty well done So out of five stars with half stars in play. I'm going to give this a three star rating. This is a solid film this is one of the Relatively good offerings as a shutter original So people check it out and when you do go ahead put some comments down there We can talk about your thoughts on the film and um, yeah, I'll talk I'll chat with you on there But do me a quick favor. Uh hit that subscribe button That's the best way for you to repay me for Spending my time doing these putting this information out there So if you like any video I've ever done Consider this the best way to support me is to subscribe because it means a lot to me And it's totally painless. You know, you're not throwing money into it or anything like that Just take that second to hit that subscribe And then if you do that also make sure you hit that notification bell Because that'll let you know whenever I have a new video coming up or when I'm doing a live stream. So I appreciate that but regardless. Thanks for taking your time to check this out And until next time keep it brutal


Coming up on DTNS, we wrap up CES 2022 week. Robert Herron's here to look at what we saw in TVs and home theaters, and Allison Sheridan identifies some of the most interesting announcements you didn't hear about elsewhere. DTNS starts now. This is the Daily Tech News for Friday, January 7th, 2022, in Los Angeles, I'm Tom Merritt. And from Studio Redwood, I'm Sarah Lane. And this is Allison Sheridan of the Podfeat podcast. Drawing the top tech stories from Cleveland, I'm Len Peralta. And I'm the show's producer, Roger Chang. And as I mentioned, co-host of AVXL, Robert Herron's along with us. Hey, Robert. Hey, how are you guys? Good to be here. Good to have you new year. Good to see you. Thank you. Happy 2022. We were just all sharing our favorite YouTube channels on Good Day Internet, and obviously we'll be talking more about the topics of CES on Good Day Internet. If you want that wider show, get it at patreon.com slash DTNS. Big, big thanks to our top patrons. Today, they include Chris Benito, Steve Aya-Darola, and Jeffrey Zilx. Let's start with a few tech things you should know. The Entertainment Software Association canceled its in-person E3 event this year, citing ongoing health risks. The ESA says it could not confirm whether or not there would be a digital event this year as well. Game monitors aren't new, curved monitors aren't new. But at CES, we got a curved game monitor that is not curved left to right. But instead, top to bottom. Samsung hopes you find that interesting. It created the 55-inch 4K Odyssey Arc coming out in the second half of this year. That's about all the details we have on it so far. However, the Verge named it their pick for best-in-show at CES. At the HealthTech keynote at CES, Abbott CEO Robert Ford announced that the medical device maker is developing a new line of consumer bio-wearables called Lingo. The devices will be aimed at general fitness and wellness able to track key signals in the body, such as glucose, ketones, and lactate with alcohol levels potentially down the line. Microsoft added new features to the PowerToys suite. Always on top lets users pin any app to always be in front of other windows. PowerToys also added web search in the run launcher using a activation command to search the web and the search will go to preferred search engine in your user's default browser. Samsung forecast its Q4 operating profit increased 52% on the year. That's up to 13.8 trillion won, which is about 11.4 billion US dollars, although this would still miss analyst estimates. The company also estimates that it hit record quarterly revenue of 24% on the year to 76 trillion won. Samsung's contract chip manufacturing business is expected to see increased profit in the next quarter. The National Copyright Administration of China issued an order Thursday preventing digital music platforms from signing exclusive agreements in most cases. China's market regulator had already ordered Tencent to end all of its exclusive agreements last year for being anti-competitive. Other companies affected by this new order include Xiaomi, China Mobile, and NetEase. If you're wondering about Apple, they partner with Tencent, so they're already covered under that in China and Spotify is not allowed to operate in China. Twitter began testing a new feature on iOS called TweetTakes that will let users post a video reaction to tweets rather than a standard quote tweet. Probably reminds you of a different app, but no, we're talking about Twitter. TweetTakes places the tweet a user is responding to as a sticker that's placed over a vertical video. Yeah, about time they came up with that TikTok, Twitter. Engadget, which awards the official best of CES awards gave the official best in show to the Chevy Silverado EV, GM's second fully electric model built on the Ultium battery platform. Chevy Silverado RST officially had the model, promises a 400 mile range, fast charging of up to 100 miles of range per 10 minutes, 10.2 kilowatt hours of off-board power, which you could use to run power tools at a work site or home accessories if you had a power outage. It'll tow up to 10,000 pounds, carry up to 1300 pounds of payload with an initial MSRP for the first edition. This is like the founder's edition of the truck of $105,000. If you're like, I just want to get one of the first ones, that will fall to a more expected $39,000 base price for the regular RST when that arrives in the summer of 2024. Yeah, I know. Quite a price to be first. All right, let's start with the news on Google and Sonos' little patent spat. Let's do it. The United States International Trade Commission ruled that Google infringed on five audio technology patents held by Sonos related to controlling a group of speakers. The ruling would block Google from importing infringing products, including Nest audio, Pixel phones, and Chromecast devices, water devices. Google responded by pushing out an ITC-approved software downgrade that changes a few group speaker features. So users will have to adjust each speaker in a group's volume individually, whereas before they were nested. And some users will face issues if they haven't updated to the latest software. Google doesn't expect any impact on device imports or sales. Of course the company would say that. So instead of paying Sonos a license, Google has decided to remove functionality. That is not great if you're a Google customer, but that is something that the company decided to do. Ars Technica quotes one commenter on the Google Nest community as saying, quote, so you got sued by Sonos and we pay the price? Either get some better lawyers or win the suit and win the suit or pay Sonos a royalty or start issuing refunds to customers. End quote. What do we think? Fair? Unfair? I mean, that's terrible. I mean, they have a choice, right? They're making it sound like their only decision. Well, you know, Sonos won't let us do it. So we have to take away the capability. And there's always a choice, right? They didn't want to spend the money to pay.  I don't know. I'm on the side of the user there. It kind of reminds me of what went on recently between YouTube and Google, or I'm sorry, YouTube and gosh, what was it? NBC Universal, right? Where they took away ASPN from my YouTube TV app. And my mom was like, oh my gosh, this is horrible. How will we cope? And I'm like, they're gonna come to a resolution. I sort of see the same thing in this scenario. Robert, what about you? I just am kind of sad to see that they spent all this time just hashing out exactly what was owned by who when it should have been pretty clear right up front if you're adopting a feature for a product line. I'm curious to know how much the lawyers made in all of this when- Probably a lot. And why wouldn't Google then just license that technology right from Sonos in order to have that continued functionality? I wonder why exactly it had to go this far. It's my job to advocate for the devil. So first of all, Google does not expect any impact on device or imports or sales because they agreed with the ITC on the downgrade, right? The ITC could ban them from importing but Google's saying we agreed with the ITC on this downgrade before we even pushed it. So we're confident that the ITC is not gonna stop us from bringing stuff in because we think we've gotten around it. Why didn't Google license it? Too expensive, maybe. What if Sonos is asking for a ridiculous amount of money for this and they just couldn't get them to bring a lower price? Maybe Google legitimately is like, we're not gonna pay that. Like we would have to raise the price of all our Nest stuff. So we'd rather take away the feature, maybe. Didn't you say in the pre-show though that there was evidence that they were actually briefed on this by Sonos and then used it so they knew they were doing it? Not evidence. Google and Sonos did cooperate on some stuff and Sonos under NDA showed them some features. Now, what Sonos is not accusing Google of is ripping off trade secrets and doing what they showed them. They haven't violated their NDA but Sonos' noses out of joint because they're saying, but they basically kinda saw how we did it and so figured out their own way of doing it which violates our path. That makes them more dirt-baggery, right? Well, I mean, yeah, it depends on how you feel about both companies. It always surprises me when a company says, and the company being Google in the sense, there's Google versus Sonos. I have a lot of Sonos products but I have a lot of issues with the Sonos business model as well and that's a story for another time but for Google to be like, well, sorry, sorry as a consumer, you're just the one who loses out. We just couldn't come to a resolution. It's like a little eye-rolly to me. I'll tell you what I would have to see. I would wanna see a bunch of other companies licensing this patent saying, yeah, the terms are pretty easy. It's not super expensive. I don't know why Google is being, if I saw that, then yes, I'm gonna look at Google and say like, you're being intractable but if nobody else is licensing this then maybe Google's got a point of like, well, we thought we had got around the patent, we were wrong, the judge disagrees in the ITC so we're just not gonna do it because I don't know that anybody else does this either. That Google Nest team post as well within their forums telling their users exactly what changes they were expecting with this downgrade, they seem related to like group volume levels for adjusting speaker simultaneously or using your phone's control to do something similar. Yeah, that's what I'm saying. Really basic kind of stuff, so, oh. Yeah, it's a method, right? It's not the code, it's not the technology, it's the method for doing it and patents always feel like that, right? They always feel like, well, but it's obvious except you can't get a patent, technically you're not supposed to be able to get a patent if it's obvious so it must not have been and Google didn't figure out a way around it. All right, I'm gonna stop advocating for the devil now and start advocating for Allison who always has a good eye for interesting CES announcements that might go under the radar elsewhere so we asked her to comb through the press releases for some notable notes. Allison, what are some interesting CES things you're hoping to find out more about? Well, I'm just betting there's enough people here that are still searching for the perfect pillow to give us a good night's sleep. Zarema is an after-event pillow that allows you to set its shape and height to what's exactly comfortable for you.  And it's got built-in sleep detection which allows you to track your sleep to see how well it's working. Zarema is made of open cell memory foam and it has a waterproof and antibacterial cover and it looks pretty interesting to me. It's available now for $250. Aw, man, you had me until the price. That's an offensive pillow. It's got a little elbow nudge. It's got little pumps and stuff in it that are pumping it up and down. If you're lucky, it's an elbow nudge. I don't know. I mean, my Fitbit tracks my sleep and that's a wearable that I wear at night. I know not everybody is into that overnight but it works for me. So this would not be something that I would necessarily buy but the wrong pillow sucks. We've all been there. And I love the idea of it saying, well, what do you need? What do you need to not only feel the most comfortable but also help your sleep friend get more sleep? I gotta say, Steve is very nice. When I'm snoring, he simply lays his hand on my chest and that makes me stop. So he's very nice about that. I don't need a pillow to do that but I still thought that was a pretty cool product. Another thing I'm always really interested in at CES is baby products. There's been a lot of things that I've found at CES that later on I've seen in the mainstream and watching my children with their newborns in the last few years has really highlighted how sleep deprivation is a real problem for parents. They're starting to hit the hallucinating point with one of the newborns. A company called Cradlewise has an inventive idea that might help keep the baby asleep. It's a smart crib that senses if your baby wakes up via a smart baby monitor that's built into the crib. So you tell it what time you think your baby should be sleeping to. It's supposed to be a three hour stint tonight. And if the baby wakes up during that time the entire crib rocks. And it's hard to describe. Not like an old fashioned rocker but pivoting around a point up above it. So it's sort of rotating and moving the baby. And it'll give you notifications to tell you the baby woke up in what time and it'll tell you, hey, I got this one. I put the baby back to sleep for you.  I thought that was all I was to sleep. Maybe you can modify that. The crib can also play white noise or playlists of your choosing. Now, you bought at the price of the pillow the Cradlewise smart crib is $1,500. But I know some people who would lay that hard cash down right now to regain sleep. And that's the crib too. It's not like an attachment to an existing crib. So, okay. I mean, it's still locked.  A hand that rocks the cradle is an AI in this case. Exactly. It's got a bassinet level at first and then it can go up to 24 months as a full-size crib. So it was very pretty too. I thought that was pretty cool. What about non-sleep items? Well, all right. I guess I was tired when I wrote these notes. When I was a kid growing up in Michigan, snowmobiles were all the rage, but they were gas powered. Now we've got electric bikes nowadays and French startup MoonBikes is bringing us an electric snow bike. They're ready to go to a range of up to 60 kilometers with an optional dual battery, which is pretty good. I did have a question, and again, I haven't gotten to talk to these people yet, but I wondered whether that range, how highly affected that's gonna be by the amount of snow you're in and how heavy that snow is. I don't know if you've ever skied in California, we refer to Sierra Cement. We have very wet, heavy snow a lot of times. And so that was a question I wouldn't have if I got to talk to them. Now MoonBike is three times lighter than a snowmobile, so they show them just hooked on the back of a truck. And I thought it looked really fun in the videos.  They're accepting pre-orders at $8,500 and $1,800 for that extra second battery. And if you want a fast charger, that's gonna add up to another $480. Wow, okay. Anything for less than $1,000. Okay, okay, let's drop it down. But it was cool, it looks really cool. It's cool, no, you're right, you're right, it's very cool. Looks fun. All right, I imagine if you're anything like me, when I was working, I packed a lunch to save money and save time, all the time going out to lunch and just waste a lot of time. I had to say though, after a while, a cold peanut butter jelly sandwich got old real fast, but so did fighting for microwave time to reheat leftovers and a microwave maybe of questionable smells. A company called Steambox has created a self-heating lunchbox that might solve all of these problems. It's a rechargeable system that can heat up three meals on a single charge. Now this isn't some giant industrial looking box that you have to carry. It's got a beautiful light wood grain lid and it makes me think of like a nice looking bento box, kind of larger than that. I wasn't able to find this dimensions of Steambox, but in the photos it looks to be easy enough to carry and big enough for a reasonable size lunch. Inside there's an insulated chamber into which you put a metal tray with your food. Now Steambox can be controlled by an app, of course it can, while showing you your battery charge. Steambox is on pre-order for 179 Euro, which is around 200 US. So I think that's finally something affordable. Yeah, affordable, but more affordable. Yeah, and interesting. This is one I definitely want to test. If you were using it on a daily basis, you would make that money back real quick and you would enjoy your food away from home that much more. I love this idea. No fish microwave, right?  Yeah, it's not popcorn. All right, my last one. I've only become more aware in the past few years, how many people are living with dyslexia? These people managed to muddle through life with this invisible-to-us challenge to reading and writing. Something called lily lamp is a small battery-powered personal lamp that emits customizable flashes of light that are almost imperceptible to the naked eye. These flashes make the perception of writing more precise for a majority of people with dyslexia, or so this company says that it does. The French developers of lily say that reading becomes smoother, faster, and less tiring as a result. The flashes of light are customizable through an iOS or Android app. You could order lily lamp, let's see, 349 euro, which is roughly the same in US dollars. Yeah, I want to see some of the more medical vetting on this, but potentially great, I love it, yeah. Yeah, I do have a friend, if I could get one, I have a friend I could give it to to have her check it out and see what it did, whether it actually does as it says on the tin. Well, I'm sure it flashes light, but whether it fixes the problem is a real question. Yeah, whether that does what it says, yeah, for sure. Well, thank you so much, Allison. These are great, these are great little finds that I have not seen anywhere else, yeah. Across the spectrum. Well, something that you might have heard about recently is cryptocurrencies. Everybody's getting into crypto. Last year, last year, remember, 2021 wasn't that long ago, we reported that Radio Shack intended to focus on cryptocurrency trading. Some folks thought that was kind of crazy. Other folks said, eh, it makes sense. GameStop just launched a cryptocurrency division to establish an NFT marketplace for game developers. It's also partnering with two cryptocurrency companies to develop games that use blockchain and NFTs, Ubisoft, Zynga, and Square Enix, have all recently announced plans to sell NFTs as well. Even antivirus makers are getting into the fun, so to speak. Crabzone Security notes that last July, Norton 360 added an Ethereum mining program called Norton Crypto to customers installation. Norton LifeLock says that the program is opt-in, so you don't have to do it, got opt-in. It'll take 15% of currency's mind though, the rest to be kept by the user. Might be worth your time, might not. Your system also must meet minimum hardware requirements, including an Nvidia GPU, and at least six gigabytes of RAM. If you enable the program, it'll work when your system is otherwise idle, so it shouldn't interrupt what you're doing when you're actually active on your system. It'll create a wallet and store your encryption key securely in the cloud. Only the user is said to have access to this encryption key. Norton Crypto makes it easy to transfer any coins to a coin-based account, so they have a partnership there, obviously. Oh, transfers will take out a 15% fee as well as gas fees associated with any Ethereum transaction, which vary by day.  They are high. The system launched back in July, but received attention on January 4th when Corey Doctro tweeted about it. Norton LifeLack not only insists it's opt-in. You don't have to do this. This is opt-in, but also issued a statement with instructions on how to remove ncrypt.exe if you so desire, if you're not cool with it, not down with it, don't want it on your system. Norton wants to help you out there. However, many users did not like the executable being downloaded at all without their permission, even if it wasn't enabled. They just didn't like it being there. So a lot of people worried about power consumption were worse. Robert, what are your thoughts? That would be my one concern overall. I like the fact that it is opt-in. That's the way to do it if you're gonna voice this on someone. The 15% fee, you know, give or take it, if that's what you want, you can take it or leave it. However, just be aware that they are specifically requesting certain GPU characteristics that imply that it's gonna be a GPU minor. These programs will run that graphics card, in particular the memory, harder than any game currently out there. And you have to be aware on certain cards, that can be well over 100 degrees Celsius on memory temperatures alone, let alone the increased power consumption, there are graphics cards out there now, exceeding 350 watts when they're grinding away. And depending on the cost of your GPU, I'm not sure if I trust something like this program from this company to be managing the health characteristics and looking out for my best end, in terms of managing that setup and making sure it's not gonna fry my freaking graphics card that may be very difficult to replace in this day and age. I mean, at that level of degrees, 100 degrees Celsius, you can't crank at that for very long before you're in trouble, right? That's the weird part right now. There are certain, on the high end of graphics cards today, they're using a form of RAM called GDDR6X. It has a list temperature of about 94 C, but often these implementations I see will well and exceed that, like 104. Even when you're gaming sometimes, depending on the cooling setup, depending on your room conditions, either way, just be aware that if you're gonna run crypto mining hardware for Ethereum, it is just gonna push that memory on your graphics card to the limit and be aware that there could be some wear and tear involved. Hopefully they're increasing the fan speeds to keep things a little cooler. Those kind of back end things that somebody might be a little more familiar with this kind of project would be aware of, I just hope that they're making that aware to the users in general. I think that's, oh, sorry, go ahead, Allison.  Oh, I can make some money, okay, click. That's true. I don't have a problem with them offering this personally. I don't have a problem with everyone saying, great, thanks, I'm not going to use it. I think what Robert brings up is the key thing is if people look into this, is Norton making it clear what they're getting into? That's the part that I do have an issue with and to your point, Allison, these are not necessarily savvy users who know this stuff. So you need to make it extra clear, like if you turn this on, here are the implications of it. I see people getting bent out of shape that they have it at all, just don't use it, right? It is opt-in, it's not opt-out. They didn't force this on people. People are getting really nose bent out of shape that the file was downloaded at all. That's pretty normal for software. If they're offering an option to not make you download it when you select it to have it there and ready for you, so I don't really have a problem with most of that stuff. It's a thing that I don't think they need to be offering. I don't have a problem that they offered it just because I don't want it. It's opt-in, you know? It's, you don't have to get mad about it if you don't want to. Hey, well, folks, if you agree with me, please let us know on social. I mean, if you disagree too, I guess that's all right too. Get in touch with the DTNS audience on our social networks. Daily Tech News Show on Twitter, it's Daily Tech News SH. Just start typing Daily Tech News Show until you run out of characters. Or DTNS Picks, DTNS PIX on Instagram. No CES coverage is complete without Robert Herron's perspective on all the TV and display panel developments that were announced at the show. And Robert, I want to start with one of the hot buzz terms of the show, QD OLED. Can you explain to us in top level terms what QD OLED is? If you think about the OLEDs offered today from companies like LG, they currently generate the picture you see. Each individual pixel is a little piece of OLED material that is glowing when stimulated by electricity. Now for LG's design, they use a white OLED material and that pushes through a color filter. And each sub-pixel will be red, blue, green, or in LG's case, they add a white sub-pixel as well. There is immediate efficiency loss right there when you're transitioning this pure white backlight through this piece of plastic to see the pixels the way you need them to be. Now with QD OLED, what they are thinking of doing and what they are and what they have done is simply replace that color filter with a material. One, start with a blue backlight material that is well engineered and very close to where it needs to be, spectrally speaking in terms of its color coordinate to be good for use in televisions. And then convert the rest of that light, the extra blue light using red and green quantum dot materials, that's the QD part in QD OLED. Those quantum dot converters are very efficient. And instead of say a 90% loss through a standard filter used on either an LCD TV or an OLED from LG, you're looking at something closer to like 10%, which is just fantastic. That's huge. And the design by nature will also be pure RGB. There will not be a white sub-pixel. So that could imply superior color saturation in addition to already the perfect black level you get from OLED anyway. All right, so overall, yeah, I mean, I know QD OLED sort of burned up the headlines as far as TVs go at CES. What else did you see at CES that is worth noting? One, the distinct lack of actual next generation OLED displays that you could actually put your eyes on. That was kind of a bummer. Yes, we had the QD OLED introduction from Samsung Display, not Samsung electronics. Samsung electronics didn't actually show off this next gen display. However, in Sony's booth, they at least announced their product, the A95K, which will be based upon this Samsung display product and available in 55 and 65 inches. That's currently listed on their website. That arguably will be one of the premium TVs for 2022, even though it is currently limited to a max size of 65 inches. LG's display division also announced, although they have not actually shown this off yet, is their next gen OLED technology, looking say to 2023 and beyond. They're actually using deuterium particles within the OLED materials to create brighter displays that are more robust. Deuterium like heavy water deuterium? Yes. Wow. And that's kind of crazy. You can Google QLED or OLED.EX and that's their technology for that. Now all of this... What's heavy water? Heavy water. It has what? It's an isotope of hydrogen. So... Yeah, and it's often used in nuclear reactors because the water can absorb radiation. I want to say it has one extra proton or not. Don't quote me. Yeah, it's something like that if that's not exactly right. Yeah, yeah. But what is also kind of cool is that coming to PC displays, we're having more and more OLED showing up there as well. So LG showed off last year, of course, their Ultrafine OLED Pro monitors. They have a new version for this year that will include hardware calibration options and just generally better performance. Alienware is showing off a monitor based upon, and so is Samsung of course, based upon that QD OLED technology as well. And these are highly anticipated just to see what kind of longevity are they going to be able to pull out of these in a PC environment. Now, LCD televisions will always remain the affordable option and for some of the biggest screens out there. And many LED LCDs is the trend that everyone has now jumped on board with. This is basically changing up the backlight system on an LCD TV. So that instead of using just a few of them and maybe they're extra bright, you're using thousands or in some cases, tens of thousands of these to create a more seamless and controllable backlighting system that can produce very good local dimming as well as just punchy bright output when you need it. Now, in the flagship TVs for 2022 from companies like Sony and that beautiful Z9K you can look at right now online as well as Samsung's QN900B and the Hisense U9 series. This year are all adopting this mini LED system that should produce anywhere from two to three. I'm looking at that new Sony Z9K maybe peeking out at 4,000 nits of light output which is significant for a home theater display. That would be impressive to say the least. And of course, those examples will be 8K screens. 8K going forward will just, I think, really kind of take over anything say above 65 inches in screen size. That's where it's most effective including I have to say, Hisense showed off their latest generation 8K projector using RGB laser technology that they've already pioneered for their award-winning 4K projector that's currently available. That design looks fantastic as well. So there's no shortage of, I think OLED getting bigger and brighter and in some cases just simply better. LG did announce a 97 inch model coming out this year. That's gigantic and a 42 inch as well. But one final thing I'm seeing across the board for the 2022 lineup is the incorporation of the NextGen TV tuners, aka ATSC 3.0. And that, if you care, is the system that will basically deliver 4K broadcast video live streaming over a potentially cheap antenna. So if that's important to you, the deployment map gets a little more filled in every year. Here in the Bay Area, it's total weak sauce at this point. Last time I checked, we didn't have a single channel currently active, but that's coming and it's built in. And I think that is a key feature that's gonna be there and hopefully occasionally people will take advantage of it. Yeah, my TV's up against a fireplace currently. So it's like, there just isn't any OTA stuff happening. Real quick, Robert, my mom is in the market for a new TV and she went to Costco recently and was like, those OLED TVs are very nice. If you're kind of in a, let's say you want a new TV, you're thinking of spending $1,000, where would you point people to? I think it depends on the room environment, most of all. And OLED would be a great option, but I'm not sure of what you would get at $1,000 for OLED. Even the 48-inch model is probably above that budget. And to stay in budget, I'd be looking at something more along the lines of a value TV. That TCL 6 series is still gonna be a fantastic money saver that gets you. Something that's bright and punchy, supports all the formats and it's really easy to use with the built-in Roku system. Otherwise, actually, there isn't the new 42-inch model. If that's big enough, you could probably find that for $1,000 real soon. Coming from LG as a 4K display at 42 inches. I think that will be far more popular as a PC display than it will be for a home theater display. Yeah. Otherwise, for about $1,200 to $1,300, that's where you get into the 55-inch screen size for OLED. In a good quality, like their C2 coming out this way. And I think for most living rooms, that's what people are going for. Anything lower than that is maybe a little small. If I need something as a light cannon to combat room lighting, that's where I'm looking more toward LCDs. Samsung's premium displays have the most wonderful anti-reflective coatings and I'll be curious to see if any of that makes it into their new QD OLED designs or their QD display designs that they'll be bringing out later this year. But HiSense is another good one for their H8 and even their H7 is a terrific value for what you get out of that TV in terms of brightness, picture quality, good factory calibration, built-in apps that you might actually use, things like that. All right. Well, that's it for Daily Tech News Show. Those of you on good day internet stick around though. We'll be carrying on the conversation. Thanks to our brand new boss, Frank Kim, who hopefully will join us in the conversation later. Frank just started backing us on Patreon. Thank you, Frank. We also have a great panel of folks to thank today. Lynn Peralta, we'll start with you. Let folks know where they can keep up with your work. Sure thing. Well, first off, this is what I got out of the great information all today. This is what I got out of this story about crypto is, you know, I know I'm a little bit late to the game here, but Radio Shack selling crypto, I think that's kind of fun and interesting. I'm thinking that they're probably gonna call it Tandycoin and, you know, they're gonna need a phone number for the transaction, of course, and you can only buy it in-store. So, I mean, you can only use Tandycoin in-store. So there you go. And then eventually you'll be able to use Tandycoin in their metaverse, Tandyland. Tandyland. I like that. Very, very good. You know, yeah, this image is available right now online at my Patreon, patreon.com forward slash lender at my online store at LynnPeraltaStore.com. I also just want to remind people that this is the last Friday I'm gonna be on DTNS. I'm not going away. I'm actually going to Thursdays. So ArtProv is going to Thursdays. Must see TV. Yes. Well, Lynn, we are lucky to have you on any day that works best for you. So look forward to your drawings in the future. Robert Herron. It's not a CES without a Robert Herron roundup. Thanks so much for being on the show with us. Let folks know where they can keep up with the rest of your work. Follow me on Twitter at Robert Herron. You can also check me out at AVXL.com for my usually weekly podcast. We're getting back on track now for the beginning of the year. And if you want more information about calibration or video services, check out HerronFidelity.com. Excellent. Alison Sheridan, also so glad to have you. Your first show of 2022 and not the last, I'm sure. Let folks know where they can keep up with your work. The best place to go is podfeat.com or you can follow me on Twitter at podfeat. Well, we are live on this show. We keep cranking out everybody Monday through Friday, 4 30 p.m. Eastern 2130 UTC. You can find out more at dailytechnewshow.com slash live. And we'd love to have you join us live if you can. We are back on Monday to talk dogs and the physics of computer animations with Blair Bazderich. Have a great weekend. This week's episodes of Daily Tech News Show were created by the following people, host producer and writer, Tom Merritt, host producer and writer, Sarah Lane, executive producer and booker, Roger Chang, producer, writer and host, Rich Strafilino, video producer and Twitch producer, Joe Coontz, associate producer, Anthony Lamos, Spanish language host, writer and producer, Dan Campos, news host, writer and producer, Jen Cutter. Science correspondent, Dr. Nicky Ackermanns, social media producer and moderator, Zoe Detterding. Our mods, Beatmaster, W. Scottus I, BioCow, Captain Kipper, Jack Shid, Steve Guadirama, Paul Rees, Matthew J. Stevens and J.D. Galloway. Modern video hosting by Dan Christensen. Video feed by Sean Wei. Music and art provided by Martin Bell, Dan Looters, Mustafa A, A-Cast, Creative Arts and Len Peralta. Live art performed by Len Peralta. A-Cast adds support from Trace Gaynor, Patreon support from Stefan Brown. Contributors for this week's show included Patrick Norton, Scott Johnson, Justin Robert Young, Shannon Morse, and Allison Sheridan. Guests on this week's show included Nate Langson and Robert Herron. And thanks to all the patrons who make the show possible. This show is part of the Frog Pants Network. Get more at frogpants.com. The Diamond Club hopes you have enjoyed this program.


Sure, for my school in Frontier, I think our administration is really focused on professional development. We actually take most Fridays out of the year, our partial days for students, allowing teachers to really focus on PD. And part of that is allowing teachers to be able to share this information from various places that we brought it. So I feel like, you know, fortunate to have a great opportunity to be able to take what I'm learning here and bring it back to the school. And, you know, fortunately my school is really open to having that being shared. So, you know, I really look forward to doing that. We have an instructional leadership team at school where Catherine and I are both members. But on the instructional leadership team, we have administration and teachers. So it's a nice fit. We all come to the table, take off our hats, and we're all talking at the same level. So taking anything that we've learned from here, we can bring back to that table and share amongst our peers and administration. So it's a good thing. We also, this year, our Pathfinder, are coming into the next school year. We have a professional development committee that I'm on with a couple other teachers, academic, vocational, and also administration. And our job is going to be to plan three professional development days for the staff. This fits, I think, a lot already with the interdisciplinary things that we've been trying to do and the skills-based skills-based pieces. The other thing that I didn't know when I signed up for this institute but has been a really interesting component is this teacher-consultant aspect where we're kind of being trained to present professional development to other people, which I am really finding to be an interesting part and something I'm interested to get more involved in.