deleted by creator

I agree.

I will add, however, that Jeff’s main concern isn’t the policy itself, but that he and other youtubers can’t see it or know what the rules are. The lack of transparency is the real issue.

They’re the 800lb gorilla, and no other platform can create “youtuber” income, so it’s a real problem for people like Jeff Geerling to move from yt, even if they know it’s bad, because it’s a major part or all of their income.

YouTube restored the video, but not until Jeff had made a huge stink about it (and rightfully so, those yt fuckers can eat a dick).

Clout and profit.

That is not the title of the linked article.

Also, I would speculate that this isn’t “World News”, but what do I know.

The most important thing is to use your common sense, think about it an extra minute before punching holes in your fw, and keep those holes documented and to a minimum.

Oh, wow, you weren’t joking. Jeez.

I have a jonsbo n1, do not buy it.

1. Cooling is insufficient. Something about the case layout makes the motherboard area not get enough ventilation and the supplied fan can’t cool 5 disks, the chassis holding the disks doesn’t allow enough air through.
2. Only room for half-height expansion card.
3. Cable routing is abysmal, with sharp edges.

It’s Morbin time.

You misread that.

The database was from prior to 21.x, because i installed NC 8 years ago at v14 and have upgraded since then. I’ve been upgrading the same system since late 2016.

Stop picking fights with strangers.

I’m not sure what gave you the impression I don’t follow the official procedure, I do follow the official upgrade procedure, and always have through its many stupid iterations for the last 8 years.

Example error, from last week:

Devs did not test with NC instances created before v21.x, so the SQL db is broken when going through the official upgrade if your nc has the old structure and I had to manually modify the actual db to work.

This kind of shit happens about twice a year. Mind you, this exact literal thing happened from v18.x to 19.x also, you’d think they has learned their lesson.

And php itself is fine. Not the most secure way to build a webapp, but fine. However, upgrading PHP on various platforms is an exercise in pulling your hair out.

Nextcloud is great when it’s working. Most upgrades are fine. But when it poops the bed, it’s another hour I can’t get back. No other self-hosted software in my stack is like that.

Thank you, I’ll try radicale.

That YouTube strike for Jeff geerling scares me… Twice in 6 months? For just mentioning libreelec?

We are all being driven underground by the profiteers who are ruining what was at one time a great free platform. I hope we find a way to keep our freedoms alive.

Fuck the yt police, and fuck their moms.

I rsync nightly to an old synology box. It’s in an out building, so if there’s a fire, it comes with me.

I’ve been using NC for about the same amount of time and I will say I’m no longer as happy with it as I once was, primarily because it’s a mess of PHP, gum and popsicle sticks held together by me going in there every 3 upgrades to fix ‘occ missing indices’, add a sql table or some such error.

The caldav integration did allow me to break free from google some more, and it works well, but I’ve since moved file sync to syncthing and I’m looking for a standalone caldav solution.

I get your meaning, but there are other “unpolluted” distros where the theming and arbitrary package selection is kept at a minimum. Debian comes to mind.

In fact, Fedora does take liberties with non-free drivers and configs for the sake of a sane and usable quality of life.

I’m not trying to start a pissing contest here, just highlighting that there’s a Linux for everyone, and that is the great thing about Linux.

What do you mean by “least polluted”?

I’m not baiting you, I don’t grok what you mean.

I went through this about 6 months ago.

Just build playbooks from basic to specific. I did so in three parts:

1. Container creation
2. Basic settings common to all my hosts
3. Specific service config & software

Ansible assumes you have a hierarchy of roles to apply for each service, so layering playbooks this way should help