21–30 of 42 posts
Just like with iodine (dns tunnel) this was one thing me and my friends talked about that would be cool.
I actually started to implement this in haskell in 2011, and gave up after I had basic writes to files working. I can get dig out that code if anyone is interested.
The c version of the project hasnt gotten very far yet as you can see, I might pick it up again though.
Can someone please explain what this does? I've read the readme, glanced through the code, and still have no idea.
If we had space probes with ICMP support, you could use this to store data in the interplanetary æther.
You don't need ICMP for that, or even an active space probe. Just encode your data in laser pulses and bounce it off one of the retroreflectors we've put out there. There are at least three on the moon, or the LAGEOS satellites ( https://en.wikipedia.org/wiki/LAGEOS ) would work.
In the pre-smtp days, email links were over UUCP, which was often relayed via dial up lines which connected intermittently, on a schedule (e.g. every hour). You also specified not just the destination, but also the route for the email to take, via a 'bang path': https://en.wikipedia.org/wiki/UUCP#Bang_path Add in the situation of disk quotas for university students, but not email quotas, and you get the means, motive…
There is a problem called “Buffer bloat”¹ which is that many manufacturers of networking equipment provide too much buffer memory, which leads to TCP latency and timeouts, since TCP was not designed with these large buffers in mind. Using Pingfs will take up buffer space in networking equipment. This could either be a good thing, since it decreases the available buffer space, or it might be a bad thing since it might make networking providers increase their buffers.
I’m not sure how much of this comment is serious.
Technically, the data is not stored in the network, but in the buffer memory of the routers (and switches) in the path of the packets. So what this is really doing is externalizing the cost of storage to the network providers. There is a problem called “ Buffer bloat ”¹ which is that many manufacturers of networking equipment provide too much buffer memory, which leads to TCP latency and timeouts, since TCP was not d…
Technically, the data is not stored in the network, but in the buffer memory of the routers (and switches) in the path of the packets. So what this is really doing is externalizing the cost of storage to the network providers. There is a problem called “ Buffer bloat ”¹ which is that many manufacturers of networking equipment provide too much buffer memory, which leads to TCP latency and timeouts, since TCP was not d…
But you are probably correct, the time in the cables is probably not even close to the time the data is stored in the equipment itself.