this post was submitted on 14 Jun 2023
166 points (100.0% liked)
/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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
No. When I see a post called “we are shutting down” I want to know what instance that post is talking about. It should definitely show the full federated magazine address
I agree with this. Context is important and it should be clear.
Not gonna lie, I've just had a look at the feed just now and it's becoming noisy. It would be nice to not have to sift through so much chaff to find wheat.
I know there's strong feelings about curated feeds around here but it should be up to the user to decide what they see for the most part. At least, they should be able to decide what they don't see.
Isn't that the nature of social networks, though xD
You can always turn off federation by going into your Kbin sidebar and clicking on the little triangle icon, next to the settings.
Or you can go to https://kbin.social/sub, to view the equivalent of your Reddit home page (i.e. with the communities you're subscribed to). https://kbin.social/ is more like r/all, where you'll see stuff from your subscriptions, plus other random stuff.
Or just block mags/bins/communities you don't care about. Just got rid of one today and now I won't see it on my all feed again.
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.
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"
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.
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?
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.
And neither works on mobile. So we're back to needing the information to be more accessible
An interesting take that I hadn’t considered. I still wish I had the option to toggle on/off the original source for the user and the magazine/community.
It’s also good because it makes the experience easier when a new user onboards. IMHO, there should be a system in place to discourage someone from creating a community that exists on a different instance. This encourages people to coalesce into groups quicker, and if someone ever abuses that group, people always have the option to just…move on to another instance
I agree. It's still interesting to see the source, but I personally do not want it to be too visible. There are of course some cases where it would be handy (like threads about fediverse since it is not always obvious what instances are concerned by the topic), but I have the feeling it is an issue specific to some magazines, and any change regarding this shouldn't impact too much all the others.