2,342 karma · joined October 14, 2014
Views my own.
So, yeah, go for it.
Cross device webauthn is the better solution here but it's still vulnerable to the oauth phishing called out here.
So automated tracking is bad when attached to a gun because it more easily enables the rest of the concerns laid out in the thread. It's not some hobbyist "paintball the squirells in my yard", but a government-purchased, corporation built project with an explicit, obvious goal in mind. Disregarding that because many other things _could_ be used for bad with a couple lines of code is not the right call, imo.
Like, yes, this is a thing that could happen, and has, we call them bugs. But the companies building those products aren't in the business of making that outcome occur. These developers and companies are in the business of helping make people die and I'd bet significant sums this is already tracked in a backlog issue or behind a //.
This is where SD-jwt comes in - https://datatracker.ietf.org/doc/draft-fett-oauth-selective-..., which selectively offers pieces from that once-signed chunk of data.
It does rely on statestudentaid.gov actually validating said assertion, of course, but that's only like... The second most common screw up with JWTs and related tokens.
I can't say that allowing those topics, or even pushing them, is targeting the right. By definition it's about some other group being supported. Maybe you meant triggering them, not targeting them?
The first paragraphs are fine - sure, redefine the founding myth and culture as lore, go for it - but around "memeing normcore into existence" my eyes glazed over.
I've linked to WebKit source before in exec reviews and no one bats an eye. So, changed, I'd say.