These levels have specifically bad ones, and more dangerous ones than normal, along with dangerous environments. Just consider these levels ones that you should avoid at all costs. Thank you so much for watching. If you enjoyed the video, please leave a like, and if you like longer videos, tell me in the comments what other ones I should do. Without further blabbering, I will see you at the end of the video in the outro section. Backroom's level 318 from the fandom is classified as a class question mark, question mark, question mark, question mark, question mark, difficulty, and is very mysterious and very obscure. That is the only backroom's level with that classification, by the way, so you know you're in for a doozy. The classification graphic says that you're safe now, and everything is okay, and it's just you. So obviously, some kind of thing or creature or entity is trying to create this level and run it. The level physically takes the appearance of a derealized looking sprawl of houses. The houses are colorful, but lifeless. And they seem to resemble those houses from iSpy books and those old weird claymation style movies, and some of them even have like a Mr. Roger's vibe to them. But overall, the level seems very fake, almost animated in a way. A soft song plays the entire time you're here, and it's almost like a carnival sound. The danger of the level tends to get worse and worse and worse the deeper you get into it. This video is a whopping 40 minutes long, and I know for a fact that you will get thirsty at some point while you're watching it. Thankfully for you and your hydration, GamerSupps is here to make it all better, man.  It's got no sugar. It's got less than a calorie. There's no fillers or any of that stuff inside, and it's absolutely and utterly, utterly delicious. I've been known to crank a cup or three cups back and edit for like five hours straight, so if you want to grab some of this amazing nectar, you're actually in luck, because right now, there's a massive Valentine's sale going on. For the next seven days, you can get 22% off your order on GamerSupps' website using code BRUGLY at checkout. Again, 22% off at checkout using code BRUGLY. There's so many flavors that you could choose from. You could go with my personal favorite, Blowhole Blast, if you want to. Anyways, if you are going to be alone this Valentine's Day, like me, why not cuddle up with a brand new tub of GamerSupps to make all the pain go away? Again, that's code BRUGLY at checkout for 22% off your order. Get it while the getting's good, because it only lasts for the next seven days, so you get seven days for that 22% off. Do it if you please. All right, all that said, back to the video. When you get sent here originally, you'll get this overwhelming calming sensation that just makes you feel at home, almost like you've been here, or that you remember you being here.  More on that later though. The actual houses that are here can be fully explored on the inside and the outside. And inside of them, you'll find some pretty unnerving stuff. Mainly, each house is empty, like completely barren of any resources, any furniture, any dust. It just seems like no one's ever lived here. It's empty 100%. There is no dust, no trash, no sign of human existence. And most of them are completely abandoned like this, except for some houses have staircases and fireplaces and that kind of thing. But in general, these houses are safe to stay in, but staying on this level as a whole is not safe. And you'll see why in a second. Just make sure you don't get stuck here for too long and you'll be all right. The paths that connect the houses and the roads in front of the houses are all made out of a weird concrete gravel type mixture. And all the houses and roads are placed on an expanse of grassy hills. The grass itself is fake like plastic and it seems like it's literally just ripped from an eye spy book. It's very similar to level 94, but with a much different layout because the houses here are more neighborhood like and not really dotted randomly like level 94. The level document is written from the perspective of some kind of entity or creature or something. Quote, it's time to wake up. This isn't the reality you're familiar with. That reality is fake. It's time to embrace the real world. End quote. That's a sentence that's right in the middle of this article. So as you can tell, this level is some kind of trap that you as a wanderer perceived to be real and not dangerous, but it is.  You'll think it's 100% reality. It'll seem more and more so the deeper you walk. And just like the level name says, you will need to wake up in order to realize that it is a trap. The third paragraph of this level entry says quote, now that you're here, I suppose I should show you what's new. Everything is simply beautiful. You can fly, teleport, do anything you ever wanted to.  End quote. Yeah, it's totally not creepy or unnerving or anything like that. Not at all. The level is also thought to be infinite since the edges of it have not been found yet, but the deeper you get inside of it, the more fake it'll actually look, but you'll be under the level spell and trance, so you won't be able to tell it. At the start of the level where you begin, the houses look like they're from your life, but eventually they'll get to where they look completely fake, like a small display someone made for a project at school, but you will still think they're real. As I said earlier, the level plays a soft cartoony sound through the whole thing, which this might be the source of the trance. We're not really sure. We're also not sure where the sound comes from if it's speakers or if it's just the atmosphere. So here we have a whole level that looks like an uncanny I spy Dr. Seuss background with strange effects that make you think you're safe at home. But who or what is literally controlling it? Who's writing this? Who is making the level go round? What is it? Well, in the entity section in this article, we might get some insight on that. The page says, quote, you want to know more about me? Well, I suppose you deserve to know. Hello, Gary. I'm what they call the awakened. I will. I made this perfect reality. I don't really have an awesome looking true form. I'm just this human, this guy in a brown jacket. And I'm always smiling. You'll never be fully dressed without one, you know? That's the only feature that really stands out about my body, though. I don't have eyes, just a smile. The rest is just a shadow, although I can see, end quote. So from that entity's disturbing self-description, we can pretty much deduce that it takes the appearance of some kind of vague humanoid shape with a jacket and pants. And the most noticeable feature of this entity is its massive smile carved into its face because besides that, it's not got any eyes or shape. And then it finishes itself by saying the rest of its body is shadow. So we can assume the creature is a physical form that takes the appearance of a shadow with a smile that kind of looks human. And that's all we know. It would probably look something like what a smiler with a body would look like. It's terrifying to think that that creature controls and traps people here. The end of the page has a hidden link that takes you to one more sentence, quote, it doesn't matter anymore. There is no end to this nightmare. There is no home. There is no true ending. That's how it's always going to be if things keep going at this rate. And I know for a fact that things will keep going on like this. Go, just go, leave. You don't deserve a good ending if you can't make one yourself. I guess it's safe to say that you've overstayed your welcome. Goodbye, Gary. Never come back. End quote. So yeah, it sounds like this entity is kind of sad, to be honest. Maybe it doesn't want Gary to leave. Maybe Bro just needs to take a chill pill. To enter the level, you have to wake up. And to exit, there aren't any. I don't know what else to say. You have to stay here. It's unknown what both of those mean, what wake up and stay here mean, but we can assume that it's really hard to enter and the exit is also really hard to attain. So for the time being, it seems as if you're going to be forced to explore this uncanny expanse of hills, houses, empty streets, and loneliness while being talked to by a shadow thing with a smile on its face. Cool. Personally, I love this level and I think it's really good. I think it's Agent Anonymous's best work I've read. I've read a ton of their levels and I've gone over them. And I 100% recommend checking the article below, reading it for yourself. This level actually is very, very well done. And I think it speaks a lot to the community of the back rooms where sometimes levels are made too kid-friendly when in reality the back rooms is a living hellscape. It's not kid-friendly. It's not safe. It's scary. And I think this level does a good job of expressing that in a cool, horrifying, limited way. The houses here, the fake ambience, it's all perfect. Hope y'all enjoyed it as much as I did. Level 99 of the back rooms is classified as highly unstable and very unpredictable. And it's such a strange place that it can even be given a regular class. You know, like one, two, three, or four. It's just unstable and insecure. The level takes the overall appearance of a twisted and entangled environment full of anomalous properties and locations. Think of shoots and ladders, but with liminal space world boxes.  The two main areas are a dreamy and surreal looking landscape. And the other one is the other several subspaces that can be accessed from those dreamy landscapes. These subspaces have warped and blended together. And you'll hear all about it. No worries. I'm gonna go over all of them in this video. This level has a nostalgic effect. It's similar to the one on level 18, if you remember that. So it's thought that because of that it might physically be close to level 18. We don't know. It's level 99 in the ranking. I don't know. But anyways, this nostalgic effect causes the level to produce places and things that the wanderer has seen before or something very familiar to them. For instance, it might be your elementary school or your childhood house or something like that. It somehow knows the places that you've been and has access to all the memories. The first part of the level where you will start at will look to be a plane of grass that goes out in all directions.  So prepare yourself. But as you're walking through this empty grass plane you'll notice that it feels empty and alone. It's just green, fake looking grass as far as you can see. And as you're walking down these planes the level will begin to produce black circles in the sky. These are called wormholes.  If you hesitate to jump inside of one something called a text hallucination will appear in the sky. Now this is an effect that happened back on level 78 as well but it's when strange lines of text will actually pop up in the physical sky. Like you're not just seeing things. They're actually there and it'll say different things. The text seems ethereal and foreboding and you're just really scared to look at it for some reason. Like it makes you feel uncomfortable. Sometimes the text will say negative things and sometimes it'll be calming and nostalgic. But the text kind of makes you want to jump into the wormholes. It's almost like it's luring you into them. This text effect can happen in any of the subspaces on this level as well. But when you enter these wormholes you will feel instantly dizzy and you'll be overcome with vertigo. You'll feel like you can't stand. You get all dizzy and numb and you start to fall into an infinite black void for an unknown amount of time until you reach your destination within these dream subspaces which I'll get into in a second. But there are three anomalous properties that you'll experience while exploring these subspaces. Those are eye decals, sensor rectangles and sky textures as well as some of the texts that I mentioned. Now eye decals are manifestations of real eyes. Again, similar to level 78.  Constantly moving and blinking. Some are floating, some are just on the ground. Some are attached to walls and other objects. It just depends. The eyes are very uncanny and unnerving to look at so try not to. Now sensor rectangles are 2D black anomalies in the shape of a rectangular void. They appear randomly throughout the sky and the ground and windows inside these dream subspaces and they seem to have no purpose but to block out random things that don't make any sense. Sky textures are the last anomaly that you might face while exploring these subspaces. And these are randomly and briefly appearing cloud textures that will show themselves where doors or windows or walls or ceilings or floors should be. The sky textures often appear inside of doors and windows and walls and if you listen really closely to them you can hear the faint sound of wind blowing through clouds. These sky textures are very unknown and strange. No one knows if you can walk into them and no one knows why they appear but you should probably try to stay away from them. I'll touch more of them later though. But now that you know about all the strange anomalies that you might find while exploring these subspaces let's talk about the actual dreamy areas that you'll have to explore to get out of the level. There are six different dream spaces that you will encounter while being here and dream spaces are the name given to the sub layers of the main level and these locations are accessed by those wormholes. This is where those feelings of nostalgia really come into play since each of these six sub areas is personalized for every wanderer who comes here. The sub areas are the grassy halls, last day of school, the store, the stairwell, playground and the walk. And let me explain them all real quick. So grass halls typically consist of one large building with rooms and corridors made out of beige drywall and there is fake grass on the floor. The grass is said to look fake and real at the same time, just strange, but inside of this building some of the walls and the windows and doors will have the appearance of sky textures which will give the strange outdoor indoor vibe to people exploring. This has been known to cause derealization effects so watch out for that as well. You also might find windows and stuff like that that opens to an outside that looks to be a plane of grass and trees. You can actually climb out of the windows and explore those grassy areas. They're just another subspace accessed from within this subspace. Yeah, I know it gets crazy, but it's gonna get even crazier. Under the grass on the floor is a carpet-like material that this grass grows out of and it's unknown how this happens. It's not dirt. It is fake grass actually growing out of carpet. I don't know, whatever, that's crazy. In this sub area, you may run across a tech solution or a sky texture, but it's pretty rare. These grass hallways are typically pretty safe. The last day of school is what looks to be an elementary school, specifically the one you went to. That looks like it's on its last day. The ambience is very calming. You can hear soft chatter of students talking and shifting papers and bags. You can't see anything like that though, you just hear it. But the classrooms and hallways and everything here is very vibrant. It's got this huge, vibrant vibe to it and it's similar to how life used to look to all of us as kids. You know, when we were younger, everything was bright and glowy. That's how it looks here. The rooms and halls will literally give you that feeling that you had on the last day of school. You know, that huge adrenaline rush that summer is about to happen? That is the vibe you get here. There's also an outside area to this last day of school subspace where you can literally walk out of the school and you can find your childhood house inside of the subspace. Like you can walk from the school to your house and it's all fully explorable. Just don't stay too long or you might never leave. You might be tempted to stay forever, which is not good. The store is exactly what it sounds like and it can be accessed from the last day of school subspace. It's an older looking store that's always after closing time. So it's dark outside and it's got this quiet, eerie silence inside. Here, you might find ID cals, mushrooms and some tech solution in the sky. Perhaps this is one of the more basic subspaces though. Now the stairwell is a very anomalous subspace, but it seems to be in the shape of a vertical staircase that goes up and down forever. The light in the staircase, it's not come from actual lights, it comes from sky textures that appear. That is the most common one here and you'll likely also see some ID cals as well while climbing the stairs. This expanse of staircase gives people the sense of dread and sadness and it just makes everybody feel like they should give up for some reason. Again, it's unknown why but it's not recommended to come here because exiting is difficult. The playground is an interesting subspace because it kind of acts as a hub for the level. Instead of it being a hub like the actual hub level, here you get on a slide and you slide down it into a wormhole and you'll be sent to a different dream subspace. This is the easiest way to travel from subspace to subspace and once you find this place you can pretty much do whatever. The slide seems to be an indoor play place type area with a massive sprawl of different plastic slides, all of which take you to different subspaces. Some of them discovered, some of them not. Be careful which ones you get on. That way you don't get lost too deep into these sub areas. And lastly, the walk. Now the walk is made up of a checkerboard floor that is floating in a place that looks like the void. I don't know if it's the void or not but it looks like it. On each side of the floor there are large mushrooms towering over you. The path is completely straight but it looks like it curves up and down but since it's so long you can't actually tell. Now this walk is very important because it is the only way of exiting the level. Like you have to come through all those other subspaces I mentioned and find this walk and you have to do the whole thing, walk the entire way to escape. The only things here that you might see are ID cows and those mushrooms appearing. You might also find a random wormhole or two but at the end of the walk there are several doors that open to different levels and that's how you escape, that's the exit. And speaking of that, let's talk about the entrance and exits. To enter the level you can no clip on level 96 and you'll have a chance of being sent here and to exit you gotta go through all the subspaces to get here then walk the entire thing and you'll find those sets of doors at the end and the doors can open to a ton of different levels like zero, four, and nine and so on. So pick carefully. There are no actual entities here that have been documented besides the strange eyes, maybe a shadow figure or two and maybe a lost human that's turned into an insanity. That might be all this here but we don't know, it's not confirmed. But yeah, level 99. It's like a huge game of shoots and ladders that's made up of weird liminal spaces that are all connected and shoved together. I really love how you can get to each different part without no clipping. It makes the level feel so big and just expansive. I think this level's fantastic. This is what a liminal space level should be like. Hope you enjoyed it, I know I did. Level 5.3 or the decaying decadence is the first sub-level that you're gonna run into after being stuck in level 5 for too long. Especially if you walk too deep inside of a hallway, you'll eventually come here. This level has been classified as a class 4E environmental difficulty, 4A being unsafe, very, very unstable, but with a low entity count. However, that entity is a handful and I'll tell you all about it later. The sub-level is an extremely elusive one and almost nobody can find it on purpose. You can't just go run into level 5 until you run across it, like you only accidentally could come here. And the level looks like a large, dark, and cold abandoned mansion, full of holes and collapsing rooms and hallways that all seem to be surrounded in the void. These holes and these cracks lead directly to the void level. And if you were to jump through those cracks, you would quite literally be there inside of the black void. It's completely unknown how the sub-level got to be so destroyed, so crumbly, so desolate, or so abandoned, or how it's so unstable, or even just why it's falling apart. But, you know, knowing me, I'm gonna get into some theories on that later, just don't worry. There is very little lighting inside these hallways and rooms and the entire place is just this one, old, crumbled mess.  The light sources aren't even connected to anything here, but they can still somehow turn on and off randomly, which is just like, how do they do that? Then again, this is the back rooms and it doesn't have to make sense. The halls and the rooms are also full of old furniture, things like beds and couches and tables and chairs and that sort of thing. And you might even run across a few floating pieces of furniture that are suspended in air, like somebody's using the force on them, they're just stuck. Now I'm sure this level's connection to the void has something to do with its crumbling and something to do with the floating chairs, but again, more on that later. While walking through these abandoned hallways inside this mansion, you'll begin to hear echoes of a disembodied voice. The source of this voice is unknown and it's often not even actual words that are spoken. It's kind of just sounds or murmurings, things like laughter or crying can be heard. Most of the times the voices sound sad or even traumatized and it seems like they're trying to speak English, although some people have claimed to hear Spanish and German too. Now there's another part of the level that is above the hallways in the rooms in this mansion part and this part takes the appearance of a large attic. The attic extends through the middle section of this mansion and it can be accessed by one of those pull down ladder things that come out of the ceiling. The attic is always freezing cold and it is the source of the cold temperature for the entire level. It stays at around 14 degrees Fahrenheit or negative 10 degrees Celsius if you don't speak American and it should be avoided at all costs. I mean that in all honesty, do not, I repeat do not go to the attic. Inside the attic you'll find broken glass and boxes and just a tight cramped environment.  The low temperatures in the broken glass are actually not the real reasons that you should avoid the attic because lurking around in this attic is an entity known in the back rooms only as cold.  Cold can seemingly teleport inside this level and it'll teleport near a wanderer only if the wanderer knows of its existence. So now that thousands of you know about cold it'll, it can teleport to you. I'm sorry, I had to tell you. I couldn't keep it in any longer. Once cold captures its prey with its hands it'll use its sharp triangle face to headbutt and to stab that prey in the face and then after that it'll drag the prey back to the attic to do whatever it does with it, eat it or I don't know. Cold is very smart and it knows the level very well so if you're gonna get stuck in this level at all you're gonna need to find an exit ASAP to avoid being spiked by its cold's head. Now other than cold there are not really any entities in large numbers. You might see a hound or a smiler but other than that you're not gonna see anything. Cold's background and story is virtually unknown and only a few encounters with the entity have been reported so tread lightly when walking on this level. There are no colonies here since it would pretty much be impossible to form one since the entire level is crumbling and there's a decaying vibe plus cold wouldn't like that. To enter the level it's literally just luck based. You can just randomly be walking around level five and you'll get sent here by accident or you could just walk too deep into a hotel room inside the level and you could be sent here. I don't know, I don't know to tell you. Now to exit you can walk in this level into one of those void pits where everything is cracking and you could go there or you can do the actual good exit and find an old phone lying around in the rubble, touch it and you'll be sent back to the regular level five and this is the most common and most safe and most reliable way to leave the level. So yeah, this level, level 5.3 is this crumbling mansion full of strange old artifacts, weird rips in the space time continuum, openings to the void and a strange entity that lives in the attic. Probably one of the best sub-levels I've read to be honest. Leave a like if you enjoyed that one too. Level 73 of the back rooms or the Redlands as it's been nicknamed is a level that is extremely dangerous and I cannot state that enough. It is extremely dangerous. It's been given a class five difficulty for being unsafe and unsecure and infested with scary entities and I'll get into all the entities later on. In fact, the first single line on this document says, quote, do not go searching for level 73, end quote. But let me tell you all about it anyway so you can figure out why you should never search for it. The Levels article was written and uploaded from deep inside a castle that's located in the middle of this level. The people that wrote the article, they ventured through the various parts of this level to get to their current location so they have pretty decent knowledge of what the level looks like and the dangers that lie within and their description of what the level looks like is what I'll be going over in this video. Level 73 is the 74th level inside the back rooms. It's most commonly known amongst wanderers as the Redlands because of its dark red stained grass and sky features. The level takes place on some sort of island with a large ocean surrounding it. The island as of right now is the only accessible and searched through part of the level since the ocean part around it has not been explored yet. Apparently the water should not be touched or entered at all due to deadly aquatic anomalies. But the island part of the level is so hard to explore and it's just a very volatile place to be, mainly due to the entities that call this place home. The island itself is a dark red grassy island in the shape of a large circle scattered across the island along the red grass are trees and small shrubs that look dead and decayed. The trees and the grass and the shrubs all are circling the island and in the middle of this circle is a large stone castle. Now the entity density on this level is estimated to be one entity per 35 square feet. Let me repeat that, one thing every 35 feet. So pretty much is gonna be constantly entities around you somewhere in your eyesight. But I'm sure you're asking, you know, what kind of creatures actually live here? Why is it so dangerous? There are smilers, death moths, clumps, dullers, hounds and skin stealers and camo crawlers. Even death rats have been seen jumping through the grass. These are the most commonly reported ones, but those are just to name a few.  Again, no idea what they are, but now you know about them. Obviously all those entities are dangerous in their own right. So when you get sent to this level, the second your feet hit the ground, you need to run as fast as you can through the field to get to the castle. Level 73 is pretty much in a perpetual state of darkness and there's no day or night cycle whatsoever. The only lot you actually have here is a full moon that casts this reddish glow across the cloudy sky. The moon itself never moves and never changes in its light intensity, giving the sky this fake uncanny type of vibe. Now, right under what I just said, there's a sentence that states this, you do not want to use an artificial light source and that you do not want to see at all until you get to the doors of the castle. And I'm sure as you can tell, being on an island with entities, you don't want to turn a flashlight on because that would just signal that you're there. Like a moth through a flame.  But I love how it says you do not want to see because that's so scary, you know? If you can't see, then I'm sure the entities can't see as well, but the second you turn that flashlight on, they'll swarm you and they can see you. So like I said, you get here, your feet hit the ground, you sneak around and run in a straight line until you get to that castle. The silhouette of the castle is visible the second you get here, it's shrouded in that reddish moonlight glow. And it is imperative that you do not deviate or move from a straight line and that you do not stop running because of the entities. When, and more likely if, you do reach the doors of the castle, you need to bang on them as loud as you can and then it'll like automatically open up for you. It's unknown if the castle is an entity itself or if it just has sentience or somebody's watching, we don't know. The castle has been named the Silver Castle and it is the only known building on this red island. The way it was built or who made it is unknown, but it's a rather expansive gothic style castle that is fully furnished and fully lit with candles and stuff like that. The castle has cold stone hallways and rooms with beds and huge halls and that kind of thing. And overall it's pretty lavishly decorated for being in the middle of an entity infested island. It even has a main dining hall in these six huge bedroom areas. There are three floors to the castle and an attic area, all of which are accessible except the attic. And that's because a level exclusive creature made that area off limits, but I'll talk about that in a second. There are windows that look out to the island from inside the castle, but the article says do not look outside in big bold letters. So I'm assuming you should listen to that. There are freshwater wells and barrels of food and grains located in the kitchen area here. And overall it seems to be a place that you can stay for a while and relax. Even though there's horrifying things happening outside, you can chill inside here. And that level exclusive entity that I mentioned lives inside this castle and its name is Koran or Koran or Koran, C-O-R-A-N is that what it's spelled. He is a large entity in a humanoid shape that is very muscular.   He's very nice to wanderers and he seems to be a protector in a way.   Apparently his goal is to eradicate all entities on this level, which is pretty cool, but I think somebody might need to help bro out. I mean, it's like one versus 5,000 right now. I don't know if he's doing very effective stuff. If you wanna enter this horrific level for some reason, whether you're crazy, whether you lost your mind or whether you just wanna put this level as a notch on your belt, some have reported being on level 14 or level six and no clipping into this field here randomly. But remember, if you do no clipping into the field, you have to run in a straight line to the castle and do not hesitate, do not deviate, run. And to exit, this is where it gets pretty sad because you simply cannot. There has not been an exit found and I'm sure if someone finds it, they'll put it on the website, but as of right now, you either will get consumed by the entity horde or you will live out your days in the castle. Level 72 of the back rooms is the 73rd level in the catalog and it's classified as a class two difficulty with an environmental difficulty of two out of five, an entity difficulty of two out of five and an exit difficulty of three out of five. Although you'll see why later, why that really doesn't matter because it's actually really dangerous here. Definitely more so than a class two. The level consists of a large island smack dab in the middle of a shallow ocean. The island seems to take the rough shape of a crab so its design is kinda like in a crab shape and the level gets its name from that shape and that's where the level gets its name, call of the crabs from. The ocean surrounding the island is virtually empty with little to no life in it, it's just water and it goes out in all directions for as far as your eyes can see, specifically around 3.7 miles or six kilometers. At the edge of that 3.7 miles, the distance of the ocean instantly just drops off into a waterfall that drops into a void. So think of this as like a floating ocean with an island in the middle and on the edges it just drops off into a void. The actual island itself is a sandy island and it's comprised of several sand dunes and palm trees and bushes and pieces of coral and seashells and all those kinda things and there are also some other things here that I'll talk about later, just know that it's not that safe. The level itself is also very hot constantly and very humid. It stays at literally a solid 100 degrees Fahrenheit or 38 Celsius at all times and it kinda feels like you're in an oven. The water here is also salt water which means that the constant breeze that's blowing the air on the island will make your skin dry out and you'll get very dehydrated since there's gonna be salty air. You pretty much look like Patrick and SpongeBob underneath the heat lamp. Now, randomly around every two-ish weeks the level seems to produce rain clouds through an unknown means and it'll rain for a few minutes at a time. This is all of the fresh water that can be attained on this level so if you're trapped here and you can't store that fresh water or grab it somehow, I don't know what you're gonna do, you're screwed. Now, ironically, underneath the island there are hundreds of fresh water aquifers of different sizes. The bigger ones are deeper underground. These aquifers are pretty much impossible to get to for every wanderer who comes here because no one brings shovels or equipment. Like, why would you bring that stuff while you're exploring the back rooms? But anyways, if you don't have that kind of stuff they're just down there. But these aquifers are where the plankton other organisms like crabs come out of on this level. And the crabs that live here go down to those aquifers for the food source which are the plankton and creel. Now, speaking of crabs there are thought to be eight species of crabs that live on this small island. Now, there's only eight species but there are supposedly millions of crabs crawling around. There are dungeonous crabs, flat-top crabs, ghost crabs, gold crabs, hermit crabs, Pacific mole crabs, red king crabs. All of these are real-life species that are found here. And those are just the recognizable species. There are other ones too. Each one of those crabs tends to only eat the krill and the plankton that's below the island but they're also seemingly genetically coded to eat themselves and their friends. Like, they'll eat each other. They will literally cannibalize one another. That's right. There's a little crab on crab crime going here. Now, these crabs that I just mentioned are typically pretty safe. They're not that dangerous. The only reason you'd have to fear them is if you have a fear of crabs because there are literally hundreds of thousands of them crawling around the small island constantly but there is a level exclusive crab that isn't safe at all. Like, it's completely not. And you should be afraid of this one. The aurora crab behaves pretty similarly to a poison dart frog from real life because this crab is very colorful, it's very bright and it's very unsafe to be near. Its shell and body are this wonderful array of shiny colors and pigments but it's the colors themselves that are the danger because they seem to be some kind of toxin because if you touch that toxic color you will get a severe reaction or rash to whatever part of your body touched it. But it doesn't stop at a simple rash. Of course it doesn't. You see, the rash is just the beginning. After it starts, your blood from the inside of your body will start to seep out of you in different orifices. Like literally right out of your skin pores it'll just start dripping out. Think of somebody wringing out a wet washcloth except this is your body being wrung out and it's not water coming out of you, it's the red stuff inside of you, if that makes sense. Now ironically the aurora crab is actually pretty safe and docile as in it doesn't attack people outright. Its shell is the only dangerous part about it and it only is dangerous if you touch it. If you see something bright, don't touch it unless you wanna literally get drained of all your juices. Now even beyond that there are whispers from people who have been to this level that say beyond the ocean where it waterfalls off into that void below there is a gigantic crab-like creature that's been seen stepping out of it. All that's been seen is the giant black silhouette at night time of huge crab legs slowly walking around the ocean. We're not sure if these reports are real or if it's just a tale to get people not to come here but as you can see that would be a terrifying sight to see when you're just kind of like sleeping on an island, you see giant stick shaped legs walking around, that's terrified. So to summarize at this level is an island shaped like a crab in the middle of a shallow ocean which itself is floating in the middle of a void. And the only things on this island are millions of crabs sprawling around constantly. There's one species of colorful crab that if you touch it you'll pretty much leak your insides and there's thought to be a giant crab-like creature that walks around at night time randomly doing whatever it does, we have no idea. So yeah, that makes perfect sense to me. Love it. Now there's supposedly a community here on this level called New Crabland that just has around 20 people. Apparently they're pretty friendly and they just chill on the island most of the time. To enter the level you can be on level 75 and find a roasted crab and consume it and then you'll wake up here. And if you wanna exit that's where it gets pretty tricky because you really and truly can't.  So if you find the exit, tell everybody because that'd be a nice thing to do, right? A lot of wanderers get to this point and they can't get past it, so be warned.


I want you to act as if you were in a crisis. I want you to act as if the house was on fire, because it is.


You can display Adafruit IO data on any HDMI display with the Raspberry Pi Pico W and Adafruit's Pi Cowbell DVI output. This Pi Cowbell add-on board is designed to work with the Raspberry Pi Pico W and lets you display images and graphics to any HDMI display or TV. The Adafruit Proto Pi Cowbell Doubler puts the Pico and an add-on board side by side with additional ports, pinouts, and lipo battery charging. We designed a 3D printed mounting plate to house the Proto Doubler. We secured it to the back of our 7-inch HDMI display which has VESA compatible mounting holes. A SCD41, CO2, and humidity sensor are set up to log data to an Adafruit IO feed. We also have a DS18B20 waterproof sensor logging our pool's temperature. Using our Pico DVI IO project we're able to display data from both of our sensor nodes on our HDMI monitor. We think this is a great way to display sensor data to any HDMI TV especially for workshops or educational office spaces. The code uses the Pico DVI library for a doing note to display images and graphics. Adafruit IO now features hardware support for the Raspberry Pi Pico W. To learn more about this project check out the tutorial on learn.adafruit.com. You can get the parts to build this project from the Adafruit shop, links are in the description. These DIY HDMI connectors and ribbon cables are great for these type of projects. You can 3D print the mounting plate in your favorite PLA filament. The mounting plate features built-in standoffs for securing the Adafruit Proto Pi-Cal Bell Doubler with machine screws. Additional standoffs are used to secure a top cover that features mounting slots for additional sensors and components. We hope this inspires you to try Adafruit IO and the Pico DVI for your next IoT project.


Don Armstrong, he will be teaching us how to locate bugs using soap. Hi, for everybody who doesn't know me, my name is Don Armstrong. I am one of a couple maintainers on Debugs. I'm actually currently right now the person who's primarily active developing it. But that's not to say that I'm the only person behind the code. There's quite a few people who have developed and spent a lot of work. And another person who deserves a round of applause is Blares Blarson. He's pretty much single-handedly responsible for keeping the BTS as free from spam as it is. I don't know how many of you are aware of it, but on a daily basis we get something on the order of 4 gigabytes of non-duplicate spam to the BTS. It's probably something on the order of 10 to 40 messages get through of that, that spam every day. And he basically deals with that, updating the rules and making that all work. So if you happen to run into Blares, buy him a beer or give him a hand, because he does most of the unforgiving work that people don't see. Okay, just before I start talking about soap, I should talk a little bit about the architecture of Debugs. Just to give you guys an overview of what's going on so that things that I talk about that I assume you understand. Well, I actually told you, even though you probably still don't understand them. Basically, mail comes in. We check out all the spam. We have a series of proc mail rules too, besides spam assassin, a custom thing called cross assassin, which avoids running spam assassin on mails which matches IG, which we know already have a spam assassin score.  Spammers love to send the exact same spam message with exactly the same message ID to 20,000 bugs in one shot. So this helps us waste process, avoid wasting processor time on that. Then mail gets handled by process all. It's basically a small, purl script which shoves mail off to process and service. Service is what deals with control at and request at. So, if any time you use a control bot, that's what's talking to you. Process deals with everything else. So if you mail submit at or bug number at or bug number dash whatever at, that's all process. All the stuff that those things do interacts with a, well, kind of a database. It's basically a series of files in db-h. That also, from that, we generate indices which is used to make the queries fast. Obviously, if we were running straight through the entire BTS, you wouldn't see anything at all when you viewed a package report page. And then there's the CGI interfaces, the soap interfaces, anything else that works is built on top of that. And there's now a series of purl modules that deal with just about everything that happens in there. So if you really wanted to and you had to parse db-h because something I did or wasn't good enough or the soap didn't do what you need, there's purl modules now that can do all that for you. Okay, let's get on to what we can do with soap. There's a couple of major things that you're allowed to do currently. And this is not to say that this is an exhaustive list that I'm never going to add anything. And in fact, if anybody here has stuff that they want me to search for or be able to find using soap that I don't currently do, please file wishlist bugs for it. I'm always looking forward to making soap serve as many needs as I can possibly make it serve. Basically, because that reduces my headaches when I break the file back end or I change the CGI's like I just did. Because otherwise I have to try to support things in reverse. I had to do this for report bug in Sarge or Woody. And I'd really rather not like to have to do that again. So that would help me a lot and you a lot if you tell me, hey, I need you to do X with soap. So let me tell you what you can do. First things, you can obviously search bugs. And this is primarily bug searching and bug selection. Everything that you can do through the basic part of selection in package report, you can do using soap. It uses exactly the same methods which are exposed via soap that package report uses. Other things you can do, you can pull the bug status information for every single bug. This is exactly the sort of information that gets displayed when we do versioning, archival. This is the underlying summary file that gets ripped out by bug status. You can use to figure out whether version is buggy and do anything like that that's more in detail than finding a bug number from a bug. You can also pull user tags. So if you've set user tags and you want to know what user tags are set using soap. Another new feature you can also pull the newest bug from the BTS. So if you give it a set of bugs, it'll say, okay, these are the 10 newest bugs. It's not quite guaranteed to give you unique bugs or bugs that actually exist, but it will give you no more than that number of new bugs. Because sometimes we delete bugs if their spam makes it through submit and stuff like that. Actually, I don't think there's any spam through submit, but sometimes bugs disappear. So that would be why that wouldn't quite work. The final thing that you can do is you can actually pull the entire set of bug logs in all the records. So every bug is basically a inbox with really, really weird control fields in the middle so you don't have to do from processing. So you can make a soap call and pull all that information. So let's play with some of the other stuff.   You just want to get bug numbers back out. So a while ago, I made a patch and Stephen Zacharoli actually made it palatable for people to BTS adding a new command called select. And so now what you can do is you can run BTS select and select bugs from a package. So let's see kind of how that works here. Let's see if I can get it. Let's find me a window that works. There we go. Let me open some terminals. Okay, so we can just run BTS select and a package, GDC 4.1, for example. So this will go out query the BTS and return us a nice list of bugs. There's a whole set of select queries that you can use. You can man BTS and search for select. And these are all the keys that are there that you can use. There's actually a couple more keys that aren't documented yet here, the one that I'll show you in a bit. But in general, this will document everything that you can use to do a select. The basic idea is if you list the same tag or the same key again, it ors different keys and if you want to or over keys make multiple select calls. It's kind of a no-brainer, but that's how it works. Eventually, if I could find some sane way to do it, I may do more complex select statements. Yeah. Video and stuff. It's not readable on the screen. Yeah, let me see. What do I have set as a font right now? Is that better? So just for the BTS record, I'll just show you what I was doing. Package, GDC 4.1. And so that selects a list of bugs. So that's just one example. So let's go back to what we were looking at before here. We can also use it to do more complicated things, like getting all the set of RC bugs. So we can do that, BTS select. And so this case we want severity, serious, severity, grave, severity, critical, et cetera. So this will give us a huge list that will scroll on for a while of bugs. So those are all the release critical bugs. Now, that also includes all the release critical bugs that are fixed, that are done, that might not be interesting. So if you want to do something more complex with that, I wrote another command called just recently that doesn't exist anywhere else, which I'll talk to you about in a bit, but let me get back to what I was talking about. So another new feature that I just added is Correspondent. If you were looking at the options bit that I just added on Package Report, which I'll hit briefly at the end of the talk, you notice that there's a new option that you probably hadn't heard about before called Correspondent. This is any bug that you've mailed. So it rips out the addresses from every single header field that I knew about and adds it into an index and tries to build basically databases of bugs that you've ever mailed. So if you want to know which bugs I've mailed in recently, we can go BTS, select Correspondent. This won't work on your version of BTS, by the way, sorry. There's a patch for it already, but it won't work. And this will select all the bugs in there anyway, which I've corresponded with that aren't archived. If you wanted to get every single bug that I've emailed with that mail address, you could also go archive both, and that will give another set of bugs. I don't use that email address all the time, so that's why it's not the complete thing, but that'll give you an idea. Now, you might be wondering what that's useful for. I'll show you some examples of why you really might care if you can't already think of them yourself. Okay, so BTS select is a tool that's useful for everybody. You don't have to necessarily screw around with soap to use it. It's pretty neat. Another thing that I just added, a patch for BTS, is status. It shows information on a single bug. I don't really sure if I like the file column thing that I invented, but whatever, it was an idea. If you want to show information on a single bug, you can just run BTS status, and it'll give you all the information on that bug. It'll probably change to being tab delineated, and I think it would be neat to make a table out of it if you gave it a bunch of bugs, but that's the idea. This is, again, the get status soap call basically made into a neat script. So, for example, we can take our little thingy here. Oops, well, so much for that. I don't spell well, so. But we can go back up here, and we can go BTS status, file. Obviously, you can select from a file. I think that's kind of figuring out how do you want to specify a standard in is always kind of lame, whatever. That sort of works, and it selects all the information on those bugs. Let me put it into less so you can see what's really going on here, and it also separates them like that. It always leads with bug number, so you could figure out your information from that. Okay, that's pretty easy. And you can probably think of other fun things to do with the select information on your own. I'll leave that to you. I mean, because it's now in a command line thing, it takes standard input, produces output. You can do all sorts of insane things with grep and cut and whatever else you need to do. Okay, let's do some more complex things with SOAP. The classic thing to ask is RC bugs and installed packages. This is obviously a thing that we already have an existing tool called RC alert or whatever it is that does a better job than the script I'm going to show you, but my script is way shorter. So let's take a look at what that would look like. Let me make this so... It's actually written in Perl, but whatever. You can figure that out. RC bugs and installed packages. I probably should make the font larger, but whatever. It's in my subversion repository, and I'll put links at the end for people who are watching on the video. But anyway, the basic idea is first we get the set of installed packages. That's probably a better way... There's better ways of doing it than using aptitude, but whatever it was what I thought about was I was sitting here two hours before the talk. Then we instantiate a SOAP request. How you do this is language dependent. If you really want to know all the funny ways of doing this, let me pull up the wiki, and you can follow along in the... I don't remember what the link is, but this page has examples. Hello, there it goes. The SOAP interface documentation has examples on how to do it for all sorts of different languages. So if Perl's not your thing, you can refer back to hit this after I'm done and switch to a language that you find sane. But anyway, we then use our git bugs thing that we did before to select bugs of RC severity. Then on all the bugs, I only pulled 100 out because it would take forever otherwise. We can get the status on all the bugs in one shot. Then loop over the status, pulling out every bug, and if a bug has a package that matches a package that's installed, then print it to standard output. So we can run this. We'll take a little bit of time, but... So this will run for a bit and thrash my disk, and then figure out a subset of 100 bugs that have RC bugs in it. So that's pretty easy. What about other stuff that we can do with SOAP? What about bugs that need help in installed packages? Well, you can already see that that's going to be just another example of the same sort of thing. Like I said, we just select tags. So let's see, RC bugs... What do I call it? Bugs needing help? Yeah. So we just again do the same thing, but instead of selecting severity, we select tags called help and do the same thing. So that's really simple. Yeah, so that's a much more useful example that would have taken me slightly longer than the five minutes that it took me to type this. But yeah, that is something that you can actually do with this. It's slightly more involved, and I can provide an example towards the end of DevConf once I actually have time to stop doing really useful things. But yeah, this is an example of a really simple script. And to do that more complex thing involving versioning, you'd actually iterate over the status bits here. And instead, at this point, you would compare the bugs to the version that you actually had installed and check is buggy at this particular version, and that would tell you. But anyway, this is just another example. And so this will also pull all bugs tagged help and install packages. And because we're doing archiving too, you're not going to see every single bug in all the BTS. You only see relatively recent bugs. So it's not as useless as it would have been prior to last year when I enabled archiving. The last thing that I was looking at was bugs that I filed that need love. So bugs filed which need love. So in my mind, bugs which need loves are bugs that haven't been... had a mail sent to them in over a year. They're getting lonely. So somebody needs to send mail to them. And since I've sent mail to them, or in this case, I've submitted them, so I should probably ping the maintainer. Probably in a lot of cases actually, these are bugs which I've submitted against packages which I maintain myself, so maybe not so useful. But anyway, this is sort of an idea of bugs that you could find that you've submitted yourself that you should maybe ping the maintainer. So all of the bugs now have a field in status called log modified. You've seen it on package report. It shows up, oh, this bug log hasn't been modified in such and such a time. Anytime the bug is modified, a message goes to it, the log gets modified. That's that big inbox of everything that gets sent to the mail. And so this will give me a set of bugs which need love because nobody's mailed them. And so again, you can see, I'm selecting all the bugs which I've submitted. So the submitter is Don at Debian.org or Don at Don Armstrong.com. Then I only rip 100 of them. And then I go through all the statuses, check the log modified to see if the mod time is below needs love, which is a year ago. And then print the bug number. So check what that looks like. So yeah, those were the RC bugs and installed packages. Only the first 100, there's way more installed than that, but bugs, yeah. Bugs filed which need love. And so the soap currently is relatively fast because it's using an index. There are some queries though that will make it really, really slow. And that's something that hopefully will put more machines or more CPUs on the CGI end so the soap becomes faster and also put databases behind it to make the queries a lot faster. But regardless, the API is going to remain the same. So queries that you write today will work tomorrow and forward. If you're going to write long standing applications though, please talk to me because there's more stuff involving versioning that I want you to do. But this is sort of a really quick introduction to it. So I should be emailing all of these bugs. They would be a good thing for me to do. Okay, so that's the end of the brief soap bit that I was going to talk about. The other stuff that I was going to mention is slightly more interesting. Well, from my perspective. But hopefully that gives you an idea of some of the things you can do with soap. You can play around with it on your own, play with BTS Select, play with BTS Status when it shows up. You can use that to find bugs that you've neglected that you've forgotten about that maybe you should get back in touch with and help them get closed. So they're happy living in archive instead of DB-H. Another thing that is... In this part, I'm going to switch more on to stuff that would be generally useful besides soap. So another thing that is extremely useful in the BTS are user tags. A new feature that I've just added called user values, which isn't completely implemented yet, but I'll talk about it briefly. And user categories. User tags is basically the ability to assign arbitrary tags to bugs. How many people here have user tags assigned to bugs in their name? Okay, so a reasonable number of people have user tags. There are some relatively popular tags that have been assigned to multiple user names. And these are them. I just did a select and ordered it by them. So these are the ones that have... For example, Origin Ubuntu has 15 different users who are using that tag for whatever reason. The same thing with Waits for Sponsor, there's seven users which are using that, etc. Overall, we have 373 unique user names which are using 3,243 unique tags. You can imagine there's no way I would ever have added all those tags to the BTS. So this is really useful. There are 57,000 or 58,000 some-odd tags on bugs. So this is a feature that gets used a lot. So if you're not using it, you should. You can assign... I should have checked that, but you can assign tags to bugs using the standard. You can set the username first to control. Otherwise, it defaults to wherever you sent the mail from, which probably isn't what you want. Set user tag. So for example, this is setting the archive user tag. You just imagine new lines where they belong. So newlineafterpackages.debian.org and newlineafterarchive. And setting the DAC tag. This is an example of user tags which I've actually set on the ftp.debian.org pseudo-package, which enables it to do useful things. Just a side note here. There are a set of users which are by default included in package queries. So if you include a query that includes ftp.debian.org as a package, it'll automatically load the ftp.debian.org user tags, and it'll automatically select them. That's why if you want or maintain a lot of packages, you want to use packages or user names like this if you want your tags to show up by default. Yes. Oh, yeah. There's missing new lines. The question was, did I need an extra comma after everyone? Yes. If I was using the BTS command line, it would have extra commas. I forgot to put the new lines in in the verbatim argument when I was typing this into latex. And I didn't look at it beforehand, so that's why it's missed out. But yeah, just imagine new lines where they belong, and that would enable you to set user tags. You don't need to do anything special beforehand. If the archive user tag hadn't existed before, this will create it for the ftp.debian.org packages.debian.org user. So that's pretty simple. Another feature that I've got most of the stuff to do, it just doesn't display anywhere useful, is user values.  You're already familiar with these. This is what owner, forwarded, and stuff like that already is. That's an arbitrary key value tag. So you can set owner, and it's set to this value. You can set forward, and it's set to that value. The main things it would be useful for is in sorting of bugs, also selects, also adding more URLs to different things. So an example here, I am setting the patch location to a specific URL, which is run off the side of the page, but just imagine that there is a URL there. And so on the bug report now, that'll show up if you're using the packages one so that you could click on and go exactly to the message that contained the patch, or exactly to download the patch instead of having to, okay, the other thing is tagged patch. Let me find where it is and then which message has the patch to enable you to do that, for example. Another thing you could do is you could set a priority. Anything. It's Perl, remember? So put random data in it. Yeah. So I haven't really figured out exactly what I'm going to do as far as the sorting. I'll probably make it smart. So if it looks like everything is numbers, then it should do number sorting. If it looks like everything is string, or it looks like there's some strings, then it should do comp sorting by string. But that part isn't written, but that's what I'm envisioning having it for. So an example here is you could assign a priority to a bug, which would be your personal priority. So you could say, okay, this bug is really important for me to work on now, and so you would have a better workflow. So when you sit down on your bug list, you would know, okay, these are the bugs that I want to work on in this order. You could also, another thing that I thought about originally was the ability to sign time durations. So if you think this bug is going to take one minute and you have one minute today, then, okay, you can fix that bug in your one minute that you've got to spend. If you think a bug is going to take five hours, okay, well, then you put in whatever, 600 or something, or 300, or whatever you decided to use for your priority or your time allotment, and you can ignore those bugs, because if you don't have five hours to spend looking at the bug, why even bother looking at the bug title or even the log to figure out what in the world this bug is about? So that'll help out, I think. But it's still slightly incomplete. You can't quite set the values yet, and they don't display, although all the stuff to store them is there, so. Hopefully at the end of DebConf this will be working and actually announce it on DDA. Another thing that's existed for a while, but again, people don't use, because it's not documented well, which I'd hoped to force myself to do in the context of making this talk, but I did other interesting things instead, is user categories. User categories is basically the ability to override the default way that the BTS splits up bugs. Currently it splits up bugs by status, like whether it's fixed or not, severity, and one other thing that I'm forgetting, but yeah, tags. So those are the three things that it separates it by. You can decide that, oh, well, that's insane. I don't like this split that it's got, and I want to split it by these values instead. So this is an example of a split that I set up for ftp.devian.org. It hasn't been kept up as well as it should, but this is an example of things that you can do. So this, for example, ftp.devian.org does different things. There are times when it's asked to remove packages. There are things that are only involving DAC, the internal archive software. There are things that only involve Brittany. There are things that involve adding new sections to the archive or removing them or stuff like that. There are things that involve overriding the override file. And there are things that are just generally related to the fact that the archive or a mirror is jacked up or something like that. So these are all separate tasks that ftp.devian.org has. And different people sometimes are interested in different tasks, so by splitting them out this way you can just check out the sub tasks that you're looking at. This obviously isn't particularly useful if you've got five bugs, but if you're one of the packages who has thousands of bugs then this suddenly becomes really useful. So you can assign, remember the tags that I was talking about before, archive, et cetera, this tells it to split based on the tag, archive, remove, override, Brittany, DAC, and section and stick everything else into uncategorized. Then the user category normal is the default categorization, and this overrides what the default was. So now when you go to ftp.devian.org, first it splits by status. So that shoves all the fixed bugs at the end, which you don't want to see usually anyway, all the other bugs that are open at the top. Then it flips by the tasks and then it flips by severity. So we can sort of get an idea of what that looks like if we hadn't seen it before. Let's see. I don't know where I put that. Very slow. So if we pull up the ftp.devian.org, you can see that it's sort of split out. The things that are uncategorized at the top, these are just the bits that haven't had the user tags assigned to them already. But you can see down towards the bottom all the things that are involved involving the archive, etc. What do you have to type the text you gave as an example to give it that result? So everything that I've shown here, you would send to request at or control at, and that would add it for the ftp.devian.org user. Yes, actually I copied it out of the email that I sent to set this. Okay, can you explain what's the... If that's the correct syntax, does it care about white space? Does it really care about star versus plus sign? Yes. Can you explain that a little bit, please? Okay, so I didn't write this, so I don't even understand it completely yet. But the basic idea is the category start out with stars and how you split out each category gets the plus signs beneath it. And then you can assign the different tags inside the brackets. I will... Once I have a life or don't have a life or don't have less of a life, we'll document this slightly better. But the basic idea is to learn by example to see what we've got. But it's something that I'm going to improve. But again, the basic idea is you first have your status. So this is the normal thing. And so status is already predefined, a default categorization that already happens automatically. You're all familiar with it. This is the new one. And so the first thing at the top sets up this categorization. And it has a name. And the hidden thing tells it not to show up in the option selection, which is currently not showing anyway, but it generally wouldn't show if it was said hidden. Okay? Oops. This defines this categorization. And so the title is at the top. That's how it would be labeled in the summary. And how it's splitting on is on tag. You could split on pending. You could split on severity. You can split on a couple other things that I can't think of right now. But those are the three main ones that people use. Then each of the individual plus bits here delineates a subcategory in the package page. So the first one is that it's archive-related. And so this has the archive tag. So tag equals archive defines it. And these work in order. So the first thing it matches is where it ends up. Okay? So if you had it tagged archive and DAC, it's going to end up in archive, not in DAC. You can also, I believe, put commas in between them in multiple tags. Same thing with removal requested. The tag equals remove. Tag equals override, et cetera. And these are just, again, the titles of each of the individual sections. Okay, so on the category. Does it care about whitespace? It cares about whitespace going this way, yes. Yeah, whitespace matters. And this whitespace new line space here matters too. Yeah, it is sensitive to whitespace. Can you, can I do that on? Oh, WNPP, yeah. Sure, you can do that in WNPP. Anybody who wanted to spend the time to categorize all of WNPP could do this to split it out into different sections. Unfortunately, it cannot be easily automated currently. Is there any way that using user categories on WNPP would allow us to cause the view to be faster by having it have to access fewer bugs? Could we, like, say, hide all the bugs that had a certain tag and a certain view, and that way we could, because currently, the WNP website has a develop slash WNPP where the bugs are listed out.  Yeah, I will show you how to make the WNPP list show up faster towards the end if I get the chance. So, but yeah, this is another thing that you could use to do that is you could just show a tag, a specific user tag that matched, which would also make it faster. You wouldn't even necessarily have to go to user categorization, but it would make the whole display nicer. So that's user categorization. Another new feature that I just added, which isn't documented yet, but it works. I tested it anyway. It works as far as I tested it, let's say, is summary. So the idea behind summary is the ability to in stupidly long threads to pick the paragraph in a particular message.  The title should be the shortest thing that you can manage that sort of conveys that, but sometimes it's not long enough. So summary just nominates a message in the log and says, okay, you're now the summary of this bug. It puts it up near the top of the title, and basically the way it works is you give it a bug number and the message number that you want to rip it out. It tries to do the right thing with quoted text by ignoring the first paragraph if it looks like it's quoted by ignoring the first paragraph. If it looks like it's pseudo headers or tags, it's not infallible. So if it screws up, give me an example and I'll try to make it even in those cases. If you're using the Gnu's quoting style with indenting, you're insane. It won't work for that, so I'm sorry. But everything else, it should do the right thing. You can see an example of that on that bug. Not a particularly useful example. It was just the one that I was testing with. So you can check that out. Skip something. Another thing that I just added is the ability to mark bugs as affecting another package. Somebody had asked for the feature and originally I thought, well, why would you want that? You just use blocks. But the idea is actually in retrospect when I thought about it on the plane, makes much more sense. A lot of times we have bugs in core packages that affect 8 billion other packages. And it really sucks when you're a maintainer of the package where the bug doesn't actually exist, but where it manifests, that users file bug after bug after bug after bug, which you reassign and merge into the actual bug. The way you would do that currently is you would just leave a bug there, mark it as blocking the other bug. And then you'd have to recognize that, okay, yeah, this other bug got fixed, and now let me mark my bug as closed. So with this, what you can do is you can nominate a bug as affecting other packages. And by default, well, once I have it totally working, it's a package selection list. There'll be an option to turn it off, of course, because most of us don't care what it is, but end-users are going to want to know that a particular bug is affecting another package. I don't know where the slide went, so... I was trying to find the right slide, but it appears to have escaped. So... So that's why the slides don't match. But that's a new feature. It'll be documented in the usual places on bug site in Donorock as well. Okay. Another thing that is the... Yeah. About the treatium, maybe, I imagine that then, on the bug list of the affected package, you see the original title of the bug, which often users will not recognize as the effect that it has on the affected package. Yeah. I mean, there's always a case where users are running into... But hopefully you would take and make the title of the affected bug so that blah, blah is broken and blah causes something else that causes every package to break or something like that that would make the title more accurate. But yeah, I don't know of a good... Part of the thing is it's a really difficult problem to figure out the right balance between being able to grab the user by the ears and say, yes, this is your bug. And being able to be informative for the developer looking at the bug list and saying, oh yeah, that's the problem with that bug. I will fix it now or no, I will deal with it later. And that's a really difficult thing to balance. So I mean, any better thoughts on how maybe better to do that? Maybe the answer is making the summary for that bug show up in the first page. That's definitely possible. So I'm being told that I have 10 minutes left so I will start speeding up slightly. So that would be something useful to think about. Okay, another thing that in Helsinki, BDL actually asked about and is finally starting to become moderately possible to do. It's still a little bit hacky but hopefully towards the end I'll have it so that I actually have packages like Experimental which enable you to do this is to run a local mirror of the BTS. So I don't know, not all of you are jet setters but there are lots of times when you are in some place that doesn't have internet but yeah, you've got your local VCS and yeah, you've got everything else you need but damn, I don't have a local copy of the BTS so I have no clue what's wrong with my packages. So the idea is actually pretty simple since bugs are all available via R-Sync and once I finish packaging CGI scripts and put them in Experimental we can rip all the bugs via R-Sync that we want based on whether we've mailed the bug, whether we've submitted the bug which we mailed it whether it's a package we maintain even if we haven't bothered to respond yet there's an RC bug hopefully we're interested in those bugs so any of those things you can add a whole set of selectors for bugs and for some reason you wanted them all it's again still possible to rip the entire BTS the db-dutch H right now is only like 8GB so it'll fit on just about anything you've got but anyway then you can R-Sync the bugs needed using Include with the little script that I pounded out in 10 minutes we'll pull the indexes and the version files which the BTS just needs to work you'll install the Debugs packages which ideally will have a little script that does everything above so you don't have to think and in this case I have to configure patching bits but I'll probably have it set up so that you can run a command and it'll run a little web server on 8080 on localhost or something like that so you won't even have to pittle around with the patching and say start little local BTS don't tell me pages so I'll sort of give you an idea of what the script looks like I think so here's a script that doesn't it probably needs to be slightly more made a little bit more robust but anyway it'll rip all the bugs yeah it's not executable but whatever so we'll go out pull all the bugs I've mailed etc. we'll start R-Syncing this will take a while so I'll ignore the fact that it's still going in the background and then after configuring Apache we can now look at bugs on this local machine so this is a very minimal mirror that only has these bugs running a small set of the CGI scripts and if you really wanted to do it right this second you can let's see that's the Apache config that does it and it just running out of a the only key thing that matters is this config file which isn't very big and the fact that I have a local copy of the BZR repository of Debugs but eventually you'll just install the package hopefully by Friday I will in assuming I announce something to devil announce you'll be able to like I don't know what command but Debugs local mirror that start the CGI and it'll just work so you won't have to do all this insane stuff okay I'm thanks some more stuff just to go run through this as fast as I can there is a bof and anything that I don't talk about I will come back and pittle about later and then I'll go back to the translation you guys won't see but it makes my life slightly better it reduces the number of times I break the BTS and the length of time that I break the BTS and the number of times that I break the BTS immediately before going to bed or disappearing from the face of the planet so basically now everything or most things are modules they relatively sane as far as pro goes there are archival most of you already know about that that was last year that I did it the other thing that's there is the new package report select options which why I just talked about with the oring and ending so you can make really complex select strings the other thing that's really major is template support in theory since I only speak English it hasn't happened but in theory you can set the locale by some means that I haven't decided how you're supposed to do yet and you could localize most of the BTS as it is now luckily everything is in templates though so this means that you can also make changes more easily without dredging through the source code and figuring out where it is yeah the question was whether I just use languages and yeah that would be the right way for the CGI stuff the other half the question was the templates are also used for the email and that was the other part that I had no clue how to do properly so but yeah it's something that's worth thinking about and hopefully once it's the templates are slightly more content in one place code in another place it'll be something that I can give to translators and ask please make these okay summary I talked about effects I talked about and corresponded was the other cool thing all these bits work in the normal package report that you're used to so future stuff more methods control is currently being abstracted out every time I look at it I have pulled out more and more bits why this matters to you is it will enable you to do all of the control methods in messages to process or to process all so anything that you would send to the NN at bugs.diamond.org or submit at bugs.diamond.org it will enable you to set any control option this also enables me to rip out code out of process which does things like setting the package it makes it do exactly the same thing no matter whether you're using control or setting it in the initial submit message it also has the possible side effect of allowing a web front end but I don't think I'm going to allow that because I don't want to control messages with soap and most likely not and the reason is because of the whole authentication issue I it could be that if enough people decide that it's worth it to allow it with messages and authentication that I will do it the only thing is it almost assuredly will not be instantaneous so there will be some sort of delay while you sit in the hall to wake up and decide that it wants to process things because currently it's a very lock intensive process when it decides to modify messages and long competitions is a little bit annoying yeah things behind you I think that one of the things I'm most missing from the BTS is a commandainer view because a lot of our infrastructure has been migrated to have a point of view so I'm going to look at this and I need to look at 10 different pages and there are a couple of bug reports I think there was something missing on the dark side maybe yeah the main thing right now that's missing for me enabling that is an uploader's file from DAC and that's something that the FTP master team knows about and is working about making available procrastinate for another couple years and then maybe it will happen another thing that I'd like is some more integration with mole and stuff so you can put per package stuff and better statistics and documentation this is how you can help okay the source is all available my source is even available on bzr.armstone.com if you want to know what I've been working on that isn't yet committed although right now my tree is still working on the main line but as I do crazy stuff it gets more and more divergent until I drop 1000 line packages onto the bts that explains all that these are the other people who have been involved with dead bugs besides me me, bars, Adam, Joseph, Anthony, Kahn and maybe you so thank you for your attention there will be a bof after so questions that I haven't answered because I'm out of time and I'd also like to talk about the new package report bits so you guys can see how that works please come at whatever 7 I think it is or something 7 or 8 today and we'll talk about that and have a discussion around table about it too thank you for your attention


Welcome back to my channel today is a video as you can see from the title. It is going to be another she in hall Thank you so much for sponsoring this video. They did send me over these clothes for free I did not purchase them with my own money, but all of my opinions will be my raw true and honest opinions So if you're new here, hey, my name's a kid Jenae. Don't forget to subscribe and join the family before you leave So I have a cute little hall for you guys. It's about Eight pieces, I believe so I'm going to start off with let me flip these clothes around I'm gonna try to do them in orders when I put them on This the first one right here I don't have the tags on them or anything because I actually wore this one when I went to Memphis I don't know what so I'm gonna put the stuff on probably right here. I'm actually with this dress to Memphis Super cute. I think I got it in a size It's in a size medium I am a true medium now. So I got in the medium. It does have a little bit of stretch to it But I know a small probably would have been extremely too tight So this is the dress you could see it on in the camera I'll probably pop in a few pictures. My pictures didn't really look too good when I was in Memphis So I probably won't show them but the dress is cute. The inner lining of the dress has that soft kind of Like it was cold in Memphis, but wearing this dress on the inside. It felt really good It was really warm and soft on the skin and then the outside is obviously that Fox leather Said is that right Fox leather or pleather pleather? Anyways, I really like it I give it a ten out of ten just a cute little regular Black dress and on the back it does have a little split. So I think that's super cute if you wear heels the Next item that I have to show you guys. I think it's this one Putting this on is a bit tricky. I'll let you know that right now. I did get it in a size small us size four Loving the brown color. So first I put this on backwards.  Like I said, I got in a small I thought it was gonna be too small kind of around the legs like right here It is a little tight, but besides that I really like it. It is giving Scarecrow at the bottom. I always say that when stuff is kind of like flared out It just reminds me of like scarecrows. I don't know But it's cute another part that I don't really care for is this piece Like if it's gonna be open to show your stomach a little bit Just let it be open like I feel like this little tight piece in the front kind of just serves No purpose if you will so I'll probably give this one about an eight out of ten I mean it's super cute on it's just this piece. It's just I feel like it should just be open Like it's it's really no purpose for it. And then this one since it kind of tug on your neck right here I don't really care for this piece. So it's super cute though. I like it Give it a 10 the next item. I have to show you is a another dress. This one does come in various Colors I got this one because all the girlies in the comments didn't really have this color I don't think I got in the size small it is super stretchy around the neck It is extremely stretchy around the arms. It's extremely stretchy. This one is cut out on the side They do give you underwear so that you can wear it to match Obviously, it's a size small since I got a small in the dress. So this is how the small looks they are They do run big so The underwear if you are like tiny and like really don't have a butt back there These definitely will give a diaper and it'll probably show like a like a bad baggy line In the back of you since the back is kind of so big, but I mean that may be a good thing Sometimes I may be a bad thing, but yeah in my case it was pretty okay Since I am a size medium it worked out for me. But like I said, the side is cut out I kept my underwear on in the video For video purposes, but like for pictures and stuff. I would have any underwear on but it just I mean shows the whole Side of your body. I did have another dress like this I don't remember feels from she in or what but the other one I had I didn't really like because it didn't come with underwear So since this one actually comes with underwear that actually matches. I definitely like this a lot better I give this one about a nine out of ten Simply just because I need to lose a little roll on the side and then it's gonna be a ten out of ten But nevertheless, it's cute super stretchy. I'll say size down If the little underwear isn't an issue for you next outfit I'm gonna show is this super cute. It gives me just like tropical Beach bops, so I got it in a size small. It is long sleeve. It is. I feel like it's a little see-through Um, it's very light. It's very flowy So that's why I feel like it'll be still okay to wear this in the summertime Even if it is hot or like, you know on a cruise just any type of vacation bops I feel like this would be super cute or picnic hill. It's kind of giving picnic also So I really like this Like I said getting a size small. This is the top. These are the shorts I got it in a size small because I knew these were gonna be stretchy So obviously the band is stretchy and then the shorts They're not that stretchy But I just knew to get a small because the medium like if you want a Kind of snug fit I guess you can say then I would say size down But if you want your bottoms and stuff to be a little bit more flowy I would say size up or get your regular size my regular size is medium But I size down and got a small because I did want it to be a little bit tight around the butts Okay, to make it pop and look real good real juicy, but it's super cute It buttons down the lady in the picture. She didn't have hers like button down You can definitely button it down so you don't show any cleavage or anything Me on the other hand I just tied it up to look like the model and I think I actually prefer it tied now if I'm going somewhere Like I said like a cruise or something and we're about to go inside to like go eat or something like that It's like a lot of people then I would probably like button it up and then put one Side in the shorts and keep one side out kind of just for like a more chill vibe Or like let's say like you're wearing this to the mall or something I would definitely kind of button my down and then kind of style it like that But I feel like I'll probably just wear some flip flip flops with this some cute little sandals and call it a day This is definitely like a vacation vibes. Just chill relax casual vacation vibes The next one that I have is this cute little Two-piece set it has butterflies on it. It's purple. I definitely am trying to get into the colors I'm trying to steer away from just black white gray and like browns, but I just can't get away So I decided to get this just the shorts. I got it in a size small These I feel like Are true to size but kind of on the bigger side like actually they're not true to size They definitely run big these fit me though because I mean, I'm a medium So the small I feel like would be a medium So if they do offer extra small, I would say get extra small If you are a true size small because the shirt you'll see in the clip It literally goes down past my butt, which I mean, it's it's like a comfortable casual fit So it really doesn't make me know. Never mind. It's just if you are the type of person who really wants stuff snug Or like don't want your shirt drooping down over your butt Then I would say size down on this because this is super stretchy like super stretchy The shorts are just as stretchy both ways in the band is out of this world stretchy So definitely size down if they have a smaller size if not, you just have to help rock out with the size small If you need something smaller than small, I'm sorry But if you are like a size large or a medium definitely size down because it runs big Let me go turn off my next two items. I have are just shirts I wanted to kind of build my shirt gang up because my shirt game Because I don't have many like just regular like t-shirts like I do but they're all like old dingy or like I just wore them completely Yeah, so I decided to just get this cute little shirt that says good vibes It is brown, but listen it got green on it. So I feel like that's the past That's past it's super cute. This is one of their stretchier materials So literally neckline stretches really well the sleeves stretches really well the shirt itself Stretches really well didn't have any problem putting it on over all of this hair and makeup and stuff like that I was able to stretch the neck completely out so it didn't even touch my face. So Definitely love this. I believe I got this one in a size tomorrow Also, yeah, I got it in a small because I just knew like you can tell from this type of material from she in This material is always so stretchy.  So it definitely I Will say size down and just get your true size. So I size it down in this case I am kind of like on the slimmer bill anyway. So size and down definitely worked out of my favor Absolutely love it. I'll give it a 10 out of 10. The last item I got is this cute long sleeve shirt But it's sheer and it got cut outs It kind of reminds me of like something that I would probably wear like to a concert or something So the sleeves are mesh and then it gives me those care crawl vibes But it's super cute. I actually really like this on of I did get it in a size medium Which I feel like I Could get away with sizing up. This one fits.  So I would definitely probably have Felt a little better with sizing up, but it do got cutouts in the top You'll see the clip that I put in so the little cutouts It gives you a little bit of boob action, but not too much But this is just super cute like I feel like I would definitely wear this to somebody's concert So I definitely give this one a 10 out of 10 my favorite outfit out of this whole haul Surprising well my favorite piece is surprisingly this one I mean it definitely took me by surprise that I actually really really like it So that shirt is my favorite and then this little two-piece is super cute It just gives me good vibes like I'm going on vacation. It just makes me feel good when I have this on So thank you so much for watching. Don't forget to like this video comment subscribe It helps me out a lot and it is free to subscribe and until my next video I will see lovely then all the links and everything in coupon codes whatever whatever will be down in the description box below so See ya