teddyh

None do at present, AFAIK. But ccTLD could do that, if they wanted to; there is no rule against it, unlike the gTLDs.

Original link: <https://web.archive.org/web/20260521130338/https://www.commi...>

Here’s how you do it: <https://www.jwz.org/doc/threading.html>

  s/^/How /

Latest version: <http://catb.org/~esr/faqs/smart-questions.html>

And Garry Kitchen's Game Maker

I had (and still have) that. On tape. Doing anything with that was so slow and tedious that I never did anything with it.

“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.

We could agree to use percolate though, it was suggested elsewhere in the thread and it's a fun word and easier to spell.

A more accurate term would be to talk about waiting until old DNS entries “age out”, or “expire”.

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.

(Repost of <https://news.ycombinator.com/item?id=45253509>)

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.

There absolutely can be a chain of resolvers.

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>

And monitoring of “cashier-free” grocery stores.

See this old thread: <https://news.ycombinator.com/item?id=19654515>

It’s still arbitrary, with no geographical (or other) form of propagation.

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.

There is if you present it to others without telling anyone it’s slop.

local vs intermediary vs backbone TTLs

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.

There are many; I often use <https://dnschecker.org/>

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.

Solve a DDoS problem by positioning yourself as the middleman (instead of designing new protocols without the vulnerability).

And for the Commodore 64.

The myth of DNS “propagation” needs to die. Changed DNS entries do not “propagate”. The old cached DNS entries in DNS resolvers simply expire, in an arbitrary order. DNS resolvers are not linked geographically; there is no “propagation”.

If this tool was querying a list of widely-used public (and/or private) DNS resolvers, it might be useful. But pretending that DNS entries propagate geographically does not do anyone any favors.

“To my loyal butler ‘You There’, for his decades of service, I leave a pittance, to be paid in 20 equal installments of 1/20th of a pittance each.”

Cloudflare is well known for breaking DNS standards whenever they feel like it; they’re too big to ignore, so they get away with murder.

I”d instead suggest RFC 9110, HTTP Semantics: <https://www.rfc-editor.org/info/rfc9110/>

This has been true for many years: <https://news.ycombinator.com/item?id=26876681>