![](https://libranet.de/photo/profile/quantumantics.jpeg?ts=1686491922)
![](https://lemmy.world/pictrs/image/f3189f30-f8c8-4c4f-b957-e3a7bfd1c784.png)
@AlmightySnoo
I’d rather not see one instance become overly dominant, it just acts to centralize content and puts undue strain on that instance.
Latin Teacher (secondary and Higher Ed) in the eastern USA; FOSS enthusiast, homelabber, gamer, coin collector, and (former) Magic: the Gathering fan.
AKA @quantumantics@lemmy.world
@AlmightySnoo
I’d rather not see one instance become overly dominant, it just acts to centralize content and puts undue strain on that instance.
@Angry_Maple As someone who uses Keepass, I highly recommend KeepassXC over the regular release. There is an open security vulnerability that the original devs aren’t really addressing: www.bleepingcomputer.com/news/… the XC release team has mitigated this and has generally been better about improving the UX.
@proycon Proxmox on an HP Z620 (2x Xeon E5-2670, 16 cores, 64GB RAM)
Inside of that I run:
Emby
AMP (game server software)
Moodle (for content development, currently idle)
Home Assistant
Paperless-ngx
Grocy (just installed recently)
+ an assortment of VMs for various purposes
(Edit: for anyone who uses Proxmox: I find the scripts here tteck.github.io/Proxmox/ to be very helpful is quickly spinning up LXC’s)
I also have an OPNSense firewall, a Pihole, and a Synology NAS.
Other than my game servers and Emby, which get port forwarding through my OPNSense firewall, everything stays internal to my network. I’m thinking of learning wireguard so I can remote into my network, but that’s not a high priority.
@hardypart
Agreed; I was more concerned with the possibility of the vast bulk of communities ending up on a couple instances rather than having major communities spread out. Having some way to keep similar communities connected and effectively moderated would be a great boon for us. How we best go about that, I’m not sure.