mnot

15 ms·

31.
by mnot 4y ago
Not in Australia, they won’t.
32.
by mnot 4y ago
This is exactly the use case that Oblivious HTTP is being built for in he IETF.
33.
by mnot 4y ago
Installed one of these last year during a Reno, love it - no more condensation, no mold, much fresher air.
34.
by mnot 4y ago
So, how would that work, exactly?
35.
by mnot 4y ago
If early hints breaks your proxy, it’s likely your proxy doesn’t handle 1xx status codes correctly. Could you tell me which proxy it is (privately if you think it necessary)? I’d like to chase the bug with them.
36.
by mnot 4y ago
Read a bit more; that’s not how the cryptography works. They’re blinded tokens.
37.
by mnot 4y ago
The precedent for that was set by http/2; while the spec didn’t require it (Snowden happened after that decision was made), all of the inplementatuons did.
38.
by mnot 4y ago
Graphql. I love autocorrect.
39.
by mnot 4y ago
If everything works out, grapnel could use it and queries would be cacheable by generic http caches. A lot would need to happen to make that work, though. The immediate motivation is to get an alternative to people who want to put a request
40.
by mnot 4y ago
The idea is to compose intermediaries run by different parties, so that no single entity has access to both the unencrypted payload and client ip address / connection context. It’s a controlled form of proxying where the proxy doesn’t
41.
by mnot 4y ago
The IETF is working on a solution to this, and Cloudlare is actively contributing and implementing; see https://blog.cloudflare.com/eliminating-captchas-on-iphones-...
42.
by mnot 4y ago
From their 'about' page: > Founded in October 2022, Make Sunsets is backed by Boost VC, Pioneer Fund, and other friends. The article lists Luke Iseman as the cofounder and CEO; from https://lukeiseman.com - > Box
43.
by mnot 4y ago
The IETF has given up on XMPP for its own chat service.
44.
Privacy as Product(berjon.com)
2 points by mnot 4y ago|1 comments
45.
by mnot 4y ago
Most businesses don't have anything that could qualify as a privacy strategy, and it shows in nonsense busywork, lower-quality products, and lost revenue. How about we take steps to fix that?
46.
by mnot 4y ago
Like the Apple Touch Bar. The problem is that it’s contextual, so you still have to look to it you can trust that a hardwired button won’t change purpose; that’s the important property here.
47.
by mnot 4y ago
Came for the LPL comments.
48.
by mnot 4y ago
FWIW, updated with a response from Jake Archibald (Chromium/Google).
49.
by mnot 4y ago
The use case that's been talked about most so far is browser telemetry. See also: https://datatracker.ietf.org/meeting/112/materials/slides-11...
50.
by mnot 5y ago
This smells funny. It doesn't list any names, at all, and it only focuses on one issue -- Apple's browser restriction, which as others point out is a nuanced issue.
51.
by mnot 5y ago
Just for context -- there's a discussion in the IETF about what collaboration tools it should use (e.g., for working group meetings and general discussion) in addition to e-mail. A few different options have been trialed, including Zul
52.
by mnot 5y ago
:(
53.
by mnot 5y ago
Not true; a substantial part of the Schrems II decision was about how the GDPR applies not only to law enforcement, but also national security surveillance. See eg ‘European Essential Guarantees.’
54.
by mnot 5y ago
I was a guard at the BMA when I was in university - great group of people, this is a wonderful idea.
55.
by mnot 5y ago
Now sorted in order of # of citations within the RFC corpus; it's rough, but definitely more usable IMO. Thanks for the suggestion.
56.
by mnot 5y ago
see https://github.com/quicwg/wg-materials/
57.
by mnot 5y ago
The leading '0' issue should be fixed; not sure why that happened, it was tested before. WRT UX - yes, it certainly could be improved. Issues and PRs gladly accepted :)
58.
by mnot 5y ago
Thanks. The back/history feedback has been (hopefully) addressed. I've been thinking about doing authors. The constraint is performance; the site loads the whole index, so adding author info would bloat the initial page load out (
59.
by mnot 6y ago
It's actually a relic of when I was testing to see how broad SNI adoption was -- see https://www.mnot.net/blog/2014/05/09/if_you_can_read_this_yo...
60.
by mnot 7y ago
And yet, many RFCs are written in markdown now. And variants like kramdown do support semantic markup.

More ›