|
|
|
|
|
by schobi
2 days ago
|
|
I guess the decoder is more than the 208 bytes that this page uses.. But maybe you can misuse this and store a session ID / cookie in a favicon (give everyone a unique one) and survive some cookie cleanup and evade privacy restrictions? Maybe you can still make it that the favicon looks like an image a little to not raise suspicion? Favicons seem to be cached across private browsing sessions. Oh no |
|
Must EVERYTHING be polluted by ad tech & privacy intrusions?