375 karma · joined October 19, 2017
1) A token gets compromised.
2) You know which token. You need to revoke access.
3) You introduce state by storing said token on disk / in memory somewhere.
Key takeaways:
1) The authentication system (not the token) is now stateful. 2) You now have to check this data store to properly allow authentication. 3) A core benefit of JWT (stateless auth) is gone.
It seems like half of the time you’re just using the escape hatch to plain JS to stitch all of this stuff together, no?
Real missed opportunity.
At least some figure indicating that a Haskell app is less prone to bugs, etc.
Otherwise why not throw Typescript at it?
Think of how remarkable it would be if Chimpanzees in captivity began to speak. This would mean chimpanzees have the language capacity but, in every observed chimp, it simply never occurred to them to use it?
It’s about as likely as finding a flightless bird somewhere and teaching it to fly.
As a layman, I see how Retina can be a buzzword, but not 7nm vs 5nm.
Ethically speaking, why not ask them?
Hence the stalemate I guess.
Of course, this isn’t a heavy commuter route. In the absence of decent surrounding public transit it seems unlikely to make any real dent in traffic.