Re:Show HN: PAST, a secure alternative to JWT
by tptacek on Friday January 05, 2018 @11:33AM
(#16079598)
To me, this rebuttal reads, "I don't understand it, ergo it must be dubious".
I'm criticizing JWT. Not you, or any other developer. If you don't understand or follow or agree with my criticism, that's OK. We can still live our lives.
Re:Show HN: PAST, a secure alternative to JWT
by zimpenfish on Friday January 05, 2018 @12:13PM
(#16079874)
> To me, this rebuttal reads, "I don't understand it, ergo it must be dubious".
That is not intended - it's more "I don't understand it, I'm happy to believe it's broken but all we get is Appeal To (self)Authority as to why rather than actual usefulness."
> If you don't understand or follow or agree with my criticism, that's OK. We can still live our lives.
Well, sure, but wouldn't you prefer to help people who don't understand by actually explaining something for once?
The Storify link is slightly more useful but again doesn't really explain anything - it's just bullet points of "I think these things are bad in a standard" which is great if you already have the knowledge of those things. Utterly useless otherwise.
And if "implementation errors should lower your opinion of a specification" means we shouldn't use JWT, where does that leave us on WIFI, SSL, HTTP, speculative execution in pipelines, ...?