I’m seeing discussions on other instances about how a “federated” corporate instance should be handled, i.e. Meta, or really any major company.

What would kbin.social’s stance be towards federating/defederating with a Meta instance?

Or what should that stance be?

  • Ragnell@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    This is why the big threat is Meta, because they are a tech company. I think any instances spun up by Silicon Valley should be blocked preemptively, but other corpora can have a probationary period.

    • Kichae@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Honestly, it Meta spun up a Mastodon site to host Meta employees and just have a corporate presence, the way they might have a Twitter account, that wouldn’t be an issue at all.

      The issue is that they’re arriving as platform developers, not social participants. And that’s their business.

      We should be super suspicious of people showing up to sell the Fediverse, because you can’t profit off of community. Community costs money, not generates it. To generate money, you need to exploit people, and exploitation is anti-social. Anti-community.