I learned a little while ago of the kinds of techniques games use to stay in near-realtime. One of these was &quot;UDP spraying&quot;, repeatedly sending the same data packets (in a tight loop, using a significant amount of bandwidth) until they&#x27;re acknowledged.<p>By your description it sounds like your current location is temporary (which is fortunate ;P) but that you&#x27;ll revisit this location in the future, so it might be worth your while to explore different UDP data transfer algorithms once you&#x27;re back with sane Internet, then test said techniques when you revisit where you are now.<p>Best case scenario, you might be able to tunnel TCP over some kind of &quot;best effort&quot; 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.<p>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 (!).<p>Also, I&#x27;m not sure if it&#x27;s relevant (my understanding of networking is sketchy), but I find it amusing that 67.201.56.75&#x2F;0&#x27;s description is &quot;Zerolag Communications&quot; xD (<a href="http:&#x2F;&#x2F;bgp.he.net&#x2F;net&#x2F;67.201.56.0&#x2F;21" rel="nofollow">http:&#x2F;&#x2F;bgp.he.net&#x2F;net&#x2F;67.201.56.0&#x2F;21</a>)