@MennoWolff @nina_kali_nina
I have the solution if you're using a Chromium-based browser:
1: Navigate to `chrome://settings/content/siteData`
2: Set *Default Behavior* to `Delete data sites have saved to your device when you close all windows`
3: In *Customized Behaviors* -> *Allowed to save data on your device*, click on the “Add” button, and add every website you need, under this format:
If you don't know the cookies you need, `[*.]example.com`
If you know, `subdomain.example.com`.
@nina_kali_nina
I believe that:
1: Cookies are being used for absolutely everything
2: Cookies are not separated by necessity (as in login cookies being separate from everything else)
3: Even if those first 2 are accomplished, people are not given the choice to opt-out of cookies that aren't really needed.
Also, it's important to note that I'd have 600 MB of storage used by cookies, if I didn't setup my YouTube filter list
1/2
@nina_kali_nina
Here's my YouTube cookie list (I don't use an account there, but this lets me save storage without losing my recommended).
Assuming you've used my solution for Chromium-based browsers, navigate yet again to `chrome://settings/content/siteData`, go to the **Allowed to save data on your device** part, and add:
`consent.youtube.com`
`youtube.com`
Have fun! 😀
@thatonecoder @nina_kali_nina is that really just cookies, or also indexed db and local storage?
Here my cookies are just a few hundred kilobytes (not megabytes), but local storage is several megabytes, with some websites storing a lot of javascript code there, the worst one being wikipedia (3-5MB,duolicated for each language since they are hosted on separate domains)
@nina_kali_nina @thatonecoder 😨
Are cookies still plain text or am I horrifically behind?
Like, thirty megs of cache I can just about believe, loading all those pfp's and too-big images etc, but cookies? Sixty times lord of the rings just for hey this guy's logged in?
@nina_kali_nina @thatonecoder What is *not* wrong with it?
Honestly, I find myself repeatedly feeling that things are not much better than during the browser wars, now we also have features only a few browsers implement, and sites that don't really care about being portable (egregious examples include github, where it's now harder to run the interface, and you can't get download links even with JS enabled, unless your browser supports whatever feature they demand;
(multipost 1/2)
@nina_kali_nina @thatonecoder Mastodon (Web UI) 4.3 also started using features that narrow down the number of compatible browsers, not sure how that is now).
As for WHATWG standards, once the specification of fetch() was changed in a backwards-incompatible way, breaking sites. No versioning, no function name change...
But when the state of affairs starts reaching hundreds of megabytes for a single page load for a text article, something must have gone terribly wrong.
(multipost 2/2)
@thatonecoder @nina_kali_nina @MennoWolff
How are you calculating that? I just checked my browser and for the instance I am in I only see two cookies, one of 509 bytes and another of 237 bytes.
Out of curiosity I also checked the Local Storage and Session storage and it seems very little data is stored there. Definitely less than 500 KBs between the two of them.