I've been a fan of systemd even if just for how much simpler creating services is. I just need to write a simple config file instead of a complex init script.
+1 - there was a misconception that initscripts were easy or simple - if you wanted _correct, bug free_ initscript you were probably looking at around 100 lines of shell script.
Or if the service didn't support pam_limits because it was legacy trash, you had to hack something into the initscript like `ulimit -n XYZ` and restart it. Now things like this are trivial and easy to solve. Using systemd makes large scale Linux systems administration much easier.
Now it has gone a bit overboard. Some of the stuff like the dns resolver or the nspawn capability seem a bit over the top, but overall, it has massively improved all Linux distributions it is used in.
Never again will I worry about trash buggy init scripts not actually stopping a service due to a stale pid file. Now it puts the service into a control group and can kill all things in the control group even if the service is bad code.
SMS is pretty much decentralized, although there's a few companies with a lot of reach. I don't remember any Global SMS outages, but it wasn't uncommon for a whole carrier to have an SMS outage and especially for inter-carrier SMS to be broken from time to time (sometimes for days). I've certainly seen some stuff with SMS aggregators: almost all of them claim a majority of direct links, but when you have accounts with 4 large aggregators and one of them has an outage, you find out which of your other account use that aggregator for which links (because their deliverability will go to zero to those destinations).
RCS was designed and specced, by GSMA, as a telco run decentralized system that would replace SMS as like for like; but there were only a handful of rollouts. It's really only gotten use as Google pushed it onto Android, using their RCS server; recently iOS started using it although I don't know what server they attach to.
Since RCS is basically the 5th wave Google IM, it's no surprise when they have a major outage, RCS is pretty much broken.
It used to be kind of distributed, but Google has been strong arming carriers to use their hosted Jibe service through a combination of proprietary extensions (e.g., E2E which is finally standard) and bypassing carrier control (if the carrier didn't provision RCS, Google Messages would use their own service iMessage-style).
From the end user's perspective, if the carrier didn't use Jibe RCS, it simply wouldn't work well.
It would be better if Notion became a full competitor to Google Workspace. If they start their own email hosting and calendar backend for Notion Calendar, it would be getting closer.
This is not true. In some organizations I work with they only allow Security Keys on Google Workspace, you can't even use TOTP.
It's possible to disable SMS and Phone verification, but if you allow TOTP then Google Prompt is also automatically allowed.
Yep NetNewsWire all the way. It syncs to iCloud. I use it to subscribe to important GitHub project releases, blogs, news, and even some YouTube channels.
I'm considering moving to Fastmail for email and calendar, Sync.com for cloud files. It would be annoying to have separate logins for each though. One nice thing about GWS was a single login for all the apps.
This happens to be exactly what I was looking for in a Terminal app. Native UI, fast, and native screen splitting, doesn't try to do too much. Five stars
reply