Create - from the EU - yes. As I said: you cannot add to existing that you already use extensively. And not create new from outside EU. That’s what makes it so shambolic. They clearly have the ability to both do it technically and to verify appropriately.
No problems using similar UK services for EU citizens I know, nor non-EU. Usual bank/address shenanigans at the start, but no issues with government gateway etc.
If you leave the country without setting up SMS you can’t ever use 2FA. They claim to support adding foreign numbers, support people being abroad, support adding new DigiD accounts from abroad, but oh no you can’t just add a number. Not even by going to an office or doing a virtual interview. I would think this violates EU law on discrimination. If you live in the UK post-Brexit it’s now totally impossible, I believe (since you aren’t even allowed to make a new account).
"Some of you might have concerns that chlorine gas will develop, but because chlorine is so reactive, and because the salt solution is dilute, it’s safe for this setup."
Right. It may also be possible that there is some hope of this action restoring normality. i.e. as a result of this protest, the Core Team become more accountable. At that point, I assume the specific incident(s) may be dealt with according to the Code of Conduct, which may or may not involve transparency. Either way, it could be premature and possibly prejudicial to air those now.
"In order to get all of the details about the tuple from the function one must analyse the bytecode of the function. This is because the first bytecode in the function literally translates into the tuple argument being unpacked. Assuming the tuple parameter is named .1 and is expected to unpack to variables spam and monty (meaning it is the tuple (spam, monty)), the first bytecode in the function will be for the statement spam, monty = .1. This means that to know all of the details of the tuple parameter one must look at the initial bytecode of the function to detect tuple unpacking for parameters formatted as \.\d+ and deduce any and all information about the expected argument. Bytecode analysis is how the inspect.getargspec function is able to provide information on tuple parameters. This is not easy to do and is burdensome on introspection tools as they must know how Python bytecode works (an otherwise unneeded burden as all other types of parameters do not require knowledge of Python bytecode).
The difficulty of analysing bytecode not withstanding, there is another issue with the dependency on using Python bytecode. IronPython [3] does not use Python's bytecode. Because it is based on the .NET framework it instead stores MSIL [4] in func_code.co_code attribute of the function. This fact prevents the inspect.getargspec function from working when run under IronPython. It is unknown whether other Python implementations are affected but is reasonable to assume if the implementation is not just a re-implementation of the Python virtual machine."
I'm not very convinced without further information - it sounds like it was already solved in CPython, and bug in IronPython? The whole PEP reads as if it's looking for excuses for removal.
Yes, of course, but you then appeared to query the "unfounded" nature of the claims. I thought you had missed the part where they turned out to be indeed unfounded.
"These claims were investigated by the FDA and the Centers for Disease Control, which found no connection between the vaccine and the autoimmune complaints."
People started to get a clue about this 5-10 years ago though. It used to be much worse. I recall having to deal with it daily and I don't think about it much any more - more like a weekly exception.
In fact, now also I get some places trying to be too helpful to the point of being confusing. For example, a trainer store that auto-detects location and lists prices in GBP but sizes in US (without indication) and doesn't actually have an EU/UK distribution centre. So whoops it's going to take ages to arrive, it gets re-listed in USD at the final checkout, whoops again, 3% charge from my credit card, and then the wrong size arrives. But at least I knew the rough GBP amount!
No, I'd expect it to mean free refills for me for the duration of my meal, like most people would.
My point is, there is quite an involved pricing model - 5 tiers, each tier has multiple charges in it, none of them obviously correspond to the advertising on the front page. They even repeatedly use the phrase "for X MB" which is unclear to me. I first read it as storage. I assume it means total upload/download? The numbers for this on other devices on the front page are not mentioned on the pricing page. Charging categories also have a mixture of sold-by-the-MB and sold-by-usage, as well as pre-sold - within a single tier.
The front page is selling "look, it's very clear and simple" and it's just obviously not clear and simple. Unclear why that view garners downvotes - this is honest feedback about their marketing and pricing. Even if they are mostly talking about the free tier, it's not clear
I don't get how the front page could be so clearly misleading and not expect to get found out. It's all about nothing hidden and "that's all you pay" until you click pricing and then there are many different charges and models.
A bit light on the technical details that matter (i.e. the actual metrics added, how they went from data to conclusions, exactly why Honeycomb helped), this reads a bit like an advert targetting managers with purchasing power. Is it a report from attending a talk? That might make sense at least.
How did you know to go to those lectures? Reputation or trying the first few lectures? Just the start of the course feels like it might not give a good enough sample.
In principle, yes. In practice my experience is that neither macOS nor iOS is very automatic. All it takes on macOS is for another user to be logged in, or for you not to leave your laptop on charger overnight, or a single app to be open that doesn’t automatically shut down. I don’t understand why iOS can go so long without doing it (I’ve seen it go weeks with an update notification & being plugged in every night)
I'm not sure about "completely false". The article is mostly about the history of the stereotype, and ends with a couple of examples of things that were not as efficient as they could have been. I don't think anybody is claiming perfect efficiency.