sdflhasjd

The Mac Studio has a 3-pin earthed C5 connector. I presumed it's not overcurrent as it trips a 32A type C RCBO in an instant.

Either way, it's certainly a problem with the computer - I've far more demanding equipment that has never done this, and have yet to find a circuit it won't *pop*.

This thread looks like a relevant one to mention an issue with the Mac Studio that causes large inrush currents when you plug it in. The power connector arcs badly enough to trip a domestic 30mA RCD, it's reproducable with several units and on different electrical circuits at both home and office.

Speaking of shitty Web app office suites... I had to use Sharepoint/word the other day. What an absolutely buggy mess that was. Bits of the document would randomly break while someone else was editing elsewhere, every table I inserted was in a supposition of "ok", "messed up", and "completely broken" until I closed the document and returned the next day. Random hot keys would just not work or perform nonsensical unrelated actions. The list goes on...

The article really doesn't explain anything. If Apple wanted to serialize their screen glass, why not just slap a sticker on it? The article doesn't explain why. How does this reduce the defect rate? Also not explained.

There's a linked article from "The Information" that I suspect goes into more detail, but it's paywalled.

I think the effort would be best spent avoiding cookies and trackers in the first place.

What do you plan on using cookies for? There might be some ways of doing similar things without cookies or trackers (server-side analytics for example) that are more respective of users and also eliminiate the need for any banners at all.

I know my company's website has a pointless cookie modal - the necessary cookies are just for session affinity on a gateway (which I don't believe you'd need a modal for anyway), and the unecessary cookies are from one analytics integration that's been used just once since it was set up, and another that is used for the most basic reports that you could get from just the access logs.

I have a heated mat decoy on my desk. It gets a little warm and uses very little power but my cat prefers it to my keyboard... most of the time.

Then when she's bothering me it's usually attention she wants.

The original source appears to be https://checkmarx.com/blog/surprise-when-dependabot-contribu...

There are projects that automatically merge dependabot PRs...

I'm just disagreeing that the patches are the same. I agree that Miculas did do the hard work by finding the cause of the issue in the first place - but he's correctly credited as the reporter.

As for the clean patch - part of the issue is that Miculas was slightly overengineering some of it with the additional macros and added noise with extra conditions on the fpidx declaration.

Ellerman's "I don't want to coach this rookie" vibe is somewhat understandable given this is the security mailing list - it's just not the time and the place to be going back-and-forth.

I'd argue the differences are not just style changes and even "just style" changes are not trivial. The kernel style guide specifically mentions to avoid using conditional compilation where possible, and as a result, Michael Ellerman's patch is far cleaner.

People who already have a job and are wanting to move will have reasons for wanting a shift (frequently besides just salary).

It's not the grammar that's giving you penalties though, it's all the chaff that comes with using AI that you don't really want.

Another issue with using AI is that you didn't write it, you're going to struggle to clarify any grandiose claims during an interview. I've come accross only a couple of these CVs before and I have to question what these candidates are expecting to happen. If you're going to write your own bullshit in you CV at least you can (try) to bullshit your way through the interview as well. If you're getting an AI to bullshit for you, you're going to be clueless in an interview.

Acer did the same thing with their "recycled" laptop - I have to ask the same question about how much effort and production process goes into getting that exact fleck effect and completely agree with you, and I feel like companies are still putting in more effort to market about their "green" activities than actual practice.

Yes. These cases just don't make it onto American online news as much.

The EU website has a list of Antitrust/Cartel cases: https://competition-cases.ec.europa.eu/search?caseInstrument...

Plenty of fines being dished out there.

Aside from the high-level concept of some cryptography based cash, there's nothing there to indicate any similarity with bitcoin.

They could have been checking the processes that initialise the VMs to ensure they've got secure defaults though

> Providing secure, reliable, and performant products and services is our highest priority.

This kind of language always grates on me. It's obviously not true, at what point is this lying or fraud?

For 11 months, they were generating these insecure passwords. Clearly this isn't a priority, can you imaging them forgetting to bill their users for 11 months? I can't.

I think the err... cat is out of the bag on this one. The market is already saturated with trackers.

Plus, this doesn't have the same potential for abuse as it has more limited battery life than NFC beacons.

Many older people I know with smartphones still prefer to sync their photos to a computer with the wire rather than pay money for (or trust) iCloud.

24kW is basically the peak when it's doing instant hot-water for the taps. You shouldn't need that to heat a home.

You're right, it can't match the _peak_ output, but the whole system is designed so this isn't necessary.

With a "traditional" combi-boiler, it will turn on occasionally to heat the water in the central heating system, and continue to pump it around. When you need hot water, it switches over the heat-exchanger to directly heat the incoming water and this is when it will ramp up and burn the most gas (24kW+).

For an air-to-water heat pump system, the system will be on almost continually, but will heat the water to a lower temperature, the peak power output is less, but it averages out the same. For hot water, the system will heat a storage cylinder.

One of the catches here is that's it not always an easy retrofit as the lower water temperature can necessitate larger radiators.

Google do maintain Flutter though, which is effectively a competitor.

Yep, just had some issues with homebrew updating the system to OpenSSL 3 which broke some workflows as OpenSSL 3 can't read Apple Developer certificates...

I think we're fortunate in the UK that you can just pick up a PAYG SIM at almost any cornershop. Perfect for these "verification" code SMSs. One of the main reasons I got dualsim phone as well.

Whereas I made the opposite mistake of having firstname@outlook.com

I get ungodly amounts of spam, relentlessly, from everyone. Because anyone over the age of 50 seems to give it as their email to companies like Target.

Also, it would make sense that they would be more likely to be paid for promoting poorer performing stock rather than what would be able to sell itself on its own merits.

From the article, it implies the patient wasn't recorded on video.

> The video, which Cruise declined to share publicly [...] does not capture the patient being loaded onto the ambulance.

I've found it disappointing for some multithreaded/multiprocess CPU heavy workloads as Apple's cooling solution doesn't keep up and begins thermally throttling down to the rough equivalent of maybe just a 2-Core CPU.

The game is the meta-experience of playing an early access game at this point.

One I remember is something a project manager once said...

I was working for an agency doing mostly apps and websites, one of our customers had a couple of projects running in parallel. One was sorting out an app that their own developers had made a pigs-ear of, and another - larger - project on new ground.

The customer's project manager called us up asking for some more resource for the larger project to keep to deadlines, it got to the point of trying to micromanage the other app project that wasn't theirs, and they blurted out:

"${app} doesn't even need a senior developer, it's just front-end!"

It wasn't eye-opening, we could already see what a state their other "front-end" projects were in, but hearing it from the horse's mouth was a little amusing.