Block / Report User
If this user/feed is violating this Pod's (VltraPlus) 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!)
Recent twts from movq
@email@example.com (#payoedq) Neato. It’s so hard to get the lighting right when taking pictures of birds. 😢 They always end up too dark. Or the background is way too bright. Guess I’d need HDR. 🥴
Every time a package has “pandoc” as a build dependency, I’m like: “Holy mother of cows, did I just install the entire haskell ecosystem? 🤯”
(#lecztrq) … aaaaaand I have a buyer. 🥳
@firstname.lastname@example.org (#boco3fq) Yes, shutters and the windows themselves rattle quite a lot, also maybe other kinds of thin-ish structures. It gets very loud here. (I live in an old tower building.)
@email@example.com (#ifphkga) Nothing wrong with asking. 😊 I think I might actually implement more aggressive subject “compression”. We should be able to remove those subject hashtags, they’re just noise. 🤔
(#ifphkga) Just for some more background: I wrote a StatusNet client years ago which worked very similar to jenny, with mutt as a frontend. That program did indeed truncate the subject lines – but it turned out to be a bit annoying in practice. It was always cut off a little bit too early. 🤣 So I eventually removed truncation altogether.
Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager. I often do that. On the other hand, if they’re truncated, then the question is: Where do you truncate them? 72, 100, 140, 200? Some people have wide terminals, others don’t. So I decided: Okay, let’s have mutt do it. 🙃 (Or you could make it a user option, but I like to avoid those, because you quickly end up with a ton of options and things get very hard to test, because I myself don’t use most of them.)
The subject lines are already “compressed”, btw. For example, a full mention like “@” gets compressed to just “@foo”. Maybe it’d be possible to expand on that idea, like also strip the hashtags of conversation grouping. 🤔
@firstname.lastname@example.org (#5jejozq) No, of course not. 😊 I still take pretty much the same precautions as before (which is very easy for me to do, I can work from home 100% and all that; I don’t mind the masks and the distancing). But all those precautions don’t protect you, you can still catch the disease – so I was worried all the time (while doing stuff like buying groceries or using an elevator). And now that I’m vaxxed, this constant worry is gone. 👌
(I don’t know if I can get my point across. Damn language barrier.)
(#5jejozq) Since I got vaccinated, I stopped worrying about this whole corona business. Yes, I can (and probably will) still get it; yes, I can still spread it; but my life is no longer in immediate danger. That’s a big win, eh?
@email@example.com (#ck2oria) I was thinking: “If we just put these two fields at the start of the twtxt message (like we do now with mentions and subject hash), it would be backwards-compatible as well. 🤔” But then I remembered: If people write twts the old way (without the two new fields), how do we reply to them? They don’t have an ID. So we’d probably need the current hashing method as a fallback – and then we wouldn’t have made a lot of progress compared to the current version. 🤔
Our devs are pushing hard for k8s. They might be happy with another solution, but they know k8s very well know and it works well (for them – just not for me as a sysadmin), so there’s very little motivation to investigate other tools …
(#lecztrq) I think it’s time to finally sell this damn thing, so I won’t be tempted again …
It’s unfortunate that editing twts breaks threading. Are there alternatives? The only thing I can think of is adding explicit IDs to all twts (like
In-Reply-To). I think @firstname.lastname@example.org already mentioned/proposed this a while ago. The downside of this is that it makes twt feeds even more noisy for users who use traditional clients (or no client at all). 🤔
@email@example.com (#3xfftqq) Ahhh, ohhh. That explains it. I was confused by the fact that this URL exists: https://f.adi.onl/conv/egdmpoa – so I was assuming that this is the correct twt/hash. Apparently, it’s just the original version of his twt which is still in his cache?
Hmm, feels like there’s a bug lurking somewhere. How does @firstname.lastname@example.org’s twt (the one about the girl and the cricket) end up with hash #egdmpoa? 🤔 https://f.adi.onl/conv/egdmpoa I get #tkdjrmq instead. 🤔 I uploaded the payload that I’m hashing here: https://movq.de/v/fe54d02fe3/hash-payload.txt cc @email@example.com @firstname.lastname@example.org
@email@example.com (#3kd355q) Yeah, I’m still seeing large amounts of traffic when jenny runs, so I guess it’s not yet fixed. But I didn’t mean to shame you. 😁 At least on my end, it’s not really an issue. 👌
@firstname.lastname@example.org (#3kd355q) I run the cron job every 15 minutes. Running it every minute imposes quite a bit of load on the feeds of other people. While jenny requests everything with the
if-modified-since header set, not all servers honor that header. Most of all, yarn does not: https://git.mills.io/yarnsocial/yarn/issues/430
Ist mir auch eben erst klar geworden: Die Uhu-Webcam (hab’ ich vor einiger Zeit mal verlinkt) war im … Ahrtal. Und da war doch was mit Unwetterkatastrophe. Ohweh. https://uhu.webcam.pixtura.de/das-ahrtal-ist-nicht-mehr-so-wie-wir-es-kannten/
I love how my Android phone unironically tells me: “Please restart your device. Your device has not been restarted for 28 days. We e …” (Yes, it ends with “we e …” and I have no idea how to show the full message.) Really? So they haven given up and don’t even try anymore to make software that, well, works?
@email@example.com (#wkjlotq) Fixing old entries is tricky and I wouldn’t do it. If you change something in an old twt, it will change its hash sum – and thus, it will break threading if someone has replied to your old twt or otherweise referenced it. 😵
(#wkjlotq) Should be fixed on jenny’s
main now. 🥳
Right now, jenny sometimes has to make up those URLs, because there simply is no cross-platform way of creating them. URLs like
https://twtxt.net/search?tag=gjt7pqa only exist on yarn.social, but there’s no equivalent on my web site … so, yeah, that’s probably where those bad links are coming from.
I guess we should update https://dev.twtxt.net/doc/twtsubjectextension.html accordingly. (Or maybe there’s a PR already, haven’t checked.)
Interesting idea. 🤔
This is a key factor:
Such an upcycling will be possible with the manufacturers obligation to publish a device’s underlying source code under a Free Software licence at the end of support for any software necessary to run or modify the initial functioning of the device.
A device’s source code isn’t worth anything if it depends on, say, a proprietary compiler.
A similar loop hole for manufacturers: They could add pointless complexity to their build system. “Sure, here’s the source code for iOS. Have fun building it! You only need to perform these 13 million steps: …”
Or design the build system in such a way that it’s impossible for most people to perform because of their hardware: Just put it enough effort for the build to require 128 GB of RAM and you’re good.
Alright, I think I like it. I pushed the changes. FYI @firstname.lastname@example.org
That’s enough changes for now. I’ll let things settle for a while, fix bugs (if we’re finding any), maybe add some more tests, and then go for a new release. 🥳