@bender@twtxt.net So true 😥

@javivf@adn.org.es Welcome indeed 🤗

@eldersnake@we.loveprivacy.club Same!

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

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 🥳

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

@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! 🙏

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

@bender@twtxt.net Soon 🤣

@bender@twtxt.net Yeah me too hmm 🧐

@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?"

🤔

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

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

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

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

@xuu@txt.sour.is I had a lot of trouble figuring out how to do this too 😂

Loved this so much I had to re-post it! 🤣

Image

@xuu@txt.sour.is LOL 😂

LOL 😂

Image

Image

:{:|:&};:

@bender@twtxt.net I gave up after page 4 (DuckDuckGo) 🤣

@bender@twtxt.net I tend to think of Twtxt like Email. It is truely decentralised. So therefore by design there really is no way to easily discovers others except through social interactions and a sort of “word of mouth” of human exchanges of communications.

@xuu@txt.sour.is no disagreements from me!

Wait! What’s going on?! 🧐

Yeah link please 🙏

@lyse@lyse.isobeef.org I think the community should be allowed to experiment mate 😅 Just make tt2 ignore such items in feeds and you’re good 👍

@eapl.me@eapl.me@eapl.me@eapl.me Yeah yarnd already filters/ignores them (for now)

It looks interesting but not enough for me to buy one 😅

@andros@twtxt.andros.dev This is cool! 😍 Migut just have to add support for this to see how it might work in yarnd 🤣

@movq@www.uninformativ.de Is that the cwrsion that still ran on MS-DOS?

@andros@twtxt.andros.dev Is this a book republished as a Markdown doc on GitHub or written that way?

@lyse@lyse.isobeef.org I’m in the banking industry, so don’t see this much🤣

@andros@twtxt.andros.dev Cool! Can I joking ciwtuau? 🤔

@andros@twtxt.andros.dev @lyse@lyse.isobeef.org ’s new client 😊

Unfortunately none of the content on the Wikipedia page for him really criticises much of his work. He must be really good at being a “businessman” and killing tech innovation 🤣

After working 14 years at IBM, he became senior vice president and chief technology officer at enterprise search vendor Verity in 2004.[16][14][12] In July 2005, he was hired by Yahoo! to lead Yahoo! Research in Sunnyvale, California.[17] At Yahoo!, he worked on research projects including search and advertising.[15][18] In 2011, he was appointed as Yahoo!’s chief strategy officer.[19]
>
In 2012, Prabhakar joined Google after severe funding cuts in Yahoo!’s research division.[19] In 2018, he was > put in charge of Ads and Commerce at Google and in 2020 his scope was expanded to include Search, Geo, and Assistant.[20] [21]
>
In 2024, he transitioned to the role of Chief Technologist at Google.[2]

@thecanine@twtxt.net I read this article and did some research. Wow! Amazing really how we can build really good tech, then kill it quietly all for the sake of more revenue and profits for shareholders 🤣

@movq@www.uninformativ.de It’s stupid that this is geo blocked right? 😂 Must be hmmm 🤔