Hi, Matthias Julius wrote: > What is much more likely is that users are tampering with either > version.txt or some source files.
Is there some kind of moral obligation to use the newest client code and to not "tamper" with the code? Why not DRM it outright and distribute only compiled binaries if that's what you want ;-) Honestly, whenever I run the client nowadays, which doesn't happen often and mostly only for debugging, all that auto-version-check-self-update thing is the first bit I disable. I simply don't want software that updates itself from an SVN which can be accessed by virtually anybody. If I were not as lazy as I am, I would also make sure that the sofware is installed by another user account than the one used to run it; that's just standard security practice. I find the version checks and self-updates rather intrusive. Of course we don't want people running old software and ruining our efforts, but I had thought that the simple version check on upload was sufficient - along, perhaps, with an *optional* auto-update for those who have the thing running in a sandbox. But you're talking as if allowing the software to update itself would be some sort of basic requirement for the client software... Bye Frederik -- Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09" E008°23'33" _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
