/kbin meta

200 readers

2 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

Could we get official word on what Kbin's stance is towards federating with Meta? (kbin.social)

submitted 1 year ago by Roundcat@kbin.social to c/kbinMeta@kbin.social

115 comments fedilink hide all child comments

I would like to know if I can feel safe here, or if I should pack it up and start looking elsewhere sooner rather than later.

If the kbin staff have already made there intentions clear, please let me know.

you are viewing a single comment's thread
view the rest of the comments

[–] stevecrox@kbin.social 1 points 1 year ago* (last edited 1 year ago)

Why would KBin be unsafe?

Federation works by instances (e.g. kbin.social) registering an interest (subscribe/follow) in a specific magazine or person on other instances.

That means content is only brought into an instance that members of that instance are interested in (its the same with lemmy instances, we don't see everything).

Similarly on kbin users can block individuals, magazines or whole domains. So even if kbin.social does federate with meta you don't have to see/interact with it.

For instance I respect kbin users might want content from lemmy.ml, as the people who run it are tankies I have no interest in anything from that instance and block the domain.

I have no issues with part of the fediverse walling itself off from meta but remaining in contact with other instances. Similar to how beehaw defederated from lemmy.world but kbin could see beehaw and lemmy.world.

I would treat meta like any other instance, if its a source of headache then deferate.

The Embrace, Extend Extinguish argument makes no sense.

Take C#, many years ago Microsoft wanted to build its own Java JDK. As part of that they added Microsoft specific extensions. Sun said that wasn't acceptable. Microsoft didn't just stop, the renamed it C# and launched the product.

Everyone agreeing to defederate from meta won't mean they stop. It won't prevent EEE.

The best way to prevent EEE is given in our example. Java had a huge userbase who simply weren't interested in migrating.

So you need to encourage organisations to deploy KBin/Lemmy instances which integrate with the fediverse. That gives them reach and when Meta tries EEE they cut off content their users want. So it forces them to be a good citizen.