Slashdot Mirror
How To Communicate Faster-Than-Light
higuita writes "With faster technologies showing up everyday, people need to prepare in advance the problems of faster-than-light communication. The main problem is that packages will arrive to the destination before they are sent, forcing a huge redesign of most protocols. Read here the first draft RFC. Any network expert is free to help fine tune this draft."
It's perfectly obvious that this is true. However, it actually isn't true at all.
Relativity is a mind fuck.
Photons also don't have rest mass so infinite energy isn't required.
Well, actually It is 11:15 pm, April 1st 2013 as I type this (Central Time Zone, USA.) So, you are incorrect.
Emphasis mine. Since both you and the person who modded me down don't seem to understand, I'll explain, and then repeat myself: am is before noon, pm is after noon.
April fool's pranks must be performed before noon on April 1st to be considered as such. It was not before noon on April 1 in any timezone when that story was posted.
So it is no longer an April fool's prank.
You can never know everything, and part of what you do know will always be wrong. Perhaps even the most important part.
This is *Not* an April fools!!... Slashdot is reporting on an RFC, published in draft status. No Joke. Like other RFC's published on April 1st, It probably wont have any real world usage (unless we actually find a way of sending things faster than light, at which point the universe collapses into a paradoxial soup), and is there mostly for its comedic value. BUT, that is not the point, the point is this is an attempt at working out how to send things over a FTL medium, and documenting them in an RFC.
IP Over Avian carriers (rfc1149), another April 1st RFC, was implemented a few years later. It worked.
He did say Gigapeople, not Gibipeople.
PlusFive Slashdot reader for Android. Can post comments.