There are plenty of people that do this, and it seems to be pretty straightforward.

There is a significant risk going forward though- if the undesirables (the ones that currently get larger instances defederated) start doing this in any major way, then the larger instances will block new federation or smaller instances by default. Starting now is actually probably a good move, since you might be grandfathered in when that occurs.

Also, be aware of local laws regarding content you host. You could be liable for illegal content you inadvertantly receive.

I host my own Mastodon instance. If you’re technically proficient enough and don’t mind the extra work, I highly recommend it.

I am hosting mine for the same reason you’re considering it: I don’t want my stuff to disappear and I want to be in control of my own social media destiny as much as possible.

Now, there are some headaches I haven’t seen mentioned here, so let me toss some things out for you:

1. Until someone follows you on an instance, no one else there will know you exist. Meaning, no one on, say, mastodon.social will see your post tagged with a hashtag—or you generally—until at least one person on the instance follows you.
2. You will not have an easy time seeing people post history before you start following them because your server doesn’t know about them.
3. Following hashtags is…not super helpful because your instance isn’t ingesting a lot of data.

You may be thinking, bro, that sucks.

And you’d not be wrong, except for the fact that you’re the admin of your own server and you can do whatever you want with it. So, head on over to GitHub and fork

1. Fedifetcher. This will ingest alllllllll sorts of stuff for you. Backfill new follows and followers, boosted and favorited threads etc.
2. GetMoarFediverse. This will allow you to define hashtags and instances or query your db and have the content ingested. Want to see all the posts from #food from mastodon.social? No big deal.

I’d suggest, if tech savvy enough to go with digitalocean and just admin the whole server yourself, but bump up one level in ram instead of going with a managed hosting solution with less control.

Feel free to message with questions if you have them!

The common term for this is “single user instance” and they’re not at all uncommon.

I’m replying to you from my single user microblog.pub instance. It actually only works for a doctor user, and I’ve really liked it since I’ve started it.

I have no problems interacting with Mastodon, Pleroma, Misskey, etc. instances. It works with Lemmy as well as Mastodon does (which is to say, it works ok with Lemmy, but not ideal).

It uses a SQLite database, so, on my computer, I need Python to run the server, and nginx/caddy/Apache to proxy requests and handle https.

There are a few downsides. I host at home, so if my Internet goes down (which it does periodically), it’s down. Also, Mastodon lets you follow hashtags, but that is somewhat useless on a single user instance, since all the posts coming in are from people I follow. Search is non-existent for me, since, again, it only knows about people and posts I’ve already interacted with.

I have a Lemmy account to do most of my interaction with Lemmy, and a Mastodon account on a somewhat large instance for searching, and for periodically browsing its local feed. But mostly, I spend my time on my own instance, and an very happy with it.

@testsnake@lemmy.blahaj.zone @asklemmy@lemmy.ml

Its been working well for me with kbin. Over the last week, while the large instances struggled to stay up and federating, my instance constantly had new content coming in from whoever was still up.

The impression I get is that personal instances are part of what is intended.

If you can, go for it. It’s not rude, and no one should care or even really notice.

I’ve been thinking of doing the same thing.

Why would there be a consensus? You don’t need anyone else’s permission to run whatever sort of instance you like.

I host my own Mastodon instance. If you’re technically proficient enough and don’t mind the extra work, I highly recommend it.

I am hosting mine for the same reason you’re considering it: I don’t want my stuff to disappear and I want to be in control of my own social media destiny as much as possible.

Now, there are some headaches I haven’t seen mentioned here, so let me toss some things out for you:

1. Until someone follows you on an instance, no one else there will know you exist. Meaning, no one on, say, mastodon.social will see your post tagged with a hashtag—or you generally—until at least one person on the instance follows you.
2. You will not have an easy time seeing people post history before you start following them because your server doesn’t know about them.
3. Following hashtags is…not super helpful because your instance isn’t ingesting a lot of data.

You may be thinking, bro, that sucks.

And you’d not be wrong, except for the fact that you’re the admin of your own server and you can do whatever you want with it. So, head on over to GitHub and fork

1. Fedifetcher. This will ingest alllllllll sorts of stuff for you. Backfill new follows and followers, boosted and favorited threads etc.
2. GetMoarFediverse. This will allow you to define hashtags and instances or query your db and have the content ingested. Want to see all the posts from #food from mastodon.social? No big deal.

I’d suggest, if tech savvy enough to go with digitalocean and just admin the whole server yourself, but bump up one level in ram instead of going with a managed hosting solution with less control.

Feel free to message with questions if you have them!

I thought I’d also mention this very useful script: Lemmy-Easy-Deploy, which was specifically made for users without much experience self-hosting. At the minimum, all that you need to do is edit one file, and then run ./deploy.sh every time you want to upgrade to a new Lemmy release.

Honestly in my opinion that’s how federation should work. Everyone should have their own instance of social media and they all talk together

I guess the question is whether or not federation is automatic. If it’s manual, then every instance you want to interact with will have to federate with your instance.