# 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 8
# self = https://watcher.sour.is/conv/2a5vnyq
I _think_ Email Message-Id(s) only ever worked because typically you are exchanging emails with recipients you know and vice versa. It's much easier to cope with the problems above, because you just ensure your client preserves the Message-Id. Email is a federated system, but by no means is it "decentralised". You still have to send your email somewhere, not just post it on a website on your own server like Twtxt 😅
There are some subtitles differences like this that makes Message/Thread Id(s) not really that suitable IMO.
I _think_ Email Message-Id(s) only ever worked because typically you are exchanging emails with recipients you know and vice versa. It's much easier to cope with the problems above, because you just ensure your client preserves the Message-Id. Email is a federated system, but by no means is it "decentralised". You still have to send your email somewhere, not just post it on a website on your own server like Twtxt 😅
There are some subtitles differences like this that makes Message/Thread Id(s) not really that suitable IMO.
@prologic about this:
> “I think Email Message-Id(s) only ever worked because typically you are exchanging emails with recipients you know and vice versa […]
Absolutely not! Maybe this is something best talked. 😅
@prologic about this:
> “I think Email Message-Id(s) only ever worked because typically you are exchanging emails with recipients you know and vice versa […]
Absolutely not! Maybe this is something best talked. 😅
@prologic about this:
> “I think Email Message-Id(s) only ever worked because typically you are exchanging emails with recipients you know and vice versa \n
Absolutely not! Maybe this is something best talked. 😅
@bender Haha, easy to demonstrate. I'll start an email thread with myself, then you see if you can join in 🤣
@bender Haha, easy to demonstrate. I'll start an email thread with myself, then you see if you can join in 🤣
@prologic @bender That's exactly the case here with us as well. Maybe not 100% applicable to yarnd, but all other clients that only fetch from their user-controlled subscription list.