this post was submitted on 12 Aug 2021
30 points (91.7% liked)
Fediverse
18200 readers
35 users here now
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of "federation" and "universe".
Getting started on Fediverse;
- What is the fediverse?
- Fediverse Platforms
- How to run your own community
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The link posted (if it has it) does not disappear from the internet. The data attached to the post does, but the same would happen if you delete a community in a meta-community, any related data to the post would disappear too. If the post is not a link then that's something that would not be comparable because the one limit that meta-community imposes is that all posts should be links to communities, by its very definition it is a community that has that constraint, so if your point is that it's different from communities without that constraint, then sure.
But let's agree to disagree. The fact that you later acknowledge that a meta-community can have community-like features shows you understand what I meant. You are discussing semantics of a concept that I made up, this direction is not bringing us anywhere useful.
Only if you compare it to a website where users need to register on the instance where the community is going. But you can have a network of instances that do not ask people to register on them and that rely on a common authentication method provided by a third service (which can also be decentralized). So they share users without the community hosters having to federate between themselves.
I already mentioned decentralized sharing of user accounts/sessions between non-federated instances. I mentioned it in at least two of my responses to your comments in this thread already.
As mentioned before, you can do this without federating between instances. In fact every user can be remote (ie. its account hosted in a third party service), no need to have any instance be the "owner" of any accounts. You can have user accounts managed by a separate service (similar as how it's done in OpenID) with no need for communication between the instances that host the content. In fact this gives much more freedom to self-host your own account and does not have the problems of instances needing whitelisting to prevent caching/hosting content they don't want.
I said "useful/used". So you could also say "used" (ie.. people actually use it, it's not abandoned). And in a sentence after that I used also the term "active".
No.
Meta-communities
Sorry, but I am still trying. What you first said is that a multireddit can be seen as a meta-community, which I didn't understand because the only similarity I see (between multi and community) is that there is somehow a list involved. Were you really talking about multireddits or are you building a concept of metacommunity around it but more similar to a community in some way ? (justifying the comparison)
So the way the content is added is the one of a multireddit, not a community.
And so is the content.
So to me it seems that your concept of metacommunity is identical to the one of multireddit rather than something you are making up. Please correct me if that's wrong and explain how it's different, that's exactly the thing I'm trying to understand with this discussion.
So, if what I said above is correct, what you are doing is stripping a post of its body, title, community, comments down to a link, so that the community (now a mere list of links) can fit the comparison with a multireddit.
Federation
You need to federate the instances where the users are. Now Lemmy has only one kind of instance, for both communities and users. You propose a model where there are two (user-instance and community-instance), that's interesting.
Community-instances would still be able to accept or reject the communities that they host, and that is not really about federation.
On the other hand, user-instances and community-instances would still be able to accept or reject each other.
Ok but communities about any kind of niche topic can be active, all you need is at least 2 users ready to publicly and regularly communicate with each other. In particular, being active does not require thousands of users, so is not bound to the big topics who already have pages on lemmy.ml.
Meta-community definition
You also cant add it to a meta-community, "the content" that is added is community links, not posts. Remember, that's the main difference between meta-community and community. When you want to post something that isn't a new community, you don't post to the meta-community, you post to a community.
If you just make a community where every post is a link to a community (which in theory you can even do right now without any code changes, as long as you moderate it to be so), then conceptually you have already the data model of a meta-community. And doing this does not necessarily stop you from having moderation, comments, and everythign a community has (because it is a community, just one where each post references a community).
But of course to make it useful as a feed, you need to add a new interface where you can see an aggregate of the posts of the communities referenced (because the posts of the meta-community would be just references to communities). And a way for users to subscribe to that aggregate instead of (or in addition to?) the aggregate of references to communities.
However, this last thing is just a different "view". Meta-community mods do not actively "manage" the posts/comments in that view (because it's not posts/comments from their community), they only manage the posts/comments in their (meta)community (in which posts happen to be references to communities whose posts show in that "view").
Multireddits are just a particular case of "meta-community" (one that does not allow user submissions or comments and has only one admin who submits/deletes entries, which is fine since the thing that makes it worth it is the aggregation of subreddits).
We are still discussing semantics on a particular made-up definition involving small details that don't necessarily matter that much, imho. I don't think we are going anywhere.
Federation
Well yes, but that's not related to instance whitelisting, plus it's a restriction totally valid.
Instances should not be forced to host content they don't want to host. Imagine if a community is about sharing ilegal content (copyright-infringing stuff, child pornography, etc.) the instance could be held responsible if it knowingly hosts that content publicly and does not delete it, even if it was uploaded by other people.
This would be comparable to lemmy.ml accepting/rejecting accounts based on whether the account email is hosted in "gmail.com", "hotmail.com" or whichever other third party service.
It's true that user-instances and community-instances can block each other, but I think it's less likely. I think whitelisting makes sense when instances have to serve or cache content from other instances, something lemmy does in order to federate. But if we stop federating and let clients access multiple instances directly (instead of each user accessing only one instance to access others through federation) then no instance has to serve content from instances that have content they dont want (or content that's ilegal). They'll no longer be responsible for the content from instances they federate with since it's no longer offered through your instance. The user-instances in my example also do not serve content from other instances, so they are also very unlikely to see a need to block anyone.
Also note how the blocking in lemmy is not transitive (if A blocks B but not C, you still can access both A and B through C), this shows they are ok with people going to other instances that migth be more permissive in their allowlist, while still allowing those users to federate with lemmy. I suspect the primary reason for the whitelisting is to avoid actively participating in the distribution of content they don't agree with.
Even if you really want to consider that level of activity (which shouldn't really be significant when we are talking about communities that become centralized nodes on a topic for the entire network). The point was that the number of active topics is limited. Those 2 users can't be active in an infinite amount of topics. At the end of the day the number of active topics is limited by the user engagement. And looking at reddit's numbers, we can see that in a mature social network there's much less active topics than active users (over a thousand times less!).
Remember the reason we talked about this: if you don't duplicate communities then the fact that the amount of popular active topics is limited can lead to huge centralized nodes forming around the active communities.
Sure, but I never said lemmy.ml is the only instance that has active communities. I'm saying it's where most of them are.
Ok so you do mean to incluse user submissions and comments, thanks ! That was not clear to me.
Now, if the idea is really to base the meta on a community, how is its list of communities established? I see two sensible options :
The admin can (un)pins posts, the links of the pinned post make up the list.
A upvote threshold decides which links are on the list. That way it's really community driven.
Great! ...but just in case there's a misunderstanding: remember submissions in a meta-community are communities. We are not talking about posts with links/articles. In the same way, comments in a meta-community would be comments in relation to that submission (the submission linking a community, not a submission linking an url/article).
Each posted link/article from a submitted community in the metacommunity already has its own comment thread, which is independent of the meta-community existance and is already in the community the posted link/article belongs to. As discussed before, meta-communities have no authority over that.
I don't necessarily think meta-communities need to allow user submissions (which would be communities) or comments (which would be on community submissions) to be useful. That's why I didn't see much point in discussing in this direction.
I just pointed out that they can have it (because you asked for it before).
Personally I think it should be possible to customize in each community which users are allowed to post/comment (if at all). I believe "private" communities is a planned feature too.
I feel we are still not understanding each other.
Note that one thing is "the submissions of the meta-community" (which each will be a reference to a community) and a different thing is "the submissions of the communities that are submitted to the meta-community" (which before I called "posts".. or to be more specific: urls/articles).
The former is moderated by the admins/mods in the meta-community. The latter is moderated by the admins/mods in the respective communities where the posts reside.
I imagine there would be 2 "views". One that shows the list of communities in the meta-community (and optionally allows users to submit a new community and comment on those submissions) and another that shows the aggregated posts of the communities that have been submitted to the meta-community.
For this latter "aggregated view of the submissions of the submitted communities", if you wanted to add additional control on what shows there then I guess you could have ways to add "weights" to each community. Maybe, for example, a combination of the number of upvotes to the meta-community submission for that community and the number of upvotes to the submission in the community submitted could be used to decide the order in which the posts show in the aggregate. You could also factor in things like number of subscribers if needed... that kind of detail on how urls/articles are aggregated is something that would require some experimentation to get right.
I think I pretty much inderstand you now. The point of my 2-item list was to draw a line between "communities submitted to the meta community" (which I also referred to as post in that part), and the ones who are actually part of the meta. I was thinking "cutoff" rather than "weight for appearance in the feed", but the latter is also interesting !