Yeah, clubbing 101 in Berlin. So refreshing

Older post: https://lemmy.techtriage.guru/post/66653

Some instances don’t have any checks or barriers for signing up, so the bots can just get accounts from these kind of instances and keep spamming.

It was already discussed in a post here, lrt me see if I can find it

I could paste an example of how we did it if you want

I used saltstack for work some years ago, the fact that you need to install salt minions and connwct them to master was enough to convince us to change.to.ansible. unless you need Saltstack for some specfic reason, I recommend ansible instead.

We had pillar data in repos, one top file total.

Ship it to Berlin and I’ll bring it when I go home for xmas. No really, Im sure you know someone in EU

Because exactly 2 peopleI know have matrix users.

I still use it, and refuse to use Whatsapp, but it takes some effort to get people over to the beautiful FOSS-side

Good bot

This got me a bit excited, until I read the article. Sadly missing documentation, so not sure about how one would go about setting it up

Yes you can do this, you can use ANY device/node as an exit-node among your tailscale nodes.

You do need a server to setup the nodes though. Tailscale offer this as a paid service I believe, or you could run your own headscale (open source project) server yourself, this requires a lot more knowledge

Germany? Ideleted it today

That’s exactly what a criminal would say! /s

Really cool article

This was such a game-changer for me

Good bot

Good bot

I’m looking for the same thing

My friend and I run most things in kubernetes (k3s), and then we use longhorn to backup volumes, which then can be re-used if your cluster crashes. Here’s a blog post describing the process (although not for nextcloud specifically, it could be applied to Nextcloud as well, as we do this for nextcloud as well)

Octopusx blog: Backup and Restore

Actually sounds really cool, why not

Jupiter Broadcasting has nice Linux and FOSS-related podcasts. Most recently with an episode about Red Hat and their decisions.