this post was submitted on 10 Sep 2023
5 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
Interesting, I've heard people say the same before. I do always sort by newest myself, but I sub to a bunch of magazines and also, say, three mastodon accounts, and that page is basically just solely the mastodon posts, very rarely do I see microblog posts in lemmy/kbin. I guess a filter of magazines vs users would be useful
Edit: Also, is the default view all time for you? I could see that causing a problem as well if it's hot / all time. I mainly have three bookmarks:
/hot/12h
,/sub/newest/24h
,/sub/microblog/newest/1d
. Getting all results for all of time by default seemed a bit weird to me, especially for microblog postsThe default view appears to be hot, but changing to new does not do much (is there an actual difference between sorting new/x and new/y? Specifying a time frame for new sorting seems kinda pointless).
I think the issue here is probably that I'm subbed to a magazine that has set up a fairly common hashtag (#opensource) for its microblog, so it naturally pulls in a lot.
Definitely, you're right that new timeframe doesn't matter, I meant to type hot all time xD I would expect that to potentially grab like whatever was boosted most in the past but then again the algorithm does tend to show newer things even under hot.
Yea the tag system might need a bit of work. It works great for some magazines, but for others not so much. For example m/help is supposed to be a magazine for kbin help but it pulls in everything under #help which can be anything in the fediverse. I did see someone suggest a way for a magazine to remove it defaulting to using the tag of its name, which doesn't seem like a bad idea to me
In hindsight I remember why I filter newest to a timespan, so wanted to make note of it. Right now:
https://fedia.io/m/kbinMeta@kbin.social/microblog/newest 500s for me but
https://fedia.io/m/kbinMeta@kbin.social/microblog/newest/1w is able to load. so cutting off some of the older posts helps me run into less 500 issues, and I generally don't care too much about old posts unless I'm searching for something. that might be a fedia specific thing though, not sure how 500s are on other instances