.com, .org have legacy contracts eliminating the shenanigans they can pull. .org did try get out of restrictions on hiking the price on renewals, but weren’t successful. So all my domains are either .com, .org or the TLD for the country where I live (of course, how trustworthy your local ccTLD is varies)

I also get “there were crawl errors”, which upon investigation are for pages that never existed (and I’ve owned the domain for 20 years, so its not a previous owner/operator thing)

Not true. Commercial or large scale use requires you to use their Web Risk API instead which is a paid service

I doubt these card readers would prevent someone leaving the part of their building they’re in, as that’s a lesson written in charred corpses and was a foundational aspect of health and safety becoming a thing: https://en.wikipedia.org/wiki/Triangle_Shirtwaist_Factory_fi...

In theory it might prevent access to other buildings, but equally often the card readers are around doors of mostly standard glass or near internal windows of the same.

So if that’s the motivation, it doesn’t seem like a particularly effective mitigation

Or the Victoria Hall disaster (183 dead), or Cocoanut Grove (492 dead), or The Station Nightclub (100 dead), or The Beverly Hills Supper Club (165 dead), or.....

Also in what world is a badge reader going to contain an armed gunman unless the walls, floors, doors, and windows are also bulletproof??

(Triangle shirtwaist fire resulted in 146 dead)

Theres footage online of a basic security door stopping an armed robber from escaping despite him trying to shoot the lock.

Bullets aren't universal door openers, and shooting your way through one lock doesn't magically unlock the next one.

And the bullets and time spent getting through the door are bullets and time that aren’t used harming the people behind that door.

I've volunteered at events hosted in older buildings before and it's always such a top of mind thing to enforce a limit on the number of people in the building at any moment. Since these places have the capacity to hold a lot more people than can escape through the exits in the event of a fire.

K-id is the vendor they were proposing which did on device processing. They were trying to downplay the initiative by saying all the k-id data stayed on device.

This was undermined by the fact they were also trialling a switch to Persona (the vendor in the story), which did not uphold that guarantee. It was horrific optics to be reassuring people that it was ok because you didn’t save data but also be trialling a switch to a vendor which did save data, which I guess is a lot of the reason this vendor switch was cancelled. (Though it does call into question discord’s judgment that they thought this was a good idea).

Anyway, Persona was also breached which is how the government links were discovered and also probably a part of this decision. This is not to be confused with the breach in November of 5CA, _another_ vendor they used in the initial UK and Australia roll outs. The fact that two vendors were breached in four months is a good example of why this is a bad idea

I don't think you can ever trust closed source software that also requires network for other features that it really does on-device processing for something specific.

It might not even send the sensitive data immediately but bundle it with other traffic once it goes online.

The person being quoted for one, who is apparently focused on safety and alignment at meta. Safety being handing over your email credentials to the shiny new thing, apparently

Are they even a developer? “Safety and alignment” as AI buzzwords are quite different from “security and privacy”. In any case, I wouldn’t take a random person with a sinecure job as exemplary of anything.

The AI ate my email is the new, plausible deniality version of "my dog ate my homework"

So, not sane.

The next set of hardware purchases will cost more than their last set of hardware purchases, and that's going to outweigh any labour economies of scale given just how many hardware components are in shortage this year.

If their growth had been in their projections in say 2024, they might have just been able to skip a round of hardware purchases, but the combination of growth meaning they must expand their hardware and hardware costs made this inevitable.

Presumably you mean profit and not income, since income is revenue

In that context, income is obviously short for net income.

Google made the first move with their initial plan to lock it down, so the onus is on Google to calm the fears they caused if they don't want people to distrust them.

Google needs to put hard evidence that they are doing it. Sorry but just saying something isn't enough proof. Talk is cheap show us the code.