any particular areas I should focus on improving implementation? always appreciate feedback

Reply to this note

Please Login to reply.

Discussion

IndexDB was 1gb in 3 days. Not sure what it's caching, but it starts to drag on the browser fast. If I delete the app data it goes back to operating smoothly for a while, but doesn't take long before 100s of mbs are back in the db. It also has my CPU fan running hard. Thanks.

haha i'm releasing an update rn that trashes indexeddb

Cool. Looking forward to it! I really like the app it's just a drag on the browser due to resource usage.

wow. what does it use now?

non persistent browser memory. so loads all your stuff every time. really wanted to make persistent indexeddb work but its too slow.

good idea!

That's what I'm doing. Minimal localStorage use but mostly just non-persistent structures and letting the relays do most of the work. It's makes things run much faster.

can you print version somewhere so we can understand an update happened?

hmm sure, not a bad idea.

can't wait for this. it should improve so much.

its live. but you need to clear your cache storage for images to get served correctly.

thank you