@asquare@asquare.srht.site (I wonder if that will ever show up without me mentioning you. 😅)

@movq@www.uninformativ.de eh? 🤔

@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? 🤔

@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.

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.

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.

@asquare@asquare.srht.site Hehw 🤣

https://twtxt.dev