/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

[–] Gull@kbin.social 6 points 1 year ago

It matters. For example, if Stormfront runs an instance, that instance will be full of Nazis. There's no way they will tolerate anybody else there. Ergo, if you know someone is from the Stormfront instance, you know they're either a Nazi or they're lost and so clueless that they don't realize what all the funny crosses mean.

Stormfront people (again, this is an example) will then sic their userbase on any thread about Judaism. They will intentionally exploit the confusion created by lack of context. They will create threads which users don't realize are transferring them from the world of ordinary humans into the Nazi dimension, where they will be confused and bewildered by the fact that suddenly 80% of their online peers are expressing the kinds of views that are expressed by a Stormfront denizen.

The same will be true when NazBols run an instance and it is already true of the pro-genocide tankies that kbin is already federated with.