“Talked about” is exactly correct. That RFC describes it as an existing practice and describes one common use where the + sign is used. Which is correct. But this is all completely independent of the email protocols and the RFCs which define them. This specific RFC is about how to handle email filtering where you want to take such an extra “detail” string into account, if such a string is present and can be parsed out of an email message, once it has been recieved. Note that this RFC does not describe the + sign convention as the only one – it shows two other possible syntaxes.
Are you implying that plus addresses are part of RFC 2822? Because they aren’t. AFAIK, no RFC documents specify the plus address convention. The RFCs merely specify that, in an email address, whatever is to the left of the @ sign is to be interpreted by the receiving system, and nobody else should make any assumptions about any of it, and certainly never alter it. And also that the + character is one of the many permitted characters to the left of the @ sign in an email address.
The plus address convention is just that, a convention, widely implemented by many email programs and servers, but not required by any standard, nor universally implemented.
The first home computers were all 8-bit machines, and memory sizes were therefore always specified in terms of 8-bit bytes. (This use then continued as the home computer market grew, and later completely dominated the field as mainframes declined.) But earlier, non-home, computers were as I described.
Spaceballs is a parody, which is specifically an exception to the rules; it’s called “fair use”. If Spaceballs was not a comedy, it would not be permitted to exist.
The author is free to ignore any and all complaints they consider unfounded. It’s not even like the author is recieving any complaints personally; they have to come here to see any. And if they come here, they will get to read the viewpoint visible from here.
In early computing history, the unit of memory was not established yet, and different hardware architectures had different word sizes, not even necessarily evently divisible by 8. And the memory sizes of these machines used to be expressed using the naitive word size. Like “this machine has 8 kilowords of core”. Therefore, when I encounter an anachronistic memory size in old fiction, I just assume that I just don’t know the word size they are using.
No, a CNAME can only point to a host name, not a URL. So Cloudflare’s servers would need to know about, and be configured to serve the correct web page for, the “real” name from your side.
A chain of proxies does not change how we should view the situation. Proxies, by definition, should not affect anything. See this old thread: <https://news.ycombinator.com/item?id=19654515>
Yes, I am constantly needing to disabuse people of their misconception that DNS changes start to apply gradually by geographic distance, instead of applying arbitrarily by pure chance of when each resolver happened to query the record previously.
This is an example of the myth in action. There are no such things. There is a single resolver, which you use, and a set of authoritative server, which that resolver will query when the TTL in the resolver’s cache times out. There is no chain of resolvers.
> It just looks like a virus that propagates when the cache expires.
No it does not. The changes do not happen geographically. There is no geographical connection whatsoever. Calling the tool “DNSGlobe”, and displaying a map, only further reinforces the myth.