# 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/lo32qmq
@ocdtrekkie I _think_ there's no way to tell Mastodon/Activity Pub actors to set a specific inReplyTo when repying. I _think_ (correct me if I'm wrong) the default behaviour for Mastodon and pretty much all Activity Pub implementations (besides Yarn.social) is to "fork".
@ocdtrekkie I _think_ there's no way to tell Mastodon/Activity Pub actors to set a specific inReplyTo when repying. I _think_ (correct me if I'm wrong) the default behaviour for Mastodon and pretty much all Activity Pub implementations (besides Yarn.social) is to "fork".
@ocdtrekkie I _think_ there's no way to tell Mastodon/Activity Pub actors to set a specific inReplyTo when repying. I _think_ (correct me if I'm wrong) the default behaviour for Mastodon and pretty much all Activity Pub implementations (besides Yarn.social) is to "fork".
@ocdtrekkie I _think_ there's no way to tell Mastodon/Activity Pub actors to set a specific inReplyTo when repying. I _think_ (correct me if I'm wrong) the default behaviour for Mastodon and pretty much all Activity Pub implementations (besides Yarn.social) is to "fork".
@ocdtrekkie Hah, hardly, the specs (AP, A2S, HTTPSig, et all) are just a few of the specs at play. WebFinger and HTTPSig are probably the more straightforward ones. It's the fact that Mastodon existed before Activity Pub and then kind of went and did its own thing (somewhat) that makes things hard. Like the fact we have to translate Twts to HTML but a specialised form of it, with Microformats (mf2) embedded for mentions. Not sure if there are other things we should be doing, tags maybe? But that's a problem for another day/weekend 😅
@ocdtrekkie Hah, hardly, the specs (AP, A2S, HTTPSig, et all) are just a few of the specs at play. WebFinger and HTTPSig are probably the more straightforward ones. It's the fact that Mastodon existed before Activity Pub and then kind of went and did its own thing (somewhat) that makes things hard. Like the fact we have to translate Twts to HTML but a specialised form of it, with Microformats (mf2) embedded for mentions. Not sure if there are other things we should be doing, tags maybe? But that's a problem for another day/weekend 😅
@ocdtrekkie Hah, hardly, the specs (AP, A2S, HTTPSig, et all) are just a few of the specs at play. WebFinger and HTTPSig are probably the more straightforward ones. It's the fact that Mastodon existed before Activity Pub and then kind of went and did its own thing (somewhat) that makes things hard. Like the fact we have to translate Twts to HTML but a specialised form of it, with Microformats (mf2) embedded for mentions. Not sure if there are other things we should be doing, tags maybe? But that's a problem for another day/weekend 😅
@ocdtrekkie Hah, hardly, the specs (AP, A2S, HTTPSig, et all) are just a few of the specs at play. WebFinger and HTTPSig are probably the more straightforward ones. It's the fact that Mastodon existed before Activity Pub and then kind of went and did its own thing (somewhat) that makes things hard. Like the fact we have to translate Twts to HTML but a specialised form of it, with Microformats (mf2) embedded for mentions. Not sure if there are other things we should be doing, tags maybe? But that's a problem for another day/weekend 😅