nothing is for sale

@bender@twtxt.net So true 😥

@javivf@adn.org.es Welcome indeed 🤗

@prologic@twtxt.net that’s you, and me, and some others. Sadly, though, a huge majority (I don’t have sources, or numbers, but “trust me, bro” :-P) will simply, gladly, and unapologetically, pirate.

@eldersnake@we.loveprivacy.club Same!

@prologic@twtxt.net Fully agreed. I’m far more likely to buy such mediums when DRM-free. I never go near Amazon eBooks etc because of their lock-in, and I have a Kobo eReader which needs to have the books side loaded unless directly from the Kobo store. I prefer DRM-free files every time.

@andros@twtxt.andros.dev That’s a shame. But here’s the thing about piracy. If I could download a PDF or MP3/OGG of a Book I’d happily pay for this. If I could download an MP3/OGG of some Music I would pay for this. If I could download an MP4 of a Movie I would pay for this.

The reason piracy exists at all is economics and greed. If you make something affordable and convenient, there’s no need to steal.

I have just received the royalties for the last book: 98 euros for the four-month period, about 24 euros a month on average. Not even enough for the gym membership.
If you have to keep some knowledge: don’t write for money, the paper (or ebook) industry is in a very bad way, the margins for the author are very small and piracy is devastating.

@lyse@lyse.isobeef.org 🤣🤣🤣

@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/

Image

@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) 🤣

Image

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.

Image

Image

Image

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

Avec l’aide de Péhä, j’ai amélioré ma collection de logos #solarpunk. Merci! https://si3t.ch/misc/solarpunk/

@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 🧐

Image

Whoohoo! 😇

Image

Image