RandomX implemented in the browser with WebAssembly is awfully slow, like 10x slower than native, and if you add native RandomX to the browser, you will just get Coinhive back.
Instagram is the worst offender, I only want to receive message notifications, but I got notifications about inane random stuff I've tried to disable but it won't work. I ended up having to disable notifications altogether.
My theory is that they rate limit that URL aggressively due to AI scrapers. At this point it's faster to just clone the repo and do your searching locally.
What privacy? Whoever is watching your traffic can see you accessed their website with HTTPS, they can guess with high accuracy which article you are reading based on the response size.
I'm guessing you're not storing the CLIP for every single frame, instead of every second or so? Also, are you using the cosine similarity? How are you finding the nearest vector?
BitTorrent v2 uses SHA-256, but in any case SHA-1 is still second-preimage resistant. And the BitTorrent piece hashes are included in the .torrent file, so you would need to find a double collision.
I'm guessing if you only calculate based on the digits, the probability is going to be slightly different than the real one, because you only have a finite number of plates you can choose from.
This is not a hypothetical, people already do it like that in my country (Argentina), you send your money to a person that buys tokens using cryptocoins, since these websites don't comply with the local regulation, even kids are addicted to gambling.