There is a kind of onion called a "Vidalia onion," grown in the town of Vidalia, Georgia. They're a sweeter onion, which is unusual, which is why it grew into a brand.
However, because of this, a lot of people's first exposure with a sweet onion is a Vidalia. But not all sweet onions are Vidalia onions. Yet sometimes people still use "Vidalia" to mean "sweet onion" in a generic sense.
I suspect it's very similar, honestly: I don't think your average American knows that Champagne is a place. Their only exposure to the word is via that style of wine. And so they associate it with the style rather than the brand/region.
(Vidalia onions are also protected legally in the same way that Champagne is; a lot of people in this thread saying that that's just some silly French thing don't realize how common this is. In the onions' case, this has been true since 1989.)
The most popular router brand is TP-Link which is a Chinese Brand. Both Eero and Nest from Amazon to Google aren't available worldwide. Netgear and Linksys has poor Firmware update frequency. That is pretty much left with ASUS which I have a decade old unfix bug with my ISP that randomly fails to get new IP.
I only wish Apple would come back with new AirPort Extreme.
Might be interesting to benchmark their implementation too to see how it compares.
- Versioning.
- Time zone identifier instead of just a fixed offset (which are ambiguous for future events).
- Native encoding of binary values.
- Graph notation with support for labels.
- Comments!
- Trying to escape lookalike characters, even though I think that's a lost cause.
Things I'm not so keen about:
- NUL character in strings being platform and settings dependent.
- Line break not being forced to a consistent value.
- The most complicated number encoding scheme I've ever seen (e.g. 0xa,3fb8p+42).
- Entity references are a footgun for anyone writing a depth-first or breadth-first algorithm.
- Arrays-vs-list feels like it doesn't belong in encoding formats.
Hexfloat can be really useful when you need precise/exact floating-point constants for numerical methods. Without them, you end up having to do more-complicated hacks to preserve exact constant values when code gets compiled, or you have to live with compilers (sometimes) subtly altering constants.
I wish more languages supported hexfloats.
Every nameserver out there, from duckduckgo to hacker news, will send back larger responses because it must echo the query.
Does anyone know why this is not considered an issue? Are we just waiting for open resolvers to be eliminated and attackers to switch over to this lesser amplification factor before we start fixing it?
The only solution given the current protocol, considering reasonable compatibility, is to use rate limiting per source IP, which means that someone can use source IP spoofing to block benign sources. This problem can be mitigated with DNS cookies, but I don't know if those are universally supported enough to simply reject any clients that don't support DNS cookies yet. It also means state keeping per client (hello IPv6). If clients would just send back a slightly larger packet than the response they expect, and servers didn't have to echo the query, amplification protection would be much easier to implement.
They’re special DVD and Blu-ray discs designed for long-term storage. DVD and Blu-ray are so widely used, it seems likely you’d be able to find some equipment in 30 years that could still read them.