Great article by Ploum about chatbots/AI and education: https://ploum.net/2026-01-19-exam-with-chatbots.html
#wn2ms2q
If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!
You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.
@movq does not follow you (they may not see your replies!)
Great article by Ploum about chatbots/AI and education: https://ploum.net/2026-01-19-exam-with-chatbots.html
When people āmake plansā, I always respond like this:
https://movq.de/v/9a8712846d/at-night.jpg
Finally found the clip where this is from:
(#kkebt2a) @prologic@twtxt.net Reminds me to have another look at LSP. Last time I checked, it was super messy in Vim. š¤
Spent basically the entire day (except for the mandatory walk) fighting with Pythonās type hints. But, the result is that my widget toolkit now passes mypy --strict.
I really, really donāt want to write larger pieces of software without static typing anymore. With dynamic typing, you must test every code path in your program to catch even the most basic errors. pylint helps a bit (doesnāt need type hints), but thatās really not enough.
Also, somewhere along the way, I picked up a very bad (Python) programming style. (Actually, I know exactly where I picked that up, but I donāt want to point the finger now.) This style makes heavy use of dicts and tuples instead of proper classes. That works for small scripts, but it very quickly turns into an absolute mess once the program grows. Prime example: jenny. š©
I have a love-hate relationship with Pythonās type hints, because they are meaningless at runtime, so they can be utterly misleading. Iām beginning to like them as an additional safety-net, though.
(But really, if correctness is the goal, you either need to invest a ton of time to get 100% test coverage ā or donāt use Python.)
(#ikxk5fq) @shinyoukai@yume.laidback.moe Yeah, I avoided that issue as well. I moved everything on the website except for the twtxt stuff.
(#5sx3vhq) @lyse@lyse.isobeef.org The thing is thatās hard to avoid if TYPE_CHECKING, but documentation tools such as pdoc donāt support that ⦠so itās either type hints or API docs. š¤·
I hope I can eventually find a way out of this mess ā¦
(#ibvedvq) @javivf@adn.org.es Oh! Thanks, should be fixed now. š
(#6g5l2oa) @lyse@lyse.isobeef.org All that short brown grass, almost looks like Scotland. š¤ (Iāve never been there. š )
What the heck is 06.jpg?
(#i6mgd3a) @prologic@twtxt.net Changed the domain of my website (except for twtxt).
(#6acyh5q) @lyse@lyse.isobeef.org (At least I didnāt break all the links again. In late 2015, I switched from a PHP backend to the current static website, which changed just about everything. I hope doing a disruptive change like this one every 10 years is tolerable. š )
(#6acyh5q) @lyse@lyse.isobeef.org Oh, right. Forgot about that. š«¤
(#i6mgd3a) Did it work? Am I still here? š¤£
(#i6mgd3a) @prologic@twtxt.net I think I found an easy way to redirect anything except the twtxt stuff. Thatās probably better. š¤
So, are you guys up for an experiment?
Iām really not happy with the domain āuninformativ.deā anymore. Iām going to switch to āmovq.deā soon (or maybe something else if I get another fancy idea).
If I keep the url = field in my twtxt file, nothing should break, right? Right? š¤£
(#m4r2yzq) @prologic@twtxt.net Yup. š
(#bkzrqsq) @bender@twtxt.net gemini-cli, something something https://github.com/google-gemini/gemini-cli/issues/16723
I recently got an email with this byte sequence:
\xf0\x9f\x8e\x81\xf0\x9f\x95\xaf\xef\xb8\x8f
Thatās U+1F381, U+1F56F, U+FE0F. The last one is a āvariation selectorā:
https://unicodeplus.com/U+FE0F
My toolkit renders this incorrectly ā and so do tmux and GNU screen.
Unicode aināt easy. š„“
https://github.com/unix-v4-commentary/unix-v4-source-commentary
A comprehensive, line-by-line commentary on the UNIX Fourth Edition source code (released November 1973; tape recovered from June 1974 distribution).
(#hddm6pa) @prologic@twtxt.net Iād love to take a look at the code. š
Iām kind of curious to know how much Assembly I need vs. How much of a microkernel can I build purely in Mu (µ)? š¤
Canāt really answer that, because I only made a working kernel for 16-bit real mode yet. That is 99% C, though, only syscall entry points are Assembly. (The OpenWatcom compiler provides C wrappers for triggering software interrupts, which makes things easier.)
But in long mode? No idea yet. š At least changing the page tables will require a tiny little bit of Assembly.
(#hddm6pa) @prologic@twtxt.net Damn, nice! I know exactly what you mean ā the output/screenshot looks trivial, but thereās so much going on behind the scenes. š
Did you do the whole dance with BIOS boot and everything?
(#4b4ypwa) @lyse@lyse.isobeef.org ⦠I sure hope that they generate these files from the general terminfo database instead of maintaining their own DB. š³
(#mqvmwva) @bender@twtxt.net Iām already using it for tracktivity (meant for tracking activities and events, like weather, food consumption, stuff like that), which is basically a somewhat-fancy CSV editor:
https://movq.de/v/f26eb836ee/s.png
I have a couple of other projects where I could use it, because they are plain curses at the moment. Like, one of them has an āedit boxā, but you canāt enter Unicode, because it was too complicated. That would benefit from the framework.
Either way, itās the most satisfying project in a long time and Iām learning a ton of stuff.
(#4b4ypwa) @lyse@lyse.isobeef.org Unix terminals are quite limited in that regard. 𫤠You know how Ctrl works? The XOR 0x40 thing? And Alt doesnāt exist at all, itās just a prefixed ESC byte.
I was surprised to see curses knowing about āShift+Tabā, wondering how that is supposed to work. Well, itās an escape sequence, of course (depending on the terminal, of course).
Some work on the menu system to brighten my mood a little bit. No mouse support yet.
(#ajerg7a) @prologic@twtxt.net Probably not, but thanks. š Itāll get better.
(#ajerg7a) @prologic@twtxt.net Work and the general state of (gestures broadly) everything.
Frustration level: Through the roof.
(#zqzv6cq) @bender@twtxt.net I vaguely remember this, some leftover from the old-style hashtags? The (#foo) stuff? š¤
(#2puspya) @lyse@lyse.isobeef.org Never heard of either, tbh. š³
(#5bf3c5q) @lyse@lyse.isobeef.org
Pep8 is deprecated, I think
Hmm, I donāt think it is, this still says āStatus: Activeā: https://peps.python.org/pep-0008/ š¤
Since I used so much Rust during the holidays, I got totally used to rustfmt. I now use similar tools for Python (black and isort).
What have I been doing all these years?! I never want to format code manually again. š¤£š
(#74u6qdq) @shinyoukai@yume.laidback.moe Hopefully, yes. Havenāt tried it yet.
(#u53qyya) @shinyoukai@neko.laidback.moe mckinley is back? Where? š¤
Okay, I had heard of āRiverā before but I was not aware of this:
https://codeberg.org/river/river
River defers all window management policy to a separate window manager implementing the river-window-management-v1 protocol. This includes window position/size, pointer/keyboard bindings, focus management, window decorations, desktop shell graphics, and more.
This sounds promising and it follows the old X11 model. River does all the nasty Wayland work and I can make just the WM? š¤š¤Æ
(#g34eztq) @lyse@lyse.isobeef.org Itās not super comfortable, thatās right.
But these mouse events come with a caveat anyway:
ncurses uses the XM terminfo entry to enable mouse events, but it looks like this entry does not enable motion events for most terminal emulators. Reporting motion events is supported by, say, XTerm, xiate, st, or urxvt, it just isnāt activated by XM. This makes all this dragging stuff useless.
For the moment, I edited the terminfo entry for my terminal to include motion events. That canāt be a proper solution. Iām not sure yet if Iām supposed to send the appropriate sequence manually ā¦
And the terminfo entries for tmux or screen donāt include XM at all. tmux itself supports the mouse, but Iām not sure yet how to make it pass on the events to the programs running inside of it (maybe thatās just not supported).
To make things worse, on the Linux VT (outside of X11 or Wayland), the whole thing works differently: You have to use good old gpm to get mouse events (gpm has been around forever, I already used this on SuSE Linux). ncurses does support this, but this is a build flag and Arch Linux doesnāt set this flag. So, at the moment, Iām running a custom build of ncurses as a quick hack. š And this doesnāt report motion events either! Just clicks. (I donāt know if gpm itself can report motion events, I never used the library directly.)
tl;dr: The whole thing will probably be ākeyboard firstā and then the mouse stuff is a gimmick on top. As much as Iād like to, this isnāt going to be like TUI applications on DOS. Iāll use āWindowsā for popups or a multi-window view (with the āWindowManagerā being a tiny little tiling WM).