# 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 23
# self = https://watcher.sour.is/conv/52smrra
Good question. Mostly because they form normal #hashtag(s) anyway. THe only _special_ thing about them is they also address a specific Twt -- i.e: Content Addressing. We _could_ make them link to the "Conversation" view, but then you' dloose the ability to search by that tag, say if a client screwed up, or twts dropped of the active cache, etc. Both the web app and mobile app know how to recognise a "reply to" and show the "Conversation" button and link to the right things. 🤷♂️
Good question. Mostly because they form normal #hashtag(s) anyway. THe only _special_ thing about them is they also address a specific Twt -- i.e: Content Addressing. We _could_ make them link to the "Conversation" view, but then you' dloose the ability to search by that tag, say if a client screwed up, or twts dropped of the active cache, etc. Both the web app and mobile app know how to recognise a "reply to" and show the "Conversation" button and link to the right things. 🤷♂️
Good question. Mostly because they form normal #hashtag(s) anyway. THe only _special_ thing about them is they also address a specific Twt -- i.e: Content Addressing. We _could_ make them link to the "Conversation" view, but then you' dloose the ability to search by that tag, say if a client screwed up, or twts dropped of the active cache, etc. Both the web app and mobile app know how to recognise a "reply to" and show the "Conversation" button and link to the right things. 🤷♂️
@adi That's because the Conversation view will show the "OP" (_original post or twt_) effectively (_even if it has since been archived_) -- where as a search cannot.
@adi That's because the Conversation view will show the "OP" (_original post or twt_) effectively (_even if it has since been archived_) -- where as a search cannot.
@adi That's because the Conversation view will show the "OP" (_original post or twt_) effectively (_even if it has since been archived_) -- where as a search cannot.
@prologic Makes more sense to me to link to the Conversation view.
@prologic Makes more sense to me to link to the Conversation view.
@prologic Makes more sense to me to link to the Conversation view.
@adi You _may_ be right, but there are good reasons it is this way 😎
@adi You _may_ be right, but there are good reasons it is this way 😎
@adi You _may_ be right, but there are good reasons it is this way 😎
@prologic Silly me, I thought the Conversation button and the hashtag were the same thing, yeah leave it like so.
@prologic Silly me, I thought the Conversation button and the hashtag were the same thing, yeah leave it like so.
@prologic Silly me, I thought the Conversation button and the hashtag were the same thing, yeah leave it like so.
@adi All good 😀 The #hashtag is more generalised and I _beliee_ we wrote a spec for it over at dev.twtxt.net -- So yeah its fine this way, client's just have to understand "Twt Subjects" and "Twt Hashes" and then they can use this to render similar "Conversation" views. I don't recall who here, but someone built a client called tt that basically renders conversation in a curses display in "threads" just like the mutt TUI. Amazing shit really 😎
@adi All good 😀 The #hashtag is more generalised and I _beliee_ we wrote a spec for it over at dev.twtxt.net -- So yeah its fine this way, client's just have to understand "Twt Subjects" and "Twt Hashes" and then they can use this to render similar "Conversation" views. I don't recall who here, but someone built a client called tt that basically renders conversation in a curses display in "threads" just like the mutt TUI. Amazing shit really 😎
@adi All good 😀 The #hashtag is more generalised and I _beliee_ we wrote a spec for it over at dev.twtxt.net -- So yeah its fine this way, client's just have to understand "Twt Subjects" and "Twt Hashes" and then they can use this to render similar "Conversation" views. I don't recall who here, but someone built a client called tt that basically renders conversation in a curses display in "threads" just like the mutt TUI. Amazing shit really 😎
@adi @prologic My tt client uses the conversation URLs in the twt subjects when creating a reply, because I think this makes more sense, too. This is also covered by the Twt Subject Extension Spec. This client is still in a terrible state right now – hence "tt" as in "terrible tui" rather than "twtxt tui". :-P