(#eyg53lq) An option would be to have /twtxt.txt be the base functionality as bukket intended without subject tags, markdown, images and such truncated to 140 chars. a /yarn.txt that has all the extentions as we know and love. and maybe a /.well-known/webfinger + (TBD endpoint) that adds on the crypto enhancements that further extend things.

(#eyg53lq) @xuu Devils advocate: what value would be really be providing here? Would, for example @lyse and/or @movq switch to following the new Uarn feeds or stick with the truncated unmarked up and out-of-context pure twtxt feeds?

(#eyg53lq) We could ask them? But on the counter would bukket or jan6 follow the pure twtxt feeds? Probably not either way... We could use content negotiation as well. text/plain for basic and text/yarn for enhanced.

(#eyg53lq) @xuu @prologic I will never give up threading! It's a very vital civil achievement.

(#eyg53lq) @xuu @prologic Yarn.social without threading (as it would be the case in a “truncated” feed) does not make sense to me. Put another way: Yarn.social is not twtxt. The content that we all have in our feeds really is much closer to a web forum or usenet or whatever. It’s threaded conversations. twtxt, as I *believe* it was originally intended, are short little status updates – that’s it. The formats of Yarn.social and twtxt might be very similar, but the content is vastly different and, in a way, incompatible. (As such, I *think* I understand very well that the original twtxt crowd is disgruntled.) That proposed truncated feed doesn’t really provide any value, if you ask me. 🤔 It’d just be chaotic.

(#eyg53lq) @movq Agreed 💯

(#eyg53lq) @lyse Same! 😆 And it works quite well 😉