/kbin meta

16 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 2 years ago

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

43 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

[–] DreamyDolphin@kbin.social 2 points 1 year ago

From my new-and-limited understanding, it can potentially be an issue if similarly- or identically-named instances are on different servers - someone over on Lemmy noted that the mod of lgbt is also the mod of conservative. If you don't know a post is from X@kbin or X@lemmy that could be a source of confusion depending on the quality of the different source-communities.

In the grand scheme of things, presumably whichever one is the more user-friendly will get the audience share and the other would wither away to the footnotes of history, but it's still a potential issue in the meantime. Happy to be corrected if I'm mistaken on all this, still very much a beginner here.