The abysmal adoption of DNSSEC is just embarrassing, and I haven’t heard any good arguments for why we shouldn’t do it. There’s one blog post that gets passed around as justification for not adopting DNSSEC, but it doesn’t really go into any technical detail and is mostly just the author saying “I’m scared of governments and TLDs”… which is maybe fair, but you still have to trust them for regular CA certs and everything, so why not make thr base secure?

Honestly, I might care slightly more about DNSSEC than IPv6 adoption… IPv4 exhaustion and NATing everywhere sucks, but the fact that you can’t trust DNS is like… insane.

DNS setups can get fairly complicated with enterprise VPNs and stuff, but the main thing is probably just that DNS is built entirely around caching, so when something does go wrong or you’re trying to update something it’s easy for there to be a stale value somewhere. It’s also really fundamental, so when it breaks it can break anything.

Overall, though, DNS isn’t terribly complex. It’s mostly just a key-value store with some caching. Running your own nameservers is pretty cool and will give you a much better understanding of how it all fits together and scales.

That’s very different than every grocery store, though. Might also be different in Canada.

I’ve got bad news for you…

Sometimes your place of work might have electronics recycling bins or something, but for the most part you’re expected to go to a special eco centre to recycle large electronics and batteries and stuff like this. Often you even have to pay a fee for them to take these items, which seems incredibly stupid to me because it just encourages everybody to throw them out with the normal trash.

You may find some stores in some places that will take this stuff, but as far as I know this is not commonplace in much of North America. There are also some services where you can pay a fee for somebody to collect an item. We did that for a swollen lithium cell recently.

It’s just going to be pulses of an 8khz signal. Why would an MP3 not encode this just fine?

Right, but artifacts in the ~8khz range will be detectable by human hearing. mp3s are going to be perfectly acceptable for many sounds in that frequency range… The fact that this works is evidence of that.

Plus, you know what else is lossy? Radio. If the signal is that fragile there’s a good chance the locking mechanism wouldn’t work in the first place.

Why is that insane? The entire point of an mp3 file is to be able to reproduce signals with reasonable accuracy. Seems like the signal has a frequency of around 8khz, which is very much in the range of human hearing and should be preserved by an mp3.

Hey, you appreciate your monkey’s paw wish and enjoy your android.

Of course, but it’s somewhat nasty when all of a sudden is_even doesn’t do what you expect :).

You know, I was going to let this slide under the notion that we’re just ignoring the limited precision of floating point numbers… But then I thought about it and it’s probably not right even if you were computing with real numbers! The decimal representation of real numbers isn’t unique, so this could tell me that “2 = 1.9999…” is odd. Maybe your string coercion is guaranteed to return the finite decimal representation, but I think that would be undecidable.

This is such a weird take to be honest… it’s weird to want CS lecturers to work in their free time, it’s weird to expect their applications to be better, and it’s weird because this is something that many lecturers and programmers already do… so I don’t get it, and it feels disrespectful to all of the volunteer foss maintainers?

I feel dumb saying that books aren’t ergonomic… But they aren’t! I hate holding them open so much. This should be a minor complaint, but it’s a huge benefit of ereaders to me.

There’s something kind of funny about one of the largest expenses being SMS and voice calls to verify phone numbers when one of the largest complaints about signal is the phone number requirement. I wonder how much this cost factors into them considering dropping the phone number requirement.