"How many product packages will need to be re-designed?"

No more than are currently slated to be done, I'd guess. They are constantly changing sizes and counts and amounts, and each change should be its own barcode update. And major brands already have 2D barcodes. So, meh.

There's literally no reason not to extend the current UPC to have a component that can be typed, and separate metadata.

No one asked the consumer about the original UPC standard, and your questions are those of ignorance.

Any app that has quality data behind it will be *well* ahead of the curve on this. I have 3,938,006 items after a year, and I gave up. You have to be in the industry to get this much data handed to you.

Sure, I could get hundreds or thousands of AWS instances to crawl the largest retailers, but they typically have anti-bot tech running. You can, and I have, crawl one site and get banned by other sites based on your cloudflare reputation.

No. When you say "The difficulty is gathering up all the data" you are understating the problem by several, several orders of magnitude. The "reams of extras" can be put there by the people who make the product, or, in your example, crowdsourced, essentially.

Reading a barcode isn't rocket science, open source can do it well, and there's no room in an open standard for junk data that can't be ignored. URI, ignore, problem solved.

There are reserved areas, like 127.0.0.* but it's not a free-for-all. "Deli item, $3.84" is being used now. Buy some turkey or a steak, that's how it works.

The extra data could be used for a lot more.

Coding should be mature enough that we can handle it. If the answer is using more mature languages like Rust instead of bare-metal C, that's the price of progress.

I'm fully onboard with requiring damages as a result of vulnerabilities, I think you're saying merely having a vulnerability shouldn't be the trigger for enforcement.

AFAIK, and we love our car analogies, auto recalls happen because something has happened enough times, not that some engineer has found a potential problem. That model seems okay.

They make jira, a bug tracking software. I don't know what the rest of this is. I also have no idea who cares about a DNS entry. I can 877 506 2011only assume that someone's ass was chapped by this, and they decided to post a half-assed story to dashslot.

Wrong. The target audience is anyone who wants a burger but... Regardless of what comes after the "but".

I have tried the Impossible Whopper, and it's just as bad as the regular Whopper. I'll have the same effect on burger production, none.

Still, I support any move away from real beef. I'm not interested, but I support it as if I were.

I love MSG, it goes on everything.

What's all this fuss?

They don't get to see it. Problem solved.

Or put it on an AI reddit thing with a note that it's not AI and to argue with the art mod about taking it down.

I don't see apple supporting a protocol that it isn't backwards compatible with existing devices. They are the company of it just works, and if it doesn't work, users will blame Apple.

"Overture is to be complementary to the crowdsourced OpenStreetMap (OSM) project and the foundation encourages members to contribute data directly to OSM.[101]"

It won't even be real computer science. It will be a high school level overview. Let's not get our panties in a bunch.

What he's charged for and what he did are not the same.

He did good, then he went nuts. I'm still not sure which side I'm on, but you're pointing out the other side of the argument, which remains to be proven.

With fiber and other high bandwidth options, IP addresses tend to be almost static, in that they don't change but are marked as dynamic. Cookies and Javascript help, but don't think for a moment your IP is not being used for tracking.