this post was submitted on 14 Jun 2023
68 points (100.0% liked)
/kbin meta
639 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
I get what you're saying -- that the link source indicator should point to the instance that hosts the group -- but it's a quirk of how federation works that the thread is actually on kbin.social. And, well, any other site that's following the thread.
Everything is actually local on the fediverse. It's just that not everything has to originate from the local website. Federation works via content mirroring, which is why the URL for any given Magazine you're viewing still starts with kbin.social. You're not viewing remote content, you're viewing local content that was imported from a remote source. And the link indicator is telling you where kbin has been told the content resides.
And that's on kbin.social.
I think maybe the link source indicator just shouldn't render if the thread doesn't have a link purposefully attached to it, and the Magazine name should show the full name@host indicator.
Cannot tell you how much I appreciate things like this and how long it's going to take me to get used to the idea of not being on a closed platform. It makes perfect sense, but it would seem to defeat the purpose of having the source there at all, like you've suggested. We know it's on kbin, that's where we are.