# 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 19
# self = https://watcher.sour.is/conv/j43fuia
Last change before the next jenny release (and then I’ll go for Feed Archival): Finally remove the conversation tag from Subject: lines https://www.uninformativ.de/git/jenny/commit/faa3046c007e48f279fc0bb1beb4806a41947da8.html
Last change before the next jenny release (and then I’ll go for Feed Archival): Finally remove the conversation tag from Subject: lines https://www.uninformativ.de/git/jenny/commit/faa3046c007e48f279fc0bb1beb4806a41947da8.html
Last change before the next jenny release (and then I’ll go for Feed Archival): Finally remove the conversation tag from Subject: lines https://www.uninformativ.de/git/jenny/commit/faa3046c007e48f279fc0bb1beb4806a41947da8.html
@movq woot! Yes! 🥳🎉
@movq
Super awesome! Running the latest now.
Funny, I’m so used to seeing these tags, it’s almost a bit confusing now that they’re “missing”. 🤣
Funny, I’m so used to seeing these tags, it’s almost a bit confusing now that they’re “missing”. 🤣
Funny, I’m so used to seeing these tags, it’s almost a bit confusing now that they’re “missing”. 🤣
@movq
> Funny, I’m so used to seeing these tags, it’s almost a bit confusing now that they’re “missing”.

They are all gone from *yarnd* as well (even from the twt body!). So much cleaner!
On this regard, why don't you do the same on *jenny*? The subject is the message-id, so, why not?
@fastidious Yeah, using the app, I didn't even notice that. 🙃
@fastidious Yeah, I might re-think that in the future. 🤔 It’s so much nicer to read without all that markup.

I kept the original twt in the mail body, because I wanted to actually see that original twt. (And in early versions, this was very important, so I could manually copy conversation hash tags and/or mentions. 😅) I don’t just want to see “@lyse”, I want to see the URL as well. On the other hand, I don’t need this *all the time*. Hm.

Yeah, dunno. I’m not 100% happy with this either. I’ll put it on the TODO list. 👌
@fastidious Yeah, I might re-think that in the future. 🤔 It’s so much nicer to read without all that markup.

I kept the original twt in the mail body, because I wanted to actually see that original twt. (And in early versions, this was very important, so I could manually copy conversation hash tags and/or mentions. 😅) I don’t just want to see “@lyse”, I want to see the URL as well. On the other hand, I don’t need this *all the time*. Hm.

Yeah, dunno. I’m not 100% happy with this either. I’ll put it on the TODO list. 👌
@fastidious Yeah, I might re-think that in the future. 🤔 It’s so much nicer to read without all that markup.

I kept the original twt in the mail body, because I wanted to actually see that original twt. (And in early versions, this was very important, so I could manually copy conversation hash tags and/or mentions. 😅) I don’t just want to see “@lyse”, I want to see the URL as well. On the other hand, I don’t need this *all the time*. Hm.

Yeah, dunno. I’m not 100% happy with this either. I’ll put it on the TODO list. 👌
@thecanine yeah, no app here. I either use a native---or as close as possible as native---app, or I use the web client (or the CLI). Not going to run a Dart VM on iOS just to use a second hand app. 😬
@movq
> I don’t just want to see “@lyse”, I want to see the URL as well

I agree on that. I was only referring to the hash. Having it on body is superfluous, and just adds unneeded noise.

I truly love where *jenny* is headed!
Actually, I was mistaken when I wrote:

> The subject is the message-id, so, why not?

The subject (hash, in case my naming is wrong) is in the in-reply-to header.
@movq yeah one thing I wanted to say is that I don’t think it’s a good idea to modify the underlying data source, i.e. yhe feed itself but rather just to layer a presentation over the top 👌 At least in yarnd this is how things are done. even the cache is just a presentation intermediary 😆
@movq yeah one thing I wanted to say is that I don’t think it’s a good idea to modify the underlying data source, i.e. yhe feed itself but rather just to layer a presentation over the top 👌 At least in yarnd this is how things are done. even the cache is just a presentation intermediary 😆