34r45sdg

Its the continued advancing of the craft. Some newer techniques but an evolution of the attack. Now all one needs is a 20 Million qubit QC..

Probably for the best. Id like an internet free of ads. Oh, I have that already thanks to ad-blocking technology. This is more user hostile crap, get it off my internet!

Decentralized identity is not useful. Its a red herring. What we need is better decentralized anonymity.

The Uyghurs siding with China was before China started rounding them up and putting them in camps. The Uyghurs now live under the worst dystopian future humanity could envisage -- Checkpoints with phone scans, mandatory government spyware that scans for illicit content, deep facial recognition and social profiling EVERYWHERE. Its a different time, and a different China. I hope the Uyghur rise up and smash this. I wouldn't bet on it happening.

Venmo isnt peer to peer, its a central service in which two users (clients) talk to a server. Its practically the opposite of p2p.

Is this another way for Google to prevent you from clearing their cookies via the 'Clear Cookies' option?

Its a step in the right direction with enforcing SameSite cookie scoping, but we must be cautious that Google doesn't use this to force you to always be logged in. Google has a long way to go to rebuild trust after that last browser login debacle. I don't trust em.

I am quite disappointed that both the article and the comments dont mention application security. USE AN ORM. Unless you are a hotshot SQL dev who knows the intricacies of every RDBMS, you should be delegating this to the ORM. Its there to prevent you from blowing your foot off by introducing SQLi vectors. Use an ORM, avoid SQLi.

I disagree, and SQLi is not simply prevented by avoiding user input. There are many cases where you need to use user input for a SQL query and its a valid pattern, and can be done securely with Prepared Statements or Parameterization.

Using an ORM discourages you from writing SQL queries and it also automatically parameterized queries. This is a good thing! In fact, from experience, the single easiest way to mitigate a naive developer from introducing SQLi is requiring them to use an ORM. People should not be constructing SQL statements by hand today, its too easy to mess this up. SQLi shouldnt be a thing in 2019, but, it is.

My point is it is VERY MUCH not orthogonal, its very much related. Avoid naive SQLi, use an ORM. Directly related.