For those that might be a little bit lost regarding my twtxt presence:

• I host my own twtxt feed here so I can remain independent of 3rd party providers, and “owner of my own feed”. However;
  
• Currently my feed is being generated and managed at twtxt.net, which allows me, amongst other things, to use goryon, a nice mobile app, to manage my feed (even if twtxt.net’s web interface works pretty well on mobile);
  
• On a geeky sidenote, I haven’t still set aside the idea of running my own single-user yarn pod instead of relying on twtxt.net, but I didn’t want to postpone this movement any longer, now that there’s a new twitter exodus;
  
• For historic purposes, you can still find my old twtxts on the old feed, now rotated into a new address;
  
• Finally, there’s still a twtxt feed of my tweets.

Hi @prologic@twtxt.net, question regarding responsible use of twtxt.net’s services. How much is “too intensive” an use of its endpoints? For eg, an “every minute” fetch of a twt feed is considered OK? (I honestly have no idea about the default frequency of communication between pods and all that…)

@movq@www.uninformativ.de I have thought of different approaches, each have strengths and weaknesses. Mostly, I’d like to know what others think :-) In any case, I suppose I’d like to “extend” the hashtag generation API, so each blog post can have its own thread hash tag (like twts do). Then, “listing” the comments could be via querying a registry, and the “leave a comment” link could link to https://preconfigured-yarn.pod/?newtwt=@blogowner%20(#hashtag) or whatever link that would open that pod ready to create that new post if you’re logged in. Bonus points if you can configure more than one pod and it displays a dropdown; more bonus if we decide to implement twt:// uris letting twt clients listen to those (including a browser plug-in letting you say ‘open twt:// uris on https://my.pod’).

Yes, I might be overengineering.

I’m not the only twtxt’er that has an bashblog blog… How cool would it be to be able to integrate twtxt comments in it, in replacement to the current twitter comments implementations? With the way threads work in yarn instances, twtxt could even provide way more than just a replacement to twitter…

European Parliament votes for Free Software in AI resolution – This position must now be included in the AI regulation

@prologic@twtxt.net here’s another question (sorry!), is something wrong going on with the feeds service? https://feeds.twtxt.net/twitter-mind_booster/twtxt.txt does not seem to be updated since January (but the source is…)

Hey @prologic@twtxt.net, https://dev.twtxt.net/doc/archivefeedsextension.html allows only for a prev filename but not a full URL. Is there any reason why? Even for non-self-hosters, being able to point to a new domain would be good for interoperability, right?

@slashdot@feeds.twtxt.net @prologic@twtxt.net There’s a lot in #DSA to unpack, EDRI is a good resource about it: https://edri.org/our-work/eu-negotiators-approve-good-dsa-but-more-work-is-needed-to-build-a-better-internet/

According to some on twitter (see https://twitter.com/disclosetv/status/1518662153343057923?t=HAwtAoxkxZ-H6E8Px7qq1w&s=19 as an example), twitter share trading has halted, and the announcement of Musk buying Twitter is imminent.

I’m a little disappointed to not see more people talking about twtxt as an alternative to twitter…

@prologic@twtxt.net So, there is an API! This is offtopic for the thread (sorry) but can you link me to its documentation? I’m thinking about creating a single-user barebones “pod”, compatible with the mobile app but that manages a single twtxt file.