• 4 Posts
  • 87 Comments
Joined 1 year ago
cake
Cake day: July 13th, 2023

help-circle














  • I think one thing you’re missing here is that under such a system the defaults would likely become your locally hosted /c/books rather than the largest one. Even still you’d probably see posts from the largest books communities because /c/books@your_instance follows multiple /c/books@big_instance. Community blocking would likely still work as it currently does so any books communities that you were not fond of could still be blocked.

    There is still the issue of where do you post and I think the answer looks something like:

    • Post in /c/books@your_instance if you want to talk to your neighbors
    • Post in /c/books@big_instances if you want to talk to everybody

    Which is more or less how most people would decide where to post book stuff anyway.






  • I think the major advantage with this model is that it gives those local communities a little more flavor while allowing the same functionality as the large communities (probably a good place to apply scaled sort). It also allows for a sort of curated multi-reddit functionality. Most importantly, it seems flexible and generalizable enough to allow for building advanced group features on all platforms, while still advancing the goal of inter-operability. A more straightforward multi-community functionality or the OP solution would have a lot of unanswered questions regarding federation. I’d be curious to see how kbin does it and whether that federates well. All that said, I think a lot of communities probably should be looking at negotiating a merge.