The entire problem is basically lazy programmers who want to pretend unix time is utc and let someone else deal with the problems*. It isn't. Changing to leap minutes actually makes this problem worse because it is even easier to ignore. Also the it being too easy to ignore is genuinely getting worse even with leap seconds. The idea was that there would be a leap second around once every 1-3 years, so everyone would deal with them regularly and it would be no big deal. But the Earth's rotation unexpectedly stopped slowing down, and then in 2020, started speeding up. (see this plot where the jumps are leap seconds) So there was no leap second between 1999 and 2006 and there hasn't been one since 2017 and there is unlikely to be one soon. There is actually discussion of whether we will need a negative leap second. That is in the spec, but has never been used and is almost never implemented because nobody thought it could happen. So the whole discussion of a leap minute is either essential or almost irrelevant because a negative leap second would break everything but we may not need one for 15 years or more.

* The problem being that the number of SI seconds between unix time of noon Jan 1 2020 (1577880000) and noon Jan 1 2010 (1262347200) is not (1577880000 - 1262347200) = 315532800, it is 315532803 SI seconds (including three leap seconds). i.e. you cannot subtract unix times to get a long time interval. Just like you can't subtract year*365+dayofyear to get the number of days between two dates. Unix time is not the number of SI seconds since 1970, it is the number of (utc) days since 1970 times 24*60*60. Exactly when those ticks happened on any given day is not well defined in the spec and different implementers have made different decisions (some repeat the last second of the day, some stretch the second for some amount of time before and/or after the leap second, sometimes the issue is ignored and the clock was just reset at some arbitrary time). Even the man page for "date" is misleading because the author was too lazy to sort this out and explain it. The simple fact is that a unix second and an SI second are not the same thing and the unix second is not even a uniform measure of time.

Mainstreaming fraud. I mean if preventing password sharing is a race to the bottom, clearly nothing can live up to this person's entitlement.

Unless Boeing just cuts their losses, keeps the planes and parts to resell or repurpose, and drops the contract. Then it would be a total failure right in line with Trump's long list of others. It's nice that people think that a fantasy world exists where a vendor has to honor a fixed-cost contract no matter what. For the most part the vendor can always just not provide the item, and that can be pretty bad if it is a national security sensitive item. Go figure, running a country is not like running a lemonade stand.

This BS. Inflation after covid was expected to be transitory - then baby WW3 started. The fact that the US Fed was able to largely get US dollar inflation back under control without causing a recession means the "economists" that matter do know what they are doing. This story is just a false narrative trying to sow distrust of an institution that is actually functioning decently.

This whole conversation is surreal - we are talking about doing this *in chrome*. Google doesn't need the proxy, it's their browser.

Pretty rich for the CEO of a company running a private AI sucking down everyone's data to talk about everyone being "joint architects". This guy is a total con artist. The name of his company, which runs an entirely proprietary, closed LLM, is "OpenAI". The problem with trained machines and their ability to do the work of trained humans is people like this guy.

You seem to be under the mistaken impression that corporations aren't entities created by law in the first place.

Yep, it's worse than that even. I have two computers, one of which can upgrade. Why would I upgrade it and then have two different OS's to help my family use? (just to say, the one that can't upgrade is a gaming machine perfectly capable of running windows 11 from a performance standpoint.)

Well that is entirely fixable. We could just separate the main "benefit" (health insurance) from employment. The entire business-run health insurance thing that we have today in the US is a broken system arrived at through historical accident. Nobody would design a national health care system this way. It's main result is to keep people in their jobs by effectively threatening their health and life and that of their families. In a sane world it would be illegal for employers to offer this as a contractual benefit because it gives the employer excessive power over the employee's access to health care (life, liberty, yada yada). It also continues to exist largely only because the wealthy are able to deceive the public into believing that the US medical system is not socialized. It is. Rendering life-saving medical care is compulsory. Individuals over 65 receive state-funded health care. This is all just rich people deceiving poor people into having worse health care so that the rich people can keep more of the wealth produced by the economy. Oh were we talking about some rich guy trying to sell a line about how his workers shouldn't be concerned about him automating their jobs away because (magic)?

Nope. Power in the senate is determined by seniority. So it makes perfect sense to vote for a tool that you hate just to keep power for your state. Voting in a new person has a huge down side that just gets bigger the longer the incumbent is in the senate. The senate "could" fix this by not structuring their committees around seniority, but term limits are basically the easiest way this could be imposed from outside in the US system.

I've never understood why the frequent flier mile system is legal. Business buys ticket. Passenger gets a kickback for choosing a particular vendor. People go to jail for stuff like that in other purchasing situations.

And likely both of those cameras produce 12MP pictures regardless of the sensor size. (I have a pixel with a 50MP camera, it saves at 12MP) These are actually different strategies for doing high zoom. You can make the optics higher magnification or you can make the sensor higher resolution and only use the middle of it. Or you can do a little bit of both, which is what the pixel does - a 48MP sensor with a 5x zoom makes for a overall 10x zoom using only the center 12 MP of the sensor - which is the size of the picture that is saved by the phone. So yeah, there are a variety of strategies. I'm interested to see how they market this for people like you who don't know what they are talking about. Even the camera app on the pixel itself is not designed correctly and presents the 10x zoom as a "digital zoom" as if the sensor were a 12MP sensor, which it is not. Individual pixels cover exactly the same amount of the picture as a 12MP sensor with a 10x zoom. (but CCD quality often matters more than sensor resolution anyway, so comparisons are hard to make and it doesn't seem like any 3rd-party reviewers are actually doing applicable evaluations.)

I'm pretty sure all phones have a hardened security chip in them. If used properly, there is no way to get the key off that chip. The problem is that most TFA apps don't use the provided hardware properly. Pretty much by definition, if you can "save" the key to the cloud, the app is not using the hardware correctly. You are correct that if you want to change phones often and have a lot of credentials, then a security key is the way to go. But that is not what was being discussed. Phones are much more secure as a second factor if the secret is stored locally in the hardened hardware.

I think the point is that the way the "sync" is implemented in Google authenticator intentionally obscures what is happening in order to make it seem more secure and to make it "scary" to disable it. The "dark pattern" mentioned in the article means a user design issue where the company (Google) uses warning messages and dialog structures to mislead the user into doing what the company prefers rather than assisting the user in making an informed decision. It seems like there is a training issue at Retool, but that the person at Retool is complaining that Google makes that training unnecessarily hard through the insecure default behavior and structure of the dialogs to disable it.

There does seem to be a drive at google to where it is more important for dialogs to be worded in plain language than it is for them to contain the necessary information. So it appears that sometimes the person writing the dialog has just given up and removed the actual meaning from the dialog. That is pointless because it means that the message has changed from one that only people familiar with the context will understand, to one that nobody will understand whether they know the context or not.

Yeah, the desire for long-running series seems rather artificial. This isn't a system to produce meaningful stories, it is a system to dry-run pieces of culture owned by the production company until they find one that they can milk for profit because the copyright system is so distorted. And they've managed to get everyone to buy into it so strongly. Variety is one thing that works somewhat in Anime - series mostly begin and end, and if you want "more" you watch something else in the same sub-genre. US production, by comparison, is dominated by franchises. I think this has gone far past ridiculousness in some cases like game of thrones where the actual resolution of the story was just delayed so long it became pointless. Someone trying way too hard to milk an intellectual property for all it is worth just by stringing out the story.