122
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Jun 2023
122 points (100.0% liked)
Technology
37727 readers
636 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
The main goal of these sites is link aggregation. It wouldn't be overly difficult for a federated server with its own /c/Technology community to see other posts from other communities linking to the same thing and combining the discussions into a single view.
The tricky part there is moderation, but even that's manageable by allowing moderators to remove content from a federated view within their own instance, it'll just be difficult when a small instance is dwarfed by a larger one.
I don't think of the threadiverse as a link aggregation platform but as a network of communities engaging in threaded discussion. The federated model is an answer to the problem of platform lock-in, the network effect, and the lack of autonomy communities have on proprietary/commercial/centralised platforms.
Each instance separately may fill the role of link aggregator but mainly for that community (instance), with that community's values and moderation policies. The ability for an instance to federate with other instances with compatible policies is the benefit here.
It may actually help if you view an instance as the community, with its "communities" as its topics.