/kbin meta

110 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

166

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

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

46 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] 14 points 1 year ago (1 children)

I mean, there'll always be way to see that. It's just not obvious at first glance. But even on Kbin, the URL of the thread you're in will have the instance after the @ sign.

My point is that we don't need to make this a dick-measuring contest between instances. If the fediverse grows and gets better, we all win.

[–] [email protected] 18 points 1 year ago

When fascists (including tankies) run instances, they purge people who disagree with them, just as in "real life" - so instances run by fascists and tankies are going to be full of fascists and tankies.

If kbin is drowned out and perma-brigaded by tankies then the tankies win, but everyone else loses.

If you're going to federate with fascists and tankies, it always matters to have that context front and center: "this thread/message comes directly from fascist/tankie central"