This is an interesting submission for educational purposes but I want to warn folks who might be inspired to "roll their own" website change monitoring tool. I

This is an interesting submission for educational purposes but I want to warn folks who might be inspired to "roll their own" website change monitoring tool. I started writing a similar tool in C# and since I was hoping to create a generalized tool for any website, I had to deal with lots of tricky edge cases. (E.g. raw HTML that changes vs visible text that doesn't, copyright dates on footers that get changed but the real meat of the page is still exactly the same triggering false alarms, etc.) I gave up and simply used Aignes Website-Watcher.[1] If you're still itching to program your own webpage change detector, I recommend reading through their 16 years of release history[2] to get an idea of the various bugs they had to solve. The scope of edge cases can be overwhelming if you want to write something very robust. [1] http://aignes.com/index.htm http://aignes.com/index.htm [2] http://aignes.com/wsw_history.htm http://aignes.com/wsw_history.htm