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

36 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

[-] 34@kbin.social 1 points 1 year ago

I agree I got tricked by a similar post today. IMO either we need to train ourselves to add full context to titles or maybe distinguish federated content someway such as different theming.

this post was submitted on 14 Jun 2023

35 points (100.0% liked)

/kbin meta

39 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