@xuu@txt.sour.is 👍🏻

@bender@twtxt.net nope.. its causing OOM issues currently.

Bad Wimpfen has a pretty cool old town with timber framed houses. Looks really beautiful: https://lyse.isobeef.org/bad-wimpfen-2025-03-28/

@prologic@twtxt.net is it up? How can we tell?

@thecanine@twtxt.net I found it! This looks like colored easter eggs when squinting.

There’s a secret art easter egg thing, hidden on my website ( https://thecanine.ueuo.com ), for this years April fools event - it’s been there for a few weeks, but now I can finally give hints.

Okay trying SqliteCache again with a slight tweak. I might have to rethink the hard-coded LIMIT 50.

Going back to old MemoryCache for now and going to bed 🛌

Hmmm this needs a bit more work.

And we’re back. On the new Sqlitecache 🥳

@kat@yarn.girlonthemoon.xyz They all just wanted to be friends with a cool gal like you. ;-) It’s sad that putting things openly on the internet just waits to be raided by script kiddies, bots or spammers eventually.

Ooops I ran a docker build on one of my production nodes (the ingress node) 😱

@movq@www.uninformativ.de Yeah, like nearly all of them. There is the so called Bannwald, where it typically is not allowed to log, but there’s only one in my entire county and I haven’t even visted it. I should change that. https://de.wikipedia.org/wiki/Bannwald

@bender@twtxt.net Okay 👌

👋 Folks that use this pod, I’ll be rolling out an experimental new caching backend to this pod shortly. Stay tuned. Please provide feedback either here via Twtxt or on IRC. Thanks! 🙏

@movq@www.uninformativ.de Hahaha, geil! :-D

@movq@www.uninformativ.de Haha, that’s cool! :-D

@movq@www.uninformativ.de That’s really great! I can’t tell the difference to the original. :-)

I see nothing wrong with the “implications”. I would call them features. I think this will be the best thing that happened to Yarn since the subject extension.

There are however a few implications to note:

• It will be possibly to page through much larger quantities of twts per feed, this is potentially unlimited (depends on disk space)
  
• Automated Feeds (bots) like @tiktok@feeds.twtxt.net will now behave/display very differently. You will see all it’s historical Twts, whereas before you’d only see the one because the MemoryCache’s behavior was to “replace” Twts.
  

I’m hoping everything else remains the same and true to what we’ve collectively built and to spec. Replies work, Forks work, various views, filters and so on still work. I’m developing this new cache in a way that uses a “delegate” pattern and a double read / double write with metrics so I can over time see that none of the “old cache” is used anymore.

I think my new SqliteCache is almost ready for prime time 🤞

This is why I blocked entire ASN(s) 🤣

Tom Waits in 2025 looks and sounds exactly like you’d expect. 🥴

Registry format is its own thing. It takes the regular feed and appends nick \t uri \t to it. Its something that existed before yarn got big. There is still a bit of work but I will put together a ui for it to make it easier to view and navigate.

@bender@twtxt.net Soon 🤣

@bender@twtxt.net Yeah me too hmm 🧐

@prologic@twtxt.net I noticed that the hash also shows (as in clearly visible) on the “in-reply-to”. That doesn’t happen with any other client—well, at least not with Yarn, nor jenny.

@prologic@twtxt.net show, or it didn’t happen. 😜

@eapl.me@eapl.me@eapl.me@eapl.me Ahh I see 😅

@xuu@txt.sour.is Got the most basic view working 😅

@xuu@txt.sour.is Actually… I’m working on a new Sqlite backend/cache for yarnd 🤣 I might revive yarns (the crawler / search engine) one day 🤞

@eapl.me@eapl.me@eapl.me@eapl.me What’s with your client not using the proper syntax for mentions?

$ bat 'https://twtxt.net/twt/lnrgahq' | jq '.text'
"(#4xaabhq) thanks @prologic! 
@bender the idea of the RFC was to reach an agreement on a difficult problem, receiving proposals, and the voting is a simple count to gauge the sentiment of \"is this a problem worth to be fixed?, are we committed to implement a change in our clients?\" 

But that's a fair point. What do the community expect? What do y'all expect?"

🤔

@eapl.me@eapl.me I am currently working on Implementing a registry that is also a crawler. It finds any feeds that are mentioned or in the follows header.

https://watcher.sour.is/api/plain/twt

https://watcher.sour.is/api/plain/users

I think @prologic@twtxt.net is also working on one.

thanks @prologic!
@bender the idea of the RFC was to reach an agreement on a difficult problem, receiving proposals, and the voting is a simple count to gauge the sentiment of “is this a problem worth to be fixed?, are we committed to implement a change in our clients?”

But that’s a fair point. What do the community expect? What do y’all expect?

I wonder if I can do away with the followers follows mutes tables and expect the client to actually filter Twts appropriately before Display? This would simplify the SqliteCache considerably and also mean it would be agnostic of single-user or multi-user as that’s delegated to another layer. Hmmm 🧐

Whoohoo! 😇

Ehhh yeah, what could go wrong 🤔 😵‍💫

hmm i need to start storing feed preambles so i can capture metadata like that

@bender@twtxt.net I never implemented it actually. That’s why we have the # refresh = metadata field for those that yell loudly enough can add to their feeds. Otherwise yarnd uses WebSub between pods and is fairly dumb. I could never find an “intelligent” way to back-off without hurting freshness.

Interesting.. so running into an issue where queries only return a partal set of rows if i run in a docker image built from scratch. i have to add the debian root image for it to work. I wonder what file is missing that the root has?

@eapl.me@eapl.me@eapl.me@eapl.me Done

@eapl.me@eapl.me other than getting a pseudo tally, what else do you aim to accomplish from this? That is, what is the tangible expectation?

For anyone following the proposals to improve replies and threads in twtxt, the voting period has started and will be open for a week.
https://eapl.me/rfc0001/

Please share the link with the twtxt community, and leave your vote on your preferred proposals, which will be used to gauge the perceived benefits.

Also, the conversation is open to discuss implementation concerns or anything aimed at making twtxt better.

@movq@www.uninformativ.de Hah I used to be a heavy mpd user myself once upon a time 😅

I’m a long-term mpd user (some 16+ years), but for $reasons I have to compile it myself now – and, boy, that is one heavy program. Takes several minutes to build. 😳