Audio issues on HP laptops…
That seems to be about par for the course, there's long been an amazing correlation between "I have no audio" and "I have an HP PC", so that particular quoted tweet doesn't amaze me.
31 posts • joined 28 Sep 2012
Too many half-baked standards, lots of concessions to legacy low-performance systems (KSK/ZSK dychotomy for example, or reliance on outdated crypto standards), stupid set-up requirements and performance at different registries (the Irish all but require you to fax in key material, if you're dealing with the Danish it may be impossible or at least hard for your registrar to automate processes, and generally you will have a lot of manual work to be done and paid for somewhere), and it's generally high-maintenance for the zone maintainer. You need to somehow set up and maintain a rollover mechanism, cater to all the above idiocy for every single registry you're dealing with, and then stupid ISPs will still randomly break name resolution so your company will randomly be unreachable in most of a country if it's the ex-state-telecom monopoly deciding to be the one.
It's just pain from start to finish, for little to no gain.
It's a bit like modern Web "standards": they're fine if you're a stereotypical tech hipster doing your little dysfunctional demo page, but once you need to do some work and generate revenue, you start to realise that all the specifications are more like rough guidelines that nobody follows and you are dealing with a deluge of fragmented little ecosystems, and if you can you just skip over the mess.
Problem: Network nodes break TLS.
Proposed solution: Wrap TLS in a *really* dumb transport (no, HTTP, is *not* the solution to your problems, it *is* a problem), make it less efficient, slow it down, and basically give it that mangy "web" smell.
How does that solve any real problems? It's still TLS, and the snoop boxes will just learn to screw with that as well. All this does is pollute the RFC ecosystem even more with yet another ill-conceived and badly thought out band-aid that nobody needs, and that will eventually spawn the mandatory half-dozen errata and clarification pamphlets. Maybe the encapsulating HTTP connection could be protected too, oh I know, let's use TLS?
Twitter's second factor is SMS. They can't send messages to my current carrier, so I had to disable it when I switched there. Twitter don't offer any kind of contact venue to notify them of those issues either, and they don't seem interested in offering anything actually working.
Because DNS works so well. All the fancy little schemes abusing DNS seem to be based around the idea of DNSSEC which, so far, has massive issues (ISP caches break every time keys roll over, management is a nightmare, registries even more so). Looking at the enthusiasm of providers to implement or support that abortion, it may not be something you'll want to base your communication on.
As a first step, it would be nice if it was possible to use TLS between mail servers, but even that fails horribly with many servers not even supporting TLS 1.0 (try using ECDSA or even just SHA-2 on your production systems, I dare you) and not falling back to unencrypted transport when they realise that your system doesn't support export ciphers or other stone-age shenanigans.
Other names are "Unemployment TV" or "Hartz 4 TV" (after unemployment legislation forcing people into poverty).
Those channels exist purely because people love to see that there's always someone at least a thousand times more stupid and asocial than themselves.
All things considered, it's rather a gain to the spectrum.
Biting the hand that feeds IT © 1998–2019