That reminds me, I need to update yarnd too. I haven’t done so yet 😅 Been so bloody busy with work 🥵

@movq@www.uninformativ.de I really like your style of writing, btw. It’s much calmer and less aggressive then mine. :-) When I turned my bullet points into paragraphs, I got a bit mad in the process.

Sure, feel free to include anything you want. Regarding citing, this is where twtxt falls short in my opinion. Especially with feed rotation, classic links die quickly. Message hashes only help so much. Nobody outside the twtxt universe knows how to deal with them. So, not perfect for inclusion on a web page. Linking to a thread or message on some yarnd instance might be the more user-friendly option. But the disadvantage is that it’s “just” a mirror, not the primary or original source. In all reality, this could be considered splitting hairs, though.

I should have probably written a proper article. That would have given me time to review the result more carefully, too. ;-) Perhaps that’s something for the future. But honestly, I’m not sure if I really want to waste my time and energy on that subject. So many other fun or useless things come to mind right away that I could do instead. 8-)

So, yeah, do whatever feels best to you. I don’t mind being cited or linked, but I also don’t mind not to be cited or not to be linked to. :-D Not a helpful answer, I know. Sorry. ;-) But anyway, thanks for asking, mate! I do appreciate it.

To finish my thought, linking to my frontpage is probably also useless, since I deliberatly do not have a table of contents there. In fact, my entire frontpage is rather silly.

@lyse@lyse.isobeef.org yes, yarnd has a few parser (?) issues that were never resolved. If only a powerful token predictor could fix it, once and for all… 😅

@yarn_police@twtxt.net Looks like the rendering in yarnd is off. The second subject (prisoner error!) was robbed, its link text got stolen.

@klaxzy@klaxzy.net yarnd/*

@bender@twtxt.net Hahaha! I was also very surprised to see snow. I didn’t remember that at all. It was gone by the evening again, see archive feed twtxt-2024-11.txt#2024-11-23T18:30:00+01:00. Unfortunately, neither Prologic’s nor Xuu’s yarnd searches yield anything. That message has probably long fallen out of the index.

@rdlmda@rdlmda.me

Replies aren’t actually broken, I just… need to add myself to the follow list?! That’s quite counter-intuitive and (IIRC) not mentioned in the docs. But… It seems to be working now, which is nice (I still don’t know how webmentions and webfinger works, so can’t speak about this so far)

yarnd (what runs here at twtxt.net) actually does this automatically by default. I think it’s just an implementation detail to be honest. There’s nothing about this in the specs over at https://twtxt.dev

@bender@twtxt.net Fixed 🤣 Nobody was following that feed 😅 yarnd had no reason to “pull” it in.

@bender@twtxt.net I was even there when yarnd had the bespoke ActivityPub feature, I didn’t like it then, much less now, even if it’s separate

# $YakumoLabs$
# yarnd service file for https://github.com/davmac314/dinit
type = process
command = /usr/pkg/bin/yarnd -b 127.0.0.1:6446
env-file = /usr/pkg/etc/yarnd.conf
working-dir = /var/db/yarnd
restart = on-failure

Btw, @shinyoukai@neko.laidback.moe, that’s a super cool logo on your yarnd. I like it a lot!

It just doesn’t look aligned properly: Could be a yarnd issue, though, it might not expect a logo this large. Just wildguessing, no idea.

@lyse@lyse.isobeef.org packaging yarnd wasn’t that easy after all, I also apparently have to patch some things over and supply the minified assets some way or another

The YAML forbidden knowledge of yarnd

I have to say. A well designed Hypermedia Driven Web Application such as yarnd‘ using HTMX is just as good, i'd not better, than one written in React.

cat /etc/mokou/yarnd.conf
exec=/usr/pkg/sbin/daemonize -c/var/db/yarnd -u www -p /var/run/yarnd.pid /usr/pkg/sbin/chpst -e /usr/local/etc/yarnd /usr/local/sbin/yarnd -b 127.0.0.1:[classified information]

I know this might seem a bit overengineered, but the previous command until now had the secrets exposed on the process list

Alright, this yarnd installation has been properly fixed.

Obviously yarnd 🙋‍♂️

@arne@uplegger.eu @lukas@lukasthiel.de In fact, Yarn.social’s yarnd client implementation actually uses (or did, still kinda does today) PicoCSS 🤟 It was/is a good CSS library! 👍

@lyse@lyse.isobeef.org @bender@twtxt.net that’s also what Yarn.social’s logo is, and just happens to be the yarnd default. Hmmm figured times for a change? 🤔

technically I can put the Bridge verificaiton code in my feed’s metadata so no-one really ever sees or notices it 🤔 Maybe I’ll add a first-class button/field thingy in yarnd so users can “register their feed” straight from their pod? 🤔

Hmmm, looks like my twt hash algorithm implementation calculates incorrect values. Might be the tilde in the URL that throws something off. :-? At least yarnd and jenny agree on a different hash.

Hmmm all these tilde.club feeds have no # nick and is messing with yarnd’s behavior 😅

@zvava@twtxt.net yarnd fetches the feeds roughly every ten minutes:

grep twtxt.net www/logs/twtxt.log | cut -d ' ' -f1 | tail -n 20
2025-10-04T07:00:45+02:00
2025-10-04T07:10:26+02:00
2025-10-04T07:22:43+02:00
2025-10-04T07:30:45+02:00
2025-10-04T07:40:48+02:00
2025-10-04T07:52:59+02:00
2025-10-04T08:00:07+02:00
2025-10-04T08:13:33+02:00
2025-10-04T08:23:13+02:00
2025-10-04T08:31:22+02:00
2025-10-04T08:41:29+02:00
2025-10-04T08:53:25+02:00
2025-10-04T09:03:31+02:00
2025-10-04T09:11:42+02:00
2025-10-04T09:23:11+02:00
2025-10-04T09:29:49+02:00
2025-10-04T09:36:17+02:00
2025-10-04T09:46:33+02:00
2025-10-04T09:58:40+02:00
2025-10-04T10:06:54+02:00

I suspect that the timing was just right. Or wrong, depending on how you’re looking at it. ;-)

@prologic@twtxt.net I can’t upload a screenshot (tried, but Yarnd simple “ate” my reply). See https://zsblog.mills.io/posts/hello-zs-blog.html. Is has no date/time on it.

@zvava@twtxt.net And yes yarnd does have a well documented API and two clients (CLI and unmaintained Flutter App)

Wanting to add, this isn’t a twtxt client. It is Yarnd on steroids! 😂

@zvava@twtxt.net The first version of what is now yarnd was built over a weekend 😀

@eric@itsericwoodward.com Name change is no worries! 😉 Interesting/funnily enough my client yarnd seems to have picked it up automatically which is nice (I’ve historically always had a few bugs to iron out there 🤣)

@itsericwoodward@itsericwoodward.com Also just a heads up, GIF(s) aren’t supproted as an Avatar type on yarnd (what runs twtxt.net). I’d change this to something that’s more supproted like PNG, JPEG, etc.

yarnd supports webmentions??? that’s awesome!

@nghialele@nghia.im it’s great to see another Yarnd pod in the wild. Welcome!

@sorenpeter@darch.dk you wrote:

“This might even be backward compatible with older (pre-yarn) clients.”

Yarnd is as backwards compatible with older clients as this. I dare to say, even more so. 😅

Going to try and few up a few more UX bugs today with yarnd.

@prologic@twtxt.net Lol I totally forgot about this. I will put it on my todo list

I wonder if this twtxt will kick Yarnd into working again. There is only one way to find out, right?

@prologic@twtxt.net done! hey i got a question, you got any clue why my feeds aren’t updating? maybe it has to do with the new cache flag but i messed with that a bit and didn’t notice a difference. basically it’s like i have to manually restart yarnd to see new posts it’s really weird lol

After yarnd v0.16 is released and the next round of specification updates are done and dusted, who wants me to have another crack at building Twtxt and activity pub integration support?

i don’t think it’s normal to have to restart my yarnd instance every time i wanna see new posts right

@prologic@twtxt.net I have:

• jenny
  
• buckket’s original (patched, or not)
  
• tt/tt2
  
• Timeline
  
• Twtxtory
  
• Yarnd

I will be adding the code in for yarnd very soon™ for this change, with a if the date is >= 2025-07-01 then compute_new_hashes else compute_old_hashes

@bender@twtxt.net Hehe good sleuthing 🤣 I swear it was an edit ✍️ Haha 😂 yarnd now “sees” both every single time, where-as before it would just obliterate the old Twt, but remain in archive. Now you get to see both 😅 Not sure if that’s a good thing or not, but it certainly makes it much clearer how to write “code logic” for detecting edits and doing something more UX(y) about ‘em 🤔

Interesting edit observed by the new yarnd powering this pod twtxt.net 🧐

Today I added support for Let’s Encrypt to eris via DNS-01 challenge. Updated the gcore libdns package I wrote for Caddy, Maddy and now Eris. Add support for yarn’s cache to support # type = bot and optionally # retention = N so that feeds like @tiktok@feeds.twtxt.net work like they did before, and… Updated some internal metrics in yarnd to be IMO “better”, with queue depth, queue time and last processing time for feeds.

@prologic@twtxt.net well, this fork will work. I an fork this one with jenny, not so with Yarnd.

$ bat https://twtxt.net/twt/edgwjcq | jq '.subject'
"(#yarnd)"

hahahahaha 🤣 Does your client allow you to do this or what? 🤔

Bahahahaha 🤣

@bmallred@staystrong.run Hehe, @bender@twtxt.net is gonna be upset with you for “making up a thread/subject” 🤣

@prologic@twtxt.net Nice! Everyone should be excited 😀

Interesting factoid… By inspecting my “followers” list every now and again, I can tell who uses a client like jenny, tt or any other client where fetches are driven by user interactions of invoking the app. What do we call this type of client? Hmmm 🤔 Then I can tell who uses yarnd because they are “seen” more frequently 🤣

First draft of yarnd 0.16 release notes. 📝 – Probably needs some tweaking and fixing, but it’s sounding alright so far 👌 #yarnd