# 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 6
# self = https://watcher.sour.is/conv/lnrgahq
thanks @prologic!
@bender the idea of the RFC was to reach an agreement on a difficult problem, receiving proposals, and the voting is a simple count to gauge the sentiment of "is this a problem worth to be fixed?, are we committed to implement a change in our clients?"

But that's a fair point. What do the community expect? What do y'all expect?
@eapl.me@eapl.me What's with your client not using the proper syntax for mentions?


$ bat 'https://twtxt.net/twt/lnrgahq' | jq '.text'
"(#4xaabhq) thanks @prologic! 
@bender the idea of the RFC was to reach an agreement on a difficult problem, receiving proposals, and the voting is a simple count to gauge the sentiment of \"is this a problem worth to be fixed?, are we committed to implement a change in our clients?\" 

But that's a fair point. What do the community expect? What do y'all expect?"



🤔
sorry @prologic, timeline doesn't autocomplete the mentions yet, and it was 'difficult' to look for your URL from the phone.
@eapl.me@eapl.me Ahh I see 😅
@prologic I noticed that the hash also shows (as in clearly visible) on the “in-reply-to”. That doesn’t happen with any other client—well, at least not with Yarn, nor jenny.
@bender Yeah me too hmm 🧐