Much simpler: just store session ids in Redis.

I skimmed over the previous articles in this blog and they don't seem to mention the one use case JWTs were made for: having a separate authentication server from the application server. Most developers will only need this for integrating into corporations with single sign in or social logins (sign in with Facebook/google/apple...). There you won't write the authentication server but integrate with them. Session Ids are dead simple to get right securely. Just use them.

That's the idea behind it. The reality is that patents are written in a way to reveal as few as possible while blocking other companies as much as possible.

There's another perspective you can see in the comparison with the dot com boom. The web is here to stay, but a lot of ideas from the beginning didn't work out and a lot of companies turned bankrupt.

Did you try the new models that came out in the end of last year? -- It's not just progress it's a breakthrough. /s

The problem is that you get a vastly distorted picture because of different survivorship rates of artifacts. In the Stone Age people used mostly wood tools but stone tools didn’t rot away.