/kbin meta

4 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

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

14 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

[–] jclinares@kbin.social 1 points 1 year ago (8 children)

That's a feature, not a bug. If you find a worthwhile discussion, and have something to bring to it, just do it. No need to marry yourself to just the one instance. That's the beauty of federation, really.

[–] dandan@kbin.social 1 points 1 year ago (2 children)

I appreciate the point you are making, but here's a solid example of how it gets confusing.

ANNOUNCEMENT: defederating effective immediately from lemmy.world and sh.itjust.works

Who is defederating?

[–] jclinares@kbin.social 0 points 1 year ago (1 children)

What I'd do is hover over the OPs name, or go into the post and check the URL. Yeah, it's different than what you're probably used to, but so is any new platform. It just takes some time to get familiar with it.

[–] parrot-party@kbin.social 1 points 1 year ago

And neither works on mobile. So we're back to needing the information to be more accessible

load more comments (5 replies)