dochtman

Apart from all the other stuff, it seems suspicious that they would use Serpent for encryption, rather than using AES or another more well-known cipher suite (also, no talk about AEAD). https:/&…

WebTransport ( https://wicg.github.io/web-transport/ ) is looking interesting for the mid-term future perhaps. In any case, building on QUIC is probably a good idea.…

Yeah, I'm annoyed by having to chose between NFC and USB-C. Apparently they're working on it, though: https://twitter.com/Yubico/status/1161003411501748224 …

Seems to me that one-stop shop is very different from one-stop tool. GitLab is aiming for the latter, whereas Atlassian (at least when I was using those tools) seems much less integrated. Jira may be …

In my experience the built-in tracking protection (now enabled by default) does a pretty good job.

That's a pretty unintuitive use, since "sigil" is more commonly used (in programming languages) as a single symbol , as in a non-alphanumeric character that's used as some kind of…

Don't they get encrypted on iOS? The last few times I tried to extract stuff from my Android phones, it turned out the SQLite databases were encrypted (AES-something IIRC) and getting them decryp…

It's unfortunate that the official Docker images haven't been updated yet (on DockerHub).

Good throughput with GC seems to come with significant extra memory use: "We compare explicit memory management to both copying and non-copying garbage collectors across a range of benchmarks usi…

I got the Tom Bihn Smart Alec after reading this: http://randsinrepose.com/archives/a-bag-of-holding/ Would always recommend diving into Wirecutter articles to figure out wh…

It's interesting that this seems to mirror our experience with Cloudflare's Rust implementation of QUIC: https://news.ycombinator.com/item?id=19019150 …

The important part of QUIC is that lost packets will not block delivery of all other data being delivered over the same connection, but only the data from any affected streams (for example, a single H…

QUIC is developed by an IETF working group where anyone can participate, and there are definitely some productive participants who don't work for Google (or any of the other big companies).

If your client or server has support for key log files, Wireshark can deal with TLS quite well. In fact, this is usually how I debug my QUIC implementation.

Discussion here: https://www.reddit.com/r/rust/comments/amat47/cargos_next_fe... https://internals.rust-lang.org/t/cargos-next-few-years/…

Thank you for openly discussing this. Ralith has mostly responded in terms of the API our quinn-proto offers; it seems like you and/or ghedo may have missed that? I just also wanted to respond to…

Definitely not! I'm merely stating that there would be advantages from pooling efforts, and that I haven't seen a compelling reason not to do so.

I still don't quite understand why Cloudflare is going their own way rather than joining our Rust implementation ( https://github.com/djc/quinn ). So far the primary maintaine…

The original version of QUIC was contributed to the IETF by Google, but at this point many people from outside of Google have contributed. Saying it is Google-developed is inaccurate at best if you&#x…

ninn is a fork of a much older, much less functional version of Quinn. I have a plan for making the security protocol fully pluggable in Quinn, so that we can easily support things like Noise.

I really like the new GitHub dashboard (have been using it for a while now), but the thing that's really annoying me is how on mobile browsers it has much less comment (missing the activity feed)…

I understand what you're saying, but I'm not sure I fully agree. If you quit a position where you get paid full time to work on Rust because of reasons having to do with your working relatio…

Firefox bug for this: https://bugzilla.mozilla.org/show_bug.cgi?id=1226042

Some experiments with Noise as the QUIC encryption mechanism have recently been published: https://dl.acm.org/citation.cfm?id=3284854 Pluggable encryption has been scoped out of QUIC …

I think it works on stable these days.

If I were writing a small blog today, I would probably still go with Rust, just for the robustness. Catching bugs at compile time is so much nicer no matter how good your unit test coverage is (and es…