What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic, I think it would achieve what you are trying to achieve with this content-type thing: if someone writes ¼ on a yarnd instance or any other client that wants to do this, it would get transformed, and other clients simply wouldn’t do the transformation. Every client that supports displaying unicode characters, including Jenny, would then display ¼ as ¼.

So many clients do client-side transformation already, mostly in the form of @-mentions. e.g: If I @falsifian@www.falsifian.org mention you, that gets transformed into the full proper Twtxt mention syntax. We could in theory transform other things too, but I see little value in doing so? 🤔 – Also it’s probably more a “Client” recommendation anyway at that point right?

@falsifian@www.falsifian.org Only that this rendering behavior comes from yarnd’s Markdown parser library that is used:

What has text/markdown got to do with this? I don’t think Markdown says anything about replacing ¼ with ¼, or other similar transformations. It’s not needed, because ¼ is already a unicode character that can simply be directly inserted into the text file.

Closed

@david@collantes.us On it! 🤣

@david@collantes.us Bahahahahaha 🤣

No apology necessary. I think it brings little to no value.

@david@collantes.us Juat buy it 🤣🧐

@bender@twtxt.net The only changes I can foresee are really to yarnd. As no other client I’m aware of really cares aall that much. 🤣 It’s only in an attempt to solve this. No I’m not sure about this 🤣

@asquare@asquare.srht.site No worries 😌

@asquare@asquare.srht.site I’m not really sure I understand sorry. Can you explain it like I’m 5? 😅

👋 PR to propose Feed Format Extension – Request for comment 🙏

@asquare@asquare.srht.site No it will not, because it needs to find the root twt. Doing so with a O(1) time complexity is far better than the alternative.

@asquare@asquare.srht.site Why “frightening”? And what does “protocol ossification” mean? Hmm 🧐

@lyse@lyse.isobeef.org Cool! Literally 🥶 When do you expect leaves to be falling from trees? 🤔

I think realistically the only way to resolve this is to formally support and define a specification for feed formats. The available mime types lists two formats that I think are important here. text/plain and text/markdown. I believe a specification that defines and formalizes this so that a feed author can state in their feed that their feed is primarily text/plain or text/markdown or via HTTP headers (not mandatory) will work here. I also think it might be worthwhile niversing this and defaulting to text/plain (by design and by default, spec TBD) and then clients like yanrd can just be updated to declare text/markdown.

@aelaraji@aelaraji.com No need to be sorry 🤗

@slashdot@feeds.twtxt.net Really?! And we expected what to happen exactly? 🤔

@thecanine@twtxt.net this is really fucked up! Do you have other examples? 🤔

@stigatle@yarn.stigatle.no No worries 🤗 Last Sat of every month 🤞

@stigatle@yarn.stigatle.no This seems cool hmmm 🧐

@bender@twtxt.net Dam that’s small 🤣 Nice! 👍

Exactly! But you still have to sign up to “their” platform. da fuq?! I smell something fishy here 🤣

But you have to sign-up though? wut?! 😟

@doesnm@doesnm.p.psf.lt I happy to be very good friends with the founder of IRCCloud who happens to be also my namesakes 😅

@bender@twtxt.net Yeah I mostly read IRC backlogs on mobile, very rarely talk per se 😅

Yeah 😔

@sorenpeter@darch.dk@darch.dk I use ITCCloud, am always online via my Desktop and ITC from the mobile app.

@Codebuzz@www.codebuzz.nl Yes 🤞

@bender@twtxt.net I tend to agree 👍

Neycer Robalino vs Hayden Green – Brisbane Flexi Season (Week 3) Div 1 Final - YouTube This is Neycer one of our coaches at the table-tennis club 🏓 that I play at vs. Hayden a top-rated QLD player (well not anymore 🤣). What a match! 😱 Go #Brisbane #Table-Tennis #BTTA

@aelaraji@aelaraji.com To be honest I thought the same too, I felt as though you were being a bit too harsh on yourself 😅 Chill 🤗

@bender@twtxt.net True, I’m just not sure we can have it both way? 🤔 I can turn smartypants off, but I do seem to recall you wanted it on 🤣

I think this works 1/4

@Codebuzz@www.codebuzz.nl I agree. At the end of the day it’s just a text file served by some means, we should get more upset by crawlers that don’t respect our robots.tzt rules 🤣

Hah 🤣

@movq@www.uninformativ.de Cool 👌

@lyse@lyse.isobeef.org Ahh thanks! 🙏

@aelaraji@aelaraji.com It even shows up here too 😅 44 feeds you follow, nice 👍

@movq@www.uninformativ.de I’ll merge it then 👌

👋 FYI: I’ve put in place 301 Moved Permanently redirect(s) for https://dev.twtxt.net/ and all relevant pages to the new domain https://twtxt.dev 👌

@bender@twtxt.net Right, so a “Cool Domain” is just a URI in your Domain space that you control and maintain stability. As you control the Domain Space, you can keep URI(s) stable even in the face of change. Okay.

But what I don’t get is @asquare ’s comment:

Imposing a norm that you can’t just use any ol’ url, looking down on people

@asquare Who’s imposing this and “looking down”? If you got that impression from me, that was not my intent. I’m merely pointing out the problem we have, nothing more. We need to solve for that.

@asquare@asquare.srht.site What do you mean by “Cool URLs”?

Yup that’s right.

@falsifian@www.falsifian.org How so? 🤔

@Codebuzz@www.codebuzz.nl I really like this idea of just using the Feed’s # nick as a sort of “identifier”. This gets us out of this mess of when feeds move locations or authors decide to host on 3 or 4 different protocols 🤣 Downside? Something picks the same nick? (they’ll still hash differently, so that’s fine).

👋 PR to Update Metadata ext to clarify avatar field cc @lyse@lyse.isobeef.org @movq@www.uninformativ.de @sorenpeter@darch.dk and @Codebuzz@www.codebuzz.nl

@cuaxolotl@sunshinegardens.org not sure that really applies strictly in a purely decentakised system? 🤔

The call is on! Come join us!

https://meet.mills.io/call/Yarn.social

@stigatle@yarn.stigatle.no Cominf yo yhe call? 🤔🤗

@xuu Thanks!