Iā€™m playing with ratterplatter again: Itā€™s a toy that watches disk I/O and emulates the noise of a real hard disk. (Linux only.) It uses sound samples from one of my older disks.

I tried a different approach at estimating the disk activity and I think I finally got it right (after almost 10 years ā€¦ šŸ¤¦).

Demo, booting a Windows 2000 VM: https://movq.de/v/1400544cc6/2kboot-ratterplatter-2.mp4

(For this purpose alone, I put a couple of mini speakers into my PC case, so that the noise comes from the right place: https://movq.de/v/a3b2dc0932/speakers.jpg)

The results arenā€™t too bad, but this thing canā€™t be super accurate due to the huge I/O caches that we have these days. For the video, I dropped the caches before booting Windows, otherwise you would have heard almost nothing.

FWIW, if you donā€™t know it yet, this is the equivalent for proper keyboard sound: https://github.com/zevv/bucklespring


#hot22xa

(#cs6lodq) @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.


#qqhnmpq

šŸ‘‹ 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! šŸ™


#j6ofzfq

(#hv7xxjq) 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.


#hr7w2nq

(#gyneajq) 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.


#mdwykfa

(#lnrgahq) @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?"

šŸ¤”


#zmhpw7q

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 šŸ§


#tk53fqa