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 🧐
@prologic@twtxt.net I don’t think so, no. Judging by their web site, they appear to be primarily a Gemini user (no concept of a “user agent” there). This also works:
gemini://sunshinegardens.org/users/xj9/twtxt/tw.txt
But there are nick, url, and description metadata headers in the feed, even an avatar. 🤔
@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? 🤔
@prologic@twtxt.net 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@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.
@prologic@twtxt.net So a new metadata field like this?
# follow_notify = gopher://foo/bar
And we ping that every now and then? 🤔
@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.
@prologic@twtxt.net Ahh, found it, there were some ideas in this thread from January 2022: https://twtxt.net/twt/ansuy4a I haven’t read all of it yet.
@prologic@twtxt.net @movq@www.uninformativ.de Looking at the raw feed, there are a six mentions (even prologic) and a seven subjects. From a few years ago, though. :-)
@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.
@prologic@twtxt.net 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
@prologic@twtxt.net @movq@www.uninformativ.de my setup is pretty old-school tw.txt hosting-wise. just a text file and a very simple static bridge for pikkulog-style subscribers on gemini. i do try to keep up on the twtxt format spec so i’m publishing a modern and well-formed feed. my dual-hosted website/gemcapsule is meant to eventually be entirely bespoke (my friend wrote the gemini server i’m using, so that counts enough for now) and i’d like to eventually support some of the server extensions that yarn has piloted. follow-wise, rn i kinda just manually try to pick up on who is following me by browsing random feeds. my custom clients usually do a FoaF crawl, but i don’t have anything that really works running rn.
I’ve been sketching out some gemini-specific offline social stuff here https://ix.cyb.red/wiki/pikabu, but for the online parts i’d be willing to adopt what tw.txt protocols work under the constraints of gemini
I’ve been sketching out some gemini-specific offline social stuff here https://ix.cyb.red/wiki/pikabu, but for the online parts i’d be willing to adopt what tw.txt protocols work under the constraints of gemini