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.
this post was submitted on 22 Aug 2023
4 points (100.0% liked)
Selfhosted
40173 readers
1067 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:
-
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!
founded 1 year ago
MODERATORS
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.
What is your definition of private?
You can disable registration (so you’re the only user and thus no one other than you can subscribe anything). You can simply not create communities on your instance (and thus no one can post anything). You can federate per normal and still browse anywhere you’d please.
Would that achieve what you’re looking for?
If you click on the link:
Use case: I run a single user instance where I don't create any of my own communities but I subscribe to and interact with a variety of communities on other instances. By making my instance non-private, everyone on the Internet can browse to it and see every remote community I've looked at which seems pretty bad for privacy.
I run my own instance only me. Make sure you setup reverse proxy right :)
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.