this post was submitted on 23 Jun 2023
72 points (100.0% liked)

/kbin meta

4 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] stoneparchment@possumpat.io 1 points 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.