Is this issue already known by the developer ? Not just in this instance, but in some of the lemmy instances as well with the size cookies going crazy
Before this upgrade, the cookie on this instance was about 89 B. What’s going on ?
Is this issue already known by the developer ? Not just in this instance, but in some of the lemmy instances as well with the size cookies going crazy
Before this upgrade, the cookie on this instance was about 89 B. What’s going on ?
Looking through the (Firefox) devtools, there is only one cookie (being my login token), but a fair bit of cached images (and IndexedDB data for managing said cache), which is what I assume most of that size is.