yarnd pod here around ~2m on average to fetch, process and cache ~700 feeds.
yarnd pod here around ~2m on average to fetch, process and cache ~700 feeds.
@<bender bender@twtxt.net> is currently wrong. The 2nd part of a mention is currently required to be a full absolute URI.
@<bender bender@twtxt.net> is currently wrong. The 2nd part of a mention is currently required to be a full absolute URI.
$ bat https://twtxt.net/twt/dn2zlga | jq '.'
{
"twter": {
"nick": "Codebuzz",
"uri": "https://www.codebuzz.nl/twtxt.txt",
"avatar": "https://www.codebuzz.nl/twtxt-avatar-800.jpg"
},
"text": "(#q5rg3ea) Hey, @<bender bender@twtxt.net> I know. Just wondering the kind of apps or software and how you all stay up to date in conversations. Is it through webmentions?",
"created": "2024-10-30T22:12:24Z",
"markdownText": "(#q5rg3ea) Hey, @<bender bender@twtxt.net> I know. Just wondering the kind of apps or software and how you all stay up to date in conversations. Is it through webmentions?",
"hash": "dn2zlga",
"tags": [
"q5rg3ea"
],
"subject": "(#q5rg3ea)",
"mentions": [],
"links": []
}
$ bat https://twtxt.net/twt/dn2zlga | jq '.'
{
"twter": {
"nick": "Codebuzz",
"uri": "https://www.codebuzz.nl/twtxt.txt",
"avatar": "https://www.codebuzz.nl/twtxt-avatar-800.jpg"
},
"text": "(#q5rg3ea) Hey, @<bender bender@twtxt.net> I know. Just wondering the kind of apps or software and how you all stay up to date in conversations. Is it through webmentions?",
"created": "2024-10-30T22:12:24Z",
"markdownText": "(#q5rg3ea) Hey, @<bender bender@twtxt.net> I know. Just wondering the kind of apps or software and how you all stay up to date in conversations. Is it through webmentions?",
"hash": "dn2zlga",
"tags": [
"q5rg3ea"
],
"subject": "(#q5rg3ea)",
"mentions": [],
"links": []
}
> Lately Iβve been browsing twtxt.net since they aggregate most of the known network
> Lately Iβve been browsing twtxt.net since they aggregate most of the known network
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.
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 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.