• 0 Posts
  • 409 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle
  • Fax machines, fine, certain organizations still require those mostly because people fall to understand that a fax machine is just a scanner and printer and this some bearaucracy failed to keep pace.

    Same story for checkbooks.

    AOL is still a thing and you can even sign up for it today, email address wise.

    Record players are in use, though more people own records than record players, more popular as display pieces than actual music medium.

    I would say everything else on the list is pretty much dead unless you go out of your way to do them, and nothing else on the list has so much nostalgia appeal compared to the problems and difficulty with them.





  • I haven’t seen the ads to have any idea about this person, but I will but from the stores.

    GameStop very rarely, because a game console store price is dumb and getting a used copy of a popular game is cheap, but overwhelmingly will get/wait for PC editions of games, so it comes up very rarely.

    Best buy I’ll buy something because they frequently are competitive with buying online, and I like the ability to just pick something up now without waiting. Also when a controller has an issue or was similarly instant to exchange. Didn’t wait a few days just to get a botched one and then wait a few days for a replacement, got it, find out of was not working, and exchanged it all in the same day.


  • While technically the truth, it can be a hassle to make sure you restart all relevant services after updating a given library.

    I just like being able to restart underlying system to take care of any possible straggler without thinking, and the services broadly be provided by multiple systems so the “experience” is starting up through a rolling reboot










  • Hardware raid limits your flexibility, of any part fails, you probably have to closely match the part in replacement.

    Performance wise, there’s not much to recommend them. Once upon a time the xor calculations weighed on CPU enough to matter. But cpus far outpaced storage throughput and now it’s a rounding error. They continued some performance edge by battery backed ram, but now you can have nvme as a cache. In random access, it can actually be a lability as it collapses all the drive command queues into one.

    The biggest advantage is simplifying booting from such storage, but that can be handled in other ways that I wouldn’t care about that.


  • While sas is faster, the difference is moot if you have even a modest nvme cache.

    I don’t know if it’s especially that much more reliable, especially I would take new SATA over second hand sas any day.

    The hardware raid means everything is locked together, you lose a controller, you have to find a compatible controller. Lose a disk, you have to match pretty closely the previous disk. JBOD would be my strong recommendation for home usage where you need the flexibility in event of failure.



  • I remember this sort of stuff a long time ago. There were wifi drivers that were either linux, but closed source, or horror of horrors having to resort to ndiswrapper…

    Of course, the Ubuntu derivatives made this easy enough by just including it, but Fedora was much more purist about open source and so wouldn’t even tell you about rpm-fusion, let alone enable proprietary drivers for basic network access.

    Now Fedora has edged a bit more practical and proactively let’s users know about how to add proprietary stuff and the wifi industry takes Linux seriously, if not for desktop use then for all the embedded use cases they would be left out of without good Linux support. Fedora is still a bit far on the ‘purist’ side still (try to play a lot of media using dnf provided software, it will tend to break), but not as hard as it used to be)


  • the TLS-ALPN-01 challenge requires a https server that implements generating a self-signed certificate on demand in response to a specific request. So we have to shut down our usual traffic forwarder and let an ACME implementation control the port for a minute or so. It’s not a long downtime, but irritatingly awkward to do and can disrupt some traffic on our site that has clients from every timezone so there’s no universal ‘3 in the morning’ time, and even then our service is used as part of other clients ‘3 in the morning’ maintenance windows… Folks can generally take a blip in the provider but don’t like that we generate a blip in those logs if they connect at just the wrong minute in a month…

    As to why not support going straight to 443, don’t know why not. I know they did TLS-ALPN-01 to keep it purely as TLS extensions to stay out of the URL space of services which had value to some that liked being able to fully handle it in TLS termination which frequently is nothing but a reverse proxy and so in principle has no business messing with payload like HTTP-01 requires. However for nginx at least this is awkward as nginx doesn’t support it.


  • Frankly, another choice virtually forced by the broader IT.

    If the broader IT either provides or brokers a service, we are not allowed to independently spend money and must go through them.

    Fine, they will broker commercial certificates, so just do that, right? Well, to renew a certificate, we have to open a ticket and attach our csr as well as a “business justification” and our dept incurs a hundred dollar internal charge for opening that ticket at all. Then they will let it sit for a day or two until one of their techs can get to it. Then we are likely to get feedback about something like their policy changing to forbid EC keys and we must do RSA instead, or vice versa because someone changed their mind. They may email an unexpected manager for confirmation in accordance to some new review process they implemented. Then, eventually, their tech manually renews it with a provider and attaches the certificate to the ticket.

    It’s pretty much a loophole that we can use let’s encrypt because they don’t charge and technically the restrictions only come in when purchasing is involved. There was a security guy raising hell that some of our sites used that “insecure” let’s encrypt and demanding standards change to explicitly ban them, but the bearaucracy to do that was insurmountable so we continue.