this post was submitted on 05 Jul 2023
30 points (94.1% liked)

Asklemmy

43777 readers
1338 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
Cloak@lemmy.ml
mekhos@lemmy.ml
tmpod@lemmy.pt
14specks@lemmy.ml
30
What's the general consensus on making private fediverse instances? (lemmy.blahaj.zone)
submitted 1 year ago by testsnake@lemmy.blahaj.zone to c/asklemmy@lemmy.ml
23 comments fedilink hide all child comments
 

I feel like over the past few months, the main thing preventing me from getting super active in the fediverse has been all of the drama surrounding federation and instances shutting down.

I just want to be able to turn my brain off, and not have to think "Will this instance be around in 6 months?" every time I post.

As a result, I've been thinking about creating a Lemmy and/or Mastodon instance that is literally just me and no one else. No communities or anything, simply me posting to other instances via this private instance. And I know that this instance will stay alive and federated for as long as I keep hosting it.

However before I go through the effort of setting these up, I want to know what people think about private instances. Is this bad taste? Is it a logistical nightmare? Have people done this before? And what would the hardware requirements for a 1 user instance look like?

you are viewing a single comment's thread
view the rest of the comments
[–] kehalo@lemmy.ml 3 points 1 year ago

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!