So if you're a kbin user and for some ungodly reason you find yourself on Mr. Undefined's page after previewing an image, you may want to add the following rules to your ublock origin list.
/kbin meta
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
@HarkMahlberg I would consider adding a bug for this to the issue tracker as it seems like a gotcha https://codeberg.org/Kbin/kbin-core/issues
@HarkMahlberg I assumed it was a default ublock rule and not one you added so I imagine a lot of people might run into this. Well, "a lot" depending on how often a filename's sha256 hash starts with ad
. At the very least it's probably good to know about it, even if nothing is changed. But perhaps there's enough reason to use a different system to name image caches like the name generators a lot of image hosters seem to use. I guess it's in the devs hands now :) thanks for sharing it
@e569668 Oh, I meant to say that my running ublock origin at all was personal, and not everyone is going to run ublock origin. But to clarify, the rule that triggered the bug came from a default ublock list: https://easylist.to/.
@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.
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