Comment by 0rzech 4 days ago Oh, I didn't know that. Thanks! 3 comments 0rzech Reply Rendello 4 days ago For me it still happens, the file has just been renamed to /js/kill.<giant hash>.js 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 4 days ago For me it still happens, the file has just been renamed to /js/kill.<giant hash>.js 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.
For me it still happens, the file has just been renamed to /js/kill.<giant hash>.js
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.