Oy, my own parss server was out of sync with atomic time due to changed servers and inappropriate firewall rules... That caused quite some inaccurate updates e.g. at Antville.org.

I reconfigured the firewall settings and hope that the updates come in more reliably from now on. Fingers crossed!

The revamping of the Parss server is completed (well, there will be always some changes but hopefully only in detail): I've added the most important information to use the service, a short API documentation and certainly a link to this weblog.

Furthermore, thanks to the very nice support of the nighthawk I was able to remove a redundant HTTP HEAD request, a relic from the pre-Rome version.

The future date issue was almost fixed in the client when we observed that it's not very nice to have less than 10 items on a page just because a few have a future (and actually wrong) date. Thus, I enabled the server to not return such items until they are "in time".

The downside of this is certainly that the client is missing items which are actually online and published. Because I've learnt my lessons pretty well ("never fix other people's bugs") I guess we'll have to live with that until somebody is correcting the dates in such a feed.

(Which reminds me again of the question whether RSS is becoming the new HTML and strict parsers and validators are really an adequate approach.)

What's still missing are up-to-date README and INSTALL files and then, fingers crossed, I think I will release Parss 2.0.