Absolutely. Each server can be entirely standalone, you can just disable federation.
this post was submitted on 13 Jul 2023
45 points (97.9% liked)
Selfhosted
40006 readers
540 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
Holy cow, that's sweet! I'll definitely give it a try then.
As I understand it, disabling federation stops you seeing other people’s content. It doesn’t stop others from seeing yours. Though how they would fibd yours is a different matter.
No not really. If you run federation and block an instance then all you do is not consume their pushes through ActivityPub. They can still consume your pushes. But if you turn of federation then you disable the whole of ActivityPub and you don't push anything. Remember that ActivityPub is primarily push based, i.e. your instance pushes new posts out to all federated instances instead of pulling new posts in.
Thanks for that. I think I was getting confused between turning off all federation and defederating with an instance.
Setting all that aside, I would caution that even turning off federation isn’t enough to necessarily make it truly private. People could still discover it through random portscanning or whatever.
Yeah running solo you still need a hostname if anyone else is to reasonably use it, without resorting to vpns, private dns and/or other complexity.
And the default deployment of Lemmy is still publicly viewable without login so you're still posting everything for the world to see. Security by obscurity is no security at all. As has been said a million times. Same naturally goes for privacy.
This is a strange one. I assumed people wanting this type of service would want to view all the content from the fediverse but not push to the fediverse
E.g. start your own instance of kbin and connect with everyone but turn off your own federation so no one sees your posts.
Wonder if that scenario has been catered to?
Truth social did it and so can you.
I honestly forgot about this, there's also that Blue Sky thing I heard people talk about. I'm very excited to give this a go now.
Blue Sky uses a different protocol.
Ah, my bad. I never really looked into it but I kept hearing similar stories, especially when the Meta leak happened.
You can run Lemmy private, without any federation.
If you are looking for something facebookish, than you could look at WordPress with BuddyPress plugins for example.
Just check the Private instance box in the settings and it'll do exactly that.
This is really an option on Calckey??? I did not expect this use case to be accounted for, let alone supported.
Yes it’s possible on calckey.
I've been mucking about with the new claude.ai from anthropic, and thought I would ask it - here's what it said:
Y
Yes, it is possible to set up a private Lemmy instance for use within a group of friends. Here are some steps to do this:
Install Lemmy on a server you control. Lemmy is open source software written in Rust. You'll need a Linux server with Rust installed to run it.
Configure the Lemmy config file. Set the following options:
- federated_timeline_enabled - false
- registration_open - false
- external_federation_enabled - false
This will disable public federated timelines and open registration.
Create user accounts manually. As an admin, you can create accounts for each of your friends on the Lemmy admin interface.
Consider enabling SSL. It's recommended to enable HTTPS encryption on your Lemmy instance. You can get a free SSL certificate from Let's Encrypt.
Share the URL only with friends. Don't publish the URL publicly, only share with your intended friend group.
Lock down the server access. Use firewall rules, VPN, or IP whitelisting to restrict access to the server.
Keep Lemmy updated. Watch for security updates and upgrade Lemmy regularly to stay safe.
Consider private federation. You could federate multiple private Lemmy instances to allow a broader reach while still keeping everything private.
That covers the basics! With those steps, you can have a private Lemmy server for your friend group to use.
I think so, you'd just need to not add any other instances on your instance settings. Not 100% sure. I just started my own instance a couple of days ago. And I could not connect to other communities unless I whitelisted them in settings. Also there's a bunch of options and variables in configuration files that enable/disable activitypub.
Yes, but literally why tho.
I stated why in the post.
I believe I see options in my admin portal that would allow making your instance private. If that doesn't do what you want I wonder if you could populate the whitelist with a phony address which would affectively defederate you from everything.
I think I recall reading something about how it used to be something available from the UI settings, but I believe as it stands, there's no official setting in the admin panel to stop anyone else from being able to see your instance. You can disable open registration, and just not federate with anyone.
view more: next ›