(#c6yyvda) Who's going to tell him that the metadata fields are a Yarn extension?

@mckinley (#c6yyvda) Well, sort of? I've been using them (copying or adapting and extending from what I saw others do) since before yarn.social was a thing. Yarn doesn't (and shouldn't) have the monopoly of "using twtxt comments how we like".

(#c6yyvda) @marado @mckinley Yhe stupid or funny thing about this (_which I find brutally offensive_) is the extensions were created out of observation of what the community was already doing. That is to say; we just formalized what was already commonly being done. 🤦‍♂️

(#c6yyvda) @prologic well, I think that's something coming along with fame from Yarn and freedom from them. Some people like to stay with simpler things even if they are obsolete, incompatible, and such. They has an option to not follow an improvement and to stay with the version 1.0 of the spec, and that's OK in my book. I agree to disagree, even if I really like the extensions, let's say 1.1, not being able to communicate with people following forks or modern protocols. Their loss.

(#c6yyvda) @mckinley 😆 No one using Yarn extensions, it seems

@prologic @eaplmx (#c6yyvda) To be fair, the only thing I can think of that makes Yarn feeds not be "standard twtxt" is the disregard for twt size (which many others also do with their non-yarn clients). But sure, I can see how reading these feeds might be frustrating: too big posts, markdown everywhere, linebreak characters, emojis... But I'll consider it the "freedom of the user" to decide whether or not to follow a feed written in a certain style. The provocative metadata comment? Easy (and better) to just ignore.

(#c6yyvda) and very often it comes from people rather that tech or specs. Could be something like "I don't like ~prologic and/or I don't like yarn.social, I won't use that because I like things by my way" It's stupid, I've felt that, and now I try to ignore it a bit, it's bad for our health to listen every feedback, IMO 🤷‍♂️

(#c6yyvda) @prologic why would they go out of their way to put that there?

(#c6yyvda) @abucci I really don't know mate, I really don't know. Its really disappointing to see to be honest and I'm really quite upset by this.

(#c6yyvda) @eaplmx The _issue_ is not @lucidiot desire to remain with the simpler (unextended) Twtxt spec. That's totally fine. It is this "lash out" and calling out Yarn.social in his feed, as if it were a bad thing that is truly deeply offensive to the work countless folks have done over two and a bit years now and the growing community that continues to build clients, spawn pods, and so on. It's like a "shove it in your face" kind of moment to see something like this, even borderline "prejudice" really. People are free to use Twtxt however they wish, and they are even free to use the Extensions we built, or not. So you are 100% right there.