this post was submitted on 22 Aug 2023
28 points (96.7% liked)

Selfhosted

46291 readers
375 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I'm reading up on self-hosting Lemmy, and I was planning on creating my own private instance for individual use on some spare Azure ASP I use to host private FreshRSS (not rich to host a public service).

This basically shuts my idea down, because I wanted to simply host my account myself and browse all of Lemmy as I please.

So is everyone hosting individual instances dealing with them being public? is there a workaround to avoid having a public service that anyone can see?

all 11 comments
sorted by: hot top controversial new old
[–] [email protected] 14 points 2 years ago* (last edited 2 years ago) (3 children)

This basically shuts my idea down

it's not very difficult to modify the code for something like this.... and closing off registration wont' let anyone else login and create new content form your istance.

Personally the load on the major servers by having one more instance that subscribes to everything is why I think people should back off from creating more than the 1500 instances Lemmy network already has. Delivery of every single vote, comment, post 24 hours a day just so one person can read content for an hour or two a day.

That makes sense for email systems where all that content doesn't have to be sent, but for Lemmy it's a huge amount of overhead.

[–] [email protected] 4 points 2 years ago

the load on the major servers by having one more instance that subscribes to everything

But why would the instance subscribe to everything?

[–] [email protected] 4 points 2 years ago

Didnt look at it like that tbh, and it makes sense now that I think about it.

[–] [email protected] 13 points 2 years ago* (last edited 2 years ago)

Private in this context means that it is isolated. If you want it to be private in the sense that it's only for you to use the you just close registrations.

Anonymity and federation are kind of oxymoronic.

[–] [email protected] 8 points 2 years ago

The federation/API end point and the web-ui are entirely independent.

If you want, you can run the federated backend with no web ui at all and use it via mobile apps only.

Or you could put some password protection via the webserver in front of the web ui only.

[–] [email protected] 0 points 2 years ago

I used a $2/mth vps and got an instance up in about 5 minutes with ansible. Took longer to pay for the instance and ssh into it than the Lemmy install

If I were worried about it gaining users then I'd just limit access to the UI or do some database maintenance

[–] [email protected] 0 points 2 years ago

I run my own instance only me. Make sure you setup reverse proxy right :)