So basically… this is a blatant cash grab, and a nearly 200% one depending on the level of service you pay/paid for. Wonder how long it will be before the lifetime pass is discontinued and everyone gets forcibly moved over to a monthly subscription model

A self-hosted photo/video viewer which presents itself as an Open Directory that maps closely to the underlying file system and also includes the ability to view images and stream videos. If videos are too large/incompatible with the user’s browser, they should be transcoded on the fly (optionally with the gpu). Genuinely surprised something like this doesn’t exist

Same, I also use Cloudflare dns, tunnels, and pages. Having these all in the same place makes it easy to deploy/keep track of everything

I use OVH. Reasonable prices, very reliable, and no bandwidth caps

If you’re technically inclined, you can selfhost metube for your friends/family

Oh yeah don’t get me wrong I love nicotine+ too! I figured I’d link to slskd since this is the selfhosted community after all 🙃

I’m not a fan of YouTube’s audio compression algorithm (optimized for saving google’s bandwidth but sounds awful on higher fidelity audio setups). If quality is a concern, I can’t recommend slskd enough

I use wiki.js in the linuxserver.io flavor. I have 3 URLs for every service I run: public, LAN, and tailscale url. My “homepage” is a big markdown table with links to all the services. It’s not pretty by any means, but it’s very functional

you can also delete them recursively with

find . -name '*.DS_Store' -type f -print -delete

(adapted from this script)

Indeed. Western portrayals of Jesus are likely historically inaccurate, it’s more probable that he was dark skinned

The pi zero is good for small projects that don’t require a lot of compute, however I personally haven’t found it to be useful in a self-hosted context. Unless you really don’t care about performance, the low specs make it unsuitable for hosting most of the services you listed above

I can’t speak specifically to apple’s testing process, but as someone who has worked in software QA, it’s simply not possible to catch all the bugs. Obviously no one wants bugs, so I’ve witnessed past employers try everything from adding more manpower to attempting engineering culture changes to adding public beta programs. None of these meaningfully reduced production bugs. If you or anyone else knows a better way, I’m listening :)

This. Also lawyers are expensive, and hiring a team of experienced lawyers is even more so. A bean counter probably crunched the numbers and found it would be more cost effective to settle now than to fight it out/ run the risk of losing (in which case they may also have to pay for the plantiff’s legal fees)

I don’t think that’s necessarily a bad thing. The unfortunate reality is that any sufficiently large software project with a lot of engineers touching the code is going to have bugs. At least someone at Apple is trying to fix these as opposed to ignoring/pretending they don’t exist