throwawayReply

You're very much not alone, this comes up frequently here at hn, because other sites also frustratingly block this behaviour often by popping up "tweet this" links after highlighting.

> a nation where 99% of people shit in simple holes in the ground

Now that is propaganda.

It's interesting how you still observe the doppler effect even though the road isn't moving.

Did it actually raise 660m or was that the size of the "market cap" when it collapsed?

if I sell 100 tokens for a dollar then convince someone to buy 1 token for 10 dollars, if I run off with the money I've not run off with $1000 even if it feels like it for the people left with tokens.

Right, and what if those connections are burned into an immutable data source through the connection event in your event sourcing?

That is what this article is about, and methods to deal with that.

The UK has had data protection laws for years, people aren't scared of GDPR because it finally provides laws, they're scared because they actually look enforceable.

1. A fingerprint is something you cannot change, cannot revoke if leaked and cannot be unique across different sites.

2. A fingerprint hash isn't a cryptographic hash because you need to be able to match to nearby matches. A small variation in input needs to have a small variation in the hash so a distance function can be applied.

Those are terrible properties for a password.

I'm not familiar with firebase, but am I reading correctly that rules cascade but without specificity rules?

How does cascading make sense at all if lower-down rules don't supersede higher rules?

I was trying out the javascript example, but managed to get a case where there is a negative conclusion but this goes against the introduction where it says negative conclusions are always definite.

My multiset was:

   a, b, c, d, e, f, g, h, j, abc, def, asd, asds, 3g46stb6vy6vsyosyvosfsdfsdsah, oooooooooooooooo

Then trying oooooooooooooooo a second time, the bloom filter correctly says it might be in the set. The cuckoo filter says it is not.

I assume this is just a javascript bug in implementation, because previously the filter said it might be in the set, actually adding it to the set then gave a false negative when trying it again.

There's a "Same-Site" cookie flag that helps prevent CSRF by preventing cookies being sent in that scenario. Can the browser be made to treat all cookies as "same-site" for a quick 'fix' to this issue?

Obviously this would need a white-list (and a pair<from,to> whitelist, not just "this domain is OK list) to allow SSO scenarios.

That makes it sound like people are upset about an isolated incident, trying to play this off as an isolated incident is going to blow up very badly as people "discover" just how much of their data is everywhere, whether they gave permission or not this isn't about a single breach.

You should be using Aurora not Nightly for those features.