newaccoutnas

There's also json_build_object for building a JSON object and then you can use json_agg inside that.

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.

Nail on the head

Yes, of course, but it became quite difficult to track when there was fire fighting across several fires

This is great. I notice it's Python 2, could this be ported to Python 3 easily or some inherent issue in upstream deps?

I worked (briefly) at a place that requested updates in 15 min intervals... on a spreadsheet. No thanks!

Agreed, it's morphed into something a lot more evil than stopping bots. The amount of heuristics it now collects in v3 is quite something. Check for your score yourself https://recaptcha-demo.appspot.com/recaptcha-v3-request-scor...

Sure but getting on the electoral register (to my knowledge) requires no ID either. I think this is a big part as to why postal voting fraud happens.

PINS for the ATM are but my online banking has a number more

We don't need ID in the UK, just turn up.

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.

REPL != Syslog TCP. They're different things. It's not TCP that was the issue but the implementation of syslog on top.

Don't know where you grew up but for some this will have definitely increased the temperature over the years - https://en.wikipedia.org/wiki/Urban_heat_island

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.

1: https://en.wikipedia.org/wiki/Reliable_Event_Logging_Protoco...

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.

Isn't that just Service Discovery? https://kubernetes.io/docs/concepts/services-networking/serv...

Eventually the status bar appears saying they're having an issue.

Definitely sarcasm

Not in the system they used, it was private. As has been noted elsewhere, it would be trivial to have the majority of peers could be under nefarious control

In addition I don't think you'd have to interrogate every line, depending on your codebase and upstream module support for Python 3. There are tools like:

http://python-future.org/automatic_conversion.html and https://python-modernize.readthedocs.io/en/latest/

Which should get you most of the way there. Look at https://docs.python.org/3/howto/pyporting.html for more info

To a degree you have to put your trust in the system and build enough checks in so that no one part of it can be corrupted. The issue with electronic voting is that it's easy to scale attacks.

Well, because you're developing against an unsupported runtime. No bug or security updates. If that's fine for you, feel free, otherwise get with the (supported) program.

If it's a new project, there are no excuses imho

Surely the number of eyes looking at that codebase will vastly diminish though? You may get RH and co backporting massively obvious issues but there will be many other smaller issues that won't be found.

Also Google have golang, which I'd imagine would be their target now, not python 3 (for migrations)

Sorry, should have stated it's a pre-release.

https://pythonclock.org/ - 5 Months and 2 days to go. Do not do any new projects in Python 2. There is no technical reason for you to do so. If management is an issue, show them the facts.

Also, Python 3.9 is now out which means there's been more than enough time to migrate - https://docs.python.org/3.9/whatsnew/3.9.html

I think this was posted at the time. It's worth saying that CERN have been massive open source users for decades