↳ In-reply-to » Given the continued hostility of jam6 and buckket over Yarn'a use of Twtxt (even after several years! 😱) I am continuing to face hard decisions.

@prologic@twtxt.net Honestly this is quite disappointing to see as someone new to the twtxt/yarn ecosystem - it feels like the entirety of the buckket argument is based on a “purist” viewpoint when nothing yarn does feels fundamentally incompatible with original twtxt

Very sad 😔

However I do agree with jan6 on that while yarn is a great twtxt client, twtxt is a terrible yarn client

That doesn’t mean that yarn should change its underlying format away from twtxt though, twtxt is probably yarn’s biggest selling point

my view of twxt is essentially a feed of arbitrary plain text data with timestamps, which can open up the ecosystem to all sorts of good experimentation in clients

and for the specific case of multiline twts, when you actively have a pr waiting which addresses the issue, the stubbornness of the opposition seems quite unreasonable

that’s just my two cents, didn’t mean to write a paragraph (lol a multiline twt for you right here)