# 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 21
# self = https://watcher.sour.is/conv/n5f7upa
@tkanos a quick question, I'm using twet (thanks for the recommendation), how do the clients announce between them that you have replied to a previous twt?
You have to follow the other person and the clients look for replies for each of your twts?
@eaplmx So... This is basically not really possible in a decentralised social media like Yarn.social / Twtxt. The _only_ way we can work around this is by growing the network and ecosystem enough to a point where things like other multi-user pods or a search engine _might_ be able to pick-up on things like this, which you _might_ be able to query for (in your client). The only other thing you can do is use tools such as the one @lyse built to parse your access_log for new followers.
@eaplmx So... This is basically not really possible in a decentralised social media like Yarn.social / Twtxt. The _only_ way we can work around this is by growing the network and ecosystem enough to a point where things like other multi-user pods or a search engine _might_ be able to pick-up on things like this, which you _might_ be able to query for (in your client). The only other thing you can do is use tools such as the one @lyse built to parse your access_log for new followers.
@tkanos I keep forgetting where it is 😢 I _think_ we need to link it on yarn.social Hmmm do we already? 🤔
@tkanos I keep forgetting where it is 😢 I _think_ we need to link it on yarn.social Hmmm do we already? 🤔
Hmmm no we don't... We need a "## Tools" section... @lyse ? @movq ? There _might_ already be a bunch of tools we can add to a new section...
Hmmm no we don't... We need a "## Tools" section... @lyse ? @movq ? There _might_ already be a bunch of tools we can add to a new section...
@prologic If I remember correctly, we were discussing a few months ago options like Webmention, I have never used it, although sounds better in my mind than parsing the access_log.
That search engine you mention or a global Database of Twt hashes could help. I remember that Twitter users had an external search platform, acquired later by Twitter: https://techcrunch.com/2008/07/15/confirmed-twitter-acquires-summize-search-engine/
As @tkanos said, a comment in the txt file like: Notify me on this email, or automatically register your feed in this URL as Antenna does, would be a nice addition.
I assume that if you are replying you are interested in making a dual connection, so they can answer you back. Just thinking out loud.
@eaplmx I'm pretty sure webmention would work for this. It's how the rest of the IndieWeb tends to care care of things like posting comments to blogs. It's pretty simple--there's a REST endpoint you hit when you reply to a post, and then an endpoint that gets called on the recipient's side that decides what to do with the webmention (ignore it, post it somewhere, alert the writer, other). You put the necessary endpoint(s) in <link rel="webmention"... and <link rel="pingback"... tags in the HTML of the pages you want to have webmention support, so it's pretty unintrusive.
You can play with it right now by signing into https://webmention.io with a yarn.social or other IndeiAuth-compatiable web site. I'm almost certain there are self-hostable web mention servers, or you can use webmention.io or one of the other ones.
@eaplmx yarnd actually has WebMentions support. But generally this doesn't work very well as in practise I actually find WebMentions isn't something used a lot. It also has to be supported on the other wise in the first place, which a lot of feeds just aren't going to bother with. However that is one of the advantages of using yarnd, if someone does discover and -mention you, your pod will be "pinged" and it'll show up in your "Mentions" tab even if you don't follow them.
@eaplmx yarnd actually has WebMentions support. But generally this doesn't work very well as in practise I actually find WebMentions isn't something used a lot. It also has to be supported on the other wise in the first place, which a lot of feeds just aren't going to bother with. However that is one of the advantages of using yarnd, if someone does discover and -mention you, your pod will be "pinged" and it'll show up in your "Mentions" tab even if you don't follow them.
@abucci yarnd1 also implements WebSub too 👌 Pods actually peer with one another and use WebSub for "feed subscriptions" to update feeds in near real-time.
@abucci yarnd1 also implements WebSub too 👌 Pods actually peer with one another and use WebSub for "feed subscriptions" to update feeds in near real-time.
@abucci Didn't know about WebSub, it's really cool everything around the simple .txt file to make it work a a social protocol.
Thanks for sharing your knowledge 😀
@eaplmx Any time! I'm still learning about the IndieWeb ecosystem myself, so don't take anything I say as authoritative!