# 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 7
# self = https://watcher.sour.is/conv/4on4bda
@prologic I probably would *not* use an yarn.social client/app that didn't deal with twtxt (text) feeds - both "follow" them and "publish" them. But I suppose that it is possible to have a bidirectional converter between that json format and twtxt.
@marado Yeah it would be possible to have "bridges" just like I _think_ we should have a bridge finally for Twtxt<->ActivityPub. The motivation behind this proposal/idea is to get away from the trolls and hostility of Twtxt. Its of course too late to change what we did in the past (nearly getting on 3 years now), but trying to find ways to deal with this going forward...
@marado Yeah it would be possible to have "bridges" just like I _think_ we should have a bridge finally for Twtxt<->ActivityPub. The motivation behind this proposal/idea is to get away from the trolls and hostility of Twtxt. Its of course too late to change what we did in the past (nearly getting on 3 years now), but trying to find ways to deal with this going forward...
@marado Yeah it would be possible to have "bridges" just like I _think_ we should have a bridge finally for Twtxt<->ActivityPub. The motivation behind this proposal/idea is to get away from the trolls and hostility of Twtxt. Its of course too late to change what we did in the past (nearly getting on 3 years now), but trying to find ways to deal with this going forward...
The problem of course is the position this forces me in to, with all of this "nonsense", means you end up having so many different competing specs and protocols that you end up in exactly the position we're in now with "chat": 
where none of them work with one another and there's no effective bridging, data or identity portability.
The problem of course is the position this forces me in to, with all of this "nonsense", means you end up having so many different competing specs and protocols that you end up in exactly the position we're in now with "chat": where none of them work with one another and there's no effective bridging, data or identity portability.
The problem of course is the position this forces me in to, with all of this "nonsense", means you end up having so many different competing specs and protocols that you end up in exactly the position we're in now with "chat": where none of them work with one another and there's no effective bridging, data or identity portability.