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

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

@bender@twtxt.net Okay 👌