Fixed misspelling standards would seem too prone to failure (i.e. RIAA figuring it out and asking for Meh Tallica to be banned, to) - at most I would expect them to double the size of the "bad filenames" list.
I'm for variable misspellings, and I think whenever anyone reposts a song that was blocked, they should use a new spelling. Random misspelling generation software would then seem to be in order.
Aren't MD5 hashes one-way? Not that I'm complaining - I think it would rock if you had to do a brute-force attack to figure out what song you're about to download...
There are lots of things we use day-to-day that aren't very strong once they start to crack, but they're overbuilt enough that regular use is below the threshold required to start cracks.
But while I know some materials have a level of stress below which they can deform and reform without permanent damage (in metal bicycle tubing, and probably more generally, one measurement of this is the "modulus of elasticity"), I don't know if composite materials have the same deal, or if they crack under even the smallest stresses (but small cracks for small stresses).
So, if e.g. carbon fiber composite stuff can be overbuilt to avoid cracking at all under normal use, I think that would be the best way to go. In some places overbuilding probably isn't the best way to go (e.g. Satellites), but if there is a choice, I would think overbuilt, non-glue-bubbly chairbacks would probably be preferable.
I'm not so sure filters looking for requests made to "www.pr0n.com" are likely to be a big problem, as the HTTP client only tells the hostname to the DNS resolver to get the IP address and optionally to the host itself in the Referer [sic] and Host headers.
Slashdot Mirror
Fixed misspelling standards would seem too prone to failure (i.e. RIAA figuring it out and asking for Meh Tallica to be banned, to) - at most I would expect them to double the size of the "bad filenames" list.
I'm for variable misspellings, and I think whenever anyone reposts a song that was blocked, they should use a new spelling. Random misspelling generation software would then seem to be in order.
Note: I'm not a napster user, I'm a napster symp.
Aren't MD5 hashes one-way? Not that I'm complaining - I think it would rock if you had to do a brute-force attack to figure out what song you're about to download...
And at one cent apiece, they aren't going to have any surge protection :)
I use velcro tape to store important pens under the desk. Smart though my coworkers may be, out-of-sight if truly out-of-mind.
There are lots of things we use day-to-day that aren't very strong once they start to crack, but they're overbuilt enough that regular use is below the threshold required to start cracks.
But while I know some materials have a level of stress below which they can deform and reform without permanent damage (in metal bicycle tubing, and probably more generally, one measurement of this is the "modulus of elasticity"), I don't know if composite materials have the same deal, or if they crack under even the smallest stresses (but small cracks for small stresses).
So, if e.g. carbon fiber composite stuff can be overbuilt to avoid cracking at all under normal use, I think that would be the best way to go. In some places overbuilding probably isn't the best way to go (e.g. Satellites), but if there is a choice, I would think overbuilt, non-glue-bubbly chairbacks would probably be preferable.
I'm not so sure filters looking for requests made to "www.pr0n.com" are likely to be a big problem, as the HTTP client only tells the hostname to the DNS resolver to get the IP address and optionally to the host itself in the Referer [sic] and Host headers.