I think you are getting slightly confused, the calendar isn't there to access archive posts but to view events that the blog owner has entered in to the system and the calendar operates independantly of which ever page is being browsed. When you are viewing the events for a given date, such as you have linked to, the calendar will change to show that month. If you are just browsing the site it will show the current month/year by default.
If you look at my update on the site (http://www.patrickrobin.co.uk/default.asp?Display =5) you will see why the MPAA blog is no longer visible.
I'm the creator of Forets Blog and, obviously, the author of this article so its only right that I respond to your queries.
1) The screenshots show as much detail as possible, I can/could only view the output of my system and not the source. 2/3) I came across the blog through my website referals when they accessed the RSS feed from my site. The site was live and online but I'm unsure whether it was ever linked to or if it was spidered by google, but it was on a live web server that was accessable by any member of the public. It has been removed from their web server since the article was written after some dialogue between myself and the MPAA.
I have been in communication with Paul Egge and Richard Kroon (Director of Application Development) at the MPAA and have copies of all of the emails that were sent.
Slashdot Mirror
I think you are getting slightly confused, the calendar isn't there to access archive posts but to view events that the blog owner has entered in to the system and the calendar operates independantly of which ever page is being browsed. When you are viewing the events for a given date, such as you have linked to, the calendar will change to show that month. If you are just browsing the site it will show the current month/year by default. If you look at my update on the site (http://www.patrickrobin.co.uk/default.asp?Display =5) you will see why the MPAA blog is no longer visible.
I'm the creator of Forets Blog and, obviously, the author of this article so its only right that I respond to your queries.
1) The screenshots show as much detail as possible, I can/could only view the output of my system and not the source.
2/3) I came across the blog through my website referals when they accessed the RSS feed from my site. The site was live and online but I'm unsure whether it was ever linked to or if it was spidered by google, but it was on a live web server that was accessable by any member of the public. It has been removed from their web server since the article was written after some dialogue between myself and the MPAA.
I have been in communication with Paul Egge and Richard Kroon (Director of Application Development) at the MPAA and have copies of all of the emails that were sent.