@kate@yarn.girlonthemoon.xyz @eldersnake@we.loveprivacy.club @abucci@anthony.buc.ci – I’ve already spoken to @xuu@txt.sour.is on IRC about this, but the new SqliteCache backend I’m working on here, what are your thoughts regarding mgirations from old MemoryCache (which is now gone in the codebase in this branch). Do you care to migrate at all, or just let the pod re-fetch all feeds? 🤔

ping? 🏓

@prologic@twtxt.net give it some time. Twtxt is very asynchronous, and travels at the speed of mules. It might take a while to reach the intended destination. 😅

@abucci@anthony.buc.ci Apologies, the basic summary is as follows:

• Decided to rewrite the cache backend.
  
• It will now be a SQLite backend going forward.
  
• I’m planning on no data migration.

I don’t think I’d personally be worried about migrating, just re-fetch. Sounds cleaner anyway?
Sorry I’m late to the party!

@eldersnake@we.loveprivacy.club No worries! 👌

@prologic@twtxt.net hm would there be any loss with the re-fetch option? i wouldn’t mind either but i’d like to hold onto what i got if possible! but if it IS possible but also really annoying to do i’ll just do the re-fetch of feeds because i’m lazy af LMAO

@kate@yarn.girlonthemoon.xyz The re-fetch should work just fine 🤞

@prologic@twtxt.net alright! i can try that… whenever i am capable of upgrading and figure out how to lol

@kate I’ll cut a release soon™, but still a few more things to iron out 🤣 One of the new challenges is figuring out what to do with the “Discover” view now that is has an unconfined limit, on my pod (at least) it’s now basically just “noise” 🤦‍♂️

@prologic@twtxt.net best of luck!!! discover view having no limit sounds scary oh god lol