↳ In-reply-to » I'm SO enjoying the new jenny --fetch-context 😁

@aelaraji@aelaraji.com @quark@ferengi.one Yep, I like it as well. 😅

There’s another situation that I’m not quite happy with.

Suppose there’s a twt like this:

2024-08-28T19:57:58Z    <a href="https://txt.sour.is/external?uri=https://foo.example.com/tw.txt&nick=person_a">@person_a<em>@foo.example.com</em></a> <a href="https://txt.sour.is/external?uri=gemini://a.b.c/tw.txt&nick=person_b">@person_b<em>@a.b.c</em></a> Hey! 👋

There’s no hash, so --fetch-context won’t do anything at the moment.

Option A: jenny asks interactively to fetch those feeds once.

No thread hash found
Do you want to fetch the entire feed https://foo.example.com/tw.txt? [Y/n] y
Do you want to fetch the entire feed gemini://a.b.c/tw.txt? [Y/n] n

(Bonus points for skipping feeds that you already follow.)

Option B: There could be an external/third-party tool that scans a twt for all mentions and asks the user if they want to follow them (permanently). Why an external tool? The thing is, the follow file has been completely user-managed so far and I kind of want to keep it that way. And if this is an external tool, then users can do all kinds of fancy stuff, like using fzf or whatever. Or it could allow the user to preview the feed before following it. I don’t want to have stuff like that in the core program, it depends too much on users’ preferences.

To “implement” option B, I’d only add some hints to the docs, maybe an example.

I think I’m leaning towards option B at the moment. 🤔