I’ve been running my own Mastodon instance for several months now, and I’ve enjoyed it. I don’t have to rely on someone else, either, which is nice. I’m in control of everything on that instance.
As for Lemmy, I just started my own instance today, and am currently writing you from it. What made me decide to setup my own instance was some performance issues I was seeing with Lemmy.world, although that might have been an UI problem. Anyway, I enjoy doing this stuff, so I’m running my own instance for the sake of doing it.
On the flip side, it’s more expensive and time consuming, and I’m the one who has to worry about backing up data, etc. Like I said, though, I enjoy doing it, so it’s no big deal.
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.
I run my own Mastodon instance, but for Lemmy it seemed more logical to join an existing instance that aligned with my interests.
I wouldn’t be adverse to abandoning my self-hosted Mastodon for a shared instance, but I would prefer a small instance run by and for people I know, rather than one of the huge ones.
What might make you want to ditch your self-hosted Mastodon instance?
With Lemmy, I didn’t feel a need to pick any specific instance because I can follow communities from anywhere, and it seems to work pretty well.
One downside I’ve encountered with my own Lemmy instance is that post and comment history in the communities I follow begins when I started following them on my new instance. New posts and comments are federated my way, going forward, but I don’t have the ability to go back and view as much history as one would on lemmy.world or lemmy.ml, for example.
I provisioned an Ubuntu 22.02 server at Linode. I chose their 2 GB Shared CPU instance type. Once I configured the server to my liking, I ran through the Lemmy-Ansible instructions. (They have other methods, so check the documentation.)
Essentially, you install Ansible on your workstation. I’m on macOS and installed it via Homebrew. You then download their git repository, create the necessary configuration files, and then have Ansible configure the server. It was fairly simple.
I have a lab at home and do host some stuff for myself from there in a small DMZ (ie: Miniflux RSS readers, Plex through Reverse proxy etc).
But I used a linode for my lemmy/kbin stuff. Reason being is that the code is fairly new and there may be exploits bugs and
I dont want to deal with my ISP made an instance is exploited and becomes some type of C2 box or spews out spam. Kbin specifically already has PRs to fix XSS and Sql injection stuff, the former of which is usually avoidable if you just follow some pretty basic principles. So its a concern.
Linode has better bandwidth than my non-symmetrical ISP uplink and is on its own quota.
It sounds like linode is the way to go then and their prices seem reasonable. The funny thing is I’ve heard of linode before because Computer Clan uses it as a sponsor, but ever since I started using sponsor block I haven’t really heard about it. I didn’t actually know what they did.
I’ve run linodes for years. My blog runs on them. I still host a variety of other services on them. They are good for everything from gaming servers to a blog etc.
They did get bought out by akamai a while back. And have raised their prices but they are still solid.
I am currently the only user. Im considering opening it up to limited users but not really having communities once i get a lot of the instances cached and indexable.
Others like @leopardboy@netmonkey.tech are running on a 2GB shared just fine. I will likely move to that if i choose to keep it solo for sure, or under 100 users and no communities.
I dont have the time to really moderate others or content on the instance. So i dont think I plan to host any communities at all. I do wish you could federate/sync specific communities to your instance to make searching/subscribing easier.
I think it’s a matter of personal preference.
I’ve been running my own Mastodon instance for several months now, and I’ve enjoyed it. I don’t have to rely on someone else, either, which is nice. I’m in control of everything on that instance.
As for Lemmy, I just started my own instance today, and am currently writing you from it. What made me decide to setup my own instance was some performance issues I was seeing with Lemmy.world, although that might have been an UI problem. Anyway, I enjoy doing this stuff, so I’m running my own instance for the sake of doing it.
On the flip side, it’s more expensive and time consuming, and I’m the one who has to worry about backing up data, etc. Like I said, though, I enjoy doing it, so it’s no big deal.
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
I run my own Mastodon instance, but for Lemmy it seemed more logical to join an existing instance that aligned with my interests. I wouldn’t be adverse to abandoning my self-hosted Mastodon for a shared instance, but I would prefer a small instance run by and for people I know, rather than one of the huge ones.
What might make you want to ditch your self-hosted Mastodon instance?
With Lemmy, I didn’t feel a need to pick any specific instance because I can follow communities from anywhere, and it seems to work pretty well.
One downside I’ve encountered with my own Lemmy instance is that post and comment history in the communities I follow begins when I started following them on my new instance. New posts and comments are federated my way, going forward, but I don’t have the ability to go back and view as much history as one would on lemmy.world or lemmy.ml, for example.
Can you tell me a bit about the process you went through to create your own instance? I’d like to make one myself.
You’re talking about Lemmy, right?
I provisioned an Ubuntu 22.02 server at Linode. I chose their 2 GB Shared CPU instance type. Once I configured the server to my liking, I ran through the Lemmy-Ansible instructions. (They have other methods, so check the documentation.)
Essentially, you install Ansible on your workstation. I’m on macOS and installed it via Homebrew. You then download their git repository, create the necessary configuration files, and then have Ansible configure the server. It was fairly simple.
I may go that route. I was wanting to host my own server but I feel like it would be easier to just use a cloud server
I have a lab at home and do host some stuff for myself from there in a small DMZ (ie: Miniflux RSS readers, Plex through Reverse proxy etc).
But I used a linode for my lemmy/kbin stuff. Reason being is that the code is fairly new and there may be exploits bugs and
I dont want to deal with my ISP made an instance is exploited and becomes some type of C2 box or spews out spam. Kbin specifically already has PRs to fix XSS and Sql injection stuff, the former of which is usually avoidable if you just follow some pretty basic principles. So its a concern.
Linode has better bandwidth than my non-symmetrical ISP uplink and is on its own quota.
It sounds like linode is the way to go then and their prices seem reasonable. The funny thing is I’ve heard of linode before because Computer Clan uses it as a sponsor, but ever since I started using sponsor block I haven’t really heard about it. I didn’t actually know what they did.
I’ve run linodes for years. My blog runs on them. I still host a variety of other services on them. They are good for everything from gaming servers to a blog etc.
They did get bought out by akamai a while back. And have raised their prices but they are still solid.
Nanodes are awesome deals frankly.
Is the 2GB the one you use for your Lemmy server? I’m getting ready to purchase one to see if I can figure it out.
Im currently on the 4GB dedicated. However heres an htop of it.
https://imgur.com/a/NpEsw4t
I am currently the only user. Im considering opening it up to limited users but not really having communities once i get a lot of the instances cached and indexable.
Others like @leopardboy@netmonkey.tech are running on a 2GB shared just fine. I will likely move to that if i choose to keep it solo for sure, or under 100 users and no communities.
I dont have the time to really moderate others or content on the instance. So i dont think I plan to host any communities at all. I do wish you could federate/sync specific communities to your instance to make searching/subscribing easier.