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.
Idea: every instance should have a community called "discovery" where admins post their instance's communities or recommendations
In the absence of relays it should be trivial for instance admins to follow each other's "discovery" community.
Only admins would be allowed to post to that community and they should publish a post on a weekly basis so that new servers who've just subscribed to their discovery community can fetch the post and show it to their users.
The post itself would contain an updated list of that instance's communities so that users from remote instances can click on them and subscribe to them. If an instance is very large, the weekly post could contain only the recommended communities and maybe some interesting instance stats or information.
Edit: to give some context, due to the way federation works communities of instance A are only visible to users of instance B if at least one person from instance B has already subscribed to that community.
Mastodon has relays to solve the kick-starting problem. But in the absence of relays it should be fairly easy to have a single specific community that's highly discoverable and from where users select other communities that they could be interested in and thus become the first user that makes those communities visible to other users of their instance.
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.
Hello! This community is visible from lemmy.ml but not yet the rest.
Maybe it'd be useful to have a list of communities so that they can be discovered more easily.
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 implemented on Lemmy.
How windows Scandisk was dumbed Down over time to avoid "scaring the user"
This is just an example of why I created this community.
Is it just me or does filtering by "Hot" seemingly give better results than "Active"?
Active seems to order based on discussion length while hot lets you discover newer content that's also popular.
I changed my default settings to hot, since it seems to be better for discovery.
That is how it was at reddit during/before/relatively after the digg exodus.
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.
How can I, as a regular user, block certain remote instances?
Hello, I'm considering hosting my own instance of Lemmy but it is crucial that users are allowed to block remote instances, not just individual communities.
This is because some of our members will want nothing to do with politics, while others will love it. And even within those who enjoy politics, some are really left leaning while others are more moderate.
In order not to stress out the moderators, it's crucial that we give each user the ability to block things on their own, instead of demanding from the staff that we ban X, Y or Z for everyone.
I haven't been able to see that feature in this flagship instance. Is that something that is possible or has been considered for future implementation?
Thank you!