@asquare@asquare.srht.site (I wonder if that will ever show up without me mentioning you. 😅)
@prologic@twtxt.net Apparently not. 🥴
This is the twt of @asquare@asquare.srht.site I’m referring to:
(#4w3ilsa) @prologic@twtxt.net Actually, my twts from the last two days aren’t showing up on , so I guess that no-one is following me and the reason my earlier twts did show up is that
yarnddoes a one-off fetch of any feed @-mentioned by a pod member. Comments in the code suggest that this is the case, seeinternal/server.go, commit7dcec70e, line 468. As the author of that code, can you confirm/deny?
@movq@www.uninformativ.de Ahh yes, that is probably the case 🤣 To be fair I don’t think too much about how things enter my cache, I just assume it’s either someone on my pod following them or whatever.
I didn’t follow at first because:
asquare may not follow you
Which probably means @asquare is probably using a client that doesn’t publicise its user agent or has it turned off? 🤔
@prologic@twtxt.net They’re using Gemini, maybe that’s why?
@movq@www.uninformativ.de Yeah I noticed that earlier, and forgot 😅 That explains everything now 🤣
I’m not using anything that you would recognize as a full-featured client. I upload twts with hut publish, “publicise my user agent” with manual curl invocations (when I remember to) (thanks to @movq@www.uninformativ.de for the informative guide https://www.uninformativ.de/twtxt-mention.html), and as for following other people’s feeds, I still haven’t decided how I’m going to do that.
Probably going to stick to my original plan, which is to implement everything I need by hand. Becaus to me part of the appeal of twtxt is that it’s simple enough for it to be feasible to roll your own implementation.