the bechdel test for an open source community is: two women in positions of formal authority discuss something, other than moderating a man's behavior
Yeah I've closed the PR, I just wanted to write it up and see what we all thought. Much easier to talk to a concrete spec proposal sometimes. I realised as I was writing it too that it wasn't really going to achieve much in practise. I think we all agree 👍
Yeah I've closed the PR, I just wanted to write it up and see what we all thought. Much easier to talk to a concrete spec proposal sometimes. I realised as I was writing it too that it wasn't really going to achieve much in practise. I think we all agree 👍
So many clients do client-side transformation already, mostly in the form of -mentions. e.g: If I @falsifian 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?
So many clients do client-side transformation already, mostly in the form of -mentions. e.g: If I @falsifian 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?
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 1/4 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.
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 1/4 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.
TXT DNS records? :-P Like so:
dig +short txt poem.netbros.com | sed 's/[\\" ]//g' | base64 -d
TXT DNS records? :-P Like so:
dig +short txt poem.netbros.com | sed 's/[\" ]//g' | base64 -d
I prefer 2024-01-04. :-)
Anyway, I don't think my eccentric decision to number my twts in the style of other social media platforms is the only context where someone might write 1/4 not meaning a quarter. E.g. January 4, to Americans.
I'm happy to keep overthinking this for as long as you are :-P
> My
1/4 -> 1/4 thing is nothing more than a minor irritation which probably isn’t worth overthinking.Yet, here we are still debating it. LOL.
twtxt.txt file.
1/4 to mean "first out of four".What has
text/markdown got to do with this? I don't think Markdown says anything about replacing 1/4 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.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
1/4 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 ¼.Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that's fine too and you don't need to change anything. My
1/4 -> ¼ thing is nothing more than a minor irritation which probably isn't worth overthinking.
> So I am really curious, now that I am building upon @sorenpeter's Timeline app, how other users write/add their twtxt, and how you follow conversations. Comment svp!
The private leaderboard from last year should still work.
The private leaderboard from last year should still work.
The private leaderboard from last year should still work.
The private leaderboard from last year should still work.
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 🤣
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 🤣
text/plain, then it will have to disabled markdown rendering for it, correct? If that's the case, are you sure you want that? 😅
/https://baldo.cat/media/photos/IMG_2486.jpeg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/IMG_2492.jpeg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
had a really hard time breathing for some reason. made the run pretty hard to get through.
#running
had a really hard time breathing for some reason. made the run pretty hard to get through.
#running
had a really hard time breathing for some reason. made the run pretty hard to get through.
#running
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.
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.
> but FWIW I’m not especially keen on changing how I format my twts to work around yarnd’s quirks.
Yet, you are asking Yarn to change the format to work around how you want it display. 🤔