Fair point, I made the meme to be silly, and, yes, this is one of the many reasons why tokens in general should expire after some point in time.
Also the meme isn’t wrong, memes don’t need logic, they’re supposed to give people a giggle.
To be Frank, who I am not (I'm Hai), I can't tell if you're a troll or not. Although, if you're not, my meme is not "wrong" or spreading misinformation it contains a logical fallacy, as many jokes do. I can list jokes that contain logical fallacies upon request.
Look at this guy over here, nerding out about the WiFi.
Jk, glad to find someone in the comments correcting the misinformation in the meme. OP is probably a hacker who likes to do session hijacking.
JWT sounds great on paper until you have to deal with logout and revocations. Might as well use standard session cookies.
Yeah, that's what I was curious about, the security issues you mentioned as I wasn't clear in my understanding until now. Thanks.
@7heo @tdawg, i only keep data from sites which i visit every day, no other, using Site Bleacher, it remove automatically cookies, local storages, IndexedDBs, service workers, cache storages, filesystems and webSQLs from all not whitelisted sites. This keeps clean the browser and HD.
https://github.com/wooque/site-bleacher
Similar alternative
Automatically clear cookies on browser exit, only whitelist the couple of websites you use regularly.
Has the added benefit of making tracking cookies fairly (but not completely) useless
That's still good practice but first party cookies aren't exactly trustworthy either. IMO, best to whitelist what you trust and use, permablock what you don't, and auto-wipe the rest.
https://termly.io/resources/articles/first-party-cookies-vs-third-party-cookies/
here's what I found
tldr: first party coolies are used to enhance your experience, with staff like login info and ur shopping cart. third party tracks you. wither way, imma start clearing most cookies from now on
To be precise, first-party and third-party just means whether the cookie set is for the domain you are currently on, or for another one. The latter do not have to be tracking cookies, but are often used as such. You can see the cookies that your browser is storing for a specific site by visiting it and looking at them in the developer tools (Storage or Application tab, depending on browser). Under the "domain" column you can see what domain it is for.
Furthermore, there you can look at the Local Storage and Session Storage tables which are also often used to store tracking data but are not prevented by cookie deletion.
Only ever using private windows and then alt F4ing to automatically delete all session data.
These days you'll need to clear localStorage, sessionStorage, and localDb to really do this. The rise in tokens means some sites only use those.
