# 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 2
# self = https://watcher.sour.is/conv/4kymicq
bender
twtxt.net
View Thread
@andros nothing stands still, I agree. I think current twtxt has surpassed the initial specification, while still being relatively backwards compliant/compatible but, for how long?

As for new extensions (DM, for example), they should be OK as long as those working on clients can reach an agreement on how to move forward. That has proven, though, to be a pickle in the past.
prologic
twtxt.net
View Thread
@bender You said:

> as long as those working on clients can reach an agreement on how to move forward. That has proven, though, to be a pickle in the past.

I _think_ this is because we probably need to start thinking about three different aspects to the ecosystem and document them out:

- Specifications (_as they are now_)
- Server recommendations (_e.g: Timeline, yarnd, etc_)
- Client recommendations (_e.g: jenny, tt, tt2, twet, etc_)