Went to the barber shop today. Got a nice talk and, surprisingly, my first “contract” to 3D print something. So, I spent the last hour reading about QR codes, versions and patterns and rescue data to embed an image in the centre of the code. Then it took me some time to convert it from a PNG to an SVG to an STL, so I can put it into Tinkercad to design the new plate. I now have a baseplate, a backplate with the QRCode & two smaller plates which I have to glue into placeholders on the backplate.

Our Minister of Defense had a good start and is seemingly more competent than the predecessor. I like him. Now, even more, after hearing which ringtone he has https://www.youtube.com/watch?v=HPiw1UWI8lE

@darch@neotxt.dk don’t we already hav RSS feeds to do that?

@prologic@twtxt.net This is undoubtedly why I went away from Hugo, Pelican, WordPress and co and wrote a small, for my needs, blog software. I also learned a lot about the Flask Framework, which I can now use to enhance our apps at work and make my boss happy. I would have chosen Go, but it was not the chosen product at work, so, sorry. KISS principle. Like almost everything in the *nix world. A small tool for a small thing. Chain it with others if you need more.

The pull-only model seems to work nice. You have multiple social networks, each one with its own unique audience. Pull things from others into your when you want.

From my point of view, I think twtxt and yarn are good as they are. The protocol s nice, easy and clean afaik. The surrounding software, makes it what it is today. Multiple clients, each having it pros and cons. The only thing I am missing is some sort of media manager for my uploaded images to yarn.social. But that is specific to this implementation and has nothing to do with the twtx protocol.

Norway, near Narvik on the way to the Loen Skylift.