/kbin meta

4 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

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

14 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

[–] jclinares@kbin.social 1 points 1 year ago (2 children)

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.

[–] Jakeypoo@kbin.social 1 points 1 year ago (2 children)

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

[–] roving6478@kbin.social 1 points 1 year ago (1 children)

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.

[–] jclinares@kbin.social 1 points 1 year ago (1 children)

It would be nice to not have to sift through so much chaff to find wheat

Isn't that the nature of social networks, though xD

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.

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.

[–] CH3DD4R_G0B-L1N@kbin.social 1 points 1 year ago

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.

[–] jclinares@kbin.social 1 points 1 year ago

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.

[–] dandan@kbin.social 1 points 1 year ago (1 children)

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?

[–] jclinares@kbin.social 0 points 1 year ago (1 children)

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.

[–] parrot-party@kbin.social 1 points 1 year ago

And neither works on mobile. So we're back to needing the information to be more accessible