this post was submitted on 29 Nov 2023
6 points (71.4% liked)

Fediverser Network

53 readers
1 users here now

Fediverser is a project to build all the required tools to help people leave legacy social networks and to join the fediverse. Currently, it provides a web application that runs alongside a traditional Lemmy service to provide the following functionality:

The Fediverser Network is a website that aims to crowdsource the information used by the different fediverser deployments and to coordinate all users and instance admins.

founded 1 year ago
MODERATORS
rglullis
6
Suggestion: prioritize topic-based instances as the recommended lemmy communities. (self.fediverser_network)
submitted 1 year ago by rglullis to c/fediverser_network
7 comments fedilink hide all child comments
 

When building out the database of recommended Lemmy communities, I think it makes the most sense to prioritize the communities that belong to instances focused on a specific topic over communities that are based in a "general" instance, even if currently the community is smaller in the topic-specific instance.

For example, for an user coming from reddit and signing up via a "fediversed" instance (like alien.top) it would make more sense if they see that the anime subreddits are on ani.social, the rpg/board games are on ttrpg.network, the programming communities are on programming.dev, the basketball ones are on nba.space, the NSFW communities are on lemmynsfw, etc, etc...

This will also avoid the issue that I am currently seeing where some communities have multiple entries in the recommended database due to the initial migration where each user was just trying to replicate their favorite subreddits in their own server they signed up for.

you are viewing a single comment's thread
view the rest of the comments
[–] imaqtpie@sh.itjust.works 3 points 1 year ago (1 children)

I misspoke, what I meant was that smaller instances are more likely to have issues, and almost all of the large instances are general purpose.

Also, I believe it would be healthier to federation if we had a cleaner separation between “servers that are for communities” and “servers that are home to the end people”. [...] It’s also a lot easier to say “we will block instance X because of their communities” then to say “we will block instance Y because we don’t like some of the people there”, which leads to some people getting caught in a cross-fire.

I totally agree and I think the model you are describing is the natural evolution of this platform. Lemmy.myserv.one is a good example of a server that doesn't host local content but simply hosts user accounts for browsing the wider threadiverse. Striving towards that ideal is definitely a worthwhile goal.

However, it will take a long time to build towards that type of structure, and in the meantime we have to make the most of the current, largely haphazard scattering of servers/communities. I would just emphasize that the priority should be that recommended communities are (1) active, (2) well-moderated, (3) on topic. If those three criteria are met by multiple communities, then by all means, prioritize the communities on topic-specific instances. But I would caution against prioritizing other factors above the three that I mentioned.

[–] rglullis 1 points 1 year ago (1 children)

Striving towards that ideal is definitely a worthwhile goal.

I'm glad we share the same view. A lot of the work on communick is to do exactly this:

[–] imaqtpie 3 points 1 year ago

Huh, I've even got an account here and I didn't realize things worked like that. Very cool, keep up the hard work and innovation 💡