In a battle of site hoster and script user, the script user has the upper hand.
To start with, any method of detecting DOM changes needs to be able to report these changes back to the server in order for the server to be aware of it. Blocking reporting back by intercepting any HTTP requests means you win. You also have access to any scripts on the page while the page does not have access to any userscripting. In the case of your simple script above I could simply remove all setTimeout and setInterval page functions, regardless of what they are named (you can access them by index). Basically in any escalating war the effort requires scales dramatically for the website developer, and will quickly start breaking the website for normal users who happen to have adblock software, or noscript software, or have images turned off because they are on a slow connection, or any other number of 'ors' that would cause them to lose traffic. In the end the only way to make your website 'userscript proof' is not to publish it in the first place. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en -~----------~----~----~----~------~----~------~--~---
