@movq@www.uninformativ.de well, emojis in the TTY (as in, what we’re used to now, not actual teletypes) are simply rendered as tofu boxes or not at all

@movq@www.uninformativ.de that’s a huge no about the last part, but you know what will happen?

The 20th anniversary of the Haruhi Suzumiya anime series, that’s what!

(Also I was told YOTLD was actually 11 years ago and everyone joining it after that is pretty much late)

@javivf@adn.org.es

@lyse@lyse.isobeef.org I haven’t spoken to a single person yet who was a fan of all this. Not even the more conservative family members.

Some people have detonated several really loud bombs yesterday. This wasn’t a “Böller”. It shook my walls, doors, windows. Family members in other parts of the country reported the same … Is this a new trend?

@javivf@adn.org.es Happy New Year! Let’s hope so. 😂

It’s that time again, I’ve just rotated my #twtxt feed!

Find last quarter’s twts at the feed, or see them on the web.

@lyse@lyse.isobeef.org It’s actually not nearly as half bad as I really thought it would be. Just having to eventually deal with the “lowering down” to machine code / ARM64 assembly in the end once you’ve verified the semantics in the VM.

@prologic@twtxt.net Not bad for a start, ey! Looking forward to see you going down these rabbit holes and opening one can of worms after the other. :‘-D Very, very impressive, hats off to you. :-)

@lyse@lyse.isobeef.org A “Hello World” binary is ~372KB in size. I currently have peephole optimization and deac code optimizations in play, and a few other performance related ones, but nothing too fancy. I have a test case that ensures fib(35) doesn’t regress too badly as I continue to evolve the language.

@prologic@twtxt.net Can you just make them optional? :-) But that of course complicates things.

@prologic@twtxt.net That’s impressive. How large are the resulting binaries? You don’t have any optimizations in place yet, do you?

@movq@www.uninformativ.de I hid in the workshop with earmuffs for the absolute worst part.

@javivf@adn.org.es Heck yeah, let’s do this! :-) Welcome to 2026.

@prologic@twtxt.net Not bad. 😃

@prologic@twtxt.net Anything by Charlotte de Witte. 😅 For example:

https://www.youtube.com/watch?v=QfkgSlmoe1I

@shinyoukai@neko.laidback.moe Happy New Year to you too! 🥳

@movq@www.uninformativ.de This is fuck’n great shit™ Where did you find this? 🤔 Got any more shit™ like this? 🙏

@dce@hashnix.club Happy New Year to you too! 🥳

@ionores@twtxt.net Very nice! 😊 Happy New Year to you too!

@lyse@lyse.isobeef.org Ooh, lovely! 🌇

I’m drowning the noise with this: https://www.youtube.com/watch?v=tgivYC2s6hs 😅

@shinyoukai@neko.laidback.moe We finally abandoned our GitLab. I publicly mirrored my code in the Mills Data Center a few days ago: https://git.mills.io/lyse/tt2

@movq@www.uninformativ.de Well, just a very limited subset thereof:

1. inline and multiline code blocks using single/double/triple backticks (but no code blocks with just indentation)
   
2. markdown links using using [text](url)
   
3. markdown media links using ![alt](url)
   

And that’s it. No bold, italics, lists, quotes, headlines, etc.

Just like mentions, plain URLs, markdown links and markdown media URLs are highlighted and available in the URLs View. They’re also colored differently, similarly to code segments.

I definitely should write some documentation and provide screenshots.

@lyse@lyse.isobeef.org You actually have a Markdown parser/renderer in there? Oh dear. I would have been (well, I am) way too lazy for that. 😅

@prologic@twtxt.net Happy New Year 🥳🎆

@lyse@lyse.isobeef.org Do you have your client’s code hosted anywhere?

@lyse@lyse.isobeef.org •́⁠ ⁠ ⁠‿⁠ ⁠,⁠•̀

@movq@www.uninformativ.de Because they’re just boxes. :-D

@movq@www.uninformativ.de Yeah, I see. Just crudely checked on my computer, with around 0.013 seconds, Python 2.7 seems a tad faster than Python 3.14’s 0.023 seconds in this little program.

The lazy imports sound not too bad, but I just skimmed over them. There are surprisingly many exceptions, but yeah, no way around them. :-)

@movq@www.uninformativ.de Mu (µ)’s startup latency appears to be ~10ms on my machine:

$ time ./bin/mu ./foo.mu 

real    0m0.011s
user    0m0.004s
sys     0m0.006s

@lyse@lyse.isobeef.org to be fair, that’s nothing, really

the logo used to be way larger and occupied the entire header, up to obfuscating the menu at my computer…

I do have a nitpick though, the logo isn’t transparent so it will look off in dark themes.

@lyse@lyse.isobeef.org

I assume you made the thing load quickly, didn’t you?

That’s the problem with Python. If you have a couple of files to import, it will take time.

I want this to be reasonably fast on my old Intel NUC from 2016 (Celeron N3050 @ 1.60GHz) and I already notice that the program startup takes about 95 ms (or 125 ms when there are no .pyc files yet). That’s still fine, but it shows that I’ll have to be careful and keep this thing very small …

Python 3.14 will bring lazy imports, maybe that can help in some cases.

I can track users’ feeds now

@prologic@twtxt.net I’d happily write API documentation for go.yarn.social/client

@movq@www.uninformativ.de the ‘writing a Yarn client’ thought goes all the way back to my ‘novaburst’ days in Yarn.social, but with the other pod apparently being gone, there’s no proof of it, except on everyone’s minds.

@movq@www.uninformativ.de That’s cool! I also like the name of your library. :-) I assume you made the thing load quickly, didn’t you?

@prologic@twtxt.net No, that’s Python/curses on Linux. 😅

@movq@www.uninformativ.de Is this on yout little toy OS? 🤔

Btw, @shinyoukai@neko.laidback.moe, that’s a super cool logo on your yarnd. I like it a lot!

It just doesn’t look aligned properly: Could be a yarnd issue, though, it might not expect a logo this large. Just wildguessing, no idea.

@shinyoukai@neko.laidback.moe Because you might not want to commit all changed files in a single commit. I very often make use of this and create several commits. In fact, I like to git add --patch to interactively select which parts of a file go in the next commit. This happens most likely when refactoring during a feature implementation or bug fix. I couldn’t live without that anymore. :-)

If you have a much more organized way of working where this does not come up, you can just git commit --all to include all changed files in the next commit without git adding them first. But new files still have to be git added manually once.

@shinyoukai@neko.laidback.moe Do we now need ad filters in twtxt clients, too? O_o I hope not! Personally, I cannot stand the “Sent with my crappy $phone/$app” e-mail footers.

But congrats on your client. :-)

@shinyoukai@neko.laidback.moe Yeah, they don’t truly support XDG. In fact, I looked in the Go stdlib source code to notice all the differences and shortcomings.

@lyse@lyse.isobeef.org You could always take a peek at the Go source

Posted from mikuru/0.0.3 @ NetBSD amd64

@lyse@lyse.isobeef.org the funny thing about it? There’s os.UserCacheDir(), it seems that the Go devs hasn’t acknowledged the $XDG_DATA_DIR yet

@shinyoukai@neko.laidback.moe Cool, I didn’t know about os.UserConfigDir() up until a few seconds ago! I always implemented that myself.

@movq@www.uninformativ.de Thanks! I’ll have a look at SnipMate. Currently, I’m (mis)using the abbreviation mechanism to expand a code snippet inplace, e.g.

autocmd FileType go inoreab <buffer> testfunc func Test(t *testing.T) {<CR>}<ESC>k0wwi

or this monstrosity:

autocmd FileType go inoreab <buffer> tabletest for _, tt := range []struct {<CR>    name string<CR><CR><BS>}{<CR>   {<CR>   name: "",<CR><BS>},<CR><BS>} {<CR>  t.Run(tt.name, func(t *testing.T) {<CR><CR>})<CR><BS>}<ESC>9ki<TAB>

But this of course has the disadvantage that I still have to remove the last space or tab to trigger the expansion by hand again. It’s a bit annoying, but better than typing it out by hand.

@movq@www.uninformativ.de Vim 9 (script) From Outer Space

@lyse@lyse.isobeef.org Well, I used SnipMate years ago (until 2012). IIRC, it’s more than just “insert a bit of text here”, it can also jump to the correct next location(s) and stuff like that. Don’t remember why I stopped using it.

Then I used nothing for a long time. Just before Christmas, I made my own plugin (… of course …), which does everything I need at the moment (and nothing more).

It can insert simple templates and then jump to the next location:

https://movq.de/v/67cdf7c827/sisni%2Dpython.mp4

And replace a string after insertion:

https://movq.de/v/67cdf7c827/sisni%2Dheader.mp4

(It’s not public (yet?) and it also uses vim9script, so I guess it wouldn’t work on your system.)

@prologic@twtxt.net Debugging this stuff on bare metal hardware (without an underlying OS) is a nightmare. 🤣

@movq@www.uninformativ.de Yeah. I had that in my Python implementation and was really missing that.

@movq@www.uninformativ.de I see. Yeah, all the Unicode stuff certainly doesn’t help here, that’s for sure.

Maybe “speedcurses” could be a name. Or just select any Palatinate curse. ;-)

@prologic@twtxt.net Oh yeah, I bet it is horrible to troubleshoot.

@lyse@lyse.isobeef.org That sounds useful. 🤔