Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Duh! (Score 4, Insightful) 261

If music/movie execs owned WalMart, they would have a big board level meeting to try and control shoplifting by:
- Put everything in locked glass cabinets.
- Ask for photo ID before entering stores.
- Strip search everyone on exit.
Then they would be scratching their heads as to why they were going broke, blaming it on the dishonest consumer.

99% of people don't want to steal, they just want convenience at a fair price.
They could have agregated all their contect, with music 10c/track, movies $2, no DRM, problem solved.

Comment Re:You can do it with just latitude / longitude (Score 1) 478

Because most people can't remember a long string of numbers but they can easily remember three english words.

If you can remember just eight digits - Two groups of four, less than a complete long distance telephone number - That will put you within half a mile of your target location. Add two more digits (the length of an LD phone number including the "1"), and it puts you to less than a football field away.

Then again, we have DNS in the first place because non-geeks couldn't manage four groups of three, so, I don't seriously expect them to do much better with lat&long.

/ob "Correct Horse Battery Staple"

Comment Re:Google should charge for bad/fake DMCA notices (Score 1) 364

They can't put any conditions upon when they'll accept a notice; refusing a notice merely means they lose their liability protection.

But yeah, they could indirectly do it, with other punative measures against recurring abusers. If, say, notices regarding "Boardwalk Empire" were to exceed 50% bogus threshold (i.e. they are wasting Google's time, costing Google money) then Google could just remove HBO's own pages from searches too. Then they could charge in proportion to HBO's abuse, to restore the HBO links. What's really cute about this idea, is that censorship mechanisms already exist at Google, thanks to the same damn industry.

I love the bonding idea too (if anyone should be posting bonds with DMCA notices, it's HBO!), but that's something Congress would have to do.

Comment Re:No need for copyright notice on every file (Score 2) 120

The problem is, adding a copyright notice when you are not the copyright holder is legally dubious, and so if there isn't one in the file you have to maintain the license information separately. This leads to a load of LICENSE.GPL, LICENSE.LGPL, LICENSE.BSD, and so on files in your tree, and separate lists of which files each relate to. It saves everyone time to just stick your license template in the top of every new file that you create.

Comment Re:Boom (Score 1) 814

the lock on that 92FS could be quickly and easily removed without much effort. That could be picked easily or removed with bolt cutters.

So our intent has shifted from "keep your 4YO from accidentally shooting himself" to "made of unobtanium".

Show me anything portable that a cutting torch won't turn into swiss cheese, if we want to invoke large tools as a means of bypassing them. But I haven't met many toddlers who've studied the MIT Guide to Lockpicking.


That "Anti-Gun Propaganda" was being spewed by a gun owner and a CWL holder.

Fair enough. I gave it about five seconds, noticed the total length, scrolled through the video looking for "here's where he defeats a trigger lock" in another five, and closed the window. Kinda my point, even if I mistook the overall focus of the video.

Comment Re:No need for copyright notice on every file (Score 4, Informative) 120

Not having a license on every file is a colossal pain for people wanting to take part of your code and integrate it into something else. I recently went through this with OpenIndiana: they wanted to take some of my code from another project and include it in their libc. This is fine - the license I'm using is more permissive than their libc so there's no legal problem - but I'd forgotten to include the license text in the file, I'd only put it in a LICENSE file in the repository root. Keeping track of the license for one file that is different from the others in the project imposes a burden for them and, without the copyright in the file, potentially means that others will grab that file and think it's under a different license.

In short: Please put licenses in files. It makes life much easier for anyone wanting to use your code. If you don't want people to use your code, then you can save effort by not publishing it in the first place.

Slashdot Top Deals

"Everything should be made as simple as possible, but not simpler." -- Albert Einstein

Working...