# 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 39
# self = https://watcher.sour.is/conv/yqke7sq
Anyone had any intereractions with @cuaxolotl yet? Or are they using a client that doesn't know how to detect clients following them properly? Hmmm 🧐
Anyone had any intereractions with @cuaxolotl yet? Or are they using a client that doesn't know how to detect clients following them properly? Hmmm 🧐
@movq Yeah okay I didn't notice that 🤦♂️ Kind of makes me wonder whether we should do something for the Gopher and Gemini folk here? 🤔
@movq Yeah okay I didn't notice that 🤦♂️ Kind of makes me wonder whether we should do something for the Gopher and Gemini folk here? 🤔
@prologic You mean a way of letting them know that someone is following them? 🤔 I guess that’s gonna be hard (I think we discussed stuff like that a few years ago), but I’m open for suggestions. 😅
@prologic You mean a way of letting them know that someone is following them? 🤔 I guess that’s gonna be hard (I think we discussed stuff like that a few years ago), but I’m open for suggestions. 😅
@prologic You mean a way of letting them know that someone is following them? 🤔 I guess that’s gonna be hard (I think we discussed stuff like that a few years ago), but I’m open for suggestions. 😅
@prologic You mean a way of letting them know that someone is following them? 🤔 I guess that’s gonna be hard (I think we discussed stuff like that a few years ago), but I’m open for suggestions. 😅
@movq I'm thinking of something like an optional metadata key that could be used as a general motivation endpoint?
@movq I'm thinking of something like an optional metadata key that could be used as a general motivation endpoint?
Similarly an optional subscription endpoint so we can optionally avoid having to pull feeds.
Similarly an optional subscription endpoint so we can optionally avoid having to pull feeds.
@movq Something like that, yeah 🤔
@movq Something like that, yeah 🤔
For HTTP WebSub is a good simple option here and there is this free inline WebSub hub anyone can use.
For HTTP WebSub is a good simple option here and there is this free inline WebSub hub anyone can use.
@prologic @movq Looking at the raw feed, there are a six mentions (even prologic) and a seven subjects. From a few years ago, though. :-)
@movq Yeah your original idea of precent encoding some information about the new follower is probably what we need to think about more. I _think_ it'll also work for Gopher/Gemini folk too right? So essentially new metadata key (_optional_) with some spec for encoding information about the new follower if either a) You don't implement the User-Agent part of the spec or extensions or b)You use a protocol that makes this impossible.
@movq Yeah your original idea of precent encoding some information about the new follower is probably what we need to think about more. I _think_ it'll also work for Gopher/Gemini folk too right? So essentially new metadata key (_optional_) with some spec for encoding information about the new follower if either a) You don't implement the User-Agent part of the spec or extensions or b)You use a protocol that makes this impossible.
@prologic There’s another thing to consider: I have a feeling that (some/most/many?) Gopher/Gemini users wouldn’t even *want* that. I’ve heard them say a couple of times: “If you follow me, just drop me an e-mail.” 🤔 I don’t know if this is a widespread opinion or not, but I do feel the need to first gather some feedback from them, before we start drafting a spec. 😅
@prologic There’s another thing to consider: I have a feeling that (some/most/many?) Gopher/Gemini users wouldn’t even *want* that. I’ve heard them say a couple of times: “If you follow me, just drop me an e-mail.” 🤔 I don’t know if this is a widespread opinion or not, but I do feel the need to first gather some feedback from them, before we start drafting a spec. 😅
@prologic There’s another thing to consider: I have a feeling that (some/most/many?) Gopher/Gemini users wouldn’t even *want* that. I’ve heard them say a couple of times: “If you follow me, just drop me an e-mail.” 🤔 I don’t know if this is a widespread opinion or not, but I do feel the need to first gather some feedback from them, before we start drafting a spec. 😅
@prologic There’s another thing to consider: I have a feeling that (some/most/many?) Gopher/Gemini users wouldn’t even *want* that. I’ve heard them say a couple of times: “If you follow me, just drop me an e-mail.” 🤔 I don’t know if this is a widespread opinion or not, but I do feel the need to first gather some feedback from them, before we start drafting a spec. 😅
For following notifications I would say use webmetion refering to the the line in your twtxt.txt as per: https://darch.dk/mentions-twtxt
Or send them an email, so it would be an idea to add a # contact = mailto:me@domain.net to ones twtxt.txt
For following notifications I would say use webmetion refering to the the line in your twtxt.txt as per: https://darch.dk/mentions-twtxt
Or send them an email, so it would be an idea to add a # contact = mailto:me@domain.net to ones twtxt.txt
For following notifications I would say use webmetion refering to the the line in your twtxt.txt as per: https://darch.dk/mentions-twtxt
Or send them an email, so it would be an idea to add a # contact = mailto:me@domain.net to ones twtxt.txt
For following notifications I would say use webmetion refering to the the line in your twtxt.txt as per: https://darch.dk/mentions-twtxt
Or send them an email, so it would be an idea to add a # contact = mailto:me@domain.net to ones twtxt.txt