this post was submitted on 14 Jun 2023
32 points (100.0% liked)
/kbin meta
25 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 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Indeed, pretty cool!
First thing I noticed though is that I'd really like to know which instance a thread is actually on.
For example, this post:
Going back to Reddit feels bad (kbin.social)
polygon, 2 hours ago to chat
... is actually on chat@beehaw.org, even though it says "kbin.social" and just "chat" below. Pretty confusing.
EDIT:
There's at least one fix for this in the meantime -- get this userscript:
https://greasyfork.org/en/scripts/468612-kbin-enhancement-script
Threads are hosted on the instance that the magazine is on. I think instances viewing it also just make a copy?
You can check the @ to see the url for both users and magazines. I'm not fond of the fact that kbin often hides the @url for things. I'd much prefer to see it since it makes things feel bigger to me. @.chat@beehaw.org just ends up being shortened to @.chat lol. see? @chat @chat they are identical lmao. it's annoying.
Also: I think usernames from other instances should show which instance they're from.
Yes the full username@instance for all remote users at a minimum would be good
you can see this if you hover over their name. but it's not displayed by default. It'd be nice to have an option to have it written out rather than hidden.
There is a userscript for this now! Works a treat!
https://greasyfork.org/en/scripts/468612-kbin-enhancement-script
I think it'd make the comments a little cluttered looking. It doesn't really matter what instance someone is from for regular conversation and if someone's curious the can click through to the persons profile
It should be an option. Some people prefer the "clean" version of just showing username, with needing action to see url. while others prefer seeing the entire username+url even if it's "messy". I'd prefer the latter, while others might prefer the former. It should be a toggleable option.
I think appending it to the username would be slightly messier for me, but for unexplainable brain reasons I seem to want to have this feature as well. Maybe if we stuck the instance below their avatar instead?? In any case, it would still be appreciated on articles
Yeah, whatever ui to show it i'm fine with as long as i don't need to hover over every name to see it lol. whether it's just added to the end like how tagging works, or if it's shown underneath or something is fine too.
I was thinking it should be included to avoid casual impersonation. I agree it would be a lop more cluttered though; maybe there's another way.
I mean - on the desktop site at least, I can just hover over someone's name and see what instance they are on.
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.