# 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 4
# self = https://watcher.sour.is/conv/3gfgmma
@quark You mean the one on this line, right at the start? I don’t think so, actually. Thinking about it, I’m not overly happy with removing it from the subject line, either (but it’s probably a bit better than having it in there).

People are often replying to feeds that I don’t follow. In mutt’s overview, this shows up as like this:



Ripped out of context. I can *guess* that this is a reply, because it’s so out of context, but it’s still weird. To make sure, I’ll have to open the twt:



Aha, now there it is, it’s a reply. Okay.

If the reply hash was removed from the body as well, I’d have to perform yet another step (toggle mutt’s weed option to show the mail headers) in order to find out if that’s really a reply or not. That’s a bit too convoluted, imho.
@quark You mean the one on this line, right at the start? I don’t think so, actually. Thinking about it, I’m not overly happy with removing it from the subject line, either (but it’s probably a bit better than having it in there).

People are often replying to feeds that I don’t follow. In mutt’s overview, this shows up as like this:



Ripped out of context. I can *guess* that this is a reply, because it’s so out of context, but it’s still weird. To make sure, I’ll have to open the twt:



Aha, now there it is, it’s a reply. Okay.

If the reply hash was removed from the body as well, I’d have to perform yet another step (toggle mutt’s weed option to show the mail headers) in order to find out if that’s really a reply or not. That’s a bit too convoluted, imho.
@quark You mean the one on this line, right at the start? I don’t think so, actually. Thinking about it, I’m not overly happy with removing it from the subject line, either (but it’s probably a bit better than having it in there).

People are often replying to feeds that I don’t follow. In mutt’s overview, this shows up as like this:



Ripped out of context. I can *guess* that this is a reply, because it’s so out of context, but it’s still weird. To make sure, I’ll have to open the twt:



Aha, now there it is, it’s a reply. Okay.

If the reply hash was removed from the body as well, I’d have to perform yet another step (toggle mutt’s weed option to show the mail headers) in order to find out if that’s really a reply or not. That’s a bit too convoluted, imho.
@movq, well, yes, that has always been the case. Not just on jenny, but on Yarn. I can't follow everything, and everyone. To see whether is a reply, a simple h on mutt shows the headers, and there you have it. That is not too convoluted, is it? I mean, if you really want to know--but why?--it is a simple key press. If I don't see a context on something as obvious as the example you used, it is simply a reply to someone I don't follow, and pretty much ignore. End of story. 😂