> I don't just want a usable signal, I want a fast signal, and one that gets faster over time. But shouldn't the government only be concerned with providing a usable signal? If you want a fast signal, then leave…
> inklesspen's objections to GETs changing server state seem to be based on web-accelerators following links. If web accelerators do not parse js, then inklesspen's objections are not relevant. Am I correct? No. GETs…
> Anything that assumes that GET links can be arbitrarily followed will break stuff all over the web. Arbitrarily performing GETs is something condoned by the HTTP 1.1 specification. Anything that assumes that GETs…
> It comes from an e-mail sent to the address associated with the account, though. The only way he can get the reset code is to have it e-mailed to him, so unless he's forwarded on the e-mail to someone else (why would…
> I don't just want a usable signal, I want a fast signal, and one that gets faster over time. But shouldn't the government only be concerned with providing a usable signal? If you want a fast signal, then leave…
> inklesspen's objections to GETs changing server state seem to be based on web-accelerators following links. If web accelerators do not parse js, then inklesspen's objections are not relevant. Am I correct? No. GETs…
> Anything that assumes that GET links can be arbitrarily followed will break stuff all over the web. Arbitrarily performing GETs is something condoned by the HTTP 1.1 specification. Anything that assumes that GETs…
> It comes from an e-mail sent to the address associated with the account, though. The only way he can get the reset code is to have it e-mailed to him, so unless he's forwarded on the e-mail to someone else (why would…