Cougar Now • 100%
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.
Cougar Now • 100%
Cougar Now • 100%
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...
Cougar Now • 100%
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.
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.
Cougar Now • 96%
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.
Cougar Now • 100%
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.
This is just an example of why I created this community.
Cougar Now • 100%
Thank god. I was thinking of getting one for a long time.
Cougar Now • 100%
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.
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.
Cougar Now • 100%
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.
Cougar Now • 100%
Good point!
Cougar Now • 100%
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.
Cougar Now • 100%
That is how it was at reddit during/before/relatively after the digg exodus.
Cougar Now • 100%
Does anyone know if there's plans for Lemmy to support reading and posting to the larger microblogging fediverse? (similar to how kbin allows you to).
Cougar Now • 100%
Can you create communities in remote instances?
Cougar Now • 100%
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.
Cougar Now • 100%
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.
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!