Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Comment Re:They don't even go back far enough. (Score 1) 152

To an extent, this was what he was warning against (though he set no time constraints) -- that eventually people would complain about the existence of copyright regardless of length of time. He argued that making the law too broad and absurd (arguable - I'm not debating whether he was right on this issue) would cause people to view the entire thing as an unnecessary evil.

What we see in the past is copyright being extended and broadened continually over time, and people eventually arguing against it as a whole once they have a means to violate it easily.

Of course it is not perfectly what he predicted (and it is extremely late), but it does kind of fit some of the points.

Comment Re:They don't even go back far enough. (Score 3, Insightful) 152

No, by the fact that there is a rising Pirate Party in a few countries. I don't dispute that it is currently very disorganized and ill-defined, but it exists.
It is by the fact that more and more people are obtaining copyrighted content from the internet illegally.
It is by the fact that more and more people think that this is okay.

Right now, many governments of the world and the recording industry are trying to fight it. Whether they are winning or not, only time will tell. In that respect, not everything he said has come true, but what hasn't come true still has the potential to.

The main point the GP was trying to make is that he predicted that in the future it would become extremely easy to copy something; so easy, in fact, that anybody could do it. That did come true, and that did take 160 years.

Comment Re:cron + rsync + tar (Score 1) 121

You could probably pretty easily write an extension for mediawiki that attaches to the 'ArticleAfterFetchContent' hook and augments the page with content fetched on the fly from Wikipedia. That would be easy enough to do. Just make sure that when the user is editing the page, the function you attach to the hook does not activate (otherwise you will end up saving the wikipedia content into your page, and it will be there twice when a user visits the page).

Comment Re:About time (Score 1) 383

Another simple way to reproduce:

1) Turn off immediately switching to new tab
2) Go to the slashdot index page
3) Middle click "Read More..." on any article
4) Try to scroll down the page
5) ???
6) Profit!

But in all seriousness, this can be a problem when browsing slashdot!

Comment Re:About time (Score 1) 383

By blocking, BitZtream is talking about blocking for a significant amount of time. Technically, all calls are blocking, but there is a significant difference between blocking for a few milliseconds or blocking for a few tenths of a second. For example, reading from a pipe can block for a long time if nothing is writing to the other end; however, you can tell the read function to be non-blocking, and just return an error or nothing if there is nothing to read at the moment.

Obviously, these are system calls. And, being system calls, they are talking to another process, namely part of the kernel. However, this does not make your program multithreaded, because if it did, by that definition, there would be no such thing as a single threaded program on any OS that uses process switching.

Comment Re:About time (Score 1) 383

> But the smaller, leaner, more approachable codebase goal?

Somewhat. It doesn't get blogged about much, and when it's blogged about the press doesn't pick it up because nitty-gritty arch work is boring. But there have in fact been significant simplifications to all sorts of stuff in the meantime...

So does this mean that it won't take several hours to compile it anymore?

Comment Re:Mung (Score 2, Informative) 288

From Jargon File (4.4.4, 14 Aug 2003) [jargon]:

    mung /muhng/, vt.

          [in 1960 at MIT, "Mash Until No Good"; sometime after that the
          derivation from the {recursive acronym} "Mung Until No Good" became
          standard; but see {munge}]

          1. To make changes to a file, esp. large-scale and irrevocable
          changes. See {BLT}.

          2. To destroy, usually accidentally, occasionally maliciously. The
          system only mungs things maliciously; this is a consequence of
          {Finagle's Law}. See {scribble}, {mangle}, {trash}, {nuke}. Reports
          from {Usenet} suggest that the pronunciation /muhnj/ is now usual in
          speech, but the spelling `mung' is still common in program comments
          (compare the widespread confusion over the proper spelling of
          {kluge}).

          3. In the wake of the {spam} epidemics of the 1990s, mung is now
          commonly used to describe the act of modifying an email address in a
          sig block in a way that human beings can readily reverse but that will
          fool an {address harvester}. Example: johnNOSPAMsmith@isp.net.

          4. The kind of beans the sprouts of which are used in Chinese food.
          (That's their real name! Mung beans! Really!)

          Like many early hacker terms, this one seems to have originated at
          {TMRC}; it was already in use there in 1958. Peter Samson (compiler of
          the original TMRC lexicon) thinks it may originally have been
          onomatopoeic for the sound of a relay spring (contact) being twanged.
          However, it is known that during the World Wars, `mung' was U.S.: army
          slang for the ersatz creamed chipped beef better known as `SOS', and
          it seems quite likely that the word in fact goes back to Scots-dialect
          {munge}.

          Charles Mackay's 1874 book Lost Beauties of the English Language
          defined "mung" as follows: "Preterite of ming, to ming or mingle; when
          the substantive meaning of mingled food of bread, potatoes, etc.
          thrown to poultry. In America, `mung news' is a common expression
          applied to false news, but probably having its derivation from mingled
          (or mung) news, in which the true and the false are so mixed up
          together that it is impossible to distinguish one from another."

See the third definition.

Comment Re:or not! (Score 1) 273

The problem with voting in people with strong principles is that they often expect everybody else to also have strong principles, and pass laws accordingly. For example, libertarianism in the strictest sense works if everybody has strong principles and foresight. In the long run, it is disadvantageous to be anticompetitive as a company because it prevents you from improving your product. Soon (or several years) after something significantly better arrives at a better price than you can give, it will take over. However, people in charge of companies do not think that way. They think in the short term, as does any competition they may have at the moment. Therefore, they cannot be trusted to not be anticompetitive.

This is only one example why strict libertarianism does not work, and also only one example why relying on politicians with strong principles does not work. Thinking of other examples is an exercise left to the reader.

Comment Re:DRM (Score 1) 417

He said, "...invented to benefit the people...", not "...invented to benefit people..."

You are twisting his words instead of coming up with a real counter-argument.

Note: there are real counter-arguments, but you have not produced one here.

Slashdot Top Deals

HELP!!!! I'm being held prisoner in /usr/games/lib!

Working...