I also totally get whet you’re saying about a twtxt file potentially growing to be huge. I guess that, and the fact that it’s necessary to work around it with a significant caching architecture, is a major downside to the model of twtxt itself which I hadn’t considered.

@caesar@twtxt.net Major downside hwo? I don’t see it as a downside at all, it’s the same idea as a logfile, and generally you have (or should have) rotation policies around it. How you manage this is up to you. yarnd for example has a builtin weekly job that ensures feeds on a pod are kept under 1MB in size (configurable) and are rotated when they exceed this. Pods will also refuse to fetch feeds over this size too.

@mckinley@twtxt.net Not yet… Coming soon™ 😅 I was a little slower to adopt that particular spec. I’ll get around it it don’t worry!

@mckinley@twtxt.net Judging by the size of your feed currently and how frequently / infrequently you post to it, I’d say you won’t have to worry for another couple of years 🤣

$ curl -v -o /dev/null https://twtxt.net/user/mckinley/twtxt.txt 2>&1 | grep -i 'Content-Length'
< content-length: 107361

@mutefall@twtxt.net Notice is here