Hi @maegul, I just wanted to let you know. It's not perfect yet, but it's something I'll be working on in the coming months after the first release. Thanks for pointing it out, it's a relatively simple change, but it makes a significant difference in the overall experience.
@ernest Woah, this makes a heck of a difference. That's powerful!
I love the way that kbin gives you far more options to sort the Microblog feed than, say, Mastodon.
Most popular posts (by people I'm subscribed to) from the last week. Go. Boom!
@soweli There is certainly some truth to that, but
it gets easeir farily quickly; and
it's worth the effort! Other platforms don't give you the same power and breadth of access across the fediverse.
You'll find you get more interaction from within kbin (and also from Lemmy) if you use 'Threads' rather than 'Posts' (like this). Posts sit in the Microblog and are more aligned to Mastodon way of working - they are harder to see unless people already follow you.
So funny thing about #kbin. I post a photo thread. I go to my profile and see the thread. I click on the image preview icon. I immediately get sent to https://kbin.social/u/undefined. Not only is Mr. Undefined a real user, hello @undefined, but somehow my image now directs to his profile.
As I dig into Firefox dev tools to find out why, I see that uBlock Origin has blocked the request for my image. But that's odd, I have no specific blocking rules for kbin, and kbin.social doesn't run ads. What's up?
.../media/ad/... That's what uBlock was upset about. So by blocking that request, the target of the AJAX fetch is... undefined. Hence my trip to a random user's profile. XD
@e569668 @HarkMahlberg
I think a bug report to ublock would be more sensible. I guess ultimately this creates a question about at what point kbin should code around a somebody else's bug (which may only be temporary)... I don't know the answer to that one.