This will take place ~24 hours from now. Feel free to post and upvote questions beforehand in this post, as it will turn into the AMA tomorrow.
This is a chance for any users, admins, or developers to ask anything they’d like to myself, @nutomic@lemmy.ml , @SleeplessOne1917@lemmy.ml , or @phiresky@lemmy.ml about Lemmy, its future, and wider issues about the social media landscape today.
Thank you! Lemmy is a tremendous contribution to the wider Fediverse, and no amount of “thank yous” is ever enough for people like you writing free software and giving freely to the public domain.
I have been on Lemmy, and around the Fediverse on various accounts since ~2021, and a suggestion I have seen promoted countless times is for communities which federate across instances. e.g. posts to Linux@lemmy.ml will show on Linux@lemmy.world as long as lemmy.ml and lemmy.world federate with one another. If I remember correctly, each of you have previously opposed this idea for multiple reasons. If you do still oppose such a feature, will you please reiterate why you think this is the wrong direction for Lemmy? Also, have you considered adding a multi-community feature similar to Reddit’s multi-reddit feature which allows end-users to combine multiple federated communities into a single page just for them?
Thx!
I see why people think that’s a problem, but in reality, its more of a feature. For example, take communities named
!news, that pertain to completely different topics, or locations, based on their instance:or
These are all news communities, yet should stand on their own: each with their own set creators, moderators, users, rules, posts, comments, culture, and topics. It makes no sense to combine them given all these differences.
Sure! Multi-Communities are an open issue, that I’m sure someone will take on eventually.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !news@startrek.website
Thank you for making it clear this is a conscious design decision. I very much disagree with it. Multicommunities, like multireddit do not adress this terrible problem. I think lemmy is now doomed to repeat reddit’s mistake. Hopefully in 10-15 years the lemmy successor will see the light about this problem.
There’s also FEP-d36d which is a standard for group-to-group following. In Lemmy terms, a community could subscribe to another community.
In this case, why not merge?
I think the major advantage with this model is that it gives those local communities a little more flavor while allowing the same functionality as the large communities (probably a good place to apply scaled sort). It also allows for a sort of curated multi-reddit functionality. Most importantly, it seems flexible and generalizable enough to allow for building advanced group features on all platforms, while still advancing the goal of inter-operability. A more straightforward multi-community functionality or the OP solution would have a lot of unanswered questions regarding federation. I’d be curious to see how kbin does it and whether that federates well. All that said, I think a lot of communities probably should be looking at negotiating a merge.
I always like there are basically two types of topics (because after all, communities are focused on a topic)
I know there is the political aspect to take into account, but for me that comes back to the first point: if enough people of the same political side want to talk about something between them, that’s good. If not, they might have to put that aside and go for the second option.
Strong agree
ooooh I like it!
I think FEP-2100 is a much more promising approach because it makes communities more resilient in case an instance goes down.