Python Bytes - #495 Banned

Episode Date: September 8, 2026

Topics covered in this episode: EuroPython 2026 videos are online The State of Django 2026: Boring is so back htmx 4.0.0 has been released 🐍 Functionally Zen Extras Joke Watch on YouTube Sponsored by us! Support our work through: Our courses at Talk Python Consulting from Six Feet Up Connect with the hosts Michael: Mastodon / BlueSky / X / LinkedIn Calvin: Mastodon / BlueSky / X / LinkedIn Show: Mastodon / BlueSky / X Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am PT. Older video versions available there too. Finally, if you want an artisanal digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: EuroPython 2026 videos are online The EuroPython Society has published all 117 recordings from EuroPython 2026 on the official EuroPython Conference YouTube channel. The conference ran July 13-19 in Krakow, Poland and celebrated the conference series' 25th anniversary. The playlist covers keynotes, panels, lightning talks, and full talk recordings across Python core, web, DevOps, data/ML, embedded, and other tracks. If you missed EuroPython 2026 in Krakow, this is the complete free on-demand archive of one of the year's biggest European Python events. 117 videos now live on the EuroPython Conference YouTube channel, last updated Aug 17, 2026. Michael’s personal watch list. Calvin #2: The State of Django 2026: Boring is so back State of Django 2026 (JetBrains/DSF survey, ~3,500 devs, 40+ countries) - "boring is so back": Django's core stays reliable while everything around it moves fast Core is stable: Postgres 76–79% for 5 years running, templates ~80%, 43% already on Django 6.0 AI is routine now (only 10% use none) but workflow's unsettled - Claude Code leads at 35%, and 56% still just use it for chat, not autonomous edits Tooling is consolidating: uv and Ruff both at 43% adoption, each replacing several older single-purpose tools Type hints are winning (57% use them) but the checker is up for grabs - IDE-built-in leads at 40%, Mypy 32%, with ty/Pyrefly emerging Two Django communities coexist happily: 72% server-rendered templates vs. 53% API-only - and htmx adoption jumped from 5% to 34% in five years Michael #3: htmx 4.0.0 has been released After 8 months of work, the htmx team shipped 4.0.0, a rewrite that moves internals from XMLHttpRequest to fetch() while keeping the API almost identical to htmx 2. Three changes may need action: attribute inheritance is now explicit via an :inherited suffix, event names follow a htmx:phase:action pattern, and history no longer caches pages in localStorage. Additions include built-in morph swaps, the new hx-partial tag, and many core extensions. htmx 2 stays supported and remains latest on npm until early 2027. htmx is the go-to frontend layer for Python server-rendered apps (Flask, Django, FastAPI), and 4.0 is deliberately low-drama: nearly behavior-compatible, so teams can upgrade on their own schedule and pick up morph swaps and streaming extensions. Explicit inheritance is the biggest migration item: hx-confirm, hx-headers, hx-target and friends no longer cascade to children unless you append :inherited; hx-disinherit and hx-inherit are gone A CLI upgrade checker (npx htmx.org@4.0.0 upgrade-check) flags spots needing :inherited, renames like hx-disable to hx-ignore, removed attrs like hx-vars, and old event names in templates and JS Events follow htmx:phase:action (htmx:beforeRequest becomes htmx:before:request); most error events collapse into htmx:error and htmx:xhr:* events are removed with XMLHttpRequest History no longer snapshots pages in localStorage; back navigation re-fetches and swaps into the body, fixing a chronic support headache, with a new hx-history-cache extension for sessionStorage caching New features: out-of-the-box morphing swaps, the [HTML_REMOVED] tag for multi-element updates, streaming over SSE/WebSockets/multipart, and hx-live, their Alpine-inspired DOM scripting solution No forced upgrade: 2.x stays latest on npm until early 2027 (4.0 remains next) and is supported indefinitely; the team even ships official LLM skill files for guidance and upgrading Calvin #4: 🐍 Functionally Zen Functionally Zen (Kyle Adams, Test Double) - riffs on "simple is better than complex" with 7 extra tenets for Python simplicity Core claims: idiomatic > non-idiomatic, data > functions, pure functions > impure functions > classes Favorite example: a medical-dosage calculator replaced with a plain lookup dict - no logic, no tests needed Big idea: keep a thin "impure shell" around a "pure core" (Gary Bernhardt's functional core / imperative shell) - push side effects (API calls, DB, files) to the edges Side note: constructors that do I/O are "poison pills" - the side effect infects every class that depends on them Payoff: pure functions and no-mock tests are just easier to read and reason about than the alternative Extras Calvin: uv ships trusted-publisher token revocation and Python 3.15 support Making a Python interpreter in 1024 bytes Michael: Steering council voting is now open Joke: Makes you look like this?

Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to your earbuds. This is episode 495, recorded on Tuesday, September 8th. I'm Calvin Hendricks Parker. And I'm Michael Kennedy. Glad to have you, Michael. If you want to support the people who make this possible, make sure support our sponsors, the fine folks at, oh, Talk Python. Make sure you check out Michael's courses. He is doing incredible work over there. It's a great way to brush up on some technology you weren't sure about, try something new. He's got some nearly coolness. You just released a couple new courses, right? Yeah, we just released a Rust course, which I think is really nice. Yeah. Very cool.

And then also check out the fine folks over at 6 feet up. They are the ones who love solving hard problems. They do a lot of Python work. They've been around for 27 years. And we'd love to talk to you about doing some cool projects. If you want to connect with the hosts online, you can find Michael, myself, and the show on Macedon, Blue Sky, and X. And you can also find Michael and I on LinkedIn.

Make sure you join us on YouTube for the live stream at Pythonbites.fm slash live to be part of the audience. Usually it's Tuesday mornings Pacific Time. Older video versions are available there too. And finally, if you want our artisanal digest of every week's show notes in email form, add your name to our friends of the show list and we'll ever share it, but you'll get a really cool recap of everything we talked about. Michael, thinking about recaps, what you got? I always look forward to when the videos of the conferences come out.

How about you? Same. I do too. I mean, a lot, sometimes I'm at the conference and I just miss a great talk, and I'm so glad that many of the good ones are recorded. Exactly the same. And sometimes you don't miss it because you just want to. There's tradeoffs, right? Like, I'm going to go to that talk instead of that one.

Or, oh, there's a really interesting group of people having this conversation. And the talk is starting now. You've got to decide, do I join the group and have the experience that's not going to be recorded or do I go to the talk? So, Europython, 2026. has all of the videos out. And I realize I need to update what I put in the show notes because this is just my subset.

So if you want to watch all the talks for Euro Python, 117 videos are now online on YouTube, which is great. That is fantastic. And quick, because the conference just happened. Yes, I know. It's really, really good. And I went through and said, hmm, what might make an interesting thing that I personally would be interested in.

This is not a voting. This is not a ranking. This is not a good, bad. This is Michael wants to watch this for two reasons. Either one is relevant to me. Or I might be considering it for a Talk Python episode. Like, for example, the very first one by Giovanni Barilari is already out over on Doc Python. Oh, nice.

As the latest. He did a cool project, rewriting ASync I.O. From a perspective of what if there was only free-threaded Python? You wouldn't write async I.O. exactly the same because you have the potential to split that work across multiple threads, whereas ASync IO is single-threaded, et cetera. So I'm finding these really interesting. We've got Marlene Magami.

Her talk or keynote is up. Updates on the Jit. Update on free threaded Python by Thomas Warders. Paul Everett is in here somewhere because it's Paul Everett. I have not watched his talk yet. I really want to because he talks a lot about kind of the future. of AI-driven development and local models and controlling your dusting and your data. Yeah, exactly. So if I'm an Ostrowski deploying Python web apps by Will Vincent, probably

with a lean towards Django, hint to your topics, maybe. Maybe. Anyway, I thought I would make my, like this morning, I did it, made my watch list public because I don't know, I went through all 117 videos and said, okay, maybe, probably. and now it's down to 29. So people can check that out or they can just look at the full list. I'd love that you make it a watch list

so you get Michael's curated version and so I can go enjoy what you think might be important because maybe I follow similar topics. So I think more folks should do that with conference videos because it's so hard to go, I mean,

you say what 117 videos, what you said? Yes. Yeah, that's a lot. That's a lot of time to invest. I would venture, there's probably not a single person that watches all videos,

all the way through, you know? Yeah, that'd be hard. That would be super hard. That's just a lot of time. That's a lot of time. Well, and I just got back from Django Cotton, which was in Chicago. And at the same time, just shortly afterwards, the Pye Charm folks and the Django Software Foundation have released the 2026 state of Django.

And I love so that William Vincent also published this over on the Picharm blog. I love the fact that it's called Boring is Back. If you've ever read the blog post about boring tokens, like you only get to have so many new shiny technologies, shiny tokens, you only get so many new shiny technologies in your project. The good news is you can have Django and you can have Postgres, and they're both considered very boring and very stable. If you look through here, it's very thriving.

Postgres is actually the database of choice for almost 80% of the respondents who are doing Django work out there, which I think is a really telling mark. Another nice thing to see here is 43% are already on Django 6.0 months after it shipped. So folks are staying up to date and pretty well on the stable side of things. It was 3,500 Django developers across more than 40 countries. So it's a fairly good representation of the world's uses of Django. Statistically, I think that that's a pretty big sample size.

Yeah. I mean, they did a good job of promoting it across multiple podcasts and conferences and things like that. I think it's been really well received. They got a nice little infographic here. What I thought was interesting is this relates to maybe a future topic of yours. HGMX is closing in on React for the front end. You see here we've gone from 2025, 26% of projects maybe using, or we're using HTMLX to now 34% catching up to React,

which is only at 38% on the front end. I'm pro that. I think that's a really great sign of maybe people are looking for the simpler, or more boring side of the web. And Django is a great place to do it. Folks obviously using AI. So it's interesting, they had a couple special sections in here. AI is mainstream, but no workflow is one.

So whether they're using it all the time, several days a week, once or more often, AI is dominating the workflow, but it's still supervised, which I think it should be. The AI is here to make us better developers not replace us as developers. I think we've seen that time and time again as we talk about AI on the various shows. And so the report here, the stats definitely show it. I mean, that's the way to get the most out of these tools. VM is still at the top of the list for managing your Python environment, not necessarily your Python dependencies, but the Python environment.

I have a feeling UV will overtake here real soon because once you see UV work for getting your Python version, it's hard to go back seeing how fast and easy that is to be managed. Docker at 31%. So I'm also quite excited to see the fact that folks are containerizing in general. just using the Python coming out of the containers. That's also a very simple and easy way to just get started on the right foot with Python. And Jango is used Python. It's already in a Docker container.

Yeah. Yeah. And we're both on Team Docker. Oh, yeah, for sure. And in fact, I'm on Team VE and V in Docker for consistency across the Dev Workflow. Me and Henneck. Right. I'm on, actually, I use Docker, but a standard container and install my own UV.

Python via UV for consistency. Exactly same. Like I don't want to pick some pre-made thing. Like well Python comes with it. It's like it's so easy to install Python into it. Pick, pick more specifically, I think. And you run into weird edge cases if you start just kind of coloring slightly outside the lines with one of the standard Python ones, it could be a C dependency or just

a weirdness of you want to install something and it gets hard. So I find just going with a standard like Debian container with the UV to install this way go. Rough, top of the list for code tooling, no surprises there. I think we should see more pre-commit coming up given what we'll see down here later. There's lots of testing going on. AI's write more code. Verification matters more. You see right here, pie test 45%. So we will, we see lots more testing happening, which I think is also a very good sign. And I'll talk a little bit about that in my second article as well. So I think, yeah, go check it out. This was also part of a fundraiser. So if you are renewing your PITRAM Pro license or looking for one, you can

get 30% off. And then you also get 100% of that purchase price goes to the Django Software Foundation. So not an ad for PITRM necessarily, but they are doing good out there in the world. I like a lot about this. Specifically, I also think this is a more, a deeper view into Python in general. When I saw the headline for the survey, I thought, oh, it's going to survey Django things. Like, who's using this feature, the ORM? And then who's deploying? this way versus that way. And no, it's more of a general thing. Just let's ask the Django people what they're doing.

What they're up to, yeah. Yeah. Nope. Really good stuff. It is good stuff. I'm glad you covered it. Speaking of good stuff. Well, I mean, boring is good.

But you mentioned HTMLX. Well, HTMLX4 is now out. And that's officially released. Officially. And it's a Jeep. No, it's not a, excuse me. No, it's a horse. It's a land cruiser, I believe.

not a Jeep. Anyway, there's a big picture on the announcement of some... Well, then that same cover art for the Game Boy Color Cartridge that they produced in the announcement as well, which I have. You have, okay. I've been playing it too. So thank you, Carson for doing that. In the release, HTMLX4.00, yay for non-zero-zerover.

It says, after eight months of work plus a game, and if you go to the game, it's, this is a real Game Boy cartridge you can get. Yep, I have said cartridge is not made up. It's legitimately a cartridge you can play through. If you play all the way through, your reward is to see the source code for H-TMX-40. Oh. Incredible. It is.

So there's a lot of interesting changes here. I think, first of all, HTMLX has been really broadly adopted by people who are just like, I don't want to take on a React front-end framework or something like that. Even though all of the AI tools leap at using React for stuff, it's still really popular, which I think people are choosing. Why do you want to develop your models twice? Yeah. Why do you want a bunch of build steps and all that stuff? Twice. Just to get your app out.

Yeah. If you don't need it, don't go all in. Also, a lot of these front-end frameworks, not HTMLX, but many of them encourage you to treat your back-end as a dumb. pipe that just routes data to the front end where the smarts live. It's fine if you want to write your code on the front end in JavaScript. But if you want to leverage the things that are really nice about Django or Flask or whatever you're writing against and just Python in general, well, then it kind of undermines that, right? Yeah. But it's the last you to stay in the batteries included world, especially with Django. Like all the HTML like filters and helpers that are built in to

Django the framework are all still very useful with a tool like this. They become useless if you're on React. Like you're right and kind of to use it. Right. Exactly. Exactly. So major changes. Attribute inheritance is now explicit.

It's a little as that a Python, isn't it? So it used to be you could do like an HX dash confirm. And if some action was going to happen, first a dialogue would pop up and say, are you sure you want to delete all the data? And you would say yes or no. But you could put that and say a div that contains some elements. there was a button way down. And if you click the button, the confirm would fire.

That no longer happens. So you have to explicitly say at the top and the confirm, and I want this to cascade down to the children. I guess part. Yeah. Except for that, it stops working. That's the only problem. On the older code, so there's an upgrade path.

It's not major, but there is, I mean, it's kind of a find and replace upgrade path. So it's not a huge deal. The invent names have been changed a little bit. We'll go through with some examples, I guess. So, yeah, there's, like, you could do it, HX confirm, and then a button with an HX delete, and now you've got to say, colon, inherited. The event, or I also used to be able to say disinherit,

so you could block a child from having stuff inherited upon it. Leave this part alone. Get away from me. Now that's gone. Now that's gone because you just, that's the default, is not to inherit. So you don't have to say, don't cascade it down. Some event were renamed, here's the find and replace, right?

So it used to be HTMLX before request. Now it's HTMLX, before colon request and so on. What else? History, this is actually, I didn't know this was happening. This is not ideal. So history support allows you go forwards and backwards,

even if, so your forwards and backwards can navigate between H-TMX events, not through just the page loads, right? So if I click a button, yeah, and it does a load, it changes something else, and I click another, maybe another row in a grid, and a master detail,

like another detail thing, loads. You can go backwards, to forwards between those. I didn't know this. It used to be that in HTMLX2, the way backwards and forward worked is it would save a copy of the pages for restoration and local storage. Like, forget the storage part. Like, wait, what if that data changed? You know, there's there's two hard thing. Yeah, dangerous. Exactly. There's like two hard things in computer science. Caching, naming things, and off by one errors, right? Love that joke. Yeah, it's there for a reason the cashing is super hard. And this was so, like, I thought it was just reloading it.

What's going on? So anyway, that's gone. Nice. Just literally reloads it like, I always thought it did. So there's that. And the last one is, well, there's like two things. There's morph swaps. So what this is, I had to look this up, folks, is a morph swap is that instead of saying

this portion of the page is changing. So we're going to get the new partial fragment from the server and just replace that. a morph swap will rewrite the DOM to match the new segment. So, for example, it doesn't, you know, jump around as much and those kinds of things, right? If maybe only some tiny element, even though you replace the whole section, changes, it's like, okay, we'll just change the little element because, you know, again, master detail. Like, there's a whole structure of the HTML there, but really as you click from page to page, it's just the values inside that structure. That sounds hard as a framework, but much easier for the end user who's building with the framework. Exactly. Let them suffer.

Apparently they did the suffering for us, which I love. Yes. I mean, honestly, it's not the point of a framework. It is. I mean, why would you do a framework if you're not going to... Right. Otherwise, you just do your... Leverage. And then the HX partial tag.

So this for out-of-band changes. This is where H-TMX used to be really brutal. And honestly, I've worked on a project before and in the end. I'm like, oh, I kind of wish I didn't choose H-T-MX for this, because I want to update something over here and something over there. and this part here and it was tough. So this lets you specify partials and then elements of it that change, right? So pretty neat.

That's slick. It allows you to sort of glue that stuff together. Very nice. Yeah, so there it is. I mean, and they definitely get best launch swag gifts or whatever. The Game Boy cartridge, over the top and real. I love it. I know.

The website, you can go to the website and play it too, but that's not. even had the imited version. That's cool. So everyone can enjoy it if you don't have a Game Boy. But that's crazy, right? It is super crazy. It works. It's a beautiful cartridge, really well done. Like, the game was surprisingly well done for, I can't imagine how much time they spent on it. Well, Carson definitely is known for interesting and catchy stuff. So. Well, well, well played. Well, well played. Well, it's awesome. Yeah, let's head over. You mentioned some Zen of Python thing. So for the, final news article for me. This is actually a local IndyPy

person. He presented about two Indypies ago. Kyle from TestDouble gave a little nice little blog post about functionally Zen and I kind of like going back over Zen of Python things. It's one of my favorite talks to give at Pycon and other conferences is something more around these initial tenets of Python and simplicity and why we love it. And for those of you don't know, you can go to your command line, you can type Python minus M this, and you will see the little Easter egg, which is the Zen of Python that is in Python. Everyone should print it out. They should frame it and you should put it in your, above your sink when you brush your teeth at night, so you can read it

every night. And you'll become a better human being instantly because you've got the Zen of Python there available to you. But Kyle took the Zen of Python, and he actually put tech, took kind of added into it like seven extra tenets for Python simplicity. So he took specifically the, simple is better than complex tenet of Python and then added these seven additional pieces that are about idiomatic code data pure functions being simpler than impure functions it kind of goes on like in class functions being maybe simpler than than classes so it's just a way to think about how to keep your code again simple there's no reason to get overly complex if you don't have to and python gives you all the tools that are right here so you can talk about again he talks about

being idiomatic. There's things you need to watch out for, for example, side effects, especially with classes that have constructors. They can have side effects in subclasses that you aren't aware of. So it just adds to the complexity and overhead as a developer. Some good examples in here. So if you looked at the idiomatic code is simpler than non-idimatic code, some functional programmers might be tempted to use the map function of Python to extend a list. But there's actually a simpler way. Just using a list comprehension is actually a clear, probably cleaner way for writing what you're looking for there. So this actually loops through and does the X times 2 for X and a list of 1, 2, 3. So now you've got 2, 4.6. And sometimes I think even better performance. Not hugely,

but a little bit. Well, now the docs should build tell us, right? Because I've got the O notation for those things in there. It's right in the docs. Data is simple than functions. This one's a little harder to do. I think the example was a little contrived because if you have an object that has age with a sub-element of weight and a sub-element of lab measurement, I don't know if you'd have that structure necessarily all the time, but if you can get your data structured that way, it's probably easier to use, again, a dictionary look-up, and actually it's probably faster, to use a dictionary look-up than it is to run a function that would be taking in arguments and looking up things based on those arguments. So I mostly agree with that example. This is about the impure function

or pure functions versus impure. So this pure function, for example, you're certain is always going to return an integer. Like it has a reliable return to it. The second example where they're talking about fetch doubles. The first one was like a double where you just return X times two. So it doubles the number.

The second one, which was like fetch under double, it actually uses requests to get the response and then it tries to return the body looking for an answer key. That is not as stable. It could be it returns to or four. It could be the returns a 500 server error. Could be the returns some other, if a developer makes a mistake someplace, some other not expected answer or a string.

So that's just an example of what impure. It might even return an exception. Right, right. And then the pure functions versus classes, I mean, if you look at the example here, a function you can do is simply and as simply as two lines with a definition of the function and a return. When you start talking about classes, you just keep. get a lot more boilerplate going on inside the class.

So if you don't need the classes, there's probably no reason to go that direction. And it kind of goes on and on and on here with more and more examples that just show some simpler ways to do that. This is the last one I'll talk about, which is the side effects. If you have a class that has a constructor in it, so you've defined a dunder and knit method,

that dunder and knit can affect subclasses, and you may not be aware of it because you've not looked at the code for it. So they have a time client example here with a dunder and knit. it that initializes a token using a request post. So it actually makes an API call in the base class. These other ones for time service and time controller are calling a constructor that uses that client,

which means that every one of these will also make an API request. So you may want to manage that a little cleaner and reduce them or say, for example, external calls you're making in that case. The last bit I'll call out in honor of Brian Ockin and his Lean TD book, Test with no mocking are simpler than tests with mocking. I think we can all agree, but I think there's a world that needs to hear it, and there's a book about it. So if you go check out Brian's Lean TDD book, he talks about this as well as part of that book.

So I thought that was pretty apt and timely that this came up. And thanks Kyle for helping remind folks of the simpler ways and the nice idioms that Python gives us out of the box. I really like it. I remember when I first got into Python, I hear Pythonic. I'm like, but I need examples. Same. worship, great, but give me examples so much.

Yeah, I learned by example, and these are just great examples of like, oh, that's how I should do that. Okay, I can follow that pattern every time. Yeah, absolutely. That's good stuff. Speaking of following a pattern, your screen's already up. Maybe you just take the extras. Yeah, I'll take the, I'll go the extras first.

In continuing in my three-week streak of talking about UV releases and new features, the latest one released four days ago, UV0.12.10, now ships the trusted public. token revocation and it has Python 315 support. So UV is on a terror of keeping up with all the latest bits that are going on, including the Python 315 releases coming up. So that's really cool that they're doing that. And then the other bit I saw a fun little release here, making a Python interpreter in 1,024 bytes.

So kind of a little example of if you've ever done code golf, do something in such and such a number of steps, This person implemented a full Python interpreter in 1,024 bytes of good old C code. So that's pretty wild. I think he first attempted with 512 bytes, which seems kind of crazy. Yeah, good for you, Austin. The subtitle was 512 bytes is not enough. Right.

No kidding, wow. So, yeah, he chronicled his whole journey. I just thought that was fun, not necessarily a full news article, but it's pretty cool the people out there doing still cool stuff like that. That's some minified python, not something you normally see. Right. But yeah. Wow.

Okay. I just got one quick one. Steering Council elections are going on. So check them out. The schedule is the voting period. Oh, two-week nomination period followed by a voting period. When is this, actually? I saw that the votes were coming up, but I don't see the actual.

Anyway, it's previously been November through December or November through November. I think it's not yet up or just started. Anyway, this is the 2026 one. And so candidates, the nominees are here. Lots of folks I see. Yeah. Yeah, it's a good list. So check it out, folks.

And yeah, so anyway, just want to give a shout out to that being a thing. Hey, Michael. You got any jokes for us? I have a band joke. A band joke. Oh, my God. You mean like band as not allowed? We're going to be kicked off of YouTube and all the...

Disallowed. We'll only get kicked off Reddit. This is not a like a trombone versus trumpet. Like, what can you do with the trombone? Like hit him with a little like slider thing. I don't know. I used to play the trombone. I never really enjoyed it though.

It was a requirement. No, the joke is, keep in mind, this is not programming exactly. It's IT, but I think we can all just like enjoy a little IT stuff, you know? And it says, what single word in IT makes you look like this? And there used to be a picture that had a, ah, like I can't take it anymore. And sorry, this post was removed by Reddit's filters. And all it was was a picture of somebody making a weird face. Like, honestly, I don't know what was wrong with it.

But. Someone got up in arms. This one took me a minute to understand what the heck it was. It said, hello. Do you know what this is about? Why would this make IT people wig out? Maybe you know. I don't know.

I didn't either. It's apparently on teams or Slack if somebody just says, hello, and then they're going to write more, but then they kind of don't. You're like, I? Okay. That could make me a little, okay. Let's go. All right, not a single word, but anytime I get a direct message along the lines, you got a minute? Or can I ask a question?

Yes, exactly. Let's see. So I got to collapse them because they all go down at like, this person says, printer. Just no, no. What year is this and we still can't reliably print? I know. I just this other, just like last week, I print maybe twice a year and I just needed to print. And it's like the printer's out of ink.

I just bought it ink. I haven't printed since the last time I bought it. I think anyway. But as in, not to interrupt your lunch, but... Could you add in a well, actually? Yeah. Rico or scan to mail? Yeah.

Now I get hello. Now I get hello. That's pretty good. Yeah. So, all right. Now I'm in my zone now. D&S. There's even like a little like Japanese style like water painting.

It says it's not D&S. There's no way it's D&S. It's always D&S, like some philosopher. Yeah. In the early days of six feet up, Gabrielle made a comic about DNS because it was so hard to explain to folks. And every time I say there's a problem, she's like, is it DNS? And so this is my co-founder partner in life and she totally gets it. DNS is absolutely the problem.

This one might be from a outlook. Crowd strike. Ever since you owe this one. Oh, my God. Ever since you're XYZ. This doesn't work anymore. Update? Update.

Yeah. I'm surprised update's not in there. Oracle. I'm on that bandwagon. SharePoint. Let's see what else we got. CVE or just Citrix? Teams.

SAP, you got my vote on SAP. Oh my gosh. Anyway, I thought this was a really fun list. It was pretty good. I don't understand why. That was a good thread. I don't understand why they banned it. But whatever.

Now that makes it even better. Yeah, I know. Awesome. I put stuff up there and it'll be like, well, it looks like you're trying to share an announcement. And that's not allowed. So blocked. Like, just. I wrote a blog post.

I thought this community would think was interesting, so I wanted to share it. It's like, I'm not selling you anything, I promise. Not in this case anyway. Not on my blog. Sorry, Michael. Not allowed. Banned.

Banned. Well, that was a good episode. Thanks for hanging out, and we'll see you all next week. I'll still be in France next week, I believe. O'Vois. O'Vois.