Implementing Groups and Topics

[thomastthai]

What interests are there in implementing groups and topics? To me, they are similar in classification structure and would reuse the same codes.

Users can subscribe to groups they want to be a part of. Messages to a group would appear on the timeline of subscribers. Groups can have names in the format of &group-name. A user can set a group to be an active group or the global group. New messages will default to that group.

Similarly, users can subscribe to a topic. A topic is similar to a subreddit or sub-topic in a forum. A topic name would have a format of !topic-name.

The main difference between a group and a topic is, that in a group, users discuss any topic of interest to the group based on the group's preferences. In a topic, discussions are focused on that specific topic among participants.

Users could have different admin rights in topics and/or groups.

If there isn't any interest in the above, feel free to make suggestions about how I should implement them to align with how Nakama is coded in case there is a desire for pull requests in the future.

[nicolasparada]

From my part I'm interested in having groups/communities mostly so users can create their own managed space with their own moderation/rules.

It's not a feature that has been requested too much by the current users of nakama.social.
But definitely worth exploring.

[thomastthai]

Thanks @nicolasparada. The user size at nakama.social is still small so the requests may be minimal. Additionally, nakama.social is already in a niche category. Scale the user size up to a million or more for a more general platform, communities will start to form and the requests will surely come.

[nicolasparada]

Probably, yes.