hydroptic

Which example do you mean?

If you meant my user ID example, you'd prepopulate the bloom filter with existing user IDs on eg. service startup or whatever, and then update the filter every time a new user ID is added – keeping in mind that the false positive rate will grow as more are added, and that at some point you may need to create a new filter with a bigger backing bit array

That's definitely not what they're most useful for. I mean, you probably can use a bloom filter for implementing spell check, but saying that's where they're most useful severely misses the point of probabilistic set membership queries.

Bloom filters and their relatives are great when you have a huge set of values – eg. 100s of millions of user IDs in some database – and you want to have a very fast way of checking whether some value might be in that set, without having to query the database. Naturally this assumes that you've prepopulated a bloom filter with whatever values you need to be checking.

If the result of the bloom filter query is "nope", you know that the value's definitely not in the set, but if the result is "maybe" then you can go ahead and double-check by querying the database. This means that the vast majority of checks don't have to hit that slow DB at all, and even though you'll get some false positives this'll still be much much much faster than having to go through that DB every time.

Do you want to learn about probabilistic data structures?

• maybe
• no

Which is why I said to contact the German DPA

Sure! This page has some general info: https://gdpr.eu/cookies/

The directive itself is kind of involved because it goes pretty deep into what its aim is and eg. what sort of information can be considers an identifier, and it's actually quite well argued and worth a read if that sort of thing is your, er, thing: https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX%3A32002L0058 (you need to scoll aaalll the way down to be able to show the body text). I had to deal with this stuff professionally when I was a CTO for a company with some stricter than average privacy requirements due to the field, and I was pleasantly surprised to find out how much sense ePrivacy and GDPR actually make

At least here in the EU the ePrivacy directive and to a lesser extent the GDPR generally require that cookies have a limited lifetime depending on their function, to eg. prevent companies just attaching a stable identifier to every random passerby essentially forever. @[email protected], if you're feeling particularly mildly infuriated you could email the German Data Protection Authority, there's a good chance the cookie could attract the Eye of Sauron

And the devs hate the real fans of the game and implement features only to spite them

You're surprised that gAmErS are complaining about something?

Something being ancient and irrelevant tdoesn't stop a lot of companies.

“Ethnically cleanse,” he said at one point, summing up his idea for a city purged of Blues (this, he says, will prevent Blues from ethnically cleansing the Grays first).

Conservatives are incredibly fucked up. They can't fathom coexisting with people who aren't like them without wanting to "ethnically cleanse" them, so they naturally assume everybody else thinks like this as well

MIT license too, huh. I was sort of expecting a more restrictive one because, well, Microsoft and IBM

lol tell us another one