Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
As someone who likes having control over their data and especially backups, and someone who normally enjoys self-hosting things, I honestly might do it. I'm not sure if I'd want to host a lemmy instance or kbin instance though, since I know they all federate together anyway. I may also end up waiting until the software is more mature too before looking into it.
That's awesome! Running my own social media instances has become a hobby for me.
Having my own Lemmy instance has felt fairly seamless versus using Lemmy.world, but there have been some kinks. For example, when attempting to subscribe to a new community, the server has to pull a bunch of data first. This takes several seconds, but the UI simply says "not found" -- and then after several seconds, the UI updates with the community you want to follow. I figured this out by tailing the logs.
Also, the installation was pretty damn easy, especially when compared to Mastodon.
I'd maybe be interested in trying out self-hosting Mastodon at some point too, good to hear that Lemmy was easy to install though. I'm not too worried since I have quite a bit of Linux experience, I figure it probably won't be too bad to setup whatever social media instances I'm interested in checking out.
Yeah, if you've got a decent amount of Linux experience, I don't think you'll have any issues. Mastodon's installation is well-documented and works. My only criticism is that it's a bit long and you have to be careful not to miss anything.
On the other hand, I recall installing Pixelfed back several months ago and having a difficult time. The documentation was lacking, and it required me to use Arch Linux, which I had never used. I was able to get it working, but eventually terminated the instance after a while because I was never using it.
Oof, yeah, requiring someone to use Arch definitely seems like a steep requirement lol
Yea, but then they can say "I use arch btw". That's what really matters in life.
#goals
LOL
It wasn't bad -- I just wasn't familiar with it.
Wait. I'm looking at the Pixelfed installation guide right now and it doesn't tell me to use Arch at all? Isn't it just a PHP app?
That's awesome. This was several months ago when there was a link to some specific Arch Linux documentation that @dansup@mastodon.social mentioned was the most complete. Sounds like it's been cleaned up.
Yeah, I think it is a PHP app.
mm. Might have been a getting started from the ground up kind of setup guide and the author might be most familiar with that. But happily it seems like there's docker files in the main repo, including docker compose files, so that should make it quite easy to set up.
Personally, I went with Lemmy because it seems to be quite a bit further along in it's development. It also doesn't look like kbin's developer is recruiting much outside help, if you look at the repos of the two projects on GitHub/Codeberg, Lemmy has tons of contributions from people while kbin is mostly just the one guy with a few commits here and there. Not to mention that Lemmy's way less of a resource hog because it's written in Rust whereas kbin is implemented in PHP. Also, as far as I know federation is still currently broken on kbin.
The reason why I'd consider kbin is because I almost think I might prefer the interface, also I'm more of a PHP developer myself so that is tempting in and of itself too lol
I may wait a little bit before trying out either one tbh and maybe I'll give both of them a try.
As someone that has spent the better part of the week mucking with it.... the kbin build docs have multiple gaps in the documentation and are functionally broken unless you have some better understanding of the setup. I WAS able to get the system built, but could never get it online. Best i got was 500 errors where the UI was up but there was a break somewhere in Redis, Postgres, Nginx etc. All the logs were clean though. This was with the docker method and build from source method on both Ubuntu 22.04 and Debian 11 (which are what he specifically referenced)
Lemmy was much easier to setup using the ansible method. I have an instance online. Though im still working out the federation thing and some other kinks. I figured it would just reach out to Activity pub and federate with everyone but now it seems I have to build a static list...If if search for an instance i know exists I get a
So there are some gaps but it seems much more mature. For example you cant mark your instance private AND have federation enabled. If you do that and restart the instance will fail to come up, but theres no warning or error in the UI.
I like the kbin dev better as people. But the lemmy code is definately more polished, even if the devs are turd sammiches.
Well that's interesting, and somewhat like I expected but not really, I am surprised the setup process for kbin is that broken, although I guess it does make some sense since kbin is that much newer.
Yeah. I like the kbin dev as a person much better. And I can empathize with what he is going through. Its why i wanted to setup an instance and help spread the load. But I just couldnt get it working and didnt have the time to really dig in (I have a lot going on otherwise with work).
He did announce he is onboarding a sysadmin/netadmin to handle the stability and scaling issues so he can focus on commits which is good. Ill keep an eye out for updates and maybe migrate then.