Vivaldi just ended support for Mojave.
I use the one from Bluebox with the updater. Perfect !Well, Vivaldi is Chromium-based, and Chrome ended Mojave support a few weeks ago, so of course they did. Time to switch to Chromium-Legacy? (Or Linux?)
I suppose everybody has added the expired root certificates to their Mojave?
![]()
Fix Let's Encrypt CURL Problems on macOS
Fix Let's Encrypt CURL issues on macOS: Resolve expired DST Root CA X3 certificate problem by updating CURL's CA bundlebytesguy.hashnode.dev
those bastages!
I got a similar message from Element Messenger a couple of days ago. Version 1.11.47 was fine, but the "minor" update to 1.11.48 broke it. Nothing in the change log, and the auto-updater didn't warn me.
Okay. Thanks for the reply. Got to check out what's wrong. My iBook G4 died when the display hinges broke. Amazing to see somebody still rocking an iMac G3. What kind of hard drives or hard drive enclosures are you still using with those Macs? Must be really reliable.Something is wrong on your end. Everything is working on my end with 10.14 and it is also working on 10.11.
IMO it was Yosemite through High Sierra that were the worst looking MacOS versions on a non-Retina display. When the full system-wide dark mode came about that actually got it looking better, at least to my eyes.I would say the end of that era really came with High Sierra, which was the OS prior to Mojave. It was the last OS to support native subpixel text rendering, and thus the last OS on which text looked great with commonly-available commodity-priced displays ($500 for a 27" 4k). For every OS after that, one needed a Retina monitor (5k for 27") to get pleasingly sharp text. To me, that's a pretty significant breakpoint.
You could reimplement it Mojave using a Terminal command, but it didn't look as good (perhaps because HS was designed to use it, while Mojave was not).