this post was submitted on 18 Jun 2023
6 points (100.0% liked)
/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 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
it should be where the magazine is from, not where the user is from.
While I'm not entirely sure about why things are set up the way they are, I guess that it was done on purpose seeing your response. Now, if explaining the why's and how's of this design is too much of a sensitive topic, I'm okay with dropping my questions and just going along with the ride ๐.
If it's possible as a compromise, how about consider displaying both "the origin of the magazine" (instance) and the "name of the magazine", rather than the existing format where kbin.social appears after the title, followed by just the "name of the magazine" (omitting the original instance from which it hails).
For example, the current layout is:
TITLE
(kbin.social)
PREVIEW OF BODY TEXT
USER
, 33 minutes ago toNAME_OF_MAGAZINE_WITHOUT_ORIGINAL_INSTANCE
(likemeta
)My suggestion is to include an option for displaying it like this (I do understand that it might be a clutter to some, but it would be a nice feature for others facing the same qualms as I do):
TITLE
(kbin.social)
PREVIEW OF BODY TEXT
USER
, 33 minutes ago toNAME_OF_MAGAZINE_WITH_ORIGINAL_INSTANCE
(like META@LEMMY.ML)To provide some context, I came across a post on either
main
ormeta
on the front page. It hadkbin.social
listed below the title along with the "name of the magazine," but the original instance name was missing. I was about to express my confusion since it didn't align with my experience on kbin.social, but upon double-checking the URL, I realized the post was not related to kbin.social at all. This "issue" generated by the behavior seems to mainly affect mags likemain
andmeta
posts, but considering these posts do often appear on the front page (since I've enabled other instances todiscover
more exciting content), I think that it's issue worth exploring.Hopefully in the meantime, I've figured better ways to work around this issue (to verify the instance of the magazine) on mobile ( apart from checking the address bar), which are to