I'm not sure why people keep saying this. There are lots of hosting provider out there. AWS isn't even the biggest (in terms of # of clients). Last time I looked GoDaddy and Google were ahead of them. I realize when people say "cloud" they refer to systems like AWS, GCP and Azure, but there are other ways to do things.

She's a lawmaker, who can't take 5 minutes to read what HIPAA is, and who/what is covered by it. Add to that the fact that I constantly hear "You're violating my HIPPA rights" (Misspelled on purpose there) from various level of conspiracy nuts makes me believe she is way down the rabbit hole.

Next thing you know she'll be claiming she's a sovereign citizen, and that the earth is flat.

I hope that AT LEAST matters to Georgia's 14th.

> The ARM reference design offers a guarantee that such side channels don't exist.

Nonsense. All modern CPUs have speculative execution side channels by nature. The only way to protect against these attacks is to change how we write software to insert speculation barriers in security-critical code paths.

The difference is that Intel doesn't just have speculative execution side channels, they had a pile of critical *security domain crossing* speculative execution side channels. All CPUs can leak data in speculation from your process into the side channel (which might be monitored by another process), but Intel has a pile of bugs which can leak data from *a completely different, innocent process*, or even the kernel (meltdown), or a VM hypervisor (L1TF). Those aren't inherent in CPU design, those are a result of what is clearly a major culture issue inside Intel.

> Spectre and Meltdown bed to differ.

Spectre and Meltdown are not covert channel issues. Spectre is a collection of speculative execution *side channel* issues, and Meltdown is a privilege domain crossing speculative execution *side channel* (the only one that hit other CPUs as well as Intel IIRC; other than Meltdown I think Intel has a monopoly on goofs this bad, e.g. L1TF). Covert channels are not the same thing as side channels, as they require cooperation from both sides.

Not only did he say that, it was LITERALLY the sentence before he said "very fine people on both sides". That was a lie about Trump. I truly detest the man, but this was a lie that the media told, and everybody latched onto. I don't blame those that replied to you, it was a lie that was repeated so much it became "fact".

Are you trying to tell me that Canadian Bacon was NOT a documentary???

or more specifically the right SIP trunk provider. I worked for a company that made lots of automated calls (legally, within the bounds of market research). We had plenty of providers who would just say no, but there were enough that didn't even bother to ask. They all made sure we sent an ANI, although they didn't seem to care what that ANI was, or if we even owned it, (which we did), and they made sure our call duration on connected calls wasn't below 12 seconds (I don't recall what the short duration regulations are, but I believe that was why we had to stay connected at least that long.)

Those trunk providers are also rampant with this: https://www.voip-info.org/fake...

Wow. I feel like notepad.exe's functionality has been the same for 20+ years.

Not only that, 0% of the effort has to do with the GNU part. The article title is accurate in using the term Linux. You get the kernel to run, then you grab a binary userspace from your favorite distro. Linux is what matters. The rest follows automatically because it is barely hardware specific if at all.

You only port GNU/Linux once to any given architecture. After that, all devices using the same architecture only require porting Linux to them.

Jesus, how did I manage to fuck up the links so badly. Link, link, link. And some bonus stuff.

Yes, because when I put Linux on a PS4 I certainly didn't spend several months figuring out how to write hardware-specific Linux components for the PS4.

Oh, wait, I did. I also happened to reverse engineer the Radeon GPU microcode instruction set. So now every AMD Radeon user can benefit from being able to understand what their GPU firmware is doing, which they couldn't in the past.

But hey, I guess GitHub is some shady website that serves shady black box binaries, and implementing kexec as a hot-patchable module for the FreeBSD kernel is a decidedly shady technique. Right.

Little ARM and AVR chips almost always have embedded Flash memory, and high-performance chips like x86 CPUs and mobile phone SoCs almost never do. It has to do with silicon technology. It is not practical to put Flash memory into a cutting edge silicon process for a bunch of technical reasons.

So yes, it's ROM. Mask ROM. Not writable.

IANAL, but as far as I know there is no such "exemption". You're probably thinking of Sega v. Accolade, where Sega used a trademark system to require games to have the string "SEGA" in them. That was chiefly about trademarks, not copyright. You're probably also thinking about the DMCA exemption for reverse engineering for interoperability purposes, but that is about anti-circumvention, it doesn't mean you get to distribute copyrighted data/code.

If you actually read the DMCA request, you'll see it's about data, not code. A game server needs data to know the allowed actions in the game, the entities in the game, the rules for interaction, the locations, etc, in order to maintain a common understanding of the world with the clients. It is this data that was copied from the WoW client and incorporated as a SQL database (into otherwise presumably bespoke server code).

You could make your own completely new game data (and somehow insert it into the Blizzard client too), but then the game wouldn't be WoW any more, just something else built on the same engine and with the same graphical assets.

That's because most Android phones do *not* do this and then succumb to the sudden death syndrome. That's what my Nexus 10 started doing after its battery went kaput. It would run for ages on standby or with the screen brightness on low and not doing much, but instantly die as soon as It tried to play back a video (but would boot right back up and the battery voltage shot up to near fully charged levels after shutdown). Internal resistance.

On the other hand, I have heard anecdotal reports from friends with some Xiaomi phones that the performance increased after a battery replacement, so I suspect those do in fact have this feature.

This isn't about making the battery last longer. It's about making the phone work at all. It has to do with battery chemistry.

Old batteries don't just "last less". They also have an increased internal series resistance. That resistance actually limits the amount of power you can pull out of it. The more current you draw, the more energy is wasted as heat, and the lower the output voltage. As internal series resistance increases, it becomes physically impossible to get more than a certain amount of power out of the battery, and this limit also decreases as the battery drains during a given discharge cycle. It's a hard physical limit. The I-V curve just never hits your power target. If you try, your voltage sags and then the phone shuts down. This is what triggers a common syndrome in old devices, where the battery meter shows 30% but then you try to open up a CPU-intensive app and the device immediately shuts down. Chances are that's not the battery meter being wrong or miscalibrated: there really was 30% charge remaining in the battery. It just wasn't capable of handling that much power draw at that charge level. There's 30% charge remaining and there's a hidden limit as to how fast you can drain it.

It's almost certain that what Apple did here was start throttling phone performance when battery voltage sags below a critical threshold, to prevent hard shutdowns. On older batteries, this would appear as a performance limit as the battery empties. But it was never about making the phone last longer. It's just a physical limitation. The alternative is your phone shuts down. That's obviously not good.

The right solution, of course, is to have a notification or something that tells users when this is happening. Something along the lines of "Your battery cannot supply enough power to keep your device working at full performance. To maintain optimum performance, a battery replacement is recommended.".