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?

So it turns out my image got uploaded to the following URL: https://media.kbin.social/media/ad/b2/adb203028331eada7f99f2b4547cbc0a7efc0ba4e203a71d9d193c02d38aa4f1.jpg

…/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

#kbinMeta

  • Teppic@kbin.social
    2·
    10 months ago

    @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.

    • e569668@fedia.io
      1·
      10 months ago

      @Teppic
      @HarkMahlberg

      I don’t disagree that could be tried, but I just doubt they would change that rule just for kbin, compared to kbin changing it from /media/ to anything else like /media/hash/ and avoiding the problem. I have to imagine most users of the fediverse use ublock and use the default lists