I’m not sure those two settings should be compatible? If it’s a private instance then it means it should not federate.

I guess it was an oversight regarding breaking changes. What error did you get? It might help some people who’re experience similar problems.

Keep in mind that this limitation only on beehaw.org

Other Lemmy instances such as allow you to create communities freely. For example lemmy.ml or sopuli.xyz

The way federation works is that as a user of one instance you can read posts and comment from and to any other instance. That is how I can reply to this post even though my account is on lemmy.ml

What is not federated yet is community creation. Currently you can only create a community on an instance you have an account in and it so happens that beehaw on which you are has community creation disabled.

The idea is that it should not matter too much which instance you join, but you’ll find a few differences between instances such as the ability to create a community or not, the existence of downvotes, etc…

Yes, but that only works once there’s one user from the local instance subscribed to the remote community. This is to allow communities to appear on that list.

Please no… For the love of Foss, no. Apple would start making private changes to the ActivityPub protocol to support mundane things like images and polls in their own way while images and polls from other instances wouldn’t load properly and would be in a green bubble.

This is normal. Servers discover each other’s accounts / communities when one a user from one server subscribes to the community to another server.

In this case you might be the first person from infosec to subscribe to sverige on helvetet.

There’s also relays to help with discovery but I’m not sure they are yet implemented on Lemmy.

Thank god. I was thinking of getting one for a long time.

Thank you, that makes sense. My biggest concern here is that “Active” often shows posts that are several days old when new content is already available.

It is possible, but it’s really no different than having two competing or complimentary subreddits.

From a users perspective you can subscribe to both !technology@lemmy.ml and !technology!technology@beehaw.org

And interact with them regardless of your own home instance.

Good point!

Check out kbin.pub, it’s like lemmy but supports microblogs (mastodon-like). It’s not yet fully federated with Lemmy but will try to. I’m not a user though, just found about it today.

That is how it was at reddit during/before/relatively after the digg exodus.

Can you create communities in remote instances?

This is a genius idea. Imagine all app developers get together and once reddit stops working they ALL from their app’s interfaces recommend switching to a lemmy instance, and mention that lemmy will be supported on their app in near future.

This could be a massive blow to reddit since the traffic these apps contribute to is huge.

Yes, this is exactly the use case I was talking about. If only instance admins can block whole instances, then there’s a perverse incentive to pressure admins into outright banning instances that users disagree with but are not necessarily bad for everyone… especially divisive topics such as politics.

It’s much better for an instance admin to let users know they can ban the instance themselves instead of having to fragment federation.