The passwords will not be of any use on any other system. This would eliminate password reuse.
Edit: also, if an attacker dumps all the data today then loses access to the data tomorrow, having access to my password hashes means they can access my account and data later.
This comment is an example of why I wouldn’t want any given website to choose my password.
I know periods don't count, supposedly, but I still get emails for someone with the same name as mine. My email is first.last, theirs is firstlast. I wonder how much of my stuff they get erroneously?
Yes, but one of those bad dependencies is the standard library.
The lie is almost always in an external API response from fetch (hence the complaint about “any” above).
> Could you provide examples?
Off the top of my head… Go’s stdlib json.Unmarshal and Rust’s Serde derive Deserialize.
I was misunderstanding your point with the deserialize.
Edit: “using” -> “uses”
Service workers are threads. They’re basically separate JavaScript processes you communicate with with IPC, with other special privileges and capabilities allotted to them.