/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

175

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

submitted 1 year ago by [email protected] to c/[email protected]

48 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 [email protected]? Or would you prefer another solution?

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

[–] [email protected] 10 points 1 year ago (1 children)

Seeing this from the Jerboa app on Android, the instance source is very clear on the post. Posts from my instance don't have the @instance attached so that's how I know.

[–] Kyoyeou 1 points 1 year ago

Although I didn't know we were going to be able to see each other today (hello peeps! Pleasure to meet you) and I thought I was on a Lemmy Instance talking about what they are doing on Kbin