Probably from the anti AI purists. There are many on Lemmy

One big reason why not to buy a Rqspberry Pi for Self Hosting is the price. If you want to run more heavy services (like jellyfin can be), you need the Pis with 8GB of RAM. Though those where already expensive before the sharp rise is RAM pricing. When you include a fitting power supply and a small cooler with fan (so that you don’t run into thermal throttle fast) you are probably already at like 110€ at least. For that money you can also get a used mini PC (those that companies use for their employees), that already has more power and offers better upgradebility (RAM, storage). Also for some services you might run into the problem, there is no version build for ARM devices (though that happens very rarely nowadays).

Though with the RAM pricing problem every computing device gets more expensive. Just include such mini PCs into your comparison to make a good decision.

Mhh, you are probably right. I’m really hesitant to invest more time into troubleshooting tailscale. My own tailscale connections at home are stable, and for troubleshooting at my family member I always have to drive and setup my notebook there.

Maybe I could try to setup wireguard directly in the fritzbox router at my family member. That might need less maintenance as running tailscale in a docker container, as it would remove the wireguard connection out of the NAS itself.

Opening a port directly gives me kind of an ick, because I don’t want to fiddle too much with the family members network. If something happens with it, I will be the one troubleshooting it, and I don’t need more work currently.

So Tailscale connection instability is not common? I don’t like debugging this, since the NAS is remote and I don’t have much time going to the family member again and again for this. It definitely is something on the remote site, since the tailscale connections at my home are stable.

I will definitely have a look at Kopia. I was in search of a good open source backup solution, since borg also has its flaws. I will check it out, when I setup the remote NAS again (as I also want to put bigger disks in it)

For proxmox on a VPS beware: Some hosters are using a kind of virtualization, that is more like a container instead of a VM. This means, that if you need kernel access (like changing active modules) you will fail. Proxmox probably won’t run on such a VPS.

Also: A VPS is already virtualized. Running nested VMs (some VMs on your Proxmos VM/VPS) will hurt the performance. Better stick to containers on a VPS.

Not federating at all would be a shame IMO. I’m really exited on this feature for git forges

Being able to self host a git forge was always possible, even before forgejo. Besides the gitea controversy I thought the federation to be the real killer feature.

So I guess I have to wait a bit more for the federation.

OOTL Wasn’t there something about forgejos capabilities to federate? I had the impression, that it would go the fediverse route with many interacting instances. Then everyone can make their own rules. There are many reason to moderate repos. So why is this such a big thing (if forgejo federates as I remembered from the back of my head)?

So, ever heard of the botnets based on thousands of private IoT devices, which executed severe DDOS attacks on many sites on the web?

While we are all making compromises and secure our systems to different degrees, saying that a compromised system is not a disaster is way out there.