Skip to main content

Science: Gravity as a Communications Mechanism?

Does gravity move at the speed of light? For instance, if I were able to change some energy into matter, how long would it take for other matter to begin to feel the attraction of the matter I created? I assume someone out there knows the answer.

If you could convert energy to matter and back again in an amazingly concise manner, and do it at a specific frequency, and if you could detect such changes in gravity at a specific frequency, you could conceivably use gravity as a communications mechanism. That's not likely to happen during my lifetime, but it does make for some interesting science fiction.

Comments

Shrutarshi Basu said…
Yes, gravity does "travel" at the speed of light. But I feel like Gravitional communication would be an incredibly wasteful method of communication. A simple laser beam would get the same speed for far less cost. Good idea though.
metapundit.net said…
I guess it's back to work on your quantum entanglement walkie-talkie.
Eddy Mulyono said…
that would make an interesting covert channel...
jjinux said…
From Jesse Montrose:

I put that idea into my (still unfinished) NaNoWriMo novel last year :)

But I just read this:

http://math.ucr.edu/home/baez/physics/Relativity/GR/grav_speed.html
Anonymous said…
In David Weber's Honor Harrington series the 'good guys' develop this an a FTL communications system.

Good concept
jjinux said…
Crazy.
Unknown said…
Well, there is at least a way to turn matter into energy. It's sort of like a one-way hash, however. It's also called an "atomic bomb". ;-)
jjinux said…
While it's true that an atomic bomb does indeed send a message, it's not quite the communications mechanism I had in mind ;)

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

JavaScript: Porting from react-css-modules to babel-plugin-react-css-modules (with Less)

I recently found a bug in react-css-modules that prevented me from upgrading react-mobx which prevented us from upgrading to React 16. Then, I found out that react-css-modules is "no longer actively maintained". Hence, whether I wanted to or not, I was kind of forced into moving from react-css-modules to babel-plugin-react-css-modules. Doing the port is mostly straightforward. Once I switched libraries, the rest of the port was basically:
Get ESLint to pass now that react-css-modules is no longer available.Get babel-plugin-react-css-modules working with Less.Get my Karma tests to at least build.Get the Karma tests to pass.Test things thoroughly.Fight off merge conflicts from the rest of engineering every 10 minutes ;) There were a few things that resulted in difficult code changes. That's what the rest of this blog post is about. I don't think you can fix all of these things ahead of time. Just read through them and keep them in mind as you follow the approach above.…