Live data from Hacker News

GNU Terry Pratchett

gnuterrypratchett.com

31–40 of 54 posts

Re: GNU Terry Pratchett

#31
post #7

I wonder how people feel about adding other names to the Clacks header? It feels a tad lonely for his name to be the only one passed around in this manner. It seems quite like a virtual graveyard, but with only one gravestone. As much as I respect Pratchett, many others are already commemorating his name, and I would feel compelled to add another. If people put their own loved ones into the Clacks header, perhaps thi…

What do you recommend as the format? Comma-delimited? My personal website has been serving this since he died, but I'd like to also add Iain M. Banks, as someone else here suggested.

Comma-delimited is probably the way to go. RFC 7230 §3.2.2 establishes that you may combine multiple header fields with the same name by joining the values with commas (noting that as a special case for historical reasons, it isn't safe to do this with Set-Cookie).

That is,

    X-Clacks-Overhead: GNU Terry Pratchett
    X-Clacks-Overhead: GNU Lain M. Banks
should be equivalent to

    X-Clacks-Overhead: GNU Terry Pratchett, GNU Lain M. Banks

Re: GNU Terry Pratchett

#32
post #5

I once accidently did this on a university computer system. Something was misconfigured with sendmail routing; when I telneted to an unexpected computer in the lab and sent an email from there it started bouncing in an infinite loop between that and another department server. About two days later the system operator noticed when log files filled the drive. My email had been making trips up and down the building a few…

I wonder if it's possible to craft a mail to be infinite-bounced like this. There have to be servers that are appropriately (mis-)configured of course. But that would let you have a lot more than just one name, and a lot more information about each person. An epitaph of sorts.

The trick is to make it so the mail isn't replicated as it's infinite bounced, so we don't get infinite copies (don't clog the tubes!). It's something I've been struggling with in a piece of software I've been writing, actually. My solution is to simply not allow for loops: There is only one canonical path between any two server (netsplits, yay!)

Re: GNU Terry Pratchett

#33
post #24

What a wonderful idea. I have just updated out frontend server config to include the header. On thing though: According to RFC6648, we should not be using the X- prefix any more for custom headers ( https://tools.ietf.org/html/rfc6648 ), but I guess it's too late to change this now.

It says:

> 1. Deprecates the "X-" convention for newly defined parameters in application protocols, including new parameters for established protocols. This change applies even where the "X-" convention was only implicit, and not explicitly provided, such as was done for email in [RFC822].

It says for application protocols. I would argue in this case that it's not any part of an application protocol as the header is never used for anything.

Re: GNU Terry Pratchett

#34
post #20

A proper implementation of this would require a packet with an infinite TTL and no destination. I tried to figure out a way to do that, but did not succeed.

Because of the way email works, if you got it working, but screwed up (which is what would probably happen), you'd end up with a recreation of The Great Worm (Well, to be more accurate, you'd actually get a recreation of Bedlam-DL3: https://blogs.technet.microsoft.com/exchange/2004/04/08/me-t.... But it would have the same effect). Do you want to see what happens when millions of poorly configured email servers round the net scream out in agony?

Re: GNU Terry Pratchett

#35
post #24

What a wonderful idea. I have just updated out frontend server config to include the header. On thing though: According to RFC6648, we should not be using the X- prefix any more for custom headers ( https://tools.ietf.org/html/rfc6648 ), but I guess it's too late to change this now.

It says: > 1. Deprecates the "X-" convention for newly defined parameters in application protocols, including new parameters for established protocols. This change applies even where the "X-" convention was only implicit, and not explicitly provided, such as was done for email in [RFC822]. It says for application protocols. I would argue in this case that it's not any part of an application protocol as the header is…

>1. Deprecates the "X-" convention for newly defined parameters in application protocols, including new parameters for established protocols.

This has already been defined, so we're in the clear, I think.

Re: GNU Terry Pratchett

#36

Somebody (I think it was ESR) called this pointless, wasteful, and stupid. It would be, were it for the benefit of the dead. But it's not. It's very much for the benefit of the living. It's a way of remembering a man who was so very important to us, but for me, it goes beyond that. Somewhere out there, there's a kid who's examining some net traffic. Maybe out of curiosity, maybe to debug some kind of problem. And he'…

"Pointless, wasteful, and stupid" strikes me as a rather uncharitable way of characterizing http://esr.ibiblio.org/?p=6703 .

Re: GNU Terry Pratchett

#37
post #2

I've had the Chrome extension for this running in my browser for a while now. The most interesting discovery I've found is that virginamerica.com is sending the "X-Clacks-Overhead: GNU Terry Pratchett" meta tag on all of their pages.

Too bad chrome's page actions are now to the right of the url/search box instead of dynamically appearing on the box. I'd like to install this, but I don't want to have the button always be there.

Re: GNU Terry Pratchett

#39

Earlier quoted context omitted.

It says: > 1. Deprecates the "X-" convention for newly defined parameters in application protocols, including new parameters for established protocols. This change applies even where the "X-" convention was only implicit, and not explicitly provided, such as was done for email in [RFC822]. It says for application protocols. I would argue in this case that it's not any part of an application protocol as the header is…

>1. Deprecates the "X-" convention for newly defined parameters in application protocols, including new parameters for established protocols. This has already been defined, so we're in the clear, I think.

RFC6648 is from 2012 though, but Sir Terry Pratchett died in 2015, which is when this initiative started. As such it's violating RFC6648 because it continues to use the X- prefix.

Re: GNU Terry Pratchett

#40
post #37
post #2

I've had the Chrome extension for this running in my browser for a while now. The most interesting discovery I've found is that virginamerica.com is sending the "X-Clacks-Overhead: GNU Terry Pratchett" meta tag on all of their pages.

Too bad chrome's page actions are now to the right of the url/search box instead of dynamically appearing on the box. I'd like to install this, but I don't want to have the button always be there.

you can slide them out of view/hide them from the menu bar.
Post reply on HN