tgsovlerkhgsel

It doesn't seem to have that many negative consequences for Israel though, and Oct 7 gave them enough justification for what they're doing in Gaza that they can get away with it internationally, and it has likely also limited the backlash they're getting for the escalating settlements in the West Bank.

Looks the same in Ukraine, and at least there it's most likely not primarily because Russians wanted flatten the city (I'm sure they'd have preferred taking it in one piece) but rather because fighting happens from buildings resulting in the buildings getting targeted.

Doesn't mean that here the targeting couldn't have been done with the primary goal of displacing the population, but the buildings being destroyed doesn't prove the motive.

> After much soul-searching, deliberation, and gnashing of teeth, my attorneys and I concluded that the statute of limitations was against us. Because of the thirty-odd years that had passed while I “sat on my rights,” it seemed unlikely we’d make it past a motion to dismiss.

That was my first thought as well.

What is so energy consuming around fabs? The light source? I always thought of these as high-precision, not-too-high-volume processes and would have expected energy requirements to be lower than e.g. a car factory (or similar to e.g. a mall) and completely negligible on a national grid scale or compared to something like a smelter or lignite mine.

Edit: AI claims HVAC and air filtering/handling can be 40-50% of energy usage. Plus a megawatt per EUV scanner (ok, the latter matches what I would have guessed, but compared to the 16 MW of a single large bucket wheel excavator or estimates I've seen for large shopping malls, that's not that insane either).

I think the C (?) mechanic in Shapez to manually fix a corner is really neat. I haven't tried the Factorio R-while-dragging mechanic, it might be the same or close enough.

No, this is just about the UX of drawing a long belt in a 2D grid. I think part of the problem is that they can't easily change the existing UX without breaking muscle memory for all existing players, and maybe they might not want to make it "too easy" to avoid throwing off timing or encouraging certain mechanics like blueprints or trains?

Although now that I'm looking at some tutorials, it's also possible that I just missed that they introduced a very similar feature.

> brimming with QoL features.

I'm surprised they didn't find a way to further improve the belt system. I thought they had it solved pretty well but e.g. Shapez is leagues better (talking about belt placement only here).

Lack of moderation is an issue everywhere, because there are few consequences for the platforms.

Booking.com kept a clearly fraudulent listing (images clearly stolen from another Booking.com listing with mirroring + some filters) fully online for at least two days (I got distracted and stopped taking daily screenshots after that). I just got a response that they've taken it down almost 10 days after I had initially reported it (although I think they marked it as not bookable some time before that).

I only use it to install the apps that aren't available on the Play store (e.g. Öffi, an excellent public transit app that gave up on dealing with the Play store after one too many arbitrary removals, Termux, and NewPipe).

The user experience was just too broken for too long to consider it usable (didn't support background updates for about two years after Google made it available, and generally just too much jank and random errors/failures). I might look into it the next time I'm setting up a device, but I think for the majority of apps I'll still go through the Play store - I don't trust F-Droid to be stable/reliable enough yet.

> But an "AV lane" will very quickly converge on the traffic characteristics of a regular road.

A regular road loses capacity with increased speed due to increased distances between cars, braking ripple effects etc.

At 75 mph/120 km/h, two seconds distance is 33 meters, likely enough to fit three more autonomous cars into the same lane.

Cost, presumably?

I assume Visa is paying some of this from their marketing budget.

I've seen Visa branded ads for some e-payment solution in a South-East Asian country. The solution worked with any credit card, but the flyers were clearly Visa marketing material.

This is why you use Firefox that keeps the cookie jars separate (by default, AFAIK). That should prevent this specific implementation, shouldn't it?

A troll farm will happily go through that effort then (if it's a high effort part of the campaign rather than just 'flooding the zone') pick the images that are most likely to pass.

> you might as well instruct your agent to try and hack their airgapped dev infrastructure responsible for loading the weights and encryption keys.

That's the beauty, you don't have to instruct them to do it, if they decide that uploading the weights is correct, they might figure this part on their own (based on the incidents we've seen).

That's not how I read the linked thread. The linked thread sounds like the JSON file also has metadata attached to it.

Since it's a JSON file, I wonder what's actually inside, and why the blog post doesn't mention opening it with a text editor.

Another related way is to store nuclear waste. The properties (as described in this article, impermeable/self sealing etc.) sound great until the reality that water dissolves salt comes knocking and further confronts you with the reality that salty brine corrodes nuclear waste barrels...

For providers that just act as middlemen, I assume data that doesn't have a residency requirement is stored outside, so probably

a) letting customers in other areas know that their data is backed up to another continent

b) asking the AI model of your choice to translate the following into PR-speak: "Because of the boneheaded data residency requirements in this country, all your data is gone, and we weren't able to do anything about it - here's an empty copy of a re-setup version of whatever infrastructure we provide, glhf setting up everything from scratch, hope you had backups"

For customers who use such a provider or operate primarily in that area: Restore from local backups, or tell whoever depended on you that everything is gone and if you really didn't have backups, probably close up shop.

I wouldn't be surprised if the engineers said "we can probably recover between 20-30% of the data but it will cost 200 hours of engineering and the data will be 7 months old by then" and the beancounters said "we'd rather have one news cycle rather than the news watching what we can and cannot recover + save those 200 hours, we'll just say it's all gone".

They're likely going to target two datacenters, not the datacenters + your medium sized company's office NAS and the safe in the office manager's home.

(Encryption handles confidentiality concerns.)

... but not only in an Azure datacenter!

(The obvious option here might be an encrypted backup on some hard drives in a safe in a local office.)

Nowadays they do #3, demand that the customer takes pictures with a special app that claims to make the process nearly as trusted as #1 while being nearly as cheap as #2.

The idea is indeed that instead or in addition to requiring an app, the insurance company would require the app to run on a phone that supports Reference Image to make sure the image wasn't tampered with. Not right now, when the phones are new, but in a while when 50% of Americans have a sufficiently new iPhone. The rest of the people gets told to either borrow one if they want to make a claim, or go through some other alternative process designed to be so annoying that most people give up.

https://www.transportenvironment.org/te-asia-pacific/topics/... acknowledges the difference between day and night but claims that the sum of the effects still results in net warming during the day.

I find your comment unnecessarily harsh. I don't see a claim that the open source solution is better or a good solution for actual production use by airlines - it reads to me as a "here's how to use what's openly available" blog post.

(Also, Scikit-decide seems to be on the Github account of Airbus, so I assume they have at least some basic knowledge of how aviation works.)

This is really clever from Apple. The journalist use case is just the PR story. This will be really useful for identity verification and insurance apps, and has the potential to shift from "you need a smartphone to be able to live normally" to "you need an iPhone to be able to live normally".

There are already plenty of insurances that require you to submit claims through a smartphone app that tries to essentially do this by capturing sensor metadata etc. - those don't need to be nation-state resilient, just Joe the Crackhead Insurance Scammer resilient, so this works. Likewise, more and more things online require identity verification (either officially or disguised as age verification).

Edit: And while "a nation state actor can spoof this" is a problem for the journalism use case, the insurance/ID verification use cases are perfectly fine with anything that raises the bar but could be bypassed with enough effort. Also, the journalism use case suffers from the same fundamental issue all of these use cases suffer from: People will "verify" the picture by looking at the repost of a screenshot of the verification UI, not by verifying the original themselves.

For the most obscene example, life safety critical announcements during disasters.

Usually just information about events, road closures etc.

The Arizona Sunshine series are also really great VR-native games. Not AAA but far closer to a complete game than most VR games.

Quest 1, the built in native streaming, with a wired connection from the beefy desktop to a WiFi 5 AP on 5 GHz in a low noise environment worked sufficiently. I'd get at least a Quest 2 if you're getting something new (not sure if the 3 is better than the 2).

36 FPS makes running it on the device a rather theoretical possibility for a VR game.

Google gets paid to show the ads.

Adding friction to the process (on the advertiser side) means less money for Google: 1) due to the cost of implementing the checking, 2) because some legitimate advertisers will be falsely denied, 3) because the scam ads were still paying money.

Not adding the friction doesn't seem to come with any serious downside. One would expect that it would, e.g. due to publishers removing the most profitable properties from the ad network or governments legislating this out of existence, but that doesn't seem to happen.

So, given these incentives, the outcome is inevitable.

If Google had to pay a massive fine for every scam ad that gets through, or was liable for the damages the ads cause, etc. - or otherwise had a strong incentive - suddenly there would be enough resources to make sure every ad is reviewed, advertisers that push scam ads get fully banned on the first offense rather than being given second, third, and fourth chances, etc.