pull down to refresh

zaps forwarded to @k00b (11%) @sox (11%) @ek (11%)

use your imagination, folks

404 [the WWW is too complicated for us!]0%
200 [lead, follow, or GitHub discussion]0%
101 [fight fire with fire; sell odds...]0%
501 [tell it like it is because it do ;)0%
999 [ consider archive.md/pPbBI etc... ]0%
0 votes \ 61 days left
reply

please consider spending [at least?] one of the zapped credits on voting for the response code[s] that you consider most appropriate, unless you honestly have no strong opinion.

I realise you might not have any relevant experience [e.g. reading raw logs of edge servers] and thus don't expect any vote from you; if you do have some strong opinion that isn't captured by the few options that I provided, please comment...

reply

voting doesn't help at all. I could even vote randomly.

reply

you spent one credit responding, although you probably have enough credits to do what I was going to propose while watching the edit countdown:

vote an approximately equal number of times on each option, e.g. once, if you hadn't already responded...

then, I like you because you have provided some minimal pseudonimity padding on the options, you like me because I have helped the site boost activity, devs like us both because an interesting conversation has begun, and voters afraid of having their votes correlated with comments are able to begin rationally coping with unreasonable paranoia.

unfortunately, you don't care whether I like you, I care too much about your opinions, and the devs probably wish I'd buy territory rather than worry about protocol engineering.

reply

smile, tomorrow will be worse

reply

In case you want the original 999 [ archive.md/#noCap ] link, that got slightly ambiguated by the capslocking:

https://archive.md/pPbBI shows that LinkedIn returned a 999 response code.

reply