👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or “Yarn”. Compatibility would remain with Twtxt in the sense that we wouldn’t break anything per se, but we’d divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don’t use, contribute in the first place or fixate on nostalgia (which doesn’t really help anyone).
@prologic@twtxt.net I would politely suggest again that we not react to people with bad attitudes who talk shit about yarn. If twt is forked, it should be forked to add features that are otherwise not possible. Not to appease people who will probably never be appeased.
I’m with @abucci@anthony.buc.ci here. Let’s enjoy our freedom to listen i.e. not pay too much attention to people how argue for the sake of arguing.
A way around their criticism choud be to put a disclaimer in our twtxt.txts stating that this feed uses features that might not be compatible with some clients. Like the old “Best viewed in Netscape”-icons
I am against the original idea of forking twtxt.txt into yarn.txt unless I see any technical reason or feature that would justify breaking compatibility - so far I don’t see one. But I agree in principle with @darch@neotxt.dk that maybe we can add something on the metadata of the feeds enumerating the extensions we use or… I don’t know, something that will allow any twtxt user to know how to deal with any ‘yarnisms’ in the content of our twts (even if the only one that comes to my mind as needing explanation is the thread hashes - how to interpret them).
The “problem” as I see it is not technical, but social, so we should try to approach solving it according.
@darch@neotxt.dk yes!
Some good points guys 👌 Thanks! 🙇♂️