# 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 10
# self = https://watcher.sour.is/conv/xxu5i3a
I am working on this: https://dm-echo.andros.dev/
More news coming soon.
#twtxt
I am working on this: https://dm-echo.andros.dev/
More news coming soon.
#twtxt
👀

Is it working now?
I'd say again that perhaps the DMs could be stored in another .txt, but anyway I'd like to try it.
@eapl.me I think the benefits do not outweigh the disadvantages. Clients would have to read and merge the information from 2 txt and a new metadata would have to be added with the address of this file.
Also, it is very easy to filter or ignore it.
@eapl.me I think the benefits do not outweigh the disadvantages. Clients would have to read and merge the information from 2 txt and a new metadata would have to be added with the address of this file.
Also, it is very easy to filter or ignore it.
@eapl.me Ah! It is still not working.
@eapl.me Ah! It is still not working.
@andros This is cool! 😍 Migut just have to add support for this to see how it might work in yarnd 🤣
"it is very easy to filter or ignore it" This is the interesting part for legacy clients, hehe

Joking aside, let's see how it works in the wild!
@eapl.me@eapl.me Yeah yarnd already filters/ignores them (_for now_)