@darch@neotxt.dk I think having a way to layer on features so those who can support/desire them can. It would be best for the community to be able to layer on (or off) the features.
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.
@xuu Devils advocate: what value would be really be providing here? Would, for example @lyse@lyse.isobeef.org and/or @movq@www.uninformativ.de switch to following the new Uarn feeds or stick with the truncated unmarked up and out-of-context pure twtxt feeds?
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.
@xuu@txt.sour.is @prologic@twtxt.net I will never give up threading! It’s a very vital civil achievement.
@xuu @prologic@twtxt.net 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.
@movq@www.uninformativ.de Agreed 💯
@lyse@lyse.isobeef.org Same! 😆 And it works quite well 😉