You see, it’s not required for me to agree with whom you are criticizing, to criticize your inability to be civil. So keep making as many strawmen you like. We are in a post complaining about user behavior/content and your behavior and content are both completely unacceptable in a community.

Also, you can stop name-calling, this may have an effect when someone else values your opinion, I don’t.

Ok, but it’s the same thing from the perspective of all the people on an instance vs from the perspective of an individual. Those people are still there, creating posts etc., and they can easily move on other instances if they want too.

It’s just a “bigger blanket”, but the concept is essentially the same, with the plus that more people are “covered” and the minus that someone might be affected against their will.

Either way, it doesn’t solve the problem, it just masks it for the members of an instance. Why would it be a fundamentally better solution in this particular instance?

I had a look at your history, and you seem really incapable of behaving in a civil way, often using insults. I don’t think this is a good strategy to get your point across.

Be respectful of others.

This comment is in clear violation of the rules of this community. Be better, if you want to criticize others.

No, you’re putting a blanket over them and pretending they’re not there any more.

Isn’t defederation the same thing? Users won’t disappear (and they can also create accounts elsewhere…).

I went to look for the video and somehow was worse than I had imagined.

Thanks (grazie?)! I was looking for something similar and kanidm looks great feature wise and simple to deploy!

I struggled with this for a long time, and then I just decided to use synology photos.

It has albums, tagging, geolocation, sharing. It has phone picture backup, it is inherently a backup as it’s on my NAS and I back that data up again.

I want to keep the thing that I really care about the most friction free and also not too dependent on myself so that I can still experiment.

I didn’t try PiGallery2 though, maybe I will have a look!

Did it sound cold? Because I didn’t mean that, I just meant to actually answer the question from my PoV. Just for the record, I also did not down vote you.

So yeah, use whatever footgun you prefer, I don’t judge :)

Or rustic! It is compatible with restic but has some nice additions, for example the fact that supports a config files. It makes operations a bit easier IMHO (I am currently using both).

I really thought swarm was dead :)

To be honest, some kubernetes distributions make the cluster operations minimal (I use k0s managed via ansible)!

Either way, the moment you go from N containers on one box to N containers on M boxes you need to start considering how to handle stateful applications, load balancing, etc. And that in general requires knowledge on a domain which is different from having simply applications wrapped in containers locally.

I think k8s is a different beast, that requires way more domain specific knowledge besides server/Linux basic administration. I do run it, but it’s an evolution of a need, specifically when you want to manage a fleet of machines running containers.

Because the lxc way is inherently different from the docker/podman way. It’s aimed at running full systems, rather than mono process containers. It has it’s use cases, but they are not as common IMHO.

You have a bunch of options:

kubectl run $NAME --image=$IMAGE

this just creates a pod running the specific image. If you kill the pod, or it terminates, it won’t be run again. In general though, you probably want to do some customization before running (maybe you need volumes, secrets, env, ports, labels, securityContext, etc.) and for that you can simply let kubectl generate the boilerplate YAML and then simply make some edit:

kubectl run $NAME --image=$IMAGE --dry-run=client -o yaml > mypod.yaml
# edit mypod.yaml
kubectl create -f mypod.yaml

You can do the same with a deployment or statefulset:

kubectl create deployment $NAME -n $NAMESPACE [...] --dry-run=client -o yaml > deployment.yaml

In case you don’t need anything fancy, the kubectl create subcommand allows you to create simple workload, so probably that’s the answer to your question.

I would say Docker. There is no substantial benefit in running podman, while docker is a widely adopted tool (which means more tooling in the ecosystem, easier to find answers to questions etc.). The difference is not huge tbh, and some time ago the biggest advantage for podman was being able to run rootless, while docker was stuck with a root daemon. This is not the case anymore (docker can run rootless), so I would say unless you have some specific argument to use podman, stick with docker.

They have millions in funding, they will always move at a faster pace. The question is in which direction they will move, I suppose.

This is a separate discussion, on which tbh I have not a strong opinion. I can understand the risks of children without proper sexual education consuming porn, but I also understand the pointless nature of trying to block it.

In fact I don’t personally agree with doing it here, but I mean, there is no other way to do age verification. There are technically ways that can make sure the only data reaching the end customer (the porn site) is a boolean (minor or not), and the identity verification is generally done by another entity, but ultimately yes I agree, I wouldn’t do it either and I personally think it’s not worth in this case at all (I think proper sex education in school is probably what I would invest on).

There is also another thing to consider though, which is that porn is different from -say- a gambling site (where you have to make identity verification) mostly due to religious/moral stigma on sex. This makes me a little bit conflicted because I would like a society in which sex is freed from stigma and shame, and where “associate yourself with a porn site” is not as bad as it is now. Definitely the age verification is not the way to pursue this objective, but overall this makes me ask questions like "why would I have not a problem doing the same for a gambling site but I would for porn? Does it align with my values or is it coming from cultural pressure I disagree with?

Many appliations do identity verification: financial platforms, crypto scams, roblox, car sharing platforms… It nowadays takes a couple of minutes and it’s done once, associated with your account. I am not saying I agree with the idea of doing it here, but I think that many people wouldn’t care to change platform. And if they do, some other platform will grow and eventually will have to do the same.

Yes, an exploitative thing that mostly consists of free labour for big orgs.