• 0 Posts
  • 2 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle
  • Your points are valid, but that doesn’t mean we should do nothing. Enforcing federation and using copyleft licensing are both strong defenses against centralization and network dominance by a well funded third party.

    As far as GPL goes, from what I’ve seen, big tech companies tend to take it pretty seriously. There is no reason we shouldn’t be using that, and other license protections if we have the option.

    As for natural centralization over time, I think that is a far less urgent problem than the current risks we are facing, those being major network fragmentation due to the use of defederation, and the risk of centralization around a proprietary platform and/or instance.

    Removal of defederation and strong copyleft licensing seem to be natural first steps in combatting that risk.


  • Seems like just another reason why defederation should be completely removed from the protocol. It’s way too easy to abuse and force centralisation.

    There are other far less destructive and abusable ways of dealing with spam and content moderation.

    I maintain that it’s better to give the users the control, and allow them to decide which instances, communities, and users they want to be exposed to. Bottom up moderation, instead of top down.

    For example, instances can provide suggested ‘block’ lists (much like how an ad blocker works) and users can decide whether or not to apply those lists at their own discretion.

    By forcing federation, the network stays decentralized. Maintaining community blacklists that can be turned on or off by the individual user protects against heavy handed moderation and censorship, whilst also protecting users from being exposed to undesirable content.