

Recent posts from feeds followed by pftnhr@blog.ratterobert.com
@andros You seem to be a bit ahead of your time: https://darch.dk/timeline/conv/jl2mf2a
Timeline of Evolution of Twtxt/Yarn.social:
well, I assume by syntax you mean Gemtext (which I like a lot, my personal blog is built on top of it), so I think it might work for twtxt clients...
I knew of twtxt in Gemini Antenna, so at least the 2017 spec might work on that protocol. I think the main issue with extensions is that they weren't designed with many URLs and protocols in mind.
Also I have to admit that the Gemini community significantly reduced in the last few years. I don't know how worth it is to add support for Gemini now.
[lang=en] @xuu gotcha! From that PR #17 I think it was reverted? We could discuss about metadata later this month, as it seems that I'm the only person using it.
I've added a [lang=en]
to this twt to see current yarn behaviour.
#genuary #genuary2025 #genuary17 Maybe related to today prompt: What happens if pi=4? https://youtu.be/tGfUaZ8hTzg
@movq How hard would it be to implement something like (#<2024-10-25T17:15:50Z https://www.uninformativ.de/twtxt.txt>)
in jenny as a replacement for (<a href="?search=twthash" class="tag">#twthash</a>)
and have it not care about if is http(s) or a g-protocol?
@movq I'm glad you like it. A mention (<a href="/profile?url=https://www.uninformativ.de/twtxt.txt">@movq</a>
) is also long, but we live with it anyway. In a way a replyto:
is just a mention of a twt instead of a feed/person. Maybe we chould even model the syntax for replies on mentions: (#<2024-09-17T08:39:18Z https://www.eksempel.dk/twtxt.txt>)
?!