Slashdot Mirror
Brightnets are Owner Free File Systems
elucido writes "OFF, or the Owner-Free Filesystem is a distributed filesystem in which everything is stored in reference to randomized data blocks, as opposed to a 1:1 copy of the original data being inserted. The creators of the Owner-Free Filesystem have coined a new term to define the network: A brightnet. Nobody shares any copyrighted files, and therefore nobody needs to hide away. OFF provides a platform through which data can be stored (publicly or otherwise) in a discreet, distributed manner. The system allows for personal privacy because data (blocks) being transferred from peer to peer do not bear any relation to the original data. Incidentally, no data passing through the network can be considered copyrighted because the means by which it is represented is truly random." Their
main wiki page discusses a bit of what this means and how it might work as well. I've been saying that we need this for many years now, if only because we all have 10 gigs free on our machines and if we could RAID the internet we'd need fewer hard drives.
My network is still on the fence when it comes to the existence of God.
Isn't this just a sophisticated form of encryption, using a large, randomly generated key?
If so, does it have any real advantages over conventional encryption? It seems that the disadvantage would be the need to have both the file (large) and the random data (large) instead of, conventionally, just the file (large) and key (small).
Also, I can't be the only one who found the summary, uh, confusing??
Is crushing a suspect's child's testicles illegal?
John Yoo: "No, [if] the President thinks he needs to do that."
As a rule, you don't copyright the exact data (i.e. the sequence of numbers representing a digital file). You copyright the actual tangible information. Attempting to abstract the law into mathematics is pointless. They are not compatible.
Incidentally, no data passing through the network can be considered copyrighted because the means by which it is represented is truly random.
It's not the data that's protected by copyright, it's what the data represents.
No matter how you mangle the data when storing it or transferring it from one location to another, the end result is the same. They're trying to use semantics and technical voodoo to get around copyright law. It won't work.
"You cannot simultaneously prevent and prepare for war." -- Albert Einstein
Yup, and attempted get-arounds like this are stuff courts love to slap down.
"copyrighted data"
to
"encrypted copyrighted data"
The first is merely infringement. The second is conspiracy to commit infringement, and you will have lost any chance of defending with "I didn't know it was copyrighted".
Curiously enough things like this are exactly why "conspiracy to commit" crimes exist.
Furthermore, unless I'm making a stupid mistake, it doesn't actually distribute the data, the key to find the data in the P2P net is the same length as the original data, in the random case, which buys you exactly ... nothing. You have to download the file twice.
This thing does not evade copyright law, and it's inconvenient to boot. I don't think I'll be placing a second look.
Doesn't Tahoe already do this?
"A simple analogy is seen in that every number has an infinite number of representations (3+2=5, 2*2+1=5, 10-5=5, 10/2=5, etc). Even if the number (file) in question can be copyrighted under current legislation, it is practically impossible and unreasonable to state that every other representation of that particular number is copyrighted."
Actually, no, it's not unreasonable or impractical. In fact, that's how it actually works. Star Wars is copyrighted as a DVD, Film, mpeg, script, live performance, song, interpretive dance, etc. ..right?
-- 'The' Lord and Master Bitman On High, Master Of All
Hmmm... I don't think that's the objective, exactly. I didn't read TFA as saying "material distributed in this way is not subject to copyright" but rather "none of the bits we're moving are copyrighted - go pester the people doing the uploading"
I also think there is a useful discussion to be had on the subject of numbers and the digital assets they may or not represent. If I zip up MS Office, for instance, I've turned it into a very long number. Is it reasonable to allow companies to claim ownership of such numbers? With the proper compression and/or encryption scheme, you could use any number (trivially in some cases) to represent a work over which you can claim copyright. Do we then let a corporation privatise the entire integer space? And if not, how do we distinguish between infringing and non-infringing uses of a large number?
Don't let THEM immanentize the Eschaton!
As a rule, you don't copyright the exact data (i.e. the sequence of numbers representing a digital file). You copyright the actual tangible information. Attempting to abstract the law into mathematics is pointless. They are not compatible.
That's not the point. The point is that if someone downloads blocks from me to be used for copyrighted material, I cannot know what it is used for. Maybe these block also encode legal stuff. Because the same block encodes multiple files, and because a request does not state what the data is gonna be used for, I (probably) cannot be holded responsable for sharing copyrighted material.
You copyright the actual tangible information. Attempting to abstract the law into mathematics is pointless. They are not compatible.
You're dead right. What is interesting is that if you're "caught" with some of these random blocks on your disk, they're just random blocks of data. You can't decode them unless you have the key, hence there's no charge of copyright infringement.
One problem with the proposal (which, by the way, is very obvious, and is how FreeNet and other systems work) is that their key length needs to be the same length as the data, because it's effectively a One Time Pad. If it's any shorter than the original data, then there will be a way to unencrypt the data without the key (proof by a simple counting argument).
Rich.
libguestfs - tools for accessing and modifying virtual machine disk images
Once I actually understood what on earth they are on about, it seems like an interesting idea with very little basis in reality. Their main claim seems to be a magic-wand approach to getting round copyright, as opposed to a particularly useful distributed filesystem:
No data passing through the network can be considered copyrighted because the means by which it is represented is truly random
Sure... So if I put in Brittany's latest album, then tell my friend to click on the url that 'reassembles' the 'truly random' data into, well, Brittany's latest album, then do you really think copyright has nothing to say?
Breaking news! Photocopying books is TOTALLY LEGAL if you use yellow paper and/or put the book in the machine upside down!
A correctly encrypted file also appears random. It does not mean it IS random, otherwise it would be, well, not very useful.
Is crushing a suspect's child's testicles illegal?
John Yoo: "No, [if] the President thinks he needs to do that."
While individuals are not passing copyrighted files to each other, the copyright violation does occur. The URL with the instructions of how to assemble the file is actually an encoded version of the file. Downloading those instructions is just as much a copyright violation as downloading a digital version of the file, or a zipped archive from which the file can be extracted. So, "nobody shares any copyrighted files, and therefore nobody needs to hide away" is erroneous. Both the person offering the URL and the person accessing it need to hide if it's a work someone's going to exercise copyright over.
From the main site: "It must be noted that up until the point of retrieval of content from the OFFSystem, storage and transfer of a so-called copyrighted file is completely legal. However, the act of re-assembling a file may be considered copyright infringment in some cases, and users should be aware of legislation regarding copyright law which applies to their jurisdiction before doing so."
I think this analysis is flawed because it assumes that the instructions to construct a file are not a file, and that only when you have the end file have you copied the work. In fact, if the instructions contain all the information of a work, they are the work, in exactly the same way that any digital representation of a work is the work. "Y'onor, I didn't copy no files, look, this is just instructions to make the files" will not fly any more than "Y'onor, this isn't a music recording, it's ones and zeros."
Look, I totally get how encryption and plausible deniabiltiy is great if you people are circulating dangerous information about government conspiracies, or organising the resistance in Burma or Zimbabwe, but lets face facts, this will be used to share torrents of Hollywood movies and top 40 albums.
This is stupid.
Either accept the fact that all the political posturing about free being a better business model is true, in which case, just go enjoy all the free music/software/games/movies out there, or admit its just smokescreens to justify getting Hollywood movies for free, whilst your entertainment is subsidised by everyone who paid to see that stuff, and thus allow it to be made.
People seem to have this attitude that this kind of thing is cool because it lets you escape prosecution for copyright infringement. If copyright is such a fucked-up system, then why is it all the stuff people want to share is produced under that system? Surely all the cool movies/software/music/games is being produced under the free model right? Or could it be that the free model isn't viable, or popular with content producers, big and small...
DRM-free indie games for the PC and Mac: Positech Games
For some of us that isn't a problem, since we don't believe in IP anyway.
---- Booth was a patriot ----
There's a lot of misinformation floating around here (RTFA please). Here's what happens: you want to upload a file. The program makes up a bunch of random numbers - really random numbers that have nothing to do with the original file. The original file is not consulted to make the random blocks - they could be pre-generated even.
Also generated is a URL that has the instructions on how to get the original file back from the random blocks. Anyone that shares this part is going to be guilty of copyright infringement (assuming the work in question is copyrighted).
It's basically a substitution cipher - with a unique way of substituting real data for the random blocks, as determined by the URL. So really, it's a one-time pad of sorts.
Whether you believe in IP is irrelevant to the law of the country of where you live. As a defence it won't hold up in court.
init 11 - for when you need that edge.
http://wiki.offdev.org/Talk:Why_is_OFF_safe%3F :
Trojan detected with avg free
Another side to the safety issue. I'm hoping this is a false positive, as I like OFF
* avg free v7.5.516 virus base 269.17.13/1208 finds
o Trojan Generic9.AKLU in
+ offsystem.exe from OFFStystem-0.18.00-win-installer.exe from sourceforge January 3 2008
This is worrisome...
Who said im going to court? I adjust my activities to compensate which avoids that situation.
Doesn't change my belief, or disregard.
---- Booth was a patriot ----
Only if you zip it twice and shake your laptop (or wiggle your PC) during the process for randomizing some bits.
I think we can keep recursing like this until someone returns 1
The problem I have with that, is I that don't think those commands work in a court of law.
Come to think of it, but I'm fairly they wouldn't work under Ubuntu either. (I wouldn't know about Debian)
Don't let THEM immanentize the Eschaton!
You're quite right.
Like it or not, copyright doesn't apply to bit-streams, but rather to particular instantiations of ideas (and derivatives thereof). No one can copyright a number. But in a particular context, a certain bit-stream can be considered protected by copyright.
This whole "you can't copyright a number!" is a red herring. No one seriously claims that particular numbers are copyrighted. But in a certain context, a particular chunk of data (a number!) can be reasonably shown to be a copy (or derivative) of a particular copyrighted work. If the same number appears in a totally unrelated context, and it's apparent that it is not being used to distribute a copyrighted work, then no court would find that instance of the number to be infringing.
Another way to say this is that copyright law is more concerned with the action of copyright violation (distributing a copy or derivative of a work without authorization), and is not concerned with maintaining a catalog of copyrighted bit-streams.
"Whether you believe in Allah is irrelevant to the Sharia law of the country of where you live. As a defense it won't hold up in the Religious court."
There, fixed it for you. Since the evidence for existence of Allah is pretty much on the same level as that for the so-called "Intellectual Property" (i.e. the concept of 'ownership' of large integer numbers and the like) and the relationship between such belief and laws passed based on it is strikingly similar, the statement you made is pretty much equivalent to the one below: arbitrary bullshit based on whatever nonsense happens to deliver power and money to whatever "law makers" and their associates happen to be at the top at the time, logic, science and reason be damned.
If the copyrighted data can be recovered it's considered distribution - in some cases even if the key itself is not distributed with the encrypted data.
The issue is that any piece of random data can be turned into copyrighted data. With the right key, you can turn John Smith's holiday photo's into copyrighted MP3's. But you can't sue John Smith because someone uploaded a key that can turn his photo's in copyrighted data. OFF stores random blocks of data, which can be used by multiple files. It doesn't store any information in particular, just random blocks. Random blocks that can be used for anything. It is the URL that turnes those random blocks into something.
It only takes one man to change the Wisdom of the Crowd to Tyranny of the Masses.
In this case, though, the law has it right. No matter what you're doing to break up, encrypt, hash, randomize, or distribute files, if the end-goal is to end up with a representation of copyrighted material then you're still breaking the law.
If you don't like the law, then go out there and do something about it. Trying to find a workaround for the law is just going to get the courts mad at you if you get caught. Information may want to be free, but right now it isn't (at least not the information that these kinds of things are being created for). Legitimize it, not strategize about how to avoid the problems that can come with it.
How are sites slashdotted when nobody reads TFAs?
feed 'em to the dog and see if it goes bananas?
What if Tetris was invented by Nazis?
For an excellent explanation of why this is legally stupid, see What Colour Are Your Bits?
If all people were as pathetic as you, feudal lords and slavery would be the norm in all societies today. USA would not even exist, merely a colony ruled by the unchallengeable laws of the King of Britain, because as you so aptly said: "we have to pay some regard to the rules of that society whether they make sense to us or not". Luckily for us all, some of our ancestors took somewhat more enlightened view, sometimes even involving sticking a sword up the "divine lawmakers" asses.
Laws are only to be respected if they are a) logical and b) just. All others are just tools of tyranny and usurpation of power to be ignored and resisted. If all else fails, violently and with deadly force. It is a difference between principled courage and spineless slavery.
First off, these people don't do themselves any favours with descriptions like this:
"No data stored or transferred in OFF is copyrighted because all data is random..."
and
"...the randomized blocks do not represent the original data inserted to begin with"
Of course the data is not random. And of course it represents the original data. If either of these two nonsensical statements were true, then it would be impossible to reconstruct the original data. They may randomly generate the blocks, but the selection of blocks and parts of blocks to represent data is anything but random. What they mean is that the distrubution across many blocks in complex relationships means that a happenstance collection of blocks alone is not of any use in reconstructing the content. Sure, private storage of copyrighted data would be acceptable in this sort of encoded, distributed format. But if you publish the URL required to decode the content, you will be every bit as much in violation of copyright law as with any other form of file-sharing.
In the end, the only possible response to this technology is "so what?". If you want online storage, you can buy it by the terabyte from Amazon S3, or for that matter from your ISP. If you want P2P, this is no better than BitTorrent - and at first glance not nearly as robust.
Plus: how many people are going to be willing to put their extra disk-space permanently online, and drill a hole in their firewall so that the world can access it? Heck, I don't even do things like Seti-Online anymore - even if I trust the application, it's extra work that I just don't have time for.
Enjoy life! This is not a dress rehearsal.
What we have here is a technical solution to a legal problem. Every time a story pops up on Slashdot with a legal solution to a technical problem, we laugh at it. Well, the other way around doesn't work either, folks.
I've upped my standards, so up yours.
Willingly facilitating in the distribution of copyrighted material is illegal. So although running a brightnet client may be legal by itself (as is hosting most web pages) as soon as you use it to distribute copyrighted material you have a problem.
It's just like piratebay.org, they don't host the data but in most countries what they are doing is considered illegal.
Just ignoring the law and breaking it doesn't make you a fearless defender of freedom. It just makes you a criminal. Only if, through your actions, you actually hope to effect real change, can you justify them using your thesis.
How dare you be so modest!! You conceited bastard!!
how is this junk different from encryption or plausible deniability file systems - distributed or localized?
Congratulation to the moderators, for moderating +4 insightful a post which is a one line question titled "Big load of BS", written by someone who clearly did not RTFA.
I love kids these days, always thinking they are clever.
A long time ago a man wrote a book, he then made an index of all the words in the book and listed them in alphabetical order.
He then re-copied the book as a reference to the index.
Original: "I am the king of scotland"
Index: AM,I,KING,OF,SCOTLAND
Story: 2-1-3-4-5
Now this idea is nothing more then seeding a network with the index of data then to rebuild a particular file you pass is an index reference.
They would simply bust people for passing the index reference.
Ironical that old book became the foundation for modern day text compression schemes that used indexes and many of the key concepts that cryptography was born from.
Clever kids, if it was still the 1500's and you were trying to smuggle banned books under the nose of the inqusition. They just burned people with the indexes just as if they had the books themselves.
Honestly do they really thing that people are that stupid? If I use a pencil to stab someone I am going to jail just the same if I had used a knife. If someone is smuggling something across the border, but I don't know what, I am still an accomplice to some degree.
Plausable deniability is a great idea but the moment one of those indexes lands on you PC your gonna get dinged for whatever the index points too.
-=[ Who Is John Galt? ]=-
Brightnets don't distribute material. They distribute random blocks. The URL distributes the material, by combining the random blocks in the Brightnet to something none-random. That none-random part can be anything, it could be something that is copyright-infringing or it could be something innocent like holiday photo's. If I'm storing random blocks for a Brightnet, I'm doing just that. Storing Random blocks of data. Nothing more nothing less. I have not clue, and can't know, how people are going to use those random blocks. It all depends on the URL, not on the Random Data.
It only takes one man to change the Wisdom of the Crowd to Tyranny of the Masses.
Rather than reply to a load of (seemingly to me misguided) postings about OFF being clever encryption or whatever, here is my take on it: Suppose I have a file I want to upload. I do something like this. I split it into blocks (128Kbytes in this case). Then for each "original" block I create a set of "new" blocks such that, if the "new" blocks are (say) XOR'd together, they create the "original" block. I then upload the "new" blocks to various servers. The URL for the file lists which "new" blocks to get from which servers; anyone with the URL can retrieve the "new" blocks, do the XOR and regenerate the original file. Now, the "new" blocks cannot be copyright. If there are N "new" blocks for each "original" block then I can generate the first N-1 randomly, and then generate the Nth to give the right result. The Nth block is random in the sense that it is generated as a result of an "original" block and N-1 randome "new" blocks. The URL itself cannot be copyright; if it was then it I give someone instructions on how to get to some place where there is a copy of a book, and the PIN number for a photocopier, then that would be copyright as well. It seems to me that copyright is only infringed when someone gets the "new" blocks and recreates the file. So, the OFF does not magically get around having a dodgy copy of a copyright work, but it does get around storing that work,
Maybe I've misunderstood you, but that sentence seems to suggest that you don't understand how public key cryptography works.
Wait, are you calling me a debian newbie, or a human-geek-slashdot newbie?
Either way, I'm fairly sure the output would actually be more like:
$ sudo apt-get install common-sense && man common-sense
common-sense is a meta package
The following NEW packages will be installed:
RMS-logic RMS-common_sense RMS-IP_thoughts
The following currently installed package(s) will be removed:
human_society
Do you want to continue [Y/n]?
Is crushing a suspect's child's testicles illegal?
John Yoo: "No, [if] the President thinks he needs to do that."
The song "Happy Birthday" is under copyright.
If I send you two emails, one that contains a numbered list of every word to "Happy Birthday" along with 1000 other words, in alphabetical order, and another email that contains the numbers of the words "Happy Birthday" in the order they appear in the song, the two together constitute a copyright violation.
The same principle applies if I give the page- and line-numbers of a common dictionary, or any other referenced source, even if the referenced source was itself in the public domain.
If two legally independent systems existed to transport this data each one would probably be immune from being prosecuted for "aiding and abetting" copyright violations, particularly if there were other legitimate uses, but a combined infrastructure which encouraged people to use it for copyright violations would be legally problematic.
Let's put it another way:
If I ran a legitimate service that operated this way, and I filtered out "re-assembly URLs" that appeared to be copyright violations, that would be legally defensible.
If, independently of me, you took copyrighted data and put it on my system with bogus re-assembly instructions and labeled the data "random_numbers", and then sent the correct reassembly data through another mechanism, I would be legally off the hook, but if you were ever caught, you would not be.
Legally, this is not much different than copyrighted data encrypted by a one-time pad. Either half can be considered the non-copyrighted pad, and proving which half is the pad and which half is derived from the original can be legally difficult or impossible, but together, it's the same as the original and anyone or any organization that says "I have a safe way for you to use my product to safely transmit both halves to circumvent copyright protection laws" is going to get hauled into court and lose. Anyone or any organization which, through gross negligence, allows such traffic and who could reasonably stop it without shutting down non-infringing uses, or which doesn't have a substantial amount of non-infringing use, is asking for a legally expensive court fight. He might win the fight but he will be financially bruised for it.
If you are going to pull a stunt like this, make sure it's broken into enough organizational pieces that each piece is clearly legally defensible, and make sure both each piece and the overall technology enjoy substantial use by legal users. Also make sure there is no cheap way of segregating infringing from non-infringing use.
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
IANAL, but my understanding of copyright law and law in general is that it is typically performance based.
That means that If it is used and appears to have the purpose of distributing copyrighted material, no mathematical slight of hand in the middle changes the fact that copyrighted material is being moved. It may, however, offer some protection to the people operating the network, but anyone at the end points (providing/retrieving) is still likely to run into trouble. At the very least, it will be a costly argument to someone in court.
If the system offered substantial benefits to non-infringing users (and was used that way) over traditional ways of transferring files, then maybe they are ok, but if it looks like a duck, walks like a duck and talks like a duck, it must be a duck.
Long story short: Seek legal advice!
More Caffeine. NOW
There is a reason that legal "solutions" to technical problems deserve the derision we heap upon them. Legal "solutions" merely attempt to artificially constrain the problem without doing anything to resolve the technical nature of the problem itself.
To make this abundantly clear:
Legal solution to a technical problem - outlawing buffer overflow exploits
Technical solution to a legal problem - showing that the arresting officer made a procedural error which taints the evidence gathered against you.
You just mixed your namespaces.
1st: [Law solution (statutory)] tries to fix [Computer problem]
2nd: [Law solution (procedural)] tries to fix [Law problem]
These aren't equivalent. A technical computer solution to a computer problem is fine, as is a technical legal solution to a legal problem. What's worthy of derision is using a law solution to a computer problem or using a computer solution to a law problem, and that's what this is.
Claiming that you didn't violate someone's copyright because you copied their works without permission in a really nifty way is nonsense. Copyright law doesn't care if you independently produce exactly the same work as somebody; it's a strict liability tort -- "innocent" infringement is still infringement.
If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
Brightnets don't distribute material. They distribute random blocks. The URL distributes the material, by combining the random blocks in the Brightnet to something none-random. That none-random part can be anything, it could be something that is copyright-infringing or it could be something innocent like holiday photo's. If I'm storing random blocks for a Brightnet, I'm doing just that. Storing Random blocks of data. Nothing more nothing less. I have not clue, and can't know, how people are going to use those random blocks. It all depends on the URL, not on the Random Data.
In other words, it's distributing liability for infringement to all the people holding the bits you use to assemble the file. Wow. That's great.
No court is going to rule that centuries of legal tradition are meaningless before mathematical sophistry. The way you store the file is just as irrelevant to infringement as whether you've got music in MP3 format or AAC format.
You may think it's mathematically clever, but the court's aren't going to be interested in the logic of the math as much as the social and economic costs of allowing the creator's interpretation of copyright law to have any meaning. Courts will also look to the difficulty of enforcement if they limit liability to only those who uploaded the original file (which would be untraceable pretty quickly) and to those who downloaded the file via the URL (which is also nigh impossible to trace). The only easily identifiable contributors to the act left are those people holding the pieces.
The most likely result of a case like this is an extension of Grokster to create liability for just running the software since it doesn't have (per Grokster) "substantial noninfringing uses," and the software actively takes steps to make it impossible for the users not to have derivative portions of copyrighted works on their system. Efforts to make the transaction untraceable (via this randomized block encryption) and open advocacy of this as a means to defeat copyright would also count as "clear expression or other affirmative steps taken to foster infringement."
I can't see this software as accomplishing anything more than distributing liability for copyright infringement. The only saving grace for it is that you have no idea whose rights you're violating or how many violations you've committed, so you can't be on the hook (civilly) for every file you share pieces of since there's no way of identifying all the victims.
However, all it takes is for the RIAA or MPAA to hire MediaSentry or some other firm to download a single file and copy down the IP addresses of every person they get a chunk from, and it's lawsuit city!
At least you're safe from criminal copyright violation since that requires willful infringement which I don't think can be proven, though again the fact that you ran a service that you can't not infringe with might be damaging, but given that the only practical means of enforcing the laws would be to make the people running data stores liable, that's exactly what the courts will do, all your protests of holding "random" data be damned.
If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
I made a longer winded post about this here, but I'll summarize for you.
That's not the point. The point is that if someone downloads blocks from me to be used for copyrighted material, I cannot know what it is used for.
That's the problem. You have absolutely no way of knowing that you're not sharing infringing blocks, you have no way to prevent it, and yet you've still willingly installed and ran the software on your system.
How are the courts going to preserve copyright law in the face of this technical challenge? Make no mistake, courts aren't going to just throw up their hands in the air and say, "Wow! Centuries of legal tradition and entire sectors of the US economy have now been made obsolete by a very clever way of copying data. Let's call the whole thing off!" Somebody has to be held to account.
What can they do?
1) Make the person who uploaded the file liable?
2) Make the person who downloaded the file liable?
3) Make the people holding chunks of the file liable?
4) Treat the URL itself as a derivative work?
The first option is technically unfeasible. So is the second, unless you run your own data-store containing pieces of your own files as a sting operation, and you know what each chunk downloaded from you is. The third is feasible, because all it requires is that an authorized agent (like MediaSentry) download the file and track the IPs of all people who give them chunks -- every one of those people had an infringing piece, after all. The fourth has some real problems with not overreach and would create massive hassles for search engines, so I doubt the courts would go with that.
I think the most likely solution is to treat the software like that in Grokster as software that aids in infringement and doesn't have substantial noninfringing uses and to extend the decision to hold users liable for contributing to infringement. It's the most practical solution (from the court's perspective) to the situation.
All this accomplishes is getting them to turn another screw. So, thanks to all the people who invented this idea. Thanks a lot. (With friends like these, who needs enemies?)
If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
The thing is, with the right archiving algorithm, you could encrypt a given piece of data into any integer desired. For instance, XOR an MS Office zip against a tar file of the linux kernel. Take the output and go to the judge and ask for a Cease and Desist order, on the grounds that the kernel tar is in fact a representation of MS Office.
You'd need to be a bit more subtle than that, but I expect you make a reasonably convincing spoof encryption program without too much effort. You probably wouldn't go after something with such a solid provenance as the kernel, either, but you could probably shut down a lot of smaller legitimate online distributors.
Don't let THEM immanentize the Eschaton!
All of those are examples of binary data and mathematical manipulation of thereof. Picture can be represented, to an arbitrary degree of precision, as binary data. The operation of "cropping" is a mathematical transform on such. Repetition is a mathematical transform. Words are equivalent to numbers. "Close meaning" is a concept representable by numbers (a pair of concepts in a table with a number indicating "cloeseness" between them). Etc. Information and numbers (and thus binary numbers) are one and the same. Furthermore, the information inside human brain is represented in a form of electrical discharges and chemical states, all of which are equivalent to numbers. There is no escape from this. All information and numbers are interchangeable. This is one of the fundamental properties of information.
All of these are already numbers (represented by electrical discharges and protein assemblies). That is what information is.
No it is not. Science has dealt with this long ago, whole scientific theories were developed and tested dealing with properties of information and its transmission. It is the brain-dead lawyers and politicians who refuse to listen, primarily because this scientific knowledge gets in the way of Lord Greed. And we all know that Greed will trump science every time.
From what I am reading (I know, WTF am I doing actually R'ing TFA?), this isn't encryption in any sense of the word. It's hash comparison using random data. The blocks of data are not, in any way, related to the "stored" data. From what I can understand, a hash is generated using XOR against a random file block, based on some portion of the file you are "uploading". These blocks are then stored all over the place, and reused if they match someone else's (and it would seem they must, eventually... 128k is not an overwhelmingly huge address space). Each "node" (storage place) has its own unique identifier, and the blocks stored on it are referenced by other nodes to "store" the "inserted" data in the OFF.
From what I'm reading, this is either a really cool method of using up all those extra few gigs of space on everyone's hard drives (although "inserted" files triple in size, according to the wiki) which has nothing to do with copyright stuff (assuming you're not sharing the locator info), or this is just one more hoop to jump through in an attempt to keep the MAFIA (Movie And Film Industries of America) from noticing that your Brittney Spears collection is growing again. If the former, it's less than ideal. If the latter... well, at least Deep Packet Inspection (is that like a colonscopy for data?) won't be able to tell that you're pulling down mixes of "Oops I did it again" again. And, as other posters have stated... if you can show that the data you downloaded is actually a linux ISO and a video of you playing with your new dog in your own back yard, why does it matter that you can also convert it into a copy of that new blockbuster movie?
Obfuscation of a ubiquitous behavior seems like a poor solution, too.
If the majority of people are doing it, why is it still a legal issue?
On the other hand, the wiki has this bit about how game patches could be distributed using just a little more bandwidth than the executable itself. I'm wondering if that's per download, or if it's a one-time bandwidth chunk.
In summary, the concept of a global network of data storage is pretty neat, but I think we will find in the end that this particular implementation is flawed... assuming it doesn't turn out to be just a hack to hide illegal activites from the authorities. Paradigm-changing new tech I'm interested in. Arms race, not so much. Fight copyright, not enforcement.
This work is licensed under a Creative Commons Attribution 3.0 Unported License.
The problem with this argument is it's reductionist. If you blend up 5 copyrighted works and pour them into 10 shot-glasses (the network), sure you can claim each individual shot-glass doesn't fall under the same copyright of any single one of the original works. But since you can extract each of the 5 original works from the collective set of the 10 shot-glasses, then the network as a whole does contain the copyrighted works, and does fall under copyright protection. In a sense, they have smeared each copyright out over many (possibly overlapping) chunks, but it's still there because the originals can still be retrieved. Banning the whole network seems a possible legal outcome, since non-infringing uses may still involve moving chunks which contain a partial copyright.
As much as the creators of OFF might claim their work is different to a darknet, actually it relies on very similar principles of obfuscation.
Maybe, maybe not. It sounds like somebody was thinking about removing duplicate data from file systems in a significant way. They appear to have gotten side tracked by this idea of avoiding responsibility for copyright infringement, but the original concept is interesting. At least what I hope was the original concept.
Lets pretend I know the original concept, as I suspect I do, due to convergent thought processes. Essentially it is this, you get a large number of people to store chunks of indexed data and as more and more people add to the list, you remove duplicate entries beyond what is required for resiliency. For a couple thousand files, there is no significant improvement over regular existing compression algorithms, but over hundreds of millions, perhaps a couple billion, you end up with needing very little additional storage for your entire library of files. You can do backups of your entire system requiring additional storage of perhaps a couple hundred megabytes. Data is compressed on the end blocks with traditional algorithms, decompressed on the fly.
There are two problems with the implementation as I read it. First, they are randomizing the data rather than the distribution alone. I should be able to fearlessly store a couple gigabytes for anonymous users since I am gaining from the service a distributed resilient and redundant file system. However, the savings in storage are negated since two copies of the same file with different origins would have different (essentially encrypted) segments requiring double the storage of unencrypted versions.
Second, the system described in the only page I read doesn't adequately deal with data collisions. I'd be happy to make backups onto such a system if it were dependable, but leaving aside the nature of a voluntary anonymous Internet system, the possibility of data corruption would cut my desire down to practically nil.
Yes nitpickers, I do know that it isn't really encryption, but it is like enough for the purposes of my point. As to technical merits, I've done it at file level backups and it was hugely significant and reliable, I did md5.sha1 which was good enough for my purposes, but add more as fits your personal paranoia level. I was explaining my closest theory on a method that does almost this to coworkers complete with mysql database and whiteboard two weeks ago, i.e. convergent thought processes.
B) Eliminate all the stupid users. This is frowned upon by society.