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. !android@lemdro.id [/c/android@lemdro.id] #### Rules 1. Stay
on topic: All posts should be related to the Android operating system or
ecosystem. 2. No support questions/rants/bug reports: All posts should benefit
the community rather than the individual. Please refrain from posting individual
support questions, rants, or bug reports. 3. Describe images/videos: Please
provide an explanation in the self-post body when sharing images or videos.
Memes are not allowed. 4. No self-promotional spam: Only active members of the
community can post their apps, and they must participate in comments. Please do
not post your own website, YouTube, or blog. 5. No reposts/rehosted content:
Submit original sources whenever possible, unless the content is not available
in English. Reposts about the same content are not allowed. 6. No editorializing
titles: Do not change article titles when submitting. You may add the author if
relevant. 7. No piracy: Do not share or discuss pirated content. 8. No
unauthorized polls/bots/giveaways: Do not create unauthorized polls, use bots,
or organize giveaways without proper authorization. 9. No offensive/low-effort
content: Avoid posting offensive or low-effort content that does not contribute
positively to the community. 10. No affiliate links: Posting affiliate links is
not allowed. ##### Elsewhere + Telegram [https://t.me/+1NN0EVuXK3sxMTQ0] +
Reddit [https://reddit.com/r/android]
I changed the url of the post to be the beehaw link to community for easy sign up.
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.idhttps://lemdro.id/c/android
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.
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?
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.
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?