Huh. I had long forgotten about text fragment URLs. Seems relevant for linking to discussions around linking to individual twtxt posts. https://alfy.blog/2024/10/19/linking-directly-to-web-page-content.html

New post (mostly follow-up on the previous with a few new points) on the twtxt v2 discussion. http://a.9srv.net/b/2024-10-08

This is only first draft quality, but I made some notes on the #twtxt v2 proposal. http://a.9srv.net/b/2024-09-25

I've added myself to the registries at registry.twtxt.org and twtxt.tilde.institute. I wonder if there's a list of registries. #meta

Huh. At some point, my twtxt-via-ssh shortcut from my phone stopped working. It does again now! I've changed nothing. Yay black boxes! 🤷🏻

One of the frustrating parts of using twtxt for conversations is the URLs are, well... ugly. Anyone (like y'all yarn folks) looked at using webfinger for translating user@domain accounts to URLs?

I realized my twtxt client isn't validating what it pulls once it gets a valid response when a domain started returning js-heavy parking pages for every URL. Oops. Weekend project, I guess. 🤦🏻

@adi Also, I noticed you followed me on Twitter, but you might enjoy @anths if you want techie stuff instead of Oregon politics. 🤣

@jlj I like your website's look, but i was disappointed to find that 'finger' doesn't seem to actually work. ;-)

First pass at sticking my twtxt in a web page. It's not escaping all the html properly, and generally needs work, but it's a start: http://a.9srv.net/tw/following.html

I am very excited about this, and it seems like something the twtxt crowd might enjoy: https://anewsession.com/

@prologic Bug in your profile links: it's repeating a segment. For example, your face tries to get to https://twtxt.net/user/https://twtxt.net/user/prologic/twtxt.txt

@xjix Saw your oldish note about wanting an offline/async twtxt workflow. Do you have something that works for you? My (very young!) client was designed with that in mind.

I'm unclear if I'm going to do the twtxt.net discovery protocol; neither my web server nor Plan 9's default capture agent strings. :-/

My silly Plan 9 rc twtxt client now has a web page: http://txtpunk.com/tw/index.html

@prologicYes, I think tags should just be #foo, and let the client figure out searching if it cares.

@lyse Yes, I often read the raw messages. But more to the point, the simplicity of the format is the bulk of the appeal.

@movq No argument that threading is an improvement. But I think (#hash) does that, and I think figuring out how to search should mostly be up to the client.

Hah... my silly twtxt client now has "stories" mode.☺

I don't think I'm implementing twtxt.net-style hashtags (for now?). The "" is bad enough for nicks, but they just make the plain text unreadable.

@prologic I've just never had it be a rewarding experience.

@prologic rc, the Plan 9 shell.

Well, my twtxt reader is a bit too simple; drops who actually wrote the message before it's printed. 🤦🏻

Okay, my #twtxt reader works-ish. Need to properly deal with timezones (and, um, maybe do any error checking).

I have a working model for the reader portion of what I want this twtxt client to do.