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?

  • stoneparchment@possumpat.io
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Are you familiar with the embrace, extend, extinguish process referenced by the top commenter? Just wondering if this comment is made with understanding of that process.

    Personally, I don’t want Meta’s money and army of paid developers to be able to make “surface level” improvements that incentivize non-technical users to join their instance, while hiding an increasingly hostile and profit-driven framework underneath.

    Here’s a blog post passed around a lot today on the issue. I’m not totally sold one way or another, so if you have insight I’d love to learn more.