10
you are viewing a single comment's thread
view the rest of the comments
[-] OsrsNeedsF2P@lemmy.ml 2 points 4 weeks ago* (last edited 4 weeks ago)

You are mostly correct, some additional insight from someone who works with security/privacy stuff:

That is different in the EU I grant you

Even in the EU, when a user requests to delete their data, you're allowed to keep enough to validate they were a previous rule-breaker so they can't just delete their data and re-register

The session staying open is bad security though.

There isn't enough context to say for sure, but in general this is standard practice. JWTs, probably the most widely adopted standard for authorization on the web, have an expiry date and cannot be revoked. Yes it's not great security, but I want to emphasize this is standard practice. Google, Apple, Meta, Slack, etc all do this.

Also, when you request data deletion, the companies have up to a month to do it. I'm not sure if OP expected it to be instant, but it doesn't have to be

[-] JakenVeina@lemm.ee 1 points 3 weeks ago

General practice for JWTs is to keep a list of "revoked but not yet expired" tokens, and check against that. That list will generally be tiny, since each item only stays on the list for as long as the normal lifetime of a token is, so it's not really burdensome to maintain and replicate.

this post was submitted on 22 Mar 2025
10 points (91.7% liked)

AssholeDesign

6776 readers
1 users here now

This is a community for designs specifically crafted to make the experience worse for the user. This can be due to greed, apathy, laziness or just downright scumbaggery.

founded 2 years ago
MODERATORS