# 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/m4gy4iq
I have got to add a "Fork" button, it's so nice to be able to "fork" conversation @markwylde help me add this to the Web interface somehow? 🤔
I have got to add a "Fork" button, it's so nice to be able to "fork" conversation @markwylde help me add this to the Web interface somehow? 🤔
@prologic It’s really funny to see how so many forms of communication gravitate towards “let’s just do full threading, we should have done it from that start”. 🤔
@prologic It’s really funny to see how so many forms of communication gravitate towards “let’s just do full threading, we should have done it from that start”. 🤔
@prologic It’s really funny to see how so many forms of communication gravitate towards “let’s just do full threading, we should have done it from that start”. 🤔
@movq Nah it’s just an interesting property of the Twt Hashes we came up with 🤣 So… We should build a button for it ☺️
@movq Nah it’s just an interesting property of the Twt Hashes we came up with 🤣 So… We should build a button for it ☺️
@prologic Let’s just say, I’ve seen this happen with multiple products at work: Step 1, someone builds something which doesn’t support a “reply” feature at all. Step 2, the thing grows, now people want “reply”. Step 3, it gets confusing with all the linear replies and now people want “full threading”. 😁 That’s also basically what happened to twtxt/yarn. Maybe, over time, everything evolves into Usenet. 🤣
@prologic Let’s just say, I’ve seen this happen with multiple products at work: Step 1, someone builds something which doesn’t support a “reply” feature at all. Step 2, the thing grows, now people want “reply”. Step 3, it gets confusing with all the linear replies and now people want “full threading”. 😁 That’s also basically what happened to twtxt/yarn. Maybe, over time, everything evolves into Usenet. 🤣
@prologic Let’s just say, I’ve seen this happen with multiple products at work: Step 1, someone builds something which doesn’t support a “reply” feature at all. Step 2, the thing grows, now people want “reply”. Step 3, it gets confusing with all the linear replies and now people want “full threading”. 😁 That’s also basically what happened to twtxt/yarn. Maybe, over time, everything evolves into Usenet. 🤣
@movq @prologic what happen to usenet? guees i'm too young for getting the reference...
@movq
> Maybe, over time, everything evolves into Usenet.
Convergent evolution, just like how creatures keep evolving to resemble crabs.
@movq \n\n> Maybe, over time, everything evolves into Usenet.\n\nConvergent evolution, just like how creatures keep evolving to resemble crabs.
@mckinley I just had a really weird mind picture of a crab-like human. Maybe something like this 
crab-like human picture?