Unless they’re implemented flawlessly, they’re more opaque than transparent.

Take BTC’s supposedly transparent proxy (cache-1-0.btc.bw) for example.

I must have missed the email that announced this new layer between us and the Internet, so I’m not exactly sure when it was implemented, but I have a gut feeling that it could be as much as a month or so ago. Maybe more, but it’s been about that long that I have been seeing some occasional weirdness on my Internet connections. Of course, I didn’t know the cause of the weirdness until recently, so it’s hard to say in retrospect.

Anyway, once I had identified this new obstacle to a better browsing experience, I set about finding out whether it was really the cause of my sluggish browsing and 503 (gateway timeout) errors. This necessitated establishing a browsing session that did not route through BTC, which is a reasonably painless exercise thanks to Mascom’s 3G network. Sure enough, after going 3G and browsing to the same sites that gave persistent 503′s, those annoyances disappeared.

So it was only a matter of implementing a bypass mechanism for the home and office systems, in order to regain a decent browsing experience.

Next on the list of things to do is to find someone at BTC that knows about this new hurdle and see if they can explain why I was getting the 503′s in the first place. Actually, if it hadn’t been for the fact that it was blocking my ubuntu security updates, I’d probably still be scratching my head over this.