Now that federation works, we need more clarity of source (kbin.social)

submitted 1 year ago by parrot-party@kbin.social to c/kbinMeta@kbin.social

32 comments fedilink hide all child comments

I'm seeing the federated content, but it's hard to tell where the content came from. Currently, the only reliable way to see the source is by reading the URL when you're viewing a thread. It doesn't work well on mobile though and it doesn't work for the feed.

How work everyone feel if the magazine included the source always? So instead of saying kbinMeta, you'd see kbinMeta@kbin.social? Or would you prefer another solution?

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

[-] Nugget_in_biscuit@kbin.social 2 points 1 year ago

It’s also good because it makes the experience easier when a new user onboards. IMHO, there should be a system in place to discourage someone from creating a community that exists on a different instance. This encourages people to coalesce into groups quicker, and if someone ever abuses that group, people always have the option to just…move on to another instance

this post was submitted on 14 Jun 2023

28 points (100.0% liked)

/kbin meta

38 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