I do this on my website with paywalled information. It respects upper/lowercasing and spacing but randomises each character. Anyone can disable the CSS blur but the data is still obfuscated.
This reminds me of Manning liveBook's obfuscation strategy [0]. It scrambles the letters to keep the majority of the specific details obfuscated while somewhat revealing the gist (word length, acronyms, anagrams, code segments) presumably to encourage sales and discourage piracy.
Potentially leaking names by giving out number of letters in name and surname? Just wondering. If so, consider killing or randomizing spaces and letter count.
I created this browser extension to solve a personal annoyance. It automatically removes obnoxious prompts on websites that interrupt your reading, like prompts to sign up or enter your email address, overlays with discount offers, pointless GDPR and cookie consent banners, etc.
It's in early development and doesn't work on most websites, yet. The aim is to build up a comprehensive set of rules over time to block modals anywhere. Creating your definitions is easy and can be done from within the extension. The project is open-source and I'm looking for contributors!
This is a different issue. You ran out of IDs for your row identifier. The PostgreSQL issue is that every transaction has an ID; normally this is a fairly invisible internal thing you don't need to worry about, but in some edge cases this transaction ID can causes problems. You could, in theory, run in to this issue with just one row.
I don't know how MySQL or MariaDB handles this; AFAIK it doesn't have this issue.
We finally ported Wappalyzer across to Safari. The process was fairly straight-forward but Safari doesn't implement every API that Chrome, Firefox and even Edge support, so we had to do a bunch of work to get a single version of the extension to work consistently in all four browsers. I'm glad it's finally here though.
https://youtu.be/5UuFqQXWneM