It goes without saying the same thing happens with list archives, where one might participate in OSS-related discussion. However, as per my journal entry, submitting a bug report gives similar results. So now, I don't submit bugs where I don't have control over my email address.
SFS is a secure, global network file system with completely decentralized control. SFS lets you access your files from anywhere and share them with anyone, anywhere. Anyone can set up an SFS server, and any user can access any server from any client. SFS lets you share files across administrative realms without involving administrators or certification authorities.
At least for FreeBSD, package maintainers must create an MD5 signature for packages that are downloaded (from source or mirror). If you try to build a port with a signature mismatch, the build bails. So, not only does the source site's code need to be trojaned, but the ports tree entry has to be modified too (and the sysadmin has to update the ports tree).
Since Gentoo has a ports-style package management system, perhaps it does something similar.
Why is there an assumption this is a driver problem? The issue is the trust model between client and server. The game engine needn't send position information to clients when not necessary? Oh sure, it's _easier_ to let the client do the work, but the game (server) engines already do much of the same work (you can't walk through walls). Why not include this funtionality and make it server-side optional? Let the big boxes do more of the work to quash the would-be cheaters.
Dan Berstein asks a similar question and finds one or two answers. It seems like the only (readily found) solutions are American Advanced Power and Amsdell.
In the mean time, Dean Edwards gives us the gift.
It goes without saying the same thing happens with list archives, where one might participate in OSS-related discussion. However, as per my journal entry, submitting a bug report gives similar results. So now, I don't submit bugs where I don't have control over my email address.
Have you seen this?
At least for FreeBSD, package maintainers must create an MD5 signature for packages that are downloaded (from source or mirror). If you try to build a port with a signature mismatch, the build bails. So, not only does the source site's code need to be trojaned, but the ports tree entry has to be modified too (and the sysadmin has to update the ports tree).
Since Gentoo has a ports-style package management system, perhaps it does something similar.
Some people have already produced excellent results in breaking visual CAPTCHAs.
Why is there an assumption this is a driver problem? The issue is the trust model between client and server. The game engine needn't send position information to clients when not necessary? Oh sure, it's _easier_ to let the client do the work, but the game (server) engines already do much of the same work (you can't walk through walls). Why not include this funtionality and make it server-side optional? Let the big boxes do more of the work to quash the would-be cheaters.
Dan Berstein asks a similar question and finds one or two answers. It seems like the only (readily found) solutions are American Advanced Power and Amsdell.