← Back to context Comment by Rendello 3 days ago For me it still happens, the file has just been renamed to /js/kill.<giant hash>.js 2 comments Rendello Reply 0rzech 3 days ago We're back to square one, then. :) Rendello 2 days ago I was wondering if the hash might be unique, then a commenter would say "it's now `kill.<hash xyz>.js`, and the webmaster would be able to connect <hash XYZ> to a user agent and IP. It wouldn't accomplish anything, but it might be fun.
0rzech 3 days ago We're back to square one, then. :) Rendello 2 days ago I was wondering if the hash might be unique, then a commenter would say "it's now `kill.<hash xyz>.js`, and the webmaster would be able to connect <hash XYZ> to a user agent and IP. It wouldn't accomplish anything, but it might be fun.
Rendello 2 days ago I was wondering if the hash might be unique, then a commenter would say "it's now `kill.<hash xyz>.js`, and the webmaster would be able to connect <hash XYZ> to a user agent and IP. It wouldn't accomplish anything, but it might be fun.
We're back to square one, then. :)
I was wondering if the hash might be unique, then a commenter would say "it's now `kill.<hash xyz>.js`, and the webmaster would be able to connect <hash XYZ> to a user agent and IP. It wouldn't accomplish anything, but it might be fun.