This is a real time recording of my git server's web access logs. It's a constant stream of requests from "Claude" attempting to access every possible item on the site.
A couple of months ago, I set up a rule to return an error code for every request its user agent makes. It has not retrieved a single valid item for many, many weeks at this point. Every request is immediately and abruptly terminated.
It hasn't even slowed down as a result.
Tell me again how their operation involves "intelligence" of any kind.

IRCv3 is shaping to be amazingly good!
here's the things it offers, today, right now, on a chat server we just set up in one evening:
you don't need a bouncer (friggin finally). there are moblie clients that work well
you can see backlog when joining a channel
you can browse chat history
you can connect from multiple devices with one account and nickname
if you disconnect, your nickname is still present in a channel you joined, marked as away
you can highlight or DM people who are away and they'll see your message when they join (without crutches like MemoServ)
there is a "last read message" marker and it is synchronized between multiple connections
you don't need to deal with fussy nonsense like NickServ authorization, ghosting, or such; connect with your username and password and that's it
there are typing notifiers, if you want them
there are message reactions, if you want them
here's the things it does not offer:
image, video, or file uploads
stickers
complex onboarding tools
unexpectly, i realized that IRCv3 can completely replace Matrix rooms for my own group chat purposes, and i'm probably not going to set up any Matrix homeservers again; it's just not worth it and frankly I should instead put that effort into coming up with a file upload IRCv3 extension or something
There's a trailer for a new #ToyStory movie out now and at one point it depicts a tablet displaying macOSey looking terminal windows with zsh as a shell being filled with Python code.
This means two things:
- we live in a timeline where fictional children toys from movies offer a more productive environment that the majority of real world's grown-up tablets
- if they don't reference #Debian one way or another in the movie I'll lose any remaining respect towards #Pixar 😜
Call me a Time Lord, cause lately whenever I dig into something in the kernel I end up fixing clocks being all over the place 🕐 🕜 🕢 🕖 #librem5 #linux #mobilelinux
Debian thanks all the contributors building and nurturing the FOSS ecosystem and wishes everyone a very happy "I Love Free Software Day" https://fsfe.org/activities/ilovefs/ #debian #ilovefs #02
CSS Clicker by @rebane2001 is probably the most impressive thing I've seen done with CSS ever. Check it out https://lyra.horse/css-clicker/
ScummVM 2026.1.0 "Like a Version" is finally released!
Another year has gone by, therefore we are releasing a new ScummVM version. As you may notice right away, we are changing our version numbering schema, but that’s not all!
Find out more about the recent updates for software ISP and GPU acceleration tomorrow in room UD2.120 at 13:00
https://fosdem.org/2026/schedule/event/TKSK3G-libcamera-softisp/
It doesn't look particularly useful for the use-case of streaming through USB 3.0 either.
With 2 lanes, at 4K we get 30 FPS with 8-bit and 25 FPS with 10-bit.
8-bit may fit into available USB 3.0 bandwidth, though it's already getting tight. 10-bit won't fit without repacking, cause we're getting 16-bit values from the CSI receiver - so you likely won't stream out more than 15 FPS anyway.
So 2 lanes it is!
This would translate to about 33 FPS when cropped to 4K.
We should be able to record up to 5 seconds of 10-bit 4K 30 FPS video to RAM, assuming 2GB of free space there. Is that worth the effort? 😁
Actually, we could probably go up to 21 FPS with 10-bit by using 3 lanes, but not sure if that's worth the effort.
So I finally understand why 4-lane MIPI CSI-2 doesn't work with the #Librem5's big cam.
Turns out it's not going to work - but I now at least understand why 😂
(this limits streaming at full res to about 16 FPS 10-bit and 20 FPS 8-bit instead of the sensor's 30 FPS, but you won't really be able to process it at this speed anyway so it's not a big loss; lower res can still work with higher framerates; with the current driver up to 120 FPS but it could go even higher)
🥳 Earlier today we landed the bits in #phosh to show the splash screens of running apps in the overview. This also hopefully looks a bit more polished than the initial version. Likely not much news on other platforms but this was bugging us for some time 😅:
Hi, I'm dos. Silly FLOSS games, open smartphones, terrible music and more. 50% of @holypangolin; 100% of dosowisko.net. he/him/any. I don't receive DMs.