![](https://sh.itjust.works/pictrs/image/fcd7fc91-dc12-4a46-b597-e36965cdebad.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
I had fully understood what you wanted to mean, even though phrased badly. However the reason I quoted it is because of how contradictory is your thought process.
I had fully understood what you wanted to mean, even though phrased badly. However the reason I quoted it is because of how contradictory is your thought process.
I personally blocked it because I want to talk to everyone on lemmy
Genius
There is literally no reason to hardcode the ads in the game. They need a placeholder that will show ads fetched from an API, like Google ads. The ads will always be up to date and targeted
There is literally no reason to hardcode the ads in the game. They need a placeholder that will show ads fetched from an API, like Google ads. The ads will always be up to date and targeted
There is literally no reason to hardcode the ads in the game. They need a placeholder that will show ads fetched from an API, like Google ads. The ads will always be up to date and targeted
And the “would of” thing
Isn’t every reinstall an opportunity for changes?
This is not correct. Your browser will submit “shark” and then the backend server will do whatever hashing is required and after that it will compare the hashes. If hashing was happening in the browser that would mean that an attacker would be be able to attack by using just the hashes of the passwords, not the passwords themselves. Also in such case, the browser would had been responsible to do the required salting which in turn would make it pointless as it would had been known.