How Safe Browsing Works in Firefox

The answer is right there in the sentence you quoted: "to protect the service from abuse". How that's supposed to work (i.e. how cookies are supposed to protect against abuse) is another question.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1109475

They are cleared the same way as normal cookies: they are visible in the cookie manager where they can be manually deleted, and they are generally included in all of the other cookie-clearing mechanisms.

You can find out more about the ways to control cookies in Firefox here: https://feeding.cloud.geek.nz/posts/tweaking-cookies-for-pri...

In that case of SafeBrowsing however, as noted in the article, for those URLs whose hash prefix doesn't match one of the hashes on one of the blacklists, the browser doesn't contact any other server. Only when there's a partial match does the browser ask for a full hash from the SafeBrowsing server.

Source: I'm a Chrome SafeBrowsing engineer.

Google has published the protocol that clients need to follow to fetch updates from the SafeBrowsing servers here: https://developers.google.com/safe-browsing/developers_guide...

Both Chrome and Firefox implement that protocol. I believe Edge uses Microsoft's own service. Not sure about Opera.

In short, it says that the prefix set uses less memory than a bloom filter.