Blakeyrat pointing out NodeBB problems
-
@boomzilla I'm not seeing it. I'm seeing Ben L doing a ton of keeping Redis and Mongo working, and I see you writing some patches to make things behave less-stupid.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
I'm not seeing it
None so blind as those that will not see.
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
I'm seeing Ben L doing a ton of keeping Redis and Mongo working, and I see you writing some patches to make things behave less-stupid.
Those things are happening, too.
-
@blakeyrat Hmm, maybe it's because the NodeBB devs choose, for the most part, to do their support from a distance instead of integrating themselves into our forum. Have you looked at the commits in NodeBB's code base? Seen the PRs written by @ben_lubar and @boomzilla that have been integrated into core? Seen the bugs that get reported to the git hub specific to our instance and then escalated to the core NodeBB github if appropriate? Have you joined the NodeBB forum where several of our members (not just ben and boomy) are now involved?
I'm betting the answer to most of those questions is "no" because you CBA to look because you don't really give a shit.
-
@abarker said in Blakeyrat pointing out NodeBB problems:
I'm betting the answer to most of those questions is "no" because you CBA to look because you don't really give a shit.
I think a large part of it is that his top priority things haven't been fixed, which is a fair thing to complain about. But it doesn't mean that nothing is happening any more than that democracy is dead if the guy you voted for loses.
-
@abarker said in Blakeyrat pointing out NodeBB problems:
m betting the answer to most of those questions is "no"
True.
@abarker said in Blakeyrat pointing out NodeBB problems:
because you CBA to look because you don't really give a shit.
I'm just going by changes I see pushed out to the product. People made a big fucking deal about how quickly issues were resolved, and I've seen no evidence of that.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
I'm just going by changes I see pushed out to the product.
Ah, so this:
@boomzilla said in Blakeyrat pointing out NodeBB problems:
I think a large part of it is that his top priority things haven't been fixed
Appears to be correct. Well, keep in mind that your top priorities are just a subset of everything that is being found and worked on. You are probably missing things.
-
@abarker said in Blakeyrat pointing out NodeBB problems:
Appears to be correct. Well, keep in mind that your top priorities are just a subset of everything that is being found and worked on.
Well of course. (Except I think a tiny bit of rational thought from the developers about the first-run experience on PC would quickly convince them the "show mobile view to PC users" bug should be right at the top of the list, but whatever.)
@abarker said in Blakeyrat pointing out NodeBB problems:
You are probably missing things.
Am I? Like what?
-
@ben_lubar Since several people are wondering these days about what advantages we have in nodebb over discourse, maybe a thread to point out things they fixed that we reported wouldn't go amiss?
-
@Yamikuronue Isn't that what the NodeBB Updates thread is for? And doing?
-
@Yamikuronue said in Blakeyrat pointing out NodeBB problems:
Since several people are wondering these days about what advantages we have in nodebb over discourse
It's amazing how quickly we forget about pain.
I mean...there are things that Discourse did (eventually, when it got around to it) that I really miss, I'm very happy with the transition.
-
-
@ben_lubar I haven't seen anything (but I'm still a n00b), but does github have anything to facilitate putting together release notes based on issues / commits links?
-
@boomzilla You mean like these?
-
@ben_lubar Yes!
-
@boomzilla said in Blakeyrat pointing out NodeBB problems:
It's amazing how quickly we forget about pain.
Reminds me of several stories in the biblical book of exodus where people complained things were so much better in Egypt.
-
@ben_lubar Good first step. Now specify a maintenance window on some schedule and create milestones for each of the windows you intend to utilize, so people can know when to expect downtime and what they get in exchange, and you'll be a real grownup dev >.>
-
@Yamikuronue said in Blakeyrat pointing out NodeBB problems:
expect downtime
I'm not sure clicking the "forum update" toaster counts as down time
-
@loopback0 said in Blakeyrat pointing out NodeBB problems:
I'm not sure clicking the "forum update" toaster counts as down time
Toasters can continue to FOADIAF. Clicking that one never works exactly right anyway. Shift-Reload works way better.
-
@flabdablet for some reason, it shows up before the javascript is done being put together and minified.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
@abarker said in Blakeyrat pointing out NodeBB problems:
You are probably missing things.
Am I? Like what?
Like all of the stuff I already mentioned that you
aren'tweren't aware of. You said we aren't getting support beyond @boomzilla and @ben_lubar, but that's because the support is less visible than it was with discourse. You say we aren't getting updates, but what you mean is we aren't getting updates to fix the pain points you feel the most.Look, people are trying to fix things. Things are getting better. You do have some legit complaints, and it sucks. But keep in mind that fixing some of those will take a bit more work than some of the other things that are getting taken care of already.
-
@ben_lubar Locked threads aren't fun
-
@fbmac the updates thread is locked for the same reason the song of the day thread is heavily regulated. Discussion goes in a different topic(s) so the whole thread is back to back content.
-
@ben_lubar is there a discussion thread we can derail? I like derailing threads.
-
-
@ben_lubar could the updates thread maybe have a very brief bulletpoint list of the key things that actually changed, in addition to the click here and get the tl;dr changelog link?
-
@abarker None of that is very reassuring when my highest priority bug report was mocked by the person here in charge of sending those bug reports to the NodeBB developers. I have absolutely no idea whether that person has bothered sending it to the NodeBB developers, or done even a single iota of work on it himself, but I imagine not because GitHub would have emailed me in any case.
So while everything you say is true, what you're missing is the reason my specific pain points aren't being addressed is because the person at DailyWTF whose job it is to address it just made fun of my ideas instead.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
You mean like these?
We want release notes, not source control barf.
I love how they marked "drop down menus can go off-screen" as "enhancement" and not "extremely embarrassing bug, jesus christ, what's wrong with us!?" Which should totally be a category they have.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
my highest priority bug report
Refreshen my memory on that, which one was it?
You have so many of them.
-
@anotherusername said in Blakeyrat pointing out NodeBB problems:
Refreshen my memory on that, which one was it?
Pretty sure that was the one where he gets the mobile view on desktop. But then when he widens his viewport by a few pixels to get the desktop view, he complains that the desktop view actually narrows his paragraph width because of the changes to the layout.
-
@abarker oh, that. Yeah, that's a combination of #NOTABUG#WORKSASDESIGNED and the fact that everything in that view pretty much just works perfectly fine, except for the composer, which I for one really hope gets fixed -- @blakeyrat definitely isn't the only person complaining about it.
-
@abarker that link is in tdwtf repo, not nodebb's
-
@abarker the bug is simple. "Mobile view should not be shown to desktop computer users".
For some reason it's impossible to communicate that bug to morons without them making it into a big "thing" and talking about window widths, CSS bugs, etc, none of which matters. But the bug itself is simple.
-
For some reason it's impossible to communicate that it's not "mobile view", it's "small size view", to morons without them continuing to harp on about how it's "mobile view" and they shouldn't ever see it on their desktop computer.
Just out of curiosity, do you consider my 1920x1080 laptop to be a mobile device or a desktop computer?
That said, the "small size view" or whatever-it-is-you-want-to-call-it does have some issues. I'd like to see them fixed too.
-
@anotherusername said in Blakeyrat pointing out NodeBB problems:
For some reason it's impossible to communicate that it's not "mobile view", it's "small size view",
Whatever you want to call it, it still happens at a resolution much higher than it should.
-
@anotherusername said in Blakeyrat pointing out NodeBB problems:
For some reason it's impossible to communicate that it's not "mobile view", it's "small size view",
Control-H, "mobile view", Tab, "small size view", Enter.
I don't give a flying fuck what it's called.
-
@loopback0 if the composer that it switches to at that size wasn't so godawful, it wouldn't matter. And that composer is godawful at any size. Fix that composer, and the issue goes away. Entirely.
But, on the other hand, fix the "mobile view" bug to make blakey happy, and that composer is still godawful. Just... at a smaller size. Or... not on his device.
-
@anotherusername said in Blakeyrat pointing out NodeBB problems:
if the composer that it switches to at that size wasn't so godawful, it wouldn't matter
Right - but the composer at that size is godawful.
This is still something that even Discourse, which seemed to hate mobile devices, did better.
Xenforo gets this right too.
-
@loopback0 right, which is why I'm trying to put the focus on "fix the composer" instead of "I'm seeing this mobile view and I don't want it".
-
@anotherusername Sorting the whole "mobile" vs "desktop" thing sorts the problem all round though. The composer is the biggest thing it causes but it's not the only thing.
-
@loopback0 if the "mobile" view only displayed on mobile devices, it'd still suck on mobile devices though.
Fixing the issues that the view creates would fix the problem. Then it would actually work at all sizes, and we could bikeshed the pixel size at which it transitions to our heart's content.
-
@anotherusername said in Blakeyrat pointing out NodeBB problems:
if the "mobile" view only displayed on mobile devices, it'd still suck on mobile devices though.
True. So "mobile" view needs to be less terrible, and also the "mobile" vs "desktop" thing needs to be less terrible.
-
@anotherusername said in Blakeyrat pointing out NodeBB problems:
Yeah, that's a combination of #NOTABUG#WORKSASDESIGNED and the fact that everything in that view pretty much just works perfectly fine, except for the composer, which I for one really hope gets fixed -- @blakeyrat definitely isn't the only person complaining about it.
I remember someone around here saying, "Some minion of mine says that's easy to fix!" but never getting back to me about what the fix was.
-
How about they make text entry on this site count as text entry? Discourse had the same bug: On windows mobile, Swype a few words. Try it. Does that work how it does elsewhere? Is it so stupid someone deserves to be fired? Text entry is pretty much the point of a forum, and it's just completely wrong!
-
@Magus said in Blakeyrat pointing out NodeBB problems:
How about they make text entry on this site count as text entry? Discourse had the same bug: On windows mobile, Swype a few words. Try it. Does that work how it does elsewhere?
Uh...it does on Android. What does Windows Phone do differently?
-
@boomzilla said in Blakeyrat pointing out NodeBB problems:
Uh...it does on Android. What does Windows Phone do differently?
Great, "You use Windows Phone, that's different" is it?
When you use literally any other text entry field, it can pick up context and get words right, and backspace whole completed words, and adds spaces automatically when you begin swyping the next word. None of those things work at all here.
-
@Magus said in Blakeyrat pointing out NodeBB problems:
Great, "You use Windows Phone, that's different" is it?
Apparently.
-
@boomzilla I mean, I feel like you know, actually testing software might be a good thing for people to do?
-
@Magus Like, with every mobile keyboard on every platform? That said, I wonder what swype is doing wrong on Windows Phone.
-
@boomzilla I think it might actually just be Edge, since its doing the same horrible thing even on google. I'll send them a bug I guess...
I hope it's just an edge bug... Which seems likely when it even happens on Bing...
-
@Magus I hope they really pay attention to the feedback app, since this is a serious usability issue. Kind of glad to know it isn't NodeBB, though. When it happened on discourse, it was by far the easiest choice to blame them.
So, Microsoft needs to test things. This would have taken around five seconds.