# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 15
# self = https://watcher.sour.is/conv/q2ow4pq
aelaraji
aelaraji.com
View Thread
I'm SO enjoying the new jenny --fetch-context šŸ˜
aelaraji
aelaraji.com
View Thread
I'm SO enjoying the new jenny --fetch-context šŸ˜
quark
ferengi.one
View Thread
@aelaraji so lovely, ain't it? A simple keystroke, and your "mystery" is solved. :-)
quark
ferengi.one
View Thread
@aelaraji so lovely, ain't it? A simple keystroke, and your "mystery" is solved. :-)
movq
www.uninformativ.de
View Thread
@aelaraji @quark 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 @person_a @person_b 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. šŸ¤”
movq
www.uninformativ.de
View Thread
@aelaraji @quark 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 @person_a @person_b 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. šŸ¤”
movq
www.uninformativ.de
View Thread
@aelaraji @quark 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 @person_a @person_b 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. šŸ¤”
movq
www.uninformativ.de
View Thread
@aelaraji @quark 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 @person_a @person_b 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. šŸ¤”
movq
www.uninformativ.de
View Thread
@aelaraji @quark 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 @person_a @person_b 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? \n y
Do you want to fetch the entire feed gemini://a.b.c/tw.txt? \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. šŸ¤”
quark
ferengi.one
View Thread
@movq I think you are worrying about a non-issue. I see nothing to do on your example twt, because there is no context. Furthermore, if I wanted to follow the feed, everything I need is already on that twt example. :-)
quark
ferengi.one
View Thread
@movq I think you are worrying about a non-issue. I see nothing to do on your example twt, because there is no context. Furthermore, if I wanted to follow the feed, everything I need is already on that twt example. :-)
movq
www.uninformativ.de
View Thread
@quark

> I think you are worrying about a non-issue.

Thatā€™s what I do best. šŸ˜
movq
www.uninformativ.de
View Thread
@quark

> I think you are worrying about a non-issue.

Thatā€™s what I do best. šŸ˜
movq
www.uninformativ.de
View Thread
@quark

> I think you are worrying about a non-issue.

Thatā€™s what I do best. šŸ˜
movq
www.uninformativ.de
View Thread
@quark

> I think you are worrying about a non-issue.

Thatā€™s what I do best. šŸ˜