 |
 |
RAM a legal US document
|
 |
|
 |
|
Moderator 
Join Date: Feb 2006
Location: on the verge of insanity
Status:
Offline
|
|
|
|
|
I like my water with hops, malt, hops, yeast, and hops.
|
| |
|
|
|
 |
|
 |
|
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status:
Offline
|
|
Yeah, great huh? That's what happens when laymen make legal rulings concerning technology.
|

"The natural progress of things is for liberty to yield and government to gain ground." TJ
|
| |
|
|
|
 |
|
 |
|
Moderator 
Join Date: Feb 2006
Location: on the verge of insanity
Status:
Offline
|
|
I'm not sure what they think they can get out of it or how it could possibly help/hurt any court case.
|
|
I like my water with hops, malt, hops, yeast, and hops.
|
| |
|
|
|
 |
|
 |
|
Administrator 
Join Date: Apr 2001
Location: San Antonio TX USA
Status:
Offline
|
|
Look at the context; the judge is saying basically that a file that hasn't yet been stored is still a file and subject to subpoena. Take a look at the case the ruling is about. Torrentspy is saying that they're not handling any "files" because it's all in RAM, and the copyright holders are saying "you're handling the data in a form that may as well BE a file, so let's all just call it a file." The judge seems to have agreed with the plaintiffs. I can't disagree either. If you're intentionally using a volatile storage medium to skirt the law in terms of file handling, then your volatile storage is going to have to be subject to the same requirements as your hard drives.
|
|
Glenn -----
OTR/L, MOT, Tx
|
| |
|
|
|
 |
|
 |
|
Posting Junkie
Join Date: Mar 2001
Location: Salamanca, EspaƱa
Status:
Offline
|
|
I don't buy it.. things in RAM are sometimes (most of the time in fact) completely out of the control of the user. When I surf the web I have no direct control over what goes into the computer's RAM.
Only indirectly, by choosing what parts of the internet I receive information from.
I can only discern, accept or refuse said information *after* I receive it, thus *after* it has been written into RAM.
In other words, illegal information can be transmitted to my computer without my authorization and I should not be held accountable for it. Whatever the circumstance may be.
So if it is a legal 'loophole' in some cases.. besides what good is RAM anyway as evidence? Yank the plug and wham-o it is gone forever. No trace, no evidence it was ever there in the first place.
Thus, this is both impractical and dubious regarding personal rights and privacy IMO.
V
|
|
I could take Sean Connery in a fight... I could definitely take him.
|
| |
|
|
|
 |
|
 |
|
Mac Enthusiast
Join Date: May 2007
Location: Portland, Oregon
Status:
Offline
|
|
|
|
|
24" iMac 2.16GHz c2d ~ 3G ram ~ 250G ~ Superdrive ~ Pure Sexiness
15" Powerbook G4 ~ 1.5GHz ~ 1.5G ram ~ 160G ~ Combo
|
| |
|
|
|
 |
|
 |
|
Addicted to MacNN
Join Date: Mar 2005
Location: Louisiana
Status:
Offline
|
|
Quick! Someone had better Email the judge!
I'm sure he'll be flabbergasted...
|
|
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Sep 2000
Status:
Offline
|
|
Originally Posted by ghporter
The judge seems to have agreed with the plaintiffs. I can't disagree either. If you're intentionally using a volatile storage medium to skirt the law in terms of file handling, then your volatile storage is going to have to be subject to the same requirements as your hard drives.
Individuals and businesses should have a right not to keep records if they so choose, regardless of the intension, and particularly for something like file sharing, which is not a matter of "national security" by any means,-- though I'm sure it could easily be spun as such.
I think we all know that the contents in RAM are indeed not documents, but incidental traces of which a computer requires to process the data in real-time. If this company is indeed doing anything illegal, there must be other means which are less detrimental to personal liberties than that of declaring the contents of RAM a legal document that can be subpoenaed.
|
|
|
| |
|
|
|
 |
|
 |
|
Mac Enthusiast
Join Date: May 2007
Location: Portland, Oregon
Status:
Offline
|
|
|
(Last edited by irunat2am; Jun 16, 2007 at 08:04 PM.
(Reason:I'm retarded))
|
|
24" iMac 2.16GHz c2d ~ 3G ram ~ 250G ~ Superdrive ~ Pure Sexiness
15" Powerbook G4 ~ 1.5GHz ~ 1.5G ram ~ 160G ~ Combo
|
| |
|
|
|
 |
|
 |
|
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status:
Offline
|
|
Originally Posted by ghporter
Take a look at the case the ruling is about. Torrentspy is saying that they're not handling any "files" because it's all in RAM, and the copyright holders are saying "you're handling the data in a form that may as well BE a file, so let's all just call it a file." The judge seems to have agreed with the plaintiffs. I can't disagree either. If you're intentionally using a volatile storage medium to skirt the law in terms of file handling, then your volatile storage is going to have to be subject to the same requirements as your hard drives.
Respectfully, you're wrong on this one, gh. Data in RAM is not stored in any file format. Data in RAM is machine readable not human readable, ephemeral, constantly changing. And data in RAM could at any particular moment contain snippets of networking, program or OS code. RAM is not file storage space (unless you're using a RAM disk, which servers definitely are not), and there can be no expectation that it should function that way. Moreover, the contents of RAM update so often there's no mechanism to capture all of the stream at any one time; even if there were, the contents would quickly fill up any permanent storage (especially on a highly utilized bank of servers). Plus, even If such a thing could be done, the contents of what got recovered would be largely meaningless. The media cartel has gotten a nonsensical order out of this judge.
|

"The natural progress of things is for liberty to yield and government to gain ground." TJ
|
| |
|
|
|
 |
 |
|
 |
|
|
|
|
|

|
|
 |
Forum Rules
|
 |
 |
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
 |
 |
 |
 |
|
 |
|