I learned a little while ago of the kinds of techniques games use to stay in near-realtime. One of these was "UDP spraying", repeatedly sending the same data pa

I learned a little while ago of the kinds of techniques games use to stay in near-realtime. One of these was "UDP spraying", repeatedly sending the same data packets (in a tight loop, using a significant amount of bandwidth) until they're acknowledged. By your description it sounds like your current location is temporary (which is fortunate ;P) but that you'll revisit this location in the future, so it might be worth your while to explore different UDP data transfer algorithms once you're back with sane Internet, then test said techniques when you revisit where you are now. Best case scenario, you might be able to tunnel TCP over some kind of "best effort" UDP retry algorithm that overcomes a proportion of the losses; it should be possible (while complicated) to implement a more intelligent packet-loss mitigation system that handles significantly broken connections better than TCP does. A far simpler system might be a VT100-esque text terminal running on top of a best-effort transfer layer like those described above. The only problem with this method would be the input latency, although it may fare better than a browser overall (!). Also, I'm not sure if it's relevant (my understanding of networking is sketchy), but I find it amusing that 67.201.56.75/0's description is "Zerolag Communications" xD (http://bgp.he.net/net/67.201.56.0/21 http://bgp.he.net/net/67.201.56.0/21)