SkiFire13

How would you get someone that only knows about IPv4 addresses like 10.20.30.40 to send a packet to someone with an address 10.20.30.40:fa:be:4c:9d?

It seems that many Android devices won't safisfy the requirements, even when using a device approved by Google:

> MEETS_STRONG_INTEGRITY also includes the requirement that the device has received a security patch _within the last 12 months_

Good luck with that.

> He is probably closer to 0% within the demographic he is trying to conscript.

To be fair going against the demographic where you have a 0% approval rate does not lose you much.

Sure, let's go back to the old days where you had to download language packs for windows and office.

> Localization files for every language on Earth - [...] - Samsung really wanted to make sure everyone on the planet could experience this suffering equally

Why are you considering localization as bloat? I bet your reaction wouldn't be positive if your native language(s) were missing instead.

> So doesn't sound like a big deal for users, this is more of a datacenter sort of vulnerability.

If I understand it correctly though this can be used for priviledge escalation though, since it allows access to arbitrary memory.

> Nobody was reviewing protoc generated code

Are you seriously comparing LLMs with a deterministic code generator?

I don't think that's standardized, it probably only has some heuristic to detect a subscription's associated payments and rejects them. It will not integrate in any way with merchants to cancel the subscription on their side, and in fact they suggest to first trying to cancel the subscription on the merchant side.

To be honest the limited popularity of F-Droid also helps it be less targetted by bad actors. If it was more popular I would bet the situation would surely be different

> Scraping static content

How do you know the content is static?

I don't see a replacement guide link on that page, but curiously there's this note:

> The aluminum upper case and installation screws are not included.

I would assume you likely need those too, as the article also mentions.

Repeated squares is a way to implement exponentiation, not multiplication.

But land is not distributed equally in the two hemispheres. In the southern hemisphere it's generally concentrated near the equator, where it gets more sunlight.

Re: specialization and the comptime/reflection initiative

Since they allow observing whether a trait is implemented or not in the current crate they would probably become unsound if impls can be declared in downstream crates. They are a partial solution but also make other solutions harder to implement soundly (and viceversa)

Rather than login failures I would monitor login successes. A sharp decrease of successes likely points to some issue, but an increase in login failures might easily be someone trying tons of random credentials on your website (still not ideal, but much harder to act on)

If that happens then the user can only communicate with hosts supporting IPv4x and you're back to the IPv6 issue

Re: async in traits, the feature was delayed because it relied on the "Generic Associated Types" and "Impl Trait in Traits" features. If Rust delayed the whole `async` feature for working on those pretty type-theoretic features what would you have thought?

> requires full access to source code

What do you mean? Editions don't require full access to source code. Rust in general relies heavily on having access to source code, but that has nothing to do with how editions work

I don't fully agree with this. Yes, surely shared mutable state can suffer from similar issues, however the cooperative nature of coroutines makes this much easier to handle. OS threads are preemptive and actually run in parallel, so you have to be aware of CPU concurrency and always be ready for a context switch.

Memory access performance depends on the _maximum size of memory you need to address_. You can clearly see it in the graph of that article where L1, L2, L3 and RAM are no longer enough to fit the linked list. However while the working set fits in them the performance scales much better. So as long as you give priority to the working set, you can fill the rest of the biggest memory with whatever you want without affecting performance.

> "Fast static analysis, easy static analysis, language designed for static analysis - pick two"

I think you might have meant "language *not* designed for static analysis".

Italy's digital ID (SPID) works by having multiple trusted providers that can attest your identity. You can sign up with multiple of them, and if one is not available you could use another one. Not perfect (it's still centralized in the hand of 10-20 providers) but better than nothing. Unfortunately most people only ever signed up with one provider, and the government is now pushing for a more centralized digital ID istead (CieID).

At the company I work at we have turnstiles that you open with an app on your phone, however the reason seems to be to know if anyone is in the elevators in case of emergency.

I'm not sure I'm following, are you claiming that C++ is still not widely used enough? That doesn't seem to be the case.

Not sure about Block and Paypal, but AFAIK a good portion of transactions on Stripe are made as part of recurring subscriptions or similar. Those can't be migrated to other services easily, so for the time being Stripe will likely continue profiting from them and from the growth of whatever businesses use it for such subscriptions.

On the consumer facing side Paypal is something I use when paying, but AFAIK I can't use Stripe (yet?). Stripe is used by businesses to let me pay with a credit card (or Paypal, Google Pay, etc etc).

C++ is still changing quite a lot though, just not in ways that fix the existing issues (often because doing so would break ABI stability).

> it’s probably impossible to not have false positives

It's possible to have no false positives or no false negatives, but it can be proven it's impossible to have neither of them.

Would you still do your best to avoid it if that involved taking a pay cut of more than $600/year?

> The biggest concern is not photographic cameras but rather the video cameras mounted on autonomous cars to gather crucial information the cars need to drive themselves.

So they don't care if that breaks my phone camera? Wtf?