mnot

9 ms·

61.
by mnot 7y ago
So cops shouldn’t be surprised when people assume everything they say is a lie. Perhaps they should consider the secondary effects of this kind of policy...
62.
by mnot 8y ago
That’s about the going rate for cheap expat tax prep. US tax is insanely complex as an expat, and if you get it wrong - even unintentionally- the penalties are massive (look up FBAR). This is why so many are expatriating.
63.
by mnot 11y ago
I'm sorry, you just broke my sarcasm detector :) FWIW, the RFC Editor is working on modernising the RFC format -- we'll even have non-ASCII characters soon! https://www.rfc-editor.org/rse/format-faq/
64.
by mnot 11y ago
RFC2616 is obsolete, see http://httpwg.github.io/specs/rfc7231.html (and friends, as referenced).
65.
by mnot 11y ago
Status code ranges are less about fault than they are about determining whether the client can retry the request without changing it. 5xx means that the client can, because there's a chance repeating the request will succeed. 4xx means
66.
by mnot 11y ago
Sorry about that, the parent Apache process SEGV'd (running the experimental mod_http2). Should be back up now, having fun with the coredump now.
67.
by mnot 11y ago
For the current thinking about this in the W3C (or at least in the TAG), see: http://www.w3.org/2001/tag/doc/unsanctioned-tracking/ There's also a document being put together by the Privacy Interest
68.
by mnot 11y ago
Not bad. The ordering of 4xx status codes isn't that deterministic (often, it's situational), and last time I checked, Twitter uses 429 instead of 420 now (they like standards).
69.
by mnot 11y ago
See: https://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar...
70.
by mnot 11y ago
Heh. Ironically, the HTTP WG (including Martin) went through a period where many of us wore bow ties, etc. to meetings. Trying to raise the sartorial standards of the IETF (under the guidance of the ever-well-turned-out Hasan).
71.
by mnot 11y ago
His words reminded me of the writing of Sumantra Ghoshal: https://www.mnot.net/blog/2005/07/23/ghoshal
72.
by mnot 11y ago
That's actually been discussed quite a lot. However, it shares the "request privacy problem" that I talked about in the blog entry; the mere fact that you're requesting information -- even if it's public -- is somet
73.
by mnot 11y ago
Other people came away with similar thoughts. Perhaps we'll hear more about that from him in other channels.
74.
by mnot 11y ago
Thanks, it seemed like the right thing to do :) I had the transcript done by a professional, and then went over it and corrected. That said, there are still some places where it may have errors, so if you find an odd statement, take it with
75.
by mnot 11y ago
That would be DPRIVE, which he mentioned as well -- http://datatracker.ietf.org/wg/dprive/charter/
76.
by mnot 11y ago
That was the reaction of many people in the room too; he came across as not only smart and well-considered, but also deeply technical.
77.
by mnot 12y ago
You keep using that word "REST"... I don't think that word means what you think it means.
78.
by mnot 12y ago
FWIW - we're gathering issues / improvements at: https://github.com/json-patch/json-patch2/issues
79.
by mnot 12y ago
It lost me when it started talking about cooking above 200C - almost all oven cooking is at temperatures below this, and the more interesting stuff happens much lower than this.
80.
by mnot 12y ago
There is no perfect URL validation regex, because there are so many things you can do with URLs, and so many contexts to use them with. So, it might be perfect for the OP, but completely inappropriate for you. That said, there is a regex in
81.
by mnot 12y ago
I was wondering how long it would take someone to notice that...
82.
by mnot 13y ago
Early to say... it's their job to be nervous about new things.
83.
by mnot 13y ago
Precisely this is actively being discussed in the W3C WebAppSec WG: http://w3c.github.io/webappsec/specs/subresourceintegrity/ The security folks I talk to are... nervous... about this use of subresource in
84.
by mnot 13y ago
Or just don't use sprites, once you're on SPDY/HTTP2. It won't be necessary; win-win.
85.
by mnot 13y ago
I really wonder what the goal is here. HTTP is the interface; making a consistent API between languages seems redundant, and doesn't leverage the features / expertise of each language. The important thing to get right in terms of
86.
by mnot 15y ago
The source of truth for this is the HTTP Status Code Registry at IANA: http://www.iana.org/assignments/http-status-codes/ It would be really nice if this page could at least refer to it.
87.
by mnot 15y ago
"Breaks the Web"? Really? Maybe you shouldn't be treating the Web as a pixel-precise platform with a single control model. The Web is all about separation of concerns and unintended reuse; it's about browsers being able to innovate and prov
88.
by mnot 15y ago
Wow, seriously? This is just as bad as the fanboy "you'll use X for EVERYTHING!" posts. Please.
89.
by mnot 15y ago
When I want make money fast spam, I'll go to my Inbox, thank you very much.
90.
by mnot 15y ago
It's nice to see this data becoming public. However, even a trivial browse shows Y!'s weakness -- their aging user base.

More ›