this post was submitted on 14 Jun 2023
139 points (99.3% liked)

/kbin meta

639 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
139
Remember that the button at the top of the sidebar expands the options to disable federation. (media.kbin.social)
submitted 1 year ago by [email protected] to c/[email protected]
59 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 1 year ago (2 children)

2 questions for whomever has the answers

  1. Are all communities shared in the entire federation multiverse thingy..For example .. if a community was created on Kbin does that mean it’s prevented from being created on any other site so only one exists?
  2. Can I subscribe to a community that’s not hosted on Kbin and still see it and participate in it from Kbin

Gracias fellow kbinians ✨

[–] [email protected] 10 points 1 year ago (1 children)
  1. no, each server (kbin.social, fedia.io, lemmy.world, etc.) can have their own communities, since there is no centralized server that manages community names it would be impossible to track which servers already have a community with the same name
  2. yes, that's the beauty of the fediverse! this post explains how you can do that. you can also view and interact with posts from other federated social media sites such as Mastodon if you are interested in that sort of thing
[–] [email protected] 9 points 1 year ago (1 children)

It wouldn’t be impossible to track. Decentralized databases are a thing. Honestly blockchain would be useful here. Never thought I’d say that.

[–] [email protected] 4 points 1 year ago

The big issue would be to get everyone to sign up for something like that though. Since things have been running for a while without any sort of checks like that, it would be difficult to switch to that system now (do you merge communities with conflicting names, do you let them change their name, do you let them delete the community, etc.). Plus there’s the whole nature of the fediverse where every instance can be customized to the creator’s needs (so one instance might want to be on that database and others might) and it just becomes too much work to get everyone on board.

Maybe I’m wrong and someone will eventually implement something like this and people will want to use it, but I very much doubt it from what I’ve seen of the fediverse so far

[–] [email protected] 7 points 1 year ago* (last edited 1 year ago) (1 children)

Hi, I'm figuring this out too. Veterans, please feel free to correct me!

  1. If you create a community on kbin, it does not prevent a community with the same name from being created on another site. We have a 'music' community here (kbin.social/m/music), but lemmy.world has a 'music' community too (lemmy.world/c/music).

(kbin calls them /m/agazines, lemmy calls 'em /c/ommunities, if you're wondering about the 'm' vs 'c' in the URLs lol.)

  1. Yes! Because Fediverse magic, you can actually interact with the lemmy.world 'music' community without leaving kbin.social. Try it out from kbin.social/m/[email protected].

You may notice this @[object]@[place] pattern a fair bit.

For example, our own 'music' community is @[email protected]. The lemmy.world 'music' community is @[email protected]. Your account is @[email protected]. See if you can spot users or threads that are from other sites! They're probably already in front of you!

As a second experiment, see if you can visit the music community from beehaw.org, without leaving kbin.social. They have one too, but you don't need a beehaw.org account to participate there!

(This link has the answer if you have any doubts!)

[–] [email protected] 4 points 1 year ago

Yes, this is correct.

As opposed to the thinking of a lot of people, being able to have duplicate communities on each instance is a feature, not a bug. It is a very good way to give people freedom of choice if, for instance, a mod for a community on one instance is taking the community in a bad direction.