nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5, I believe auto-purge happens when the app enters background mode (which I believe might not happen if the user is in low power mode)

In either case, nostr:npub1g7j38pndthqgguqjft6zdgccqfhc0xvwgudpgtjyr5p8kdw7t4sqpqlqqt reported that he cleared cache completely and it only went down from 27GB to about 17GB, so something else must be consuming a significant chunk of storage. nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s, do you think it’s possible that NostrDB could get that big?