Hi, its safari. And i just noticed that the extension isn't there no more?

you need to ask Apple for a refund, if that is what you want:
https://blog.supereasyapps.com/mac-app-store-refund-in-6-steps-how-to-get-a-refund-for-any-macos-app/

I have this fixed in v5.9.8 which is available on my servers now. hopefully the App Store version will be reviewed quickly

it does need to be running, but you can configure it to not show in the Dock.

that would be great if you could send me the crash log:
[email protected]

could you send me the crash log next time it crashes. you can also find previous crash logs here:
~/Library/Logs/DiagnosticReports/

[email protected]

are those Cache or HSTS cookies?
if so, you need to restart Safari for Safari to update correctly.

also, if you're on the Mac App Store version, make sure you have the latest version of the scripts. there was a change in Cookie 5.9.7 with better support for Safari 12.1:
https://sweetpproductions.com/products/cookie5/safari.htm

Ive just released v5.9.7 with the fix on my site, and also uploaded it to Apple for review.

thanks for the help in tracking this down and getting it fixed.

I found the issue with the HSTS cookies, its working on High Sierra, but is broken on Mojave. It should be fixed in the latest beta
https://sweetpproductions.com/products/cookie5/CookieBeta.dmg

v5.9.6.1
-attempt at fixing HSTS cache removal

https://sweetpproductions.com/products/cookie5/CookieBeta.dmg

are there tracking cookies in your blog?
if so, you most likely need to whitelist them:

pause any timers in Cookie login to your blog expand the domain in Cookie by clicking the small triangle look for any RED colored tracking cookies right click (control-click) on the tracking cookies select "Add to Whitelist" re-enable your timers

perfect!

Still hoping for Cookie to let us manage each Firefox profile separately, like it does for Chrome.

I think it hovers around 70Mb on my laptop? I can’t check right now, as it’s in getting serviced.

@alainlankers perfect!

Hi Russel - well, we can't whitelist all red cookies, right? Doesn't this defeat the purpose of cookie?

Also, I believe Safari history may be the source of these issues.

I always tell Safari to "clear history but keep website data." Even so, when I subsequently try to log into Twitter, Facebook etc. the websites often think I'm registering a new device

Yep, it just happened again. I did "clear history but keep website data" and suddenly Twitter can't recognize my device. I just whitelisted both "ga" and "gat" - are either of those cookies "tracking" cookies?

Hi Russell - still having issues, alas. : (