ELK stack

Lolol yes, elastic was a pig for me too

That’s a good point, and it’s one that isn’t solved yet in the foss space.

There are some success stories like Blender, and other projects like Thunderbird and KDE who have recently made their model work through voluntary donations, albeit by hiring competent management of such donations. And there are lots and lots of projects somewhere in between.

The interesting questions to me aren’t so much about Plex, but the infrastructure behind all the tools we use: NTP on Linux, build tools, ffmpeg libraries, etc. Lots of other companies make products that make money, yet kick back nothing to these.

Would a royalty system work? I dont know.

Yes, you got this bang-on. Plex made the decision long ago.

There are a few ways Plex could have played this:

1. By attrition. Stop the sale of plex pass, but leave those users and their access alone. New sign-ups get new rules about features/$.
2. By using some of their revenue to paywall Premium features, keep a cut-down but functional version for non-paying plebs. It doesn’t have to be all-or-nothing, even for streaming outside your network (which you could cap at X number of hours per month)
3. Start making Plex features a-la-carte, meaning, $2/mth for HDR, 4$ for streaming, etc. Or bundles.

The point is there are lots of companies who do this right and don’t have such a blatant disregard for the user. In the long run, this will not help Plex, it will help other streaming service helpers who are actually willing to respect users.

I know you’re not defending Plex and I acknowledge that. However, I see a lot of “How are they supposed to make their money?” arguments here, hence my description above of just a few models Plex could have chosen instead of f**king the customer.

deleted by creator

deleted by creator

deleted by creator

deleted by creator

I agree they aren’t the same, especially if you need uniq to count things.

However, be aware that pipes can be a real problem in scripts because of globbing and expansion.

Enlightenment is SO configurable that it almost doesn’t have a look, and therefore doesn’t really have "brand’ per se. Take a look at galleries and collections of enlightenment setups: they’re all massively different in look and behaviour.

I remember in my early days of Linux (late 90s) it was too much for me.

That’s not true, our phones, ms teams, discord, etc do this real time all the time. Audio isolation is one of the most widespread audio processing.

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).

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.

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.