Something tells me NodeBB's check is at fault here
Yeah, no...in more recent messages it passes. I updated the version when they implemented the breaking change for 1.3.0 but before 1.3.0 had been released. That's what I get for looking at old logs that don't have good timestamps at the beginning of the line.
OOC: dammit, I'm totally going to offer a bounty if someone can implement "filter posts in a thread by user" - it's so much harder to catch up when you've half-read the thread at work and are now composing responses
I hereby offer a box of Thin Mints (or a similar mutually acceptable option) as bounty for implementation of a filter posts by user option. My thinking is either:
it would work similarly to the DiscoUserCard feature - either some sort of pop up on the user avatar that gives you options to filter or interact with their profile
or add a action icon underneath the user avatar.
Why ask me? I'm not a node dev, I just gave my observations.
I'm willing to bet that the 0_ comes from some failed attempt to get the file size at pre-upload time.
It's probably because the plugin was made without the anticipation of in-post meta attributes. What you see is what you get, and it's rather difficult to create things in NodeBB that aren't seen.
For images it's not that big a deal, since (assumedly) you don't see the title text (first file name thing), and aren't going to steal the image directly (hence the second file name), and need some way to distinguish multiple files that happen to have the same name (hence the timestamps).
It's a bodge, for sure. but not one I'm going to defend or attack it. It can be improved, for sure, and so long as someone is willing to do so, I'm fine with that.
Or how about you wait like 6 weeks, which is about how long it takes to completely forget everything apparently, then propose we implement this exact same fucking broken code then even though it's still broken.
If you're not going to even try to be productive, get out of this thread.