I would think that even if it were a very short time there would still be problems -- after all you WERE destroyed.
Yes, but if you were "rebuilt" on a particle level, no matter how long you'd be destroyed/dead, it seems logical to me that you should be in the exact health as you were when you were destroyed".
The problem might of course be to rebuild an entire person with the billions of particles in the exact same relative positions as before.:-)
Bell Labs also have a history of Unix on their web site, written by one of the creators of UNIX. Do not miss the "Next" links below the articles and read how the story of Unix unfold! I almost did and thought they just had a short blurb about it.:-P
It's actually pretty in-depth and I found it interesting at least.:-)
It also discuss how the B language (first letter in BCPL; the basis for B) evolved into C, and some of the obstacles they met when creating "The bext B" that became C, the idea of Unix pipes, a discussion of the syntax of Unix commands,
It proceeds into discussing the Unix "wars" between Sun and AT&T, the creation of the Open Software Foundation, etc.
Some quotes:
"Like another legendary creature whose name also ends in 'x,' UNIX rose from the ashes of a multi-organizational effort in the early 1960s to develop a dependable timesharing operating system."
"He [Ken Thompson] put pipes into UNIX, he put this notation into shell, all in one night," McElroy said in wonder.
"Thirty years after its creation, UNIX still remains a phenomenon," Ritchie marveled.
A calculation of what would happen if we'd dilute all the urine from one days urination of the world population into all the 1.4 billion trillions litres water on earth. Yes, thank god for the internet putting questions like these into rest.:-)
Now tell me what FLAC has that lzip hasn't! I constantly compress my CD rips down to a few MB's. You can too!
Some impressive stuff from the FAQ that made me leave that Monkey-compression-thingy once and for all:
"We're talking about a constant-time algorithm that can reduce a file down to 0% of its original size. What's not to like?" --- "You will most likely experience a feeling of euphoria or lightheadedness as you watch your free disk space cascade upwards to 100%." --- Are there any drawbacks?
"Not that we know of. Occasionally, in the pre-1.0 days, someone would compress a file down to 0K and it would be lost for good. But that has been happening less and less frequently, and these days it has been a long time since we received any complaints from the people who reported this originally." ---
I'm especially impressed by their complex PLACeBO and Lessiss-Moore algorithms.
I have come to the conclusion that the only way to get away from these stupid laws, and stay away from them in the future, is to create SlashNation, where attempts to keep any forms of information, such as source code, secret has a death penalty. CowboyNeal for president!
This might provide solutions to your points mentioned above except the first "1st world type living". The Geeks of SlashNation would have a long way to get there, but I'm sure we can do it!
.. sounds like a poor idea to me. Yes, you can measure the amount of redundancy in a message, but:
a) Spammers might not always use messages redundant enough to be detectable from regular text.
b) If I happened to use some words a little too often, especially when writing mails discussing technical stuff or posting computer code fragments, would that be classified as spam?
I think this is a nice filter when sorting out more or less repetitive mails (spam or not) from novels, but a filter based on a spam database sounds better to me.
1. Design p2p client using a network offering the performance of eMule. 2. Make it as anonymous and decentralized as FreeNet. 3....? (add spyware?) 4. Profit!
This plan of course fails in the occasion where FreeNet offer the same performance as eMule, but I don't think it does.:-(
1. Minimum share restrictions. The hubs with most varied content usually requires 50 Gb+ shared material. I'll never buy a new hard drive just for a special kind of p2p network. It's not *that* good. Many ppl "fix" the problem by sharing bogus files. Wee, watch the network quality go down the drain.
2. The hub philosophy. I don't want to restrict myself to a couple of hubs when Kazaa is an enormous, global, network (same with Overnet). eMule seem to work in a similar fashion where one server finds another, which finds another, etc. Hubs suck when you wish to get a lot of sources for a file *or* wish to get a rare file.
The only pro I can see about DC/DC++ is that you usually get fast download speeds since you can decide to connect to relatively local hubs that are at least in your country.
how is it possible to download one's first movie from Overnet without appearing "evil"?
While you download your first movie from Overnet, everyone will be able to download the movie you're currently downloading from you, as long as your upload queue doesn't fill up. So it's not that bad IMHO, especially if you keep your downloaded stuff shared after you've got it.
Then it's worse to bypass the leech restrictions put into Kazaa since they was put in for a reason. If a guy that haven't contributed much to the network just steal my bandwidth, I wouldn't be as happy as if I knew the guy I was uploading to was *truly* a "supreme being" on the p2p network.
Yes, using IPv6 where the phones are of course connected to a DNS as well is an interesting thought... An international standard for how to "build" these "dial addresses" would be useful as well. They could reuse country codes too. My phone number could be something like:
<number>.pitea.bd.se
"pitea" is the city. "bd" is for Norrbotten, the equivalent of a state in the USA. "se" is Sweden.
Quite short for being international too and you'd just need to add a number when necessary (i.e. not restricted to a special format of, say, 9 digits).
But there might be some "funny" moments when someone hack the DNS to redirect a "phone address" to a pr0n number, redir CowboyNeal's number to Hilary Rosen, etc.:-(
Or if a DNS with its backups get an error and you have to phone using IPv6 format to get to the right place: 3ffe:8114:2000:240::1... eww
I can only say that if the Linux users are missing the movies until they get that part included, they aren't missing much. I didn't find the movies very necessary for the storyline. They pretty much only tell what happens as a consequence of the previous Chapter you completed, which isn't hard to figure out by yourself. Also, the movies consists of still pictures that fade in/out, are zoomed into, etc. You aren't exactly missing any movies of "Blizzard quality". This was kind of an anticlimax to me since the *intro* movie is decent, but the inter-chapter movies are of a very different quality.:-/
the laying of songs "onto a copy-controlled CD in multiple layers, one that would permit normal playback on a stereo and a PC."
I guess we all need more technical information for this not to sound like a real dumbass copy protection.:-) Or is there a difference between "normal playback" and "copy" that I missed?
Those kernel panics can even be dangerous for other people than to the guy getting the surgery... Just think about what would happen if the "surgeon" suddenly got a:
"Aarggh: attempting to free lock with active wait queue - shoot Andy"
Slashdot Mirror
Sorry I couldn't find the Google News link for the NYT article.
In the URL of the NYT article, replace "www" with "archive".
I would think that even if it were a very short time there would still be problems -- after all you WERE destroyed.
:-)
Yes, but if you were "rebuilt" on a particle level, no matter how long you'd be destroyed/dead, it seems logical to me that you should be in the exact health as you were when you were destroyed".
The problem might of course be to rebuild an entire person with the billions of particles in the exact same relative positions as before.
Yes, I'm 100% sure I read a similar photon teleportation experiment some year(s?) ago. It wasn't over a mile that time though.
Bell Labs also have a history of Unix on their web site, written by one of the creators of UNIX. Do not miss the "Next" links below the articles and read how the story of Unix unfold! I almost did and thought they just had a short blurb about it. :-P
:-)
It's actually pretty in-depth and I found it interesting at least.
It also discuss how the B language (first letter in BCPL; the basis for B) evolved into C, and some of the obstacles they met when creating "The bext B" that became C, the idea of Unix pipes, a discussion of the syntax of Unix commands,
It proceeds into discussing the Unix "wars" between Sun and AT&T, the creation of the Open Software Foundation, etc.
Some quotes:
"Like another legendary creature whose name also ends in 'x,' UNIX rose from the ashes of a multi-organizational effort in the early 1960s to develop a dependable timesharing operating system."
"He [Ken Thompson] put pipes into UNIX, he put this notation into shell, all in one night," McElroy said in wonder.
"Thirty years after its creation, UNIX still remains a phenomenon," Ritchie marveled.
Not to mention all dinosaurs... :-)
Avogadro, urine and eternal recycling
:-)
A calculation of what would happen if we'd dilute all the urine from one days urination of the world population into all the 1.4 billion trillions litres water on earth. Yes, thank god for the internet putting questions like these into rest.
So no, lzip ain't as good as FLAC.
Read in their FAQ and it says that you probably won't notice that data you'll loose since it chooses the most unimportant parts anyway.
Oh, and it's a joke.
Now tell me what FLAC has that lzip hasn't! I constantly compress my CD rips down to a few MB's. You can too!
Some impressive stuff from the FAQ that made me leave that Monkey-compression-thingy once and for all:
"We're talking about a constant-time algorithm that can reduce a file down to 0% of its original size. What's not to like?"
---
"You will most likely experience a feeling of euphoria or lightheadedness as you watch your free disk space cascade upwards to 100%."
---
Are there any drawbacks?
"Not that we know of. Occasionally, in the pre-1.0 days, someone would compress a file down to 0K and it would be lost for good. But that has been happening less and less frequently, and these days it has been a long time since we received any complaints from the people who reported this originally."
---
I'm especially impressed by their complex PLACeBO and Lessiss-Moore algorithms.
And don't forget to read their Free-Object Oriented License (or simply "FOO"):
We should see FLAC streaming support in Icecast soon, at least I hope so.
:-)
I'm not sure your ISP hope so, though.
I have come to the conclusion that the only way to get away from these stupid laws, and stay away from them in the future, is to create SlashNation, where attempts to keep any forms of information, such as source code, secret has a death penalty. CowboyNeal for president!
This might provide solutions to your points mentioned above except the first "1st world type living". The Geeks of SlashNation would have a long way to get there, but I'm sure we can do it!
Still, you use hotmail (aka "spammer's heaven") here on Slashdot. But thanks for the tip, perhaps we should start trying it out? :-)
.. sounds like a poor idea to me. Yes, you can measure the amount of redundancy in a message, but:
a) Spammers might not always use messages redundant enough to be detectable from regular text.
b) If I happened to use some words a little too often, especially when writing mails discussing technical stuff or posting computer code fragments, would that be classified as spam?
I think this is a nice filter when sorting out more or less repetitive mails (spam or not) from novels, but a filter based on a spam database sounds better to me.
Yeah, but there are some problems still...
...? (add spyware?)
:-(
Here's a plan that should work:
1. Design p2p client using a network offering the performance of eMule.
2. Make it as anonymous and decentralized as FreeNet.
3.
4. Profit!
This plan of course fails in the occasion where FreeNet offer the same performance as eMule, but I don't think it does.
I have two problems with DC:
1. Minimum share restrictions. The hubs with most varied content usually requires 50 Gb+ shared material. I'll never buy a new hard drive just for a special kind of p2p network. It's not *that* good. Many ppl "fix" the problem by sharing bogus files. Wee, watch the network quality go down the drain.
2. The hub philosophy. I don't want to restrict myself to a couple of hubs when Kazaa is an enormous, global, network (same with Overnet). eMule seem to work in a similar fashion where one server finds another, which finds another, etc. Hubs suck when you wish to get a lot of sources for a file *or* wish to get a rare file.
The only pro I can see about DC/DC++ is that you usually get fast download speeds since you can decide to connect to relatively local hubs that are at least in your country.
Doh...
Restrict your upload speed in Kazaa then.
how is it possible to download one's first movie from Overnet without appearing "evil"?
While you download your first movie from Overnet, everyone will be able to download the movie you're currently downloading from you, as long as your upload queue doesn't fill up. So it's not that bad IMHO, especially if you keep your downloaded stuff shared after you've got it.
Then it's worse to bypass the leech restrictions put into Kazaa since they was put in for a reason. If a guy that haven't contributed much to the network just steal my bandwidth, I wouldn't be as happy as if I knew the guy I was uploading to was *truly* a "supreme being" on the p2p network.
If you don't wish to trust CNet words too much, it might help to throw in a more official link:
j ul02/0724palladiumwp.asp
http://www.microsoft.com/presspass/features/2002/
This is an old press release, but read the "Editor's Update".
What are you rambling on about? And why are you modded up? If I wasn't confused enough today, I am now. :-)
Yes, using IPv6 where the phones are of course connected to a DNS as well is an interesting thought... An international standard for how to "build" these "dial addresses" would be useful as well. They could reuse country codes too. My phone number could be something like:
:-(
... eww
<number>.pitea.bd.se
"pitea" is the city. "bd" is for Norrbotten, the equivalent of a state in the USA. "se" is Sweden.
Quite short for being international too and you'd just need to add a number when necessary (i.e. not restricted to a special format of, say, 9 digits).
But there might be some "funny" moments when someone hack the DNS to redirect a "phone address" to a pr0n number, redir CowboyNeal's number to Hilary Rosen, etc.
Or if a DNS with its backups get an error and you have to phone using IPv6 format to get to the right place: 3ffe:8114:2000:240::1
I can only say that if the Linux users are missing the movies until they get that part included, they aren't missing much. I didn't find the movies very necessary for the storyline. They pretty much only tell what happens as a consequence of the previous Chapter you completed, which isn't hard to figure out by yourself. Also, the movies consists of still pictures that fade in/out, are zoomed into, etc. You aren't exactly missing any movies of "Blizzard quality". This was kind of an anticlimax to me since the *intro* movie is decent, but the inter-chapter movies are of a very different quality. :-/
... the trolls tremble in fear!
the laying of songs "onto a copy-controlled CD in multiple layers, one that would permit normal playback on a stereo and a PC."
:-) Or is there a difference between "normal playback" and "copy" that I missed?
I guess we all need more technical information for this not to sound like a real dumbass copy protection.
New != Better
No, but the chances are greatly improved.
A decent result for a first try, perhaps?
Those kernel panics can even be dangerous for other people than to the guy getting the surgery... Just think about what would happen if the "surgeon" suddenly got a:
;-)
"Aarggh: attempting to free lock with active wait queue - shoot Andy"
Would his/her relatives shoot Andy?