Kind of a little too bureaucratic when they can't even use Google without a warrant... LaBarbara: But something changed when my man turned pro. Hermes: I was sortin' but I wasn't smilin'. LaBarbara: He forgot that it's not about badges and ranks. Hermes: [punning] It's supposed to be about da filin'! People!
Actually, I believe that there was an attempt to port Quake so that it's playable via Sneakernet. Maybe for a short-range, medium-latency sneakernet. For the networking stats of this sneakernet, you might need a different variant.
Still, this brings up an interesting idea for a project: construct a network where multiple packets are carried in bursts on physically delivered storage media (such as a USB drive) where you can only retrieve those packets addressed to you when it arrives and not monitor the others. Obviously encryption would be required, but design it for reasonable packaging and retrieval from the thumb drive. Anyone could add packets to the media after retrieving their own. Basically, formalize a community sneakernet. Best if it can be made compatible with a private LAN of, say, an apartment building that has no direct connection to the Internet.
You have 26 days left to get the RFC in by April 1.
Not to say that I think it is entirely a joke. This could be useful when we discover we cannot trust the common carriers any more.
When you establish a scheme where you withhold your exclusive rights from your contemporaries for their lifetime, you will have contemporaries that will say, "Nuts to that," and disregard your rights. There's no benefit for them to wait until the work passes into the public domain if they'll be long dead before that ever happens.
As it stands now, copyright law might as well be based not on author's lifetime but rather the lifetime of the last (mortal) survivor of the year when the work was first published. Disregarding Disney, that would appear to be the goal of Lifetime + 70 years: to ensure that your work is never exploited by anyone that directly knew of your being alive.
HTTP is clear that the client must honor the Content-Type provided by a server when provided. If that type is text/plain, the client must treat it as text/plain, not text/html, image/gif, or application/octet-stream. If and only if the server does not provide the Content-Type may the client inspect. "Content-Type: text/plain" != "". Quoting:
Any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the media type of that body. If and only if the media type is not given by a Content-Type field, the recipient MAY attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the resource. If the media type remains unknown, the recipient SHOULD treat it as type "application/octet-stream". Strongness added by me. I have yet to hear of an IE version that passes HTTP compliance in this one regard by default. (I've heard that even the option to force compliance in this regard in some versions doesn't work either.)
The consequence of IE's non-compliance is misconfigured servers that serve binary data as text/plain because people building the sites only test with IE and never learn how to teach the server to send the proper Content-Type header. Put a.ISO file on your website without telling the server that.ISO should be served as application/octet-stream and you get users with compliant browsers loading the disk image as plain text in their browser windows.
The only thing wrong with RFC 2616 in this section is that it strays from the terminology defined in RFC 2119 in using "if and only if" in conjunction with a SHOULD to hide what should have been labeled a MUST NOT as a MAY. The intent was that clients MUST implement support for what the server SHOULD provide and not nullify the benefit of a server implementing a SHOULD but rather give accommodation to servers which do not do what they SHOULD do. A rewrite would say it more clearly:
Any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the media type of that body. If included, the recipient MUST honor the media type provided by the Content-Type field and MUST NOT attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the resource. Only if the media type is not given by a Content-Type field MAY the recipient so guess the media type and, if the media type remains unknown, the recipient SHOULD treat it as type "application/octet-stream". Or just separate the client responsibilities from the server responsibilities, or update RFC 2119 to include a definition for and require the capitalization of IF AND ONLY IF.
In 2006, the authorities banned download speeds on private computers faster than 128 kilobytes per second. OK folks, it's high time someone developed some tight compression algorithms so the Iranians can watch live DissidentTV on the Intertubes at 127Kbps. Bits and bytes, dude. 128 KBps == 1 Mbps.
A lot of people in the US don't even have 1 Mbps download. Even more don't have 1 Mbps upload.
The original Cylons were the tin cans. Somehow the tin cans built the later humanoid models (and demonstrated a very finely developed aesthetic sense with regards to the female form). So how are the later models the "children of humanity" rather than the Children of Aluminum Foil?
NB: I watched the first two seasons and became so utterly bored during the third that I have not watched it since then. I guess you missed the Razor Flashbacks then, where it was revealed that it was shortly before the end of the first war that the Cylons were experimenting with creating the next biological models.
(I was a little disappointed not to see an original-design Basestar in either the flashbacks or in Razor itself.)
Or maybe it happened because they did implement the Three Laws? Sometimes I wonder if any of the people constantly referencing those laws have actually read Asimov. You mean like "Little Lost Robot" where a robot with a modified First Law (striking all after and including "or through inaction...") was able to convince other robots to violate their complete First Law in the short term in order to adhere to it in the long term?
Interestingly, in doing so that robot negated its own reason for manufacture as normal robots would only need similar training to allow humans to work in a hazardous environment which would be fatal to robots without the robots sacrificing themselves. But IIRC that point was not touched on in the story.
If you could make boats go where you wanted to from the comfort of your own home, wouldn't you? And if one of them didn't do what you told it to do, who wouldn't send Superman in to punch a few holes in its hull?
So, which is it, Julius Baer? Are these documents forgeries, or are they real documents and therefore subject to banking privacy laws? You don't get to have your cake and eat it, too. Have you not heard of superposition? It's a matter of quantum legal entanglement.
That's easy, you just skim the atmosphere just enough to slow it down, but not so much that it crashes to earth. Nor any bits break off big enough to survive re-entry.
But if it comes hurtling between the Earth and the Moon, it will unleash cosmic destruction. Man's civilization will be cast in ruin. It will take two thousand years for Earth to be reborn, a strange new world rising from the old. A world of savagery, super-science, and sorcery.
90% of software is written within organisations and never sees light of day outside of the organisations that create it.
What Open Source does is to liberate a little of this 90%, the bits which other organisations might find useful and can easily adopt into their IT systems. The companies that release it get: feedback, bug fixes and enhacements. The guys who receive/use the software send their patches back because doing so is less (long term) work than putting the patches into each new release that comes out. Unless the patches they make are to make it work with their other proprietary systems. Then they can't release it, can't submit patches back, and the version they run stagnates to the point that even they forget what the patches they applied were, so they can't apply them to newer versions anyway.
And that is why I today in 2008 I write code at work using an XEmacs version ca. 1995.
The point you are all missing here is that no one is going to pay support for a game like tetris Not even psychiatric support to get rid of the persistent Tetris dreaming?
Slashdot Mirror
Hermes: I was sortin' but I wasn't smilin'.
LaBarbara: He forgot that it's not about badges and ranks.
Hermes: [punning] It's supposed to be about da filin'! People!
Still, this brings up an interesting idea for a project: construct a network where multiple packets are carried in bursts on physically delivered storage media (such as a USB drive) where you can only retrieve those packets addressed to you when it arrives and not monitor the others. Obviously encryption would be required, but design it for reasonable packaging and retrieval from the thumb drive. Anyone could add packets to the media after retrieving their own. Basically, formalize a community sneakernet. Best if it can be made compatible with a private LAN of, say, an apartment building that has no direct connection to the Internet.
You have 26 days left to get the RFC in by April 1.
Not to say that I think it is entirely a joke. This could be useful when we discover we cannot trust the common carriers any more.
Before today you would have thought "Government Seeks Warrant to Search the Internet" was a headline from The Onion.
When you establish a scheme where you withhold your exclusive rights from your contemporaries for their lifetime, you will have contemporaries that will say, "Nuts to that," and disregard your rights. There's no benefit for them to wait until the work passes into the public domain if they'll be long dead before that ever happens.
As it stands now, copyright law might as well be based not on author's lifetime but rather the lifetime of the last (mortal) survivor of the year when the work was first published. Disregarding Disney, that would appear to be the goal of Lifetime + 70 years: to ensure that your work is never exploited by anyone that directly knew of your being alive.
I propose a 21 Cast-Magic-Missile-into-the-Darkness salute.
The consequence of IE's non-compliance is misconfigured servers that serve binary data as text/plain because people building the sites only test with IE and never learn how to teach the server to send the proper Content-Type header. Put a
The only thing wrong with RFC 2616 in this section is that it strays from the terminology defined in RFC 2119 in using "if and only if" in conjunction with a SHOULD to hide what should have been labeled a MUST NOT as a MAY. The intent was that clients MUST implement support for what the server SHOULD provide and not nullify the benefit of a server implementing a SHOULD but rather give accommodation to servers which do not do what they SHOULD do. A rewrite would say it more clearly: Any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the media type of that body. If included, the recipient MUST honor the media type provided by the Content-Type field and MUST NOT attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the resource. Only if the media type is not given by a Content-Type field MAY the recipient so guess the media type and, if the media type remains unknown, the recipient SHOULD treat it as type "application/octet-stream". Or just separate the client responsibilities from the server responsibilities, or update RFC 2119 to include a definition for and require the capitalization of IF AND ONLY IF.
A lot of people in the US don't even have 1 Mbps download. Even more don't have 1 Mbps upload.
Having your own people try to save (and mate with) the survivors really doesn't help meet your goal of genocide.
Google Goggles
Google Goggles
We incept them
We incept them
One of ours
One of ours
paradigm change Change for a pair of dimes
See also "nickel and dime you to death".
(I was a little disappointed not to see an original-design Basestar in either the flashbacks or in Razor itself.)
Interestingly, in doing so that robot negated its own reason for manufacture as normal robots would only need similar training to allow humans to work in a hazardous environment which would be fatal to robots without the robots sacrificing themselves. But IIRC that point was not touched on in the story.
Not all the pr0n, just the really fast pr0n.
Measuring data quantity by its speed over a distance in kilometers? What's next, measuring its speed by its acceleration over a volume in Liters?
No, it's a Sunday.
But if it comes hurtling between the Earth and the Moon, it will unleash cosmic destruction. Man's civilization will be cast in ruin. It will take two thousand years for Earth to be reborn, a strange new world rising from the old. A world of savagery, super-science, and sorcery.
Wasn't that a historical drama about legislation legalizing prostitution management?
What Open Source does is to liberate a little of this 90%, the bits which other organisations might find useful and can easily adopt into their IT systems. The companies that release it get: feedback, bug fixes and enhacements. The guys who receive/use the software send their patches back because doing so is less (long term) work than putting the patches into each new release that comes out. Unless the patches they make are to make it work with their other proprietary systems. Then they can't release it, can't submit patches back, and the version they run stagnates to the point that even they forget what the patches they applied were, so they can't apply them to newer versions anyway.
And that is why I today in 2008 I write code at work using an XEmacs version ca. 1995.