(#oyi5iua) @marado See, even if we (for example) did something to change the behaviour of `yarnd` such that it: 1. produced a `twtxt.txt` feed that stripped `\u2028` so all posts are single-line. 2. converted Markdown to "plain text" 3. limited posts to 140 characters Would this make few that scream and shout the loudest happier that Yarn is more _properly_ using Twtxt? 🤔 Would Yarn _then_ be considered to be using Twtxt as-it-is/was intended? 🤔 Of course this would have the side effect of: - Your longer posts would now be truncated and meaningless. - Posting links to images would no longer work. - Threading would no non-existent. And so we're back to square one, where Twtxt as-it-was-is intended is a spec that whilst on its own useful for a very limited number of use-cases it lacks certain features that make microBlogging and interacting with others viable.

(#oyi5iua) @darch 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.

(#oyi5iua) An example feed would look like this: ```json { "name": "prologic", "desc": "\"Problems are Solved by Method\" 🇦🇺👨‍💻👨‍🦯🏹♔ 🏓⚯ 👨‍👩‍👧‍👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)", "key": "kex17m00vqjduqlf6j5xcvtpyhk2zg3shv2x8r5qzyancjlhgl4ytj8slvt7h0", "links": [ { "title": "My CV", "href": "https://prologic.shortcircuit.net.au/" }, { "title": "My Projects", "href": "https://git.mills.io/prologic" }, { "title": "My Github profile (@prologic)", "href": "https://github.com/prologic" } ], "items": [ { "id": "https://yarn.mills.io/permalink/xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa", "hash": "xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa", "sig": "3vdKTvI_WGDcM_cUUPGmWHPFpZ9IpORgFkhVFndcxbuUm3XF2w895nEvh2CIA0P3OekfmW6pWQP4wSsXZSCMAA", "format": "text/markdown", "time": "2023-04-16T11:04:28+10:00", "content": "Hello World" } ] } ```