Anyone had any intereractions with @cuaxolotl@sunshinegardens.org yet? Or are they using a client that doesn’t know how to detect clients following them properly? Hmmm 🧐

@movq@www.uninformativ.de 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@www.uninformativ.de 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.

@movq@www.uninformativ.de Something like that, yeah 🤔

For HTTP WebSub is a good simple option here and there is this free inline WebSub hub anyone can use.

@movq@www.uninformativ.de 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.

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