- 0 Posts
- 5 Comments
dudeami0@lemmy.dudeami.winto Selfhosted@lemmy.world•How do services like Mastohost work on a fundamental level?English0·4 months agoCentralization is a weakness. These services can be targeted by governments that want to limit communication. Free speech is a commodity, and servers host this free speech. If a hostile organization, such as a government, targets a channel of free speech such as those hosted on a platform that makes it easy to setup a mastodon instance, this become an easy target that will affect a large portion of users. If you are serious about freedom, you have the freedom to self-host your own platforms.
Edit: I realize my post doesn’t answer the question proposed, but it’s more of an argument against such services. I would argue self-hosting doesn’t rely on paying third-parties to host your software, but I guess this is in the eye of the hoster.
Then the menu is a broken webpage with “old” prices and the restaurant tries to charge you more than the menu prices. I thought the point of these were to be easily updated.
dudeami0@lemmy.dudeami.winto Selfhosted@lemmy.world•Looking to start self hosting by going through Louis Rossman's recently released guide. Any pointers for a newbie are most welcome.English0·5 months agoI’d just skip OpenVPN altogether and get started with Wireguard or Headscale/Tailscale.
This one was huge for me. OpenVPN is pretty heavy with CPU overhead, where as wireguard is almost free. I was getting throttled due to the overhead of OpenVPN and roasting the CPU on my Netgear R6350 (it’s what I had lying around). With wireguard I get nearly the same speeds as without a VPN and my loads are very reasonable.
Also with weaker routers like mine, be wary of trying to use QoS, this will probably not help network congestion and instead become a bottleneck (like it did for me). This is where a beefy dedicated router really shines.
Disclaimer: I have no experience with Bazzite. A quick web search shows that it’s a distro based on Fedora Atomic. That being said, if you did everything according to the documentation, this is probably a bug that should be raised with the developers.
The first line states
/init: error while loading shared libraries: libsystemd-core-256.11.1-fc41.so: c
. This is basically the issue, for whatever reason the shared library for systemd (which if being used, is basically the backbone to your systems startup) isn’t available. The next place I would look is whatever tool/command you use to upgrade/build your system, this might of spit out an error related to why this library could not be built or why it’s inaccessible on the next boot. If the solution isn’t obvious from those logs, I would report this to the distro developers as a ticker in their bug tracker.As to look at the positives, you have discovered the beauty of immutable/atomic distros. You can just go back to the working version instead of cussing at your PC.