User: othermark

technical solutions exist for this problem.

On: Bad Behavior on the 'Net - Who Pays the Bandwidth Bill?

It's called QOS. Either that or don't buy the bandwidth in burst. Smart ISP's buy flat rate and charge burst to the customer (unless they pay premium for flat). If you're only paying flat, you don't have to eat the cost for unintended bandwidth usage.

--
othermark

Depends on where and how the code is used.

On: Do Scripters Suffer Discrimination?

Code you release to a customer that you don't want to be touched, should probably not be script.

Code you do for in-house projects can probably be a script. For QA projects, scripts are the rule rather than the exception for 2 reasons.

QA is never given enough time, so it's script, script, script.

Scripting, because of it's high level, is easier to modify quickly in response to changing requirements.

--
othermark

you need dcc.

On: Jupiter Forecasts 50% Increase In Spam

Many people use this at their site in conjunction with spamassasin.

http://www.rhyolite.com/anti-spam/dcc/

Checksumming is a great solution today. It allows you to whitelist servers you do want, and it's possible to setup interfaces to allow individuals to control what's whitelisted, as well as tune the threshold of what's acceptable.

It allows you to choose which checksum provider(s) you want to trust. It allows you to contribute to the blockage of spam in a community architecture by providing checksums of external mail you recieve to other checksum providers.

--
othermark