Discussion of NodeBB Updates
-
@pie_flavor said in Discussion of NodeBB Updates:
can we just switch back to discourse
You should ask:
-
@boomzilla said in Discussion of NodeBB Updates:
@pie_flavor said in Discussion of NodeBB Updates:
can we just switch back to discourse
You should ask:
Is it after a 2016 yet?
-
@pie_flavor said in Discussion of NodeBB Updates:
can we just switch back to discourse
Can you just fuck right off?
-
The only thing I miss about is my badge.
-
Edit: Lovely, it double posted. If I tap the post button and both menus open and I suddenly end up in a DM with @wharrgarbl with the scrollbar in the center of the page and the contents of my post in the reply box, I would assume that it didn't actually successfully post to the thread.
-
This post is deleted!
-
@boomzilla
*checks it on desktop*
*relaxes eyes because text is at optimal wrap location*
*clearly displays which individual posts I haven't read*
*checks it on mobile*
*does not take six years to load threads*
*does not lag browser significantly*
*does not require stupid pagination by default*
*does not scroll to a location determined by /dev/random whenever a scroll segment is loaded*
*does not scroll to a location determined by /dev/urandom every time an image or iframe is loaded*
*does not select a grouping of random read and unread notifications to show you*
*does not scroll anywhere other than the last read post when clicking a watched unread notification*
*does not glob mention and unread notifications together*
*does not require you to click every single like notification*
*does not misinterpret nearly every tap*
*does not move controls around randomly with a setting to change them back for a few hours*
*does not place scrollbar in center of page*
*does not fill entire screen with composition box*
*does not place text behind opaque diseased boobs*
*does not ignore 'Request Desktop Page' setting due to determining mobile status via @blakeyrat's preferred window size*
*does not glitch everything everywhere before settling down after a few seconds*
*does not flip a coin on whether a new post will be loaded*
*is regrettably run by someone who doesn't take well to constant verbal abuse*
oh thank you wise sage i now see that nodebb is the true way
-
@pie_flavor said in Discussion of NodeBB Updates:
relaxes eyes because text is at optimal wrap location
clearly displays which individual posts I haven't read
checks it on mobile
does not take six years to load threads
does not lag browser significantly
does not require stupid pagination by default
does not scroll to a location determined by /dev/random whenever a scroll segment is loaded
does not scroll to a location determined by /dev/urandom every time an image or iframe is loaded
does not select a grouping of random read and unread notifications to show you
does not scroll anywhere other than the last read post when clicking a watched unread notification
does not glob mention and unread notifications together
does not require you to click every single like notification
does not misinterpret nearly every tap
does not move controls around randomly with a setting to change them back for a few hours
does not place scrollbar in center of page
does not fill entire screen with composition box
does not place text behind opaque diseased boobs
does not ignore 'Request Desktop Page' setting due to determining mobile status via @blakeyrat's preferred window size
does not glitch everything everywhere before settling down after a few seconds
does not flip a coin on whether a new post will be loadedYeah...I am starting to think you are getting different versions of NodeBB and/or Discourse. A lot of those are not true of NodeBB and those that are most of them are also true of Discourse.
@pie_flavor said in Discussion of NodeBB Updates:
is regrettably run by someone who doesn't take well to constant verbal abuse
Or is able to handle any difference of opinion whatsoever, to the point that he has perfectly engineered two echo chambers.
-
@polygeekery Every single one of those behaviors, I observe in WTDWTF's NodeBB. Every single one of those behaviors, I do not observe in Sponge's Discourse. I have not spent enough time on meta.d to gauge any differences between Sponge's and meta.d's, but as far as I can tell there are none.
And I haven't interacted with @wood, so I wouldn't know. But Discourse is miles better, and this latest NodeBB update leaves me wondering just how bad he was that you would prefer this barely-functional crap over a forum that, amazingly enough, does not log you out when you hit the up vote button. All the bloat of an SPA with none of the continuity.
-
@pie_flavor said in Discussion of NodeBB Updates:
does not log you out when you hit the up vote button.
What in the actual fuck are you doing? I have never had that happen. The only time I have ever been logged out is on the laptops that I only use once or twice a month.
-
@polygeekery I tap the button. The retarded sidebar swiping interprets it as me opening the sidebar. For some unspecified reason, it taps again at the same spot. Last time I used the sidebar, I had it scrolled to the precise spot where this re-tap is now over the log out button. It logs me out.
Like that.
-
@pie_flavor said in Discussion of NodeBB Updates:
For some unspecified reason, it taps again at the same spot.
I believe your touchscreen may be dirty.
-
@pie_flavor said in Discussion of NodeBB Updates:
@polygeekery I tap the button. The retarded sidebar swiping interprets it as me opening the sidebar. For some unspecified reason, it taps again at the same spot. Last time I used the sidebar, I had it scrolled to the precise spot where this re-tap is now over the log out button. It logs me out.
Like that.
PEBKAC
-
@polygeekery said in Discussion of NodeBB Updates:
@pie_flavor said in Discussion of NodeBB Updates:
@polygeekery I tap the button. The retarded sidebar swiping interprets it as me opening the sidebar. For some unspecified reason, it taps again at the same spot. Last time I used the sidebar, I had it scrolled to the precise spot where this re-tap is now over the log out button. It logs me out.
Like that.
PEBKAC
Does that even work with a mobile phone? What if you're kneeling and using the chair seat as a table?
-
- No.
- I don't CARE.
This behavior occurs on NodeBB.
This behavior does not occur on Discourse.
There is literally no benefit (and a good amount of detriment) to the reasons which go into it occurring on NodeBB.
-
@ben_lubar you are about to work your way in to my home arson backlog.
-
@polygeekery Evidently you haven't tried using it on mobile recently. Nearly everything you try to tap, including the button for the opposite bar, results in the sidebar or chats bar appearing. Even in the fucking compose box, meaning I'm starting to stick entirely to spacebar swipe navigation while composing. I'm glad Lorne isn't around for this - if he can't keep his finger steady enough to select text, then he definitely can't keep it steady enough to not open the new and improved sidebar, and would go into full insane rage again.
Edit: Oh, and your post loaded but @ben_lubar's didn't until I refreshed. Like I said, coin flip.
-
@pie_flavor said in Discussion of NodeBB Updates:
Evidently you haven't tried using it on mobile recently.
I have. I am on mobile most of the time.
@pie_flavor said in Discussion of NodeBB Updates:
Nearly everything you try to tap, including the button for the opposite bar, results in the sidebar or chats bar appearing. Even in the fucking compose box, meaning I'm starting to stick entirely to spacebar swipe navigation while composing.
Are you by any chance a spastic?
Seriously though, I have had it open several times when I did not intend it to. It is a minor annoyance.
@pie_flavor said in Discussion of NodeBB Updates:
Edit: Oh, and your post loaded but @ben_lubar's didn't until I refreshed. Like I said, coin flip.
Yeah, that happens on occasion also which has caused me to miss replies to my posts.
But that one for damned sure happens on Discourse when the traffic is high enough. The forums you are on may not have near the number of posts that we do. If they did, you would notice it on Discourse also.
-
@pie_flavor I decided to test this for myself, since I almost never use this on mobile. I have no issues with any menus appearing at the slightest glance. In fact, sometimes I have trouble getting it to appear. No random swiping or touch related issues occur on any other site?
-
@erufael Nope! Especially not, and I cannot stress this enough, Discourse.
You know, maybe it's a Puffin issue. Let me check Chrome real quick.
*deals with absolutely glacial slowness for a quick minute*
Stupidity is greatly decreased from this afternoon, but the rates are precisely the same across both browsers.
-
@pie_flavor Weird... As a note, I'm using Edge on Android. Lemme see if Chrome is any different.
-
@erufael Chrome exhibits a little more jankeyness, especially when trying to scroll when a thread is still loading. Still nothing like what you're experiencing though. This is quite puzzling.
As an aside, I find it hilarious that Edge on Android works better than any of the other browsers I've used on a phone.
-
@erufael As I understand it, Edge on Android is an actually new browser, whereas Edge on Windows is IE with a new coat of paint (which painted everything shut).
-
@pie_flavor Wait, you said above that you had managed to get logged out when opening the menu? How?? On mine, I have to scroll a significant amount (relatively) to see those buttons. O.o
-
@erufael But the scroll is preserved, so it'll be right there when you reopen it. One of the exceedingly few reminders that this is actually an SPA.
-
@pie_flavor Ah. So it is. So you (maybe accidentally) swipe the menu open, and it for some reason registers a click?
-
@erufael That is exactly what I said. With the 'accidentally' part being way the fuck too easy.
-
Ok, if you go to https://what.thedailywtf.com/assets/nodebb.min.js?v=3dpknvlj4u3 and do a hard refresh, it should remove the mobile slidey thing.
-
@ben_lubar said in Discussion of NodeBB Updates:
Ok, if you go to https://what.thedailywtf.com/assets/nodebb.min.js?v=3dpknvlj4u3 and do a hard refresh, it should remove the mobile slidey thing.
-
@tsaukpaetra said in Discussion of NodeBB Updates:
@ben_lubar said in Discussion of NodeBB Updates:
Ok, if you go to https://what.thedailywtf.com/assets/nodebb.min.js?v=3dpknvlj4u3 and do a hard refresh, it should remove the mobile slidey thing.
NodeBB, why are you trying to single-page-app the
assets
directory?Edit: In any case, doing a hard reload or two on that will still work.
-
@ben_lubar
E_NO_REPRO
. Just shows me a bunch of JS code.
Is it supposed to be executing it, or...
-
@pie_flavor said in Discussion of NodeBB Updates:
@ben_lubar
E_NO_REPRO
. Just shows me a bunch of JS code.
Is it supposed to be executing it, or...All you need to do is clear your browser's cache of that script and it should disable the slide-sideways thing.
-
@ben_lubar Nope. And that's a full clear of the browser's cache, followed by hard resetting the browser.
-
Clicking on a thread from the topic list just now, it dumped me to some post I had already seen from 2 days ago, and again when I tried it a second time to make sure there wasn't some caching issue. I think at some point someone said the most recently viewed post might be moved to local browser storage instead of server-side. That was obviously a joke and not a real idea, right?
-
@hungrier said in Discussion of NodeBB Updates:
That was obviously a joke and not a real idea, right?
You never know. There was that joke 'what if we didn't let users with underscores in their names log in', and that made it into release. But no, that's probably because you went there at some point and NodeBB decided that was now your 'last read location'.
-
@hungrier said in Discussion of NodeBB Updates:
Clicking on a thread from the topic list just now, it dumped me to some post I had already seen from 2 days ago, and again when I tried it a second time to make sure there wasn't some caching issue. I think at some point someone said the most recently viewed post might be moved to local browser storage instead of server-side. That was obviously a joke and not a real idea, right?
That is the case for non-logged-in users.
-
@pie_flavor said in Discussion of NodeBB Updates:
@ben_lubar Nope. And that's a full clear of the browser's cache, followed by hard resetting the browser.
Oh crap I did it wrong just refresh this page normally and it should be fixed.
-
@ben_lubar That makes sense, but I had it happen while logged in. However I haven't had it happen again; other threads are behaving normally. Maybe it was a temporal bug
-
@hungrier said in Discussion of NodeBB Updates:
@ben_lubar That makes sense, but I had it happen while logged in. However I haven't had it happen again; other threads are behaving normally. Maybe it was a temporal bug
Can you give me a thread ID? Sometimes NodeBB fucks itself up when posts get moved or deleted.
-
@ben_lubar It's... uh... well... swiping seems to have been completely and utterly removed. Both for opening and closing. A bit tricky if the title bar gets stuck. It used to be just that you could swipe it, but only if you started from the edge.
But okay. I am, uh, happy's not the right word for it. Less annoyed? Less annoyed now that the giant step backwards has had a decent-sized step forwards. Another one of those and this version will almost have most of the features of the last version! And we've managed to procure a forum that does not log you out when you hit the upvote button! That's quite the accomplishment.
I'm sorry if I seem a bit blakeyish, but I still can't believe something this fundamentally broken on all levels got pushed into production. That's far past generic FOSS bugginess. It's still completely impossible to compose a thread, for instance - only the glow of the button peeks out from under the title bar.
-
@ben_lubar It was the WTF Bites thread. Were there like 2 days worth of posts deleted between earlier this afternoon and a few minutes ago?
-
@hungrier said in Discussion of NodeBB Updates:
@ben_lubar It was the WTF Bites thread. Were there like 2 days worth of posts deleted between earlier this afternoon and a few minutes ago?
Well, the topic seems fine in the database - your bookmark matches mine, and I get the last post in the topic when I click on it.
What does
localStorage['topic:20319:bookmark']
in the JavaScript console show? If it's notundefined
, that might be why.
-
@ben_lubar said in Discussion of NodeBB Updates:
'topic:20319:bookmark'
It's undefined. I've got a couple category bookmarks in there, but no topic ones.
Maybe I had the thread open a couple days ago and my session timed out on this computer, and it stuck around until I went there tonight? If it's there, does it override the one from the db?
-
-
@pie_flavor said in Discussion of NodeBB Updates:
I'm sorry if I seem a bit blakeyish, but I still can't believe something this fundamentally broken on all levels got pushed into production.
When you seem to be the only person seeing this behaviour it's a bit less surprising. What you describe almost sounds like a dodgy touchscreen that's registering extra movement and touches.
Do you have access to another phone you could try on?
-
@jaloopa Clearly you most the posts where Tsaukpaetra was having the exact same issues as me with the sidebar and I think one other person.
-
@pie_flavor said in Discussion of NodeBB Updates:
But Discourse is miles better
It is very possible that they fixed a lot of stuff since we've been gone. The bottom line is that the site was quite often literally unusable because unicorns were...I dunno...doing something or other. It was never quite clear.
Either way, that bridge is beyond burned.
-
@pie_flavor said in Discussion of NodeBB Updates:
@polygeekery Evidently you haven't tried using it on mobile recently. Nearly everything you try to tap, including the button for the opposite bar, results in the sidebar or chats bar appearing. Even in the fucking compose box, meaning I'm starting to stick entirely to spacebar swipe navigation while composing. I'm glad Lorne isn't around for this - if he can't keep his finger steady enough to select text, then he definitely can't keep it steady enough to not open the new and improved sidebar, and would go into full insane rage again.
Edit: Oh, and your post loaded but @ben_lubar's didn't until I refreshed. Like I said, coin flip.
I don't disbelieve you, but I've used the site a bit recently on mobile and your experience just doesn't sound like mine.
-
@boomzilla A forum with zero noticeable bugs versus a forum where you navigate around six of them every time you post (on mobile)? Yeah, maybe they fixed stuff.
-
@pie_flavor said in Discussion of NodeBB Updates:
Especially not, and I cannot stress this enough, Discourse.
You've already stressed it too much. It's simply not an option. No matter how badly you wish it could be. Even if NodeBB gets caught colluding with underage Russian actresses behind its Bond villain locked office door. Discourse won't be the answer.