JWT is a scam and your app doesn't need it
The article critiques JSON Web Tokens (JWT), arguing that they do not provide the promised benefits of stateless authentication. It claims that JWTs create more problems than they solve, including issues with token invalidation and security. The author suggests that simpler and more secure alternatives exist for managing authentication in applications.
- ▪JWTs cannot be invalidated before they expire, leading to potential security risks.
- ▪Using refresh tokens as a workaround for long-lived JWTs complicates the authentication process.
- ▪The author advocates for simpler solutions, such as using bearer tokens stored in a database.
2 outlets in our directory ran this story, first to last over 1 hour. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ JWT is a scam and your app doesn't need it — DEV.to (Top)
Hacker News (Front Page) files mainly under programming. We currently carry 993 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Dusan Malusev |
| Canonical URL | https://www.dusanmalusev.dev/blog/jwt-is-a-scam-and-your-app-doesnt-need-it |
| Publication time | Sat, 23 May 2026 17:42:08 +0000 |
| Retrieval time | 2026-05-23T18:22:27.580Z |
| Last seen | 2026-05-23T18:22:27.580Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | rhlCyx47KEJu · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
JWT is a scam and your app doesn't need it JWT promises stateless authentication and delivers neither. It's a cargo cult that makes your app slower, less secure, and harder to maintain — and almost every developer shipping it has no idea why. Published 2026-05-23 · 9 min read · 2,080 words · #auth#security#architecture#jwt#rant · PGP Verified On this page what JWT actually is, and what the pitch wasyou cannot invalidate a JWT. you just can't.refresh tokens are a confessionthe per-request cost is real and people lie about itthe frontend "verification" nobody has ever shippedencrypted JWT (JWE) is even more nonsensical"just put the JWT in an httpOnly cookie""no system is stateless" — please stop pretendingwhat to ship instead"but I'm building an…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Dusan Malusev.
Discussion
0 commentsMore from Dusan Malusev
