movq

uninformativ.de

No description provided.

Recent twts from movq

Huh, just noticed that my client currently holds 51839 twts (28 MB). Way more than I expected. 😅 (I’m not following any bots.)

⤋ Read More
In-reply-to » I was about to throw away some “Gelbe Seiten”, then I remembered this twt. It kind of … works … a bit … nah, it doesn’t.

@lyse@lyse.isobeef.org That’s right. 🤔 Those sheets are not exactly A4. And they’re super thin, very little stability – that’s the main problem, I guess.

⤋ Read More
In-reply-to » It was a cold and misty November day. Just like November is supposed to be. It rained in the forest a little bit, but on the way back the sun came out for a short time. And then it turned very cloudy and dull for the rest of the day. Mixed with rain time after time. Looking outside now, it's very dark and foggy again. Closing the shutters at 16:30.

@lyse@lyse.isobeef.org Sneaky edit. 😏 I had to look up if it could be real. 😅

⤋ Read More
In-reply-to » Paper airplane instructions. Some things never get boring. For example: making paper airplanes. The "Fold'NFly" database offers a number of simple and well-illustrated instructions on how to build true record-breaking fighters yourself.

I was about to throw away some “Gelbe Seiten”, then I remembered this twt. It kind of … works … a bit … nah, it doesn’t.

Image

⤋ Read More
In-reply-to » I felt this weird last time when I tried to seriously use Plan 9. I don't even know even how to reply to someone as it doesn't seem like the original twtxt Python client supports the topic in brackets. But I managed Gopher, Z80 assembly, and paddleboarding, I will manage twtxt as well.

@logout@i-logout.cz (I’m not even sure if you can properly read my multiline reply with the old original client. Hmm.)

⤋ Read More
In-reply-to » I felt this weird last time when I tried to seriously use Plan 9. I don't even know even how to reply to someone as it doesn't seem like the original twtxt Python client supports the topic in brackets. But I managed Gopher, Z80 assembly, and paddleboarding, I will manage twtxt as well.

@logout@i-logout.cz Yeah, none of the original twtxt clients support the newer stuff that was developed in the context of Yarn.social. That topic in brackets, in particular, is specified in these two documents:

(Which reminds me, @lyse@lyse.isobeef.org and @prologic@twtxt.net, that the latter is a bit outdated. We don’t use the URL part anymore, just the hash.)

On https://yarn.social/, three clients are listed:

jenny is my own client, so, to be honest, I never gave the other ones a try. Nevertheless, I presume that they all support the aforementioned extensions.

There certainly is a lack of clients, that’s for sure. We could use more of them. :-)

⤋ Read More
In-reply-to » I quit Newsboat three days ago without noticing. Well, now that I think about it, I remember again. I was compiling it from source to test my latest fix. So this evening I got plenty of new articles after starting it again.

@lyse@lyse.isobeef.org Oh, it was by accident. At first, I thought you found something better. 😅

⤋ Read More
In-reply-to » Paper airplane instructions. Some things never get boring. For example: making paper airplanes. The "Fold'NFly" database offers a number of simple and well-illustrated instructions on how to build true record-breaking fighters yourself.

@carsten@yarn.zn80.net That’s neat. Instead of throwing away all the useless snail mail spam, I’ll make paper planes now. 😁

⤋ Read More
In-reply-to » That's pretty cool. Earth now weighs six ronnagrams. New metric prefixes voted in France: https://phys.org/news/2022-11-earth-ronnagrams-metric-prefixes-voted.html

@lyse@lyse.isobeef.org Huh, that’s interesting! Also didn’t know that Yotta and Zetta only existed since 1991. I leared “Milli, Micro, Nano, Pico, Femto, Atto” at a young age from an old book. But not “Zepto, Yokto”. Never thought about it, now I know why! 😅

⤋ Read More

Chris’ Wiki: Monitoring if our wireless network is actually working in locations

Oh dear. Wifi monitoring is really hard. We have the same problem. We tried to do what he proposes (setting up Raspberry Pis as “wifi probes”, setting up entire laptops, you name it, …), but we hardly gained any insights.

The nasty thing about wifi is that it’s not enough to know whether a device is connected or not. Yes, sure, if all your wifi probes in one area suddenly disconnect, then you have a problem. But how do you test for roaming? How do you test for client behaviour, like “wifi chip $a behaves ever so slightly different than chip $b”? How many probes do you deploy, one per room? That adds up quickly.

At the end of the day, many of our users are dissatisfied with our wifi – and we admins can’t reproduce their problems, because we don’t use the exact same configuration that they do. 😢

(We recently switched to offering Ethernet by default again. That’s much more convenient these days, because many laptops have USB-C: Users connect one cable and get everything – power, monitor, Ethernet, USB hub. Not all workplaces have such a setup, though.)

⤋ Read More
In-reply-to » @lyse Looks like I got something new to play with: gopher://uninformativ.de/0/phlog/2022-11/2022-11-17--gps-logger.txt (tl;dr: "GPS Logger" does the trick for me, it creates GPX files 🥳)

@prologic@twtxt.net Do I understand correctly that Yarn uses https://github.com/gomarkdown/markdown for rendering twts in the web UI? I’m asking because it irks me that Gopher URLs aren’t converted into links. 😅 There’s probably nothing that Yarn can do because this is done here, right? https://github.com/gomarkdown/markdown/blob/master/parser/parser.go#L724

⤋ Read More
In-reply-to » Comparatively speaking extremely boring. Not many leaves left.

@rsdoiel@twtxt.net My main concern would be uploading GPS data to some cloud service. The big question is: Does my Android phone collect such data in the background and then upload it to Google? I don’t know. It’s annoying that I have to think about this. 🫤 For the moment, I’m just ignoring it. (A dedicated device would not have this problem.) Also, use more Gopher! 😅

@lyse@lyse.isobeef.org I had to think twice what “Bauchaufzüge” means. :-) Nice visualization. “Strecke 2D” vs. “Strecke 3D” is interesting - didn’t expect it to make that much of a difference for such a short path. 🤔 Also, you might be right, basic navigation probably works with the OSM app. The only thing is, it greets me with “unpaid version, 5 downloads” remaining, so, dunno how long it’ll remain usable.

⤋ Read More
In-reply-to » @lyse ``

@prologic@twtxt.net Hm, I think there’s some edit confusion going on.

When my client fetched @xuu@txt.sour.is’s twt, it read like this (I’m posting screenshots here to avoid something parsing this as markdown):

Image

The hash I got for this was v6kvlma. That’s what’s still stored in my client.

Note the wrong mention. xuu must have edited it, because it now reads like this:

Image

And I get dmypf5q for that.

This latter hash also exists on twtxt.net, but it’s not the one that @lyse@lyse.isobeef.org replied to: https://twtxt.net/conv/dmypf5q

lyse replied to u4bs34q (https://twtxt.net/conv/u4bs34q), but I can’t find out what the original raw content of that twt was. Can someone show me that raw twt line? Then I can check which hash I get. 🙂

The simplest explanation is that xuu edited several times and lyse replied to something other than the current/final twt.

(For that original twt from your test cases (the one the say “Great, last system update broke something …”), I get bd3yzvq, just like your test suite.)

⤋ Read More
In-reply-to » Missed the Artemis launch due to a big outage at work. 🫤

@lyse@lyse.isobeef.org Nice logo indeed. 😁 It was a network outage. Well, the root cause was not in our network, but we had to find ways to avoid the broken path. It would have been a trivial task, if we didn’t need said broken path to reconfigure some routers … Chicken and egg. In the end, someone went into a server room and we instructed him via video chat on what to do. In situations like these, it’s really bad if the more experienced network guys all work from home. 🥴

(Please don’t ask why we have such a single point of failure in the first place. It’s a sad story. 🙄)

@carsten@yarn.zn80.net Rocket goes whoosh! 😅 I did rewatch it by now. There’s nothing like following it live, though.

⤋ Read More
In-reply-to » I'm stupidly angry because a stupid race...

@eaplmx@twtxt.net Bah. 🫤 I was hoping for some legitimate reason like “if we try to do that, the guy behind us (Ocon?) might be able to overtake as well”. Oh, well. 🫤

(F1 has become pretty expensive here in Germany, so I don’t follow it closely anymore …)

⤋ Read More
In-reply-to » Meddling with Wayland (Sway) again.

Spent the better part of the day trying to get urgency hints / terminal bells to work on Wayland. Digging through GTK docs, reading GTK/GDK source code. No success. It’s all still very young.

https://www.uninformativ.de/git/xiate/commit/0d8b2f924d8f8e6c8786e940835d346a78d72f3e.html

It works fine with foot, though. Maybe I should just throw away my work and use that …

⤋ Read More
In-reply-to » Giving newsboat/newsbeuter another try. 🤔 After a break of ~10 years.

Hmm, turns out, I really need/want an e-mail-based workflow after all. Newsboat isn’t bad, e-mail just works better for me.

So, instead of patching newsboat, I polished my “feed-to-mail” script, added support for Gopher and Gemini, and finally made it public:

https://uninformativ.de/git/feednotify

I’ll let it mature for another week or two and then issue a release.

Probably not useful to anybody, but whatever. 🥴

⤋ Read More
In-reply-to » Meddling with Wayland (Sway) again.

You have to appreciate Drew DeVault’s work, though. The entire Sway team, actually. If it wasn’t for them and their persistence, the situation would probably be much worse, because I have a feeling that nobody would consider the use cases of lightweight desktops at all. And, of course, wlroots wouldn’t exist.

⤋ Read More
In-reply-to » Meddling with Wayland (Sway) again.

As for redshift, there is this protocol extension:

https://wayland.app/protocols/wlr-gamma-control-unstable-v1

“Protocol extension” sounds complex, but it basically just means: “Here’s an XML file that describes our thing.” It’s much more formalized than specs like EWMH, which are mostly written in prose. If a compositor decides to implement it, it knows exactly which functions to implement, which arguments they get, and so on.

This is a generic extension that allows you to set a gamma table. So, on Sway, you can use this:

https://github.com/minus7/redshift/tree/wayland

However, scroll down to this table:

https://wayland.app/protocols/wlr-gamma-control-unstable-v1#compositor-support

This only works on Sway, not GNOME nor KDE.

For GNOME, there is this other fork:

https://github.com/prahal/redshift/tree/add-gnomerr-method-v0.2

It’s using “GnomeRR”, which appears to be part of “libgnome-desktop”. I couldn’t find official docs for this library (I didn’t search for long, though). Here’s the code: https://gitlab.gnome.org/GNOME/gnome-desktop/-/tree/master/libgnome-desktop They’re basically doing their own thing, outside of Wayland protocol specs (or I misunderstood). It probably makes sense from their point of view.

⤋ Read More