And then you are basically hiring an infra team to run the services and have the redundancy, and then with salaries you’re nearing just paying for software again

You’re looking for namespaces. Have a public and private namespace

Correct. It would only be for government officials, so anyone federated with them would know that they are in fact, validated as the government official.

I think it’s perfect for governments. You can subscribe anywhere, you know it’s legit, and that’s a much better way to do notifications than twitter.

It’s not… it’s the fediverse. I’m completely fine with them having their own instance, it’s not like they control it by any means. Hell they can be defederated. It’s a lot better than them choosing some random instance.

I mean there should be a mastodon.gov.uk

about time…

Start pushing for mastodon! Honestly there should be an official mastodon instance

I was just talking to a member of my devops team and I was talking about this exact thing and they said “I didn’t know you could attach a GPU to a container”. So, yup, just stay on top of this stuff at home and you’ll do fine

It’s always the people who don’t want to admit their opinions aren’t just rejected by a platform, but by the society as a whole. There’s a reason they feel rejected, it’s because they are. We reject hateful inflammatory things at a societal level, and they feel “persecuted” when they’re called out for their bad beliefs.

We don’t want them here, we don’t want them there. If the problem is following you site to site, the problem isn’t the sites, it’s your beliefs.

I’ll be honest man, just don’t do it. I tried, I really did, to make this exact scenario to work. You can get it to work - but it will be extremely brittle. You’re essentially hacking around LXC to do things it wasn’t built to do, and most of it is disabling security that’s there for a reason. At the end of the day you are essentially running docker directly on the host anyway, the passthrough lxc becomes less and less “there” vs passing stuff through. Then, every update to proxmox became anxiety riddled because every update would change or break something on my setup.

If you want to continue, more power to you, but I hope you heed my warnings. This is a path you will spend a lot of time on and experience a lot of frustration. Spin up a tiny debian VM and run the containers there, the overhead of the VM has been negligible, and any speedup I might have had has been made up 10x by cutting the amount of time I’ve had to hack proxmox to make it work.

the default is root, but most containers will specify a UID/GID to run under. That makes it even harder with docker on lxc on proxmox.

Sometimes yes, but I haven’t seen that lately. 5 years ago I had several of those, but I haven’t seen it recently

Weird for the UI to be crashing, it’s all javascript, once it’s loaded in your browser it’s loaded. Are there any extensions that are causing issues? Anything in the browser console? Network calls hanging?

Best buy wd elements. On sale every couple of weeks. Crack open the shell and you have a wd red or white.

Doesn’t freeze for me, what sort of hardware are you running it on?

There were some automod things built by 3rd larties, and they help, but it’s still a worry. There’s also image proxying now, so at least I’m not directly hosting it, but I’m not 100% that the feds will see it that way immediately

While I run my own Lemmy instance, I can say with 100% certainty - do not host a Lemmy instance on your own hardware.

It’s tempting, and I did, but don’t. The reason? CSAM. Your hosting stuff for other people, and if someone uploads something horrible to another instance, that is federated with you. That means now you are hosting that content.

The feds then have full rights to kick down your door and seize your hardware. On the cloud however, they’ll seize your VM , but your home stuff is okay.

Hosting Lemmy is great - but it’s something you really have to think about. Hosting your content is awesome, fun, and rewarding. I’ve learned hosting other people’s content is… Not as fun.

It’s so easy to set up, just tick a box during os install most times. Then if you do rcline just use an encrypt on top of your remote, make sure your conf is backed up, and you’re golden

Tried that once. It was not a fun route to go down. If let’s encrypt ever dies it anything fine, I’ll look into it again. Until then, let’s encrypt all the way