Had to manually download my entire library (5 items at a time with no useful labels) before requesting account deletion. I’m glad they’re making account deletion easy, but disappointed that it had to go.
Had to manually download my entire library (5 items at a time with no useful labels) before requesting account deletion. I’m glad they’re making account deletion easy, but disappointed that it had to go.
Do you know what a chosen-plaintext attack is?
So, no. Got it.
Based on just your comments here, you have no right to judge anyone else’s intelligence.
I think I can run strings through the same visual hash until I find a match, but you do you.
Emails have two known symbols in them, the ‘@’ and the ‘.’, and you’ve said what two blurs you used. I would have called it a birthday attack myself (where the blur steps are the encryption key and depends on letters roughly blurring differently, aka hashing differently).
Of the people here they’re not the one showing what they don’t know
Aaaaaaaaackthually… You do not need a dot. Putting an MX record on a TLD is perfectly valid. Though pretty much 100% of all email validation forms are doing it wrong and requiring it. So in this case it almost certainly has a dot.
Oh what’s technically valid as an email is insane. I’ve looked into it before for work and went “nope” and just grabbed one of the standard “wrong” regexes everyone uses.
Yepp, the spec is super weird and too complex. Like @ is allowed if quouted in the local part.
Almost no one has a MX on TLD though so most just reject it, you can also argue that it is a good thing to check for. If someone writes “gmail”, they really just forgot the .com part so having the UI warn about it makes sense.
The best way to validate is to send an email to it.
You’re saying that this is reversible when you don’t know any of the parameters?
Have fuckin fun proving that.
Bet, post your credit card info and I’ll put in the effort