this post was submitted on 19 Jun 2023
3 points (100.0% liked)
/kbin meta
25 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 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Honestly, I think that a big part of the problem is that the best way to currently find a new lemmy or kbin instance to register at is to browse the fediverse observer site, and while that does a decent job of finding a geographically-near place, it does not make the instance's policies particularly easy to find. In some cases (take, say, beehaw) those policies may be rather different from what some users are expecting.
Also, specifically for lemmy and kbin, while one can get a list of lemmy or kbin instances, unlike with most of the Fediverse packages, they don't currently actually have a link to kbin.fediverse.observer or lemmy.fediverse.observer from fediverse.observer.
For a kbin instance, the rules for a given instance are at /terms. So for kbin.social, one can see them at:
https://kbin.social/terms
For a lemmy instance, the convention is apparently for the rules to show up in the right-hand sidebar when one browses to the web UI for the instance.
Neither is immediately-accessible when browsing through the list of instances on the fediverse observer site. Basically, the only material about the server is the language, the uptime, the user count, and whether signups are allowed (and I think the mobile version of the site only shows the uptime). That's not really enough information to help one choose an instance. Even just an IRC-chat-room-style single line of description would do a lot to help people find an instance that fits what they're looking for.