mckinley

twtxt.net

A guy on the internet. https://mckinley.cc/

Recent twts from mckinley

I just typed out a message here on Yarn, undid a few things with ctrl+z, and then tried to redo something with the vi redo key combination. That means it’s time to go to bed.

⤋ Read More
In-reply-to » I noticed some unnecessary horizontal rules being rendered at the bottom of twts in the conversation view lately with yarnd's new design change. They can be seen at least when not being logged in. Not sure if it is the same experience with an active user session. I reckon there will be fork buttons then, so in that case they would be fine, indeed.

@prologic@twtxt.net Markdown horizontal rules never worked on the Web client, as far as I know.

@darch@twtxt.net, I think that specific line had a use as a visual separator between the non-interactive text and the interactive buttons, but it’s not a hill I’m willing to die on.

⤋ Read More
In-reply-to » I noticed some unnecessary horizontal rules being rendered at the bottom of twts in the conversation view lately with yarnd's new design change. They can be seen at least when not being logged in. Not sure if it is the same experience with an active user session. I reckon there will be fork buttons then, so in that case they would be fine, indeed.

@prologic@twtxt.net @darch@twtxt.net It looks like the horizontal rules are completely gone, though. I thought they looked nice…

⤋ Read More
In-reply-to » @mckinley Cool! 👌 So... Let's nuke it? 🤔 Are you thinking of writing a new spec?

@prologic@twtxt.net Yes, I’ve been thinking of writing a new, unambiguous version of the original spec with some small changes to bring it in line with how feeds are actually being constructed in the wild. The comment syntax, for example, but not the Yarn extensions.

Is there community interest for such a thing?

⤋ Read More
In-reply-to » Testing something... https://txt.sour.is/external?uri=https://example.com/~foo/twtxt.txt&nick=

Outside of this thread, this comment syntax has been used exactly twice when searching every known, currently accessible twtxt feed on the Web.

$ grep -r '@<[^ ]*>'
buckket.org.txt:2016-02-12T18:37:00+01:00	Hey @<http://vigintitres.eu/twtxt.txt>, @<teddy https://data.trafficking.agency/twtxt.txt> und @Jim@example.org was geht? Ich bin’s @GEHEIM@buckket.org!
[...]
hecanjog.com.txt:2020-09-03T17:36:00-05:00	@https://tilde.town/~lucidiot/twtxt.tx@ twtxt via DNS TXT would be insane and fun.

⤋ Read More
In-reply-to » @mckinley here is the dump https://github.com/tkanos/we-are-twtxt (on the tarball all-twtxt.tar.xz)

Here are the top ten feeds by size. @prologic@twtxt.net is artificially low on the list because it’s separated into chunks, and @movq@www.uninformativ.de is listed twice. Once as www.uninformativ.de, once as uninformativ.de. I blame yarnd.

du -b * | sort -nr | head -n 10
5253921	www.lord-enki.net.txt
842733	cnbeta-com-rssding-yue.txt
755925	search.twtxt.net.txt
654717	prologic.txt
394380	jlj.txt
371632	assets.txt
246520	off_grid_living.txt
243953	mckinley.txt
225256	www.uninformativ.de.txt
225256	uninformativ.de.txt

cnbeta-com-rssding-yue.txt seems to be a syndication feed for https://cnbeta.com/ in twtxt format, assets.txt is @maya@maya.land, and the rest are fairly self-explanatory.

⤋ Read More
In-reply-to » Testing something... https://txt.sour.is/external?uri=https://example.com/~foo/twtxt.txt&nick=

For people using clients other than yarnd, does that appear as a valid mention? It’s valid according to the spec but I’ve never seen it in use anywhere.

Mentions are embedded within the text in either @<source.nick source.url> or @<source.url> format and should be expanded by the client, when rendering the tweets.

cc @movq@www.uninformativ.de @lyse@lyse.isobeef.org

⤋ Read More