Especially if you're paying for one of the better services, like Andrews and Arnold etc. They have caps listed on their broadband pages. There have been regular stories where customers have been sent letters about their bandwidth usage even though they're on 'unlimited' plans. The ISPs generally refer to clauses in ToS, which (imho) doesn't mean anything can be 'unlimited'.
A couple of petabytes in a month? A 1Gbit connection does about 75 Terabytes a week so unless you have a truly exceptional connection, that seems excessive
With respect, if nobody finds the issues in the upstream dependencies and works to make them compatible with Python 3, they won't be supported. That would be a shame for this project and others that use the same upstreams.
I'd have hard time finding support for some Ruby 1.8 upstream dependencies for recent projects, so I don't agree with you.
I take your point but you can't also discount the air quality in cities being quite a big factor as to becoming less dependent on cars. LEV's (Low Emission Vehicles) are taxed less, for example (although the infrastructure is still lacking, perhaps CAV's (Connected Autonomous Vehicles) may one day solve that as parking could be placed further away and there may be more of a 'sharing' system in place, such that you don't really own a car, just dial one up like an Uber)
I'm not sure that's the case, otherwise why would community driven projects like https://b4rn.org.uk/ exist if BT was serving low-value customers properly? In reality they're the company that doesn't see the value in investment there, completely counter to what the pubic purse was supposed to be supporting.
There's RELP[1] but if you can don't use syslog's protocol. You could use something like the beat protocol (if using ELK stack) or just a plain old message queue. Things like logstash (and fluentd etc) can have multiple input/output targets.
You'd have something like filebeat or fluentd reading the logs locally and then shipping via that protocol to a central system where they'd be ingested. For application logging, definitely use structured data (like JSON, for example) over log-lines. It's easier to parse in the long-run.
Interesting TCP is recommended with pain old Syslog. I've seen that take out systems due to not being able to dequeue. There are better protocols that you can use for reliable delivery
I would not discount government 'incentives' to BT. Hundreds of millions have come the public purse for contracts that were supposedly put up for public tender. BT got about 95% of them.
edit: there are other issues in the UK, like fibre tax, that makes the situation even more difficult for competition.