It’s alright, it’s art. You can’t expect it to reach everyone the same way.

This smells like ego projection. These are tools for jobs, they don’t have to compete.

Different tool, different purpose.

You could make a client or browser add-on or something that just uses a separate account for all your voting.

NC deck could be cool but I found it really disappointing.

Sorry you’re getting down voted so much. I personally don’t have this problem, but if you do it’s a valid experience. UX is not easy to get right for the masses.

I’ve been running it for about 6 years, literally never did me dirty.

Docker compose pull every couple weeks, bump the major version whenever it’s time, migrations always work.

Nextcloud news is alright

Docker and docker-compose. Then learn podman after you have some experience, if you want to…

Or jump into kubernetes (or minikube) instead of podman if you want to do highly useful things.

But first, get comfortable building images with a Dockerfile, and then running them in a meaningful way, and networking them, and locking them down.

False.

I’m a big fan of running home stuff on old laptops for this reason. Most UPSs give you a few minutes to shut down, laptops (depending on what you run) could give you plenty of extra run time and plenty of margin for a shutdown contingency.

I used to use Ampache, say 14 years ago, and I liked it a lot. Until I ran an unrelated batch job to reorganize my music files that went sideways, and started streaming from Google music. I’ve been meaning to try it out again, or something like it.

They’re beating the algorithm

I don’t remember much about how to use kubernetes but if you can specify a tag like nextcloud:28 instead of nextcloud:latest you should have a safer time with upgrades. Then make sure you always upgrade all the way before moving to a newer major version, this is crucial.

There are varying degrees of version specificity available: https://hub.docker.com/_/nextcloud/tags

Make sure you’re periodically evaluating your site with https://scan.nextcloud.com/ and following all of the recommended best practices.

I have only ever run nextcloud in docker. No idea what people are complaining about. I guess I’ll have to lurk more and find out.

Things should not care or mostly even know if they’re being run in docker.

Always works great for me.

I just run it (behind haproxy on a separate public host) in docker compose w/ a redis container and a hosted postgres instance.

Automatically upgrade minor versions daily by pulling new images. Manually upgrade major versions by updating the compose file.

Literally never had a problem in 4 years.

I also wonder how the rest of the fediverse can do better to demonstrate its value, in terms of users and content, which would cause threads users to desire content from us.

Yeah the mutuality argument is a strong one IMO.

It would be great if the fediverse did have the leverage to influence meta to accept other content.

At the same time, I wonder if there could ever be an implementation that detects asymmetrical & unfair practices across instances to give them consequences in real time.

If the majority of us are truly here specifically to enjoy the freedom of choice, then it would follow that peering with Facebook wouldn’t be a major risk for active users here, and possibly an opportunity to reach a less savvy audience.

Lemmy and mastodon are platforms good for connecting broadly. There could even be a separate instance that is a subsidiary division of a major player.

And as far as hoovering up our data, we’re already out here putting it out there. Don’t put sensitive data on here and don’t sign up for an instance owned by surveillance-capitalists.