this post was submitted on 03 Jul 2023
142 points (100.0% liked)

Technology

37638 readers
26 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

I changed the url of the post to be the beehaw link to community for easy sign up.


cross-posted from: https://lemm.ee/post/605147

cross-posted from: https://lemmy.world/post/978235

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

General discussion about devices is welcome. Please direct technical support, upgrade questions, buy/sell, app recommendations, and carrier-related issues to other communities. Join Here: !android@lemdro.id https://lemdro.id/c/android

you are viewing a single comment's thread
view the rest of the comments
[–] esaru 2 points 1 year ago (1 children)

I hear you, but you can't have the positive effects of decentralization and want everyone on one platform. Also consider that a community of a few thousand members for a specific topic should be big enough for fruitful discussions, so a group of 1 Mio can easily split to a few sub groups without negative effects.

[–] fisk 3 points 1 year ago

I think you're not entirely understanding what I'm saying - which is definitely not requiring everyone to be on the same platform.

Instead, what I'm suggesting is to give users control over meta-communities, just as admins have control over instances, and mods have control over communities. This would require that meta-communities could be built by individual users, ideally in a way that they could be shared (but still individually managed) much like a Spotify playlist or GitHub. Users could build their own meta-communities, or "subscribe" to meta-communities curated and shared by others. Additional QoL improvements would be the ability to check a meta-community to determine if a specific user could access/engage with that community, hence the package manager thing.

In this kind of framework, the broader Fediverse resists echo chambers and fosters diversity by allowing for the creation of instanced communities, while allowing users to determine how posts from those communities are organized and displayed.

If the Fediverse is taking a stance on the number of instanced communities that an individual should be able to read or participate in, why not make that explicit rather than creating these knee-high barriers?