Yeah cookies aren’t needed for any of the site we pull files from. (ftr ravenjs helps us track client side errors that happen)
The unfortunate thing with “blocking cookies” is there isn’t a separate setting “allow local storage”, which is where we keep all that stuff 
blocking cookies but allowing the browser to store data for the site (but not send it back to the server for tracking) would totally work in our case… but browsers lump the two things together. (Understandable since if you can remember anything you could just send the server some tracking data manually… but still, it’s annoying for sites like ours where we just store a bunch of stuff like settings and cached data, and don’t care at all about tracking).
Anywho, it’s somewhere on the todo list to support setting defaults for all those things that are currently set on a per-browser basis… just hasn’t raised to the top of the todo list yet.