I think you significantly overstate the gravity of their announcement. You can entirely bot the process of finding a flight to suit and handing you a link; open it, pay with stored credit card, and you'll still be entirely within what they explicitly allow.

In practice they don't necessarily have much incentive to do anything about bookings they have some sloppy-implementation reason to suspect are fully botted(in their ideal world comparison searching would presumably be harder; but cat is obviously out of the bag on that one an concealing that almost all of the work was automated will be relatively simple so there's a high false positive risk); but since you were specifically directed to not do that they are better placed to deal with cases where someone's openclaw fiasco buys them a nonsense route and they want to try to make it the airline's problem.

Alleged professionals checking secrets into github and shipping them in retail binaries is at least as old as 'devops' being a thing people say with a straight face; and standards in 'AI' and for amateurs are even lower than in software development generally. There's some diversity in terms of the ignorant vs. the negligent; but in practice egregious mishandling of secrets is to be expected.

Is anyone else surprised that the DoJ ended up asking; rather than Satya just giving Dear Leader the access as part of a lobbying effort?

I don't think linkedin has, or has ever claimed to offer, any sort of protection of user data against administrator access, and the broligarchy has been nothing but eagerly cooperative.

I expected this to be worse.

DR scenarios that we rehearse do not (yet?) include drone attacks; at a bare minimum we'd need to physically relocate backup machines, which would also require adding rather large pipes we could dedicate to backup traffic. After that we'd probably need think about redundancy - drones can attack multiple sites at once. And after that, we'd need to think about multiregion setups for resiliency against flying bombs, not just overworked engineers.

That all starts getting expensive very quickly; I doubt Yandex did any of that. So maybe they just got lucky, or maybe they were clever, hard to tell.

Too bad it weren't worse. But drones are cheap and Ukraine is very competent and getting more so, so there's hope for a round II.

That's honestly the weird aspect, to me. Infidelity is pretty common and unsurprising, even among people who don't dress like the midlife crisis is hitting pretty hard; but if you've got options why pick the almost comically politically compromising one?

Even if it has to be a workplace thing, and wouldn't be the same with some sort of heavy-mutual-NDA escort, there have to be more than a few AI lunatics who want him to be their accelerationist daddy sprinkled across areas Nvidia can actually export to.

It's been long proven that outrage gets more traction on the internet than positivity...really, it predates the internet; nightly news stories have led with rage bait for decades.

The existing social media platforms have gotten to the point where everyone is outraged about something - whether it's The Orange Man or The Illegals or The Guns or The Abortions or The Terrible Men or The Terrible Women...and even if we somehow managed to make a new social media platform, tomorrow, that was 100% bot/AI free and exclusively human-made content with no import of content from existing social networks, all the Chronically Online humans would bring their rage about those issues with them to the platform.

The solution, then, is highly restrictive moderation to keep the outrage out of the space. Many vBulletin-style bulletin boards did exactly that to keep users on topic throughout the 2000s and 2010s...but such a heavy-handed moderation system requires dedicated moderators and a group of people who generally agree with the moderation for the sake of group cohesion on the topic. A general-purpose social network would find the required amount of moderation prohibitive. Reddit's moderation requirements basically meant that anyone who was successful at being a moderator, was commonly a Chronically Online person who isn't great at separating disagreement from justified moderation.

So, yes, any new social network, save for maybe a Mastodon server of known friends or an extension of an in-real-life social club, is going to speedrun itself into the flame wars and spam that made Usenet fall out of favor. Personally, I think that it's a result of the removal of the online/offline paradigm of dial-up internet - when there were limits on time and connectivity, it helped keep some distance between our Internet Selves and our Real Selves. Once the internet was always online and in our pocket all the time, there was no stop-and-think, it was just an outlet for every impulse. Any new social network will inherit that problem.

This sounds awfully like a cynical rebadge of the same process termination and endpoint isolation features EDR packages all already have. Yup, 'agentic' is software too; so if you think a process tree looks dodgy you can terminate it or isolate the endpoint; assuming none of the (relatively common) 'EDR-killer' malware flavors are in use; in which case hopefully you have a more network-level isolation plan in mind.

It beats having literally nothing short of calling whoever is closest to the power cable and telling them to pull it; but it's only modestly helpful if determining whether the unpredictable-by-design software is doing wicked unpredictability or virtuous unpredictability to the authorized administrator; especially if it's anything time-sensitive.

I've never used the consumer version; but historically there was a significant amount in common between that and the "user state migration tool" they made available for command line operations or SCCM integration. If 'roaming profiles' had ever found a way to suck less I suspect it would have been a nonissue; but roaming profiles always found a way to suck; so that one was a pretty common IT toolkit item.

The Space Nazi sold ~70,000 trucks in roughly 3 years, after building out a production line to build 125K/year.

They had tons of hi-visibility production problems because of all the dipshit decisions they made; I seriously doubt the full retail cost of 70K of those even grossed the development costs, let alone came close to breaking even overall.

It was the Crystal Pepsi of vehicles. Battlefield Earth in truck form.

What kind of free market are we supposed to run with greater access to price signals and less asymmetry of information?

Brutal collectivists in Whitehall will be demanding low barriers to entry next!

Please show where this "open border policy" was articulated by anyone in the Biden admin. I'll wait while you ask your pet robot.

In this universe, Biden attempted to pass comprehensive immigration reform that was actually a bit harsher than Republicans were asking for. Republicans tanked it anyway, paving the way for people like to to continue to lie about it.

Defunding the police

Whining about kids protesting is just weak-ass bullshit. When you're done whining about a fucking protest chant, take a moment to notice Republicans were the ones attacking cops. They've destroyed the DOJ and the FBI and pardoned the thugs that beat cops on Jan 6.

If you're going to respond, start by naming elected (D)s with power to do so calling for that, or don't fucking running your flaps. You know who I saw calling to defund the police? Marjorie Taylor Greene.

Come back and try again when you're visiting consensual reality.

It's certainly more plausible than some cuts we've seen; but it's hard not to still see it as the usual "described as fat-trimming; inevitably ends up reaching bone" exercise just because of how software usually ships. Not everything ships in full abject brokenness; but at least for commercial-grade software (specialty formally verified stuff and projects that have been laser focused on solving a specific problem that bothered an academic computer scientist in 1980 since 1980 can be a different story) you don't generally see software that makes you think "Nope, it's finished, any additional resources allocated would be wasted or actively spoil the product. There are no edge cases that could have used a little more love, nothing interesting but currently too rough or subject-to-change to use".

Even if you go with a fairly optimistic view of productivity effects, 10%-ish gain and no serious side effects, just axing 10% of the employees so you can status-quo the product with lower payroll costs absolutely seems like a chop-shopping move when the status quo for software is so mediocre. As PE cuts go they don't seem to be speedrunning the hollowing-out and immediately going to a skeleton crew of junior vibe coders and a 'support' chatbot; but precious little software ships in a state where "efficiency is up 10%" means that you've already maxed out possible product quality and just need to start cutting people since you no longer have anything for them to do. If the optimistic projections pan out they might be able to approximately maintain their existing level of polish with fewer people; but that level was always a compromise.

It's good to know that this is purely a matter of technological change; no need to look at the classic "get picked up be PE chop shop"/"gradually get stripped for parts" hypothesis. Seems very credible.

And MITMProxy is here to help you do it.