The next jenny release will (probably) stop supporting the old “Hash Tag Extension”, which was deprecated at the end of 2022. It was once used for threading and looked like this:

<a href="https://twtxt.net/search?tag=tsvhqdq">#tsvhqdq</a>

I don’t see them being used in the wild anymore. But if you happen to fetch really old feeds (or some archived feeds), things might break a little.

@aelaraji@aelaraji.com lol 😅🙈

I think I’m not going to query Yarn pods for the moment. Let’s first see how often I’d actually need that. 🤔

@quark@ferengi.one Yay 🥳

@lyse@lyse.isobeef.org That is one crazy looking mushroom. 😳 How about tasting it? 🤪

I’m so glad the temperatures were down a bit. Went on a long walk as well, first time in weeks. And there were so few cars yesterday! It was surprisingly quiet.

There was a garbage bag incident last night and I had to clean up the kitchen for two hours. 😂 Now I’m sore as fuck. Good thing I have a day off today, huh? 🤪

@falsifian@www.falsifian.org @bender@twtxt.net I pushed an alternative implementation to the fetch-context branch. This integrates the whole thing into mutt/jenny.

You will want to configure a new mutt hotkey, similar to the “reply” hotkey:

macro index,pager <esc>C "\
<enter-command> set my_pipe_decode=\$pipe_decode nopipe_decode<Enter>\
<pipe-message> jenny -c<Enter>\
<enter-command> set pipe_decode=\$my_pipe_decode; unset my_pipe_decode<Enter>" \
"Try to fetch context of current twt, like a missing root twt"

This pipes the mail to jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If there’s no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)

The whole thing looks like this:

https://movq.de/v/0d0e76a180/jenny.mp4

In other words, when there’s a missing root twt, you press a hotkey to fetch it, done.

I think I like this version better. 🤔

(This needs a lot of testing. 😆)

@prologic@twtxt.net Yeah, I need to clean this up in jenny. It still supports a ton of old formats that aren’t used anymore at all. 🧟

@bender@twtxt.net Yeah, I switched to OpenBSD a couple of years ago when sysupgrade(8) became available. I like it a lot, requires very little maintenance. 👌

@bender@twtxt.net I am considering it. 😅 (I might end up being too lazy to set any of this up. 🤪)

Thought: If the invocation including --only-twt-hash fails to find that twt, it could ask a couple of Yarn instances for it (if configured).

(All this needs polishing.)

Honestly, the only thing I want to do on Mastodon is follow the #retrocomputing hashtag and sometimes post under that hashtag. That’s it. 😂

There was an outage of the Mastodon server I use this morning. A good reminder that this is a service that someone else hosts (and I don’t even pay for it). Could be gone tomorrow.

Now that I’ve got a server to spare (the Matrix one is gone), I might look into hosting a snac instance. 🤔

RIP, Matrix server. 🪦

$ doas rcctl stop synapse
synapse(ok)

@prologic@twtxt.net I would be so damned proud of that. 💪

@falsifian@www.falsifian.org I’ve pushed a draft into the git repo.

You can now do a “oneshot fetch” for a URL:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest

This fetches the entire feed, which might be too much. So there’s also this, which only fetches a single twt:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest --only-twt-hash r6rbinq

Let me know what you think. 🤔

@quark@ferengi.one It’s really only about the hash, isn’t it? 🤔 The user mention (@<quark …) should still be visible in full?

@prologic@twtxt.net Ok, wow, yes, I really only do want that one single missing twt. The slashdot/hackernews feeds are huge. 🥴

@prologic@twtxt.net Where can I find Yarn’s API docs for that endpoint? 🤔 (If there is any. 😅)

@mckinley@twtxt.net That’s the file sharing stuff, right? I couldn’t care less about that. Frankly, I think it’s a shame that Usenet turned into that. 🫤

@prologic@twtxt.net I’m so sorry, I just can’t muster up the social energy for that. 😂 I’m sitting in video calls all week long and it’s … just … so … exhausting. I can’t, sorry. 😅

@lyse@lyse.isobeef.org Oh, has this changed? Last time I checked, there was quite a bit of stuff going on. 😅

(The jenny code is getting a bit long and convoluted. I feel the need to refactor this quite a bit. That’s why I’m not implementing any of this right away.)

@lyse@lyse.isobeef.org Ah, actually reading the spec helps. 🤦

(Btw, I deliberately don’t join #yarn.social all the time. If I did, I suspect that a couple of development discussions would move over from twtxt to IRC. 🤪 Okay, and I often prefer slow asynchronous communication.)

Btw, it’s kind of annoying that we have two syntax options for this. 😆

It can be

(<a href="https://we.loveprivacy.club/search?tag=hash">#hash</a>) @<nick url>

or

@<nick url> (<a href="https://we.loveprivacy.club/search?tag=hash">#hash</a>)

The latter is from an earlier convention/spec. How about deprecating or even removing this?

https://dev.twtxt.net/doc/twtsubjectextension.html

@prologic@twtxt.net @falsifian@www.falsifian.org This just popped up in my head: How about adding a “fetch context” feature? Point jenny to some mail file that contains a twt (or pipe it to stdin) and it will try to auto-discover and fetch all related things. Like, if it sees something like @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process could include explicitly querying some user-configurable Yarn pods as well. 🤔

It won’t always work. There’s no guarantee that tkjafka will be present in the given URL.

Hmm. 🤔

@bender@twtxt.net No idea, but I haven’t used GNOME since 2008. 😅 I, too, like Xfce much better. Xfce (and KDE to some degree) look and feel rather “traditional”, though. You get a standard taskbar and that’s it. Maybe that’s too oldfashioned? 🤷 I’m just speculating.

You might have seen me popping up on IRC. This is how it looks:

https://movq.de/v/3a4f9833f3/

That’s EZirc from the 1990ies. (It says it needs Warp 4, but runs fine on Warp 3.)

Lots of this old stuff still works (technically), but as @lyse@lyse.isobeef.org said: A lot of it really is dead. There’s not much going on anymore in Usenet.

@aelaraji@aelaraji.com What terminal are you using? 🤔

@lyse@lyse.isobeef.org Stell dir vor, es wären NaN Grad! 😱

This has become quite a large thread. 😅

https://movq.de/v/5c51be2cd3/s.png

@quark@ferengi.one I once decided against that, didn’t I? 🤔 I don’t remember why anymore. I’ll think about it. 🤔

@bender@twtxt.net Yes, I see the same. Right-to-left Unicode breaks mutt (and apparently neomutt). It was once reported as an issue:

https://gitlab.com/muttmua/mutt/-/issues/131

They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?

@falsifian@www.falsifian.org Ah, I see. 🤔 Maybe I’ll add that. To be honest, I have the same “problem” regarding the slashdot feed. 😅 It’s mostly stuff that I’m not interested in – but from time to time someone replies and then I want to see what it’s about.

@falsifian@www.falsifian.org You mean fetching the feed temporarily and then discarding all its twts again? 🤔 I don’t think there’s an easy way to do that, other than filtering in your mail client, yeah. 🤔

@aelaraji@aelaraji.com That’s good to know. 🤔 Luckily, the phone wasn’t full of 3rd party stuff. There were so few of them actually, that I didn’t really bother looking. That’s why I only found out recently about that Meta stuff.

The soundtrack of World of Goo 2 is amazing. It’s quite epic and melancholic at times.

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

It doesn’t fit the “cuteness” of the game at all – but there are a lot of contradictions in that game anyway, it’s an important aspect.

@lyse@lyse.isobeef.org 4.75 seconds, are you kidding me? 🤯

@prologic@twtxt.net Yep. ✅

@xuu@txt.sour.is Ahhhh, ohhhh, ouch. 🫤

@lyse@lyse.isobeef.org Hmmm, the user agents indicate two different pods. 🤔 Most of them are twtxt.net, though, only one user is something else. 🤔

@lyse@lyse.isobeef.org Yeah, indeed, but still. 😂

@mckinley@mckinley.cc Uhhh, I bet the support people at Lenovo love this. (Assuming it’s accurate.)

@lyse@lyse.isobeef.org Ahh, good old Senfglastradition. Looks delicious. 👍

Speaking of web server logs: Unless someone posts one of my blog posts on HackerNews (I never do that myself, don’t even have an account), my twtxt.txt file is always the most requested resource. 😂 It easily gets several thousand hits, way more than the blog’s Atom feed. 😂

@prologic@twtxt.net I didn’t want to hijack @bender@twtxt.net’s thread: There’s two things that feel a bit unexpected regarding the requests of 159.196.9.199 in my logs:

1. It doesn’t respect HTTP 301 and instead asks for the same URL every time, thus needing a redirect.
   
2. Is this one Yarn pod or several? I’m seeing multiple requests from this same IP with different user agents. It’s not a lot, just about 5 different ones (every couple of minutes), but I thought that Yarn only issued one such request? 🤔 You know, when several users follow the same feed, Yarn would only fetch that feed once?

@xuu@txt.sour.is I don’t even have a WhatsApp password, it never asked me? 🤔

@prologic@twtxt.net Maybe one day I’ll have the motivation to learn enough about JPEG, so I can understand the reason behind this. But not today. 😅

I run it in a Work profile on my GrapheneOS phone that I can switch off at any time

So this kind of works in stock Android, too. You have to reboot after switching back to the main profile, then the second profile won’t get loaded at all.

(I bet that this stops working in the future. It feels like the second profile doesn’t get loaded as a means to save CPU power. Once those smartphones get even more powerful, there’s no need to do that anymore …)