[yourapostasy]

I dealt with those kinds of limitations a few years back when I lived in a rural area, and if faced with the same limitations today, I recommend the following, as this is my current operating mode when on overseas trips and on limited connections while still needing to work. It still sucks, but I've done what I can to make it suck less. It still blows my mind when I observe while traveling that much of the "fly-over" communities in the US have worse or similar broadband terms, at more expensive rates (in both absolute and local PPP terms) than Nepal, or many other developing nations. The US post-industrial revolution is seemingly rotting out from within.

Basically, the high level solution is live in the CLI as much as possible, and remote into your "main driver" as much as feasible. I had to accept that I won't ever be working with my daily processes transparently. I had to make conscious decisions all the time, for example: do I work with this customer-sent Word file on the remote Windows box or download and work on my laptop?

Mostly I live in SSH and screen to various Unix boxes. Will add Mosh and tmux this year to try them out over unreliable connections. Windows RDP was okay on bandwidth caps, a license of NX was used for those few times I could not escape X11 (ship it to a remote Windows box to maintain state). ESXi for those times I had to work through a VPN and view the remote display via the VM video because the VPN cuts off all other remote access.

If you are in this for the long-haul, then your own Supermicro Mini-1U with up to 128GB RAM colo'd will probably be cheaper than even an OVH annual dedicated server.

Hope this helps.

There should be a public list of politicians who voted for blocking municipal broadband, to give tech-oriented voting blocs an easy way to inform single-issue voters how to vote against them.