Discussion of NodeBB Updates
-
@blakeyrat said in Discussion of NodeBB Updates:
@ben_lubar Thank you, that makes me feel a lot better.
Maybe you should take a quick break to tell them, "hey if you hadn't half-assed your dumb database design, you dumbshits, you wouldn't have to do this shit now."
Working on that one too:
-
@ben_lubar Ben if they had hired you from day one, their product would be infinitely superior. You actually seem to know what the fuck you're doing. Sometimes.
-
@ben_lubar said in NodeBB Updates:
Killed off
mubsub
because it keeps breaking the forumDarkly theme not so dark now.
-
@zecc said in Discussion of NodeBB Updates:
@ben_lubar said in NodeBB Updates:
Killed off
mubsub
because it keeps breaking the forumDarkly theme not so dark now.
You've entered Reduced Enhanced mode!
-
It's dark again (except the composer panel, which never was).
I don't know why, but neither do I care.
I'd guess it tried to load CSS which was unavailable before the update ended, and so it used the browser's default, or something.
-
These days I have an odd feeling that the last read positions aren't being properly synchronized between my work computer and my phone.
-
@sockpuppet7 said in Discussion of NodeBB Updates:
These days I have an odd feeling that the last read positions aren't being properly synchronized between my work computer and my phone.
If your socket goes stale, it doesn't update your read position when you navigate in topics. When this happens, the simplest way to tell is that the hamburger menu on posts will not load. Also you won't be able to post. A page refresh with F5 or the browser's refresh button will fix this.
Also, you have to at least navigate to refresh the links in the topics list if you've been browsing on a different device. Otherwise the topic links will still point to the post that was the first unread before you browsed it on a different device. This doesn't take a full refresh, though. Clicking the recent icon should be sufficient to update the links.
-
These last days nodebb is being so screwed up with my unstable connection (I think it's because of the connection, otherwise I don't believe it would be released this way), that it's now strongly placed in the list of software that I would never choose or recommend. It's almost unusable.
-
@sockpuppet7 said in Discussion of NodeBB Updates:
screwed up with my unstable connection
What do you expect? :/
-
@tsaukpaetra Everything else works fine. Even discourse is fine with my shitty 3rd world 4G. Fuck nodebb with a 10 foot pole.
-
@sockpuppet7 said in Discussion of NodeBB Updates:
Fuck nodebb with a 10 foot pole.
@pie_flavor I think I found you a friend.
-
@tsaukpaetra There is no reason for the composer to be fucked up, or for the touches to go to the wrong html element, or for it to fail to recover until I close the tab. That's shitty software.
-
@sockpuppet7 said in Discussion of NodeBB Updates:
There is no reason for the composer to be fucked up
There is, but you're not going to like it.
@sockpuppet7 said in Discussion of NodeBB Updates:
for the touches to go to the wrong html element
Ah, @pie_flavor mentioned the same happening. Perhaps you can compare notes?
@sockpuppet7 said in Discussion of NodeBB Updates:
for it to fail to recover until I close the tab.
That's a bug, you should file a report on that if you can reproduce it on https://try.nodebb.org/
-
@tsaukpaetra said in Discussion of NodeBB Updates:
Ah, @pie_flavor mentioned the same happening. Perhaps you can compare notes?
That happens to me also.
-
@polygeekery said in Discussion of NodeBB Updates:
That happens to me also.
Pretty sure it happens to everyone on mobile. I think the reason it hasn't been fixed yet is that debugging tools on mobile are of course utter shit. I've been trying to figure out a way to track it down myself and am at a bit of a loss (other than using a Fiddler proxy to throw modifications to the CSS/JS at the wall and see what sticks -- that's the sort of solution a net admin would come up with).
-
@heterodox said in Discussion of NodeBB Updates:
Pretty sure it happens to everyone on mobile.
I must be special.
I blame it being in phablet mode.
-
@tsaukpaetra said in Discussion of NodeBB Updates:
I blame it being in phablet mode.
Possibly. It never happens on my tablet.
-
@polygeekery said in Discussion of NodeBB Updates:
Possibly. It never happens on my tablet.
3px lolol MEME
-
@tsaukpaetra said in Discussion of NodeBB Updates:
if you can reproduce it on https://try.nodebb.org/
I'm able to reproduce the "confused about the browser url bar" issue on there on Android, but I can't figure out how to reliably.
Can't seem to reproduce the issue on iPhone though.
-
@polygeekery said in Discussion of NodeBB Updates:
@tsaukpaetra said in Discussion of NodeBB Updates:
Ah, @pie_flavor mentioned the same happening. Perhaps you can compare notes?
That happens to me also.
And me.
But I think I noticed it on another site too, so... maybe it's a mobile Chrome bug. Or maybe I just imagined it.
-
@anotherusername the annoying thing is that I have started tapping above links on other sites now. Whatever it is it needs fixed now.
-
@anotherusername said in Discussion of NodeBB Updates:
But I think I noticed it on another site too,
This is the only site I've noticed it on. Then again, I don't really do a lot of mobile browsing on other sites — links from here or looking stuff up on Wikipedia, but mostly just look at that one thing and then close the tab. So,
-
@ben_lubar said in NodeBB Updates:
Update scheduled for 12:30 UTC
- Update to NodeBB v1.10.0.
- Updated emoji. (thanks, @pie_flavor)
- You can disable global TDWTF CSS changes via setting the override_disable-tdwtf-css query string parameter to anything.
@ben_lubar making the user type the full URL with a query string parameter on mobile devices is , to put it politely
-
@sockpuppet7 said in Discussion of NodeBB Updates:
@ben_lubar said in NodeBB Updates:
Update scheduled for 12:30 UTC
- Update to NodeBB v1.10.0.
- Updated emoji. (thanks, @pie_flavor)
- You can disable global TDWTF CSS changes via setting the override_disable-tdwtf-css query string parameter to anything.
@ben_lubar making the user type the full URL with a query string parameter on mobile devices is , to put it politely
You can click the link in that post and then it stays like that until you refresh without the query string parameter.
-
By the way, this script is taking ages: https://github.com/NodeBB/NodeBB/blob/v1.10.0/src/upgrades/1.10.0/hash_recent_ip_addresses.js
-
@ben_lubar said in Discussion of NodeBB Updates:
You can click the link in that post
It did nothing for me.
-
@ben_lubar said in Discussion of NodeBB Updates:
By the way, this script is taking ages: https://github.com/NodeBB/NodeBB/blob/v1.10.0/src/upgrades/1.10.0/hash_recent_ip_addresses.js
About the only thing that I can see that could possibly be improved for performance is that it's using
nconf.get('secret')
(which I presume returns the same thing every time it's called) inside the loop.
-
@ben_lubar said in NodeBB Updates:
Update scheduled for 12:30 UTC
- Update to NodeBB v1.10.0.
- Updated emoji. (thanks, @pie_flavor)
- You can disable global TDWTF CSS changes via setting the override_disable-tdwtf-css query string parameter to anything.
/unread/new
no longer exists, apparently it's been moved to/unread?filter=new
, but when I set that as my custom homepage in my settings, it just uses/unread
without the filter. What should I do instead?
-
@ben_lubar said in NodeBB Updates:
Update scheduled for 12:30 UTC- Update to NodeBB v1.10.0.
- Updated emoji. (thanks, @pie_flavor)
- You can disable global TDWTF CSS changes via setting the override_disable-tdwtf-css query string parameter to anything.
Clicking on that link makes some broken stuff at the top: see screenshot.
-
Apparently the new CSS changes somehow craptified the necro post indicators:
Before:
After:Fake edit: Oh it's probably the more specific selector making it override the customization.
html:not([data-disable-tdwtf-css]) .necro-post { margin-bottom: 20px; text-align: center; font-size: 1.5em; text-transform: uppercase; color: rgba(127,127,127,.5); }
Fake edit 2: Yep, added
html:not([data-disable-tdwtf-css])
to my rule and all is well again.
-
@anotherusername Not, like, "use a database that doesn't suck ass" or "normalize your fucking data instead of just storing everything as a key/value" or "maybe consider a computer language that isn't fried ass".
-
@ben_lubar said in NodeBB Updates:
- You can disable global TDWTF CSS changes via setting the override_disable-tdwtf-css query string parameter to anything.
Holy shit, the site's usable!
Edit: Holy shit, the site's fast! This update has got rid of every speed complaint about the site I've ever had.
-
@pie_flavor are you referring to the update, or the option to disable the custom CSS? Because I really doubt the custom CSS is slowing it down very much.
-
@anotherusername I initially was referring to the CSS, but then realized that I refreshed the JS file at the same time I refreshed the CSS file and it was probably just the update.
-
@pie_flavor said in Discussion of NodeBB Updates:
This update has got rid of every speed complaint about the site I've ever had.
Except, of course, for fucking mobile.
-
Did you brokeneded CSS? Or something? Custom emoji don't work. Avatars are round and have what appear to be online/offline indication dots on them. Reply/Quote buttons aren't blue.
-
@hardwaregeek said in Discussion of NodeBB Updates:
Did you brokeneded CSS? Or something? Custom emoji don't work. Avatars are round and have what appear to be online/offline indication dots on them. Reply/Quote buttons aren't blue.
Noticed that and just fixed it. Try refreshing.
-
Did WTDWTF CSS just get turned off site-wide? Because I'm not using the URL parameter and holy UI changes, Batman.
-
@heterodox said in Discussion of NodeBB Updates:
Did WTDWTF CSS just get turned off site-wide? Because I'm not using the URL parameter and holy UI changes, Batman.
@ben_lubar said in Discussion of NodeBB Updates:
Noticed that and just fixed it. Try refreshing.
-
@ben_lubar Ah, there we go, thanks! (That exchange happened while I was posting. :))
-
-
@ben_lubar I blame NodeBB.
-
-
@polygeekery I blame @boomzilla
-
@polygeekery said in Discussion of NodeBB Updates:
I blame @ben_lubar
@pie_flavor said in Discussion of NodeBB Updates:
@polygeekery I blame @boomzilla
Wouldn't "so do I" have been quicker to type, instead of quoting what @boomzilla said?
-
@heterodox said in Discussion of NodeBB Updates:
I blame NodeBB.
@polygeekery said in Discussion of NodeBB Updates:
I blame @ben_lubar
@pie_flavor said in Discussion of NodeBB Updates:
I blame @boomzilla
I don't blame this sleeping satellite.
-
@ben_lubar said in NodeBB Updates:
- Updated emoji. (thanks, @pie_flavor)
- Added code required to run a PostgreSQL database for the forum.
Is there some pie flavor thread where we can put fixed emojis?
Also another one I found in the same post
-
@hungrier said in Discussion of NodeBB Updates:
@ben_lubar said in NodeBB Updates:
- Updated emoji. (thanks, @pie_flavor)
- Added code required to run a PostgreSQL database for the forum.
Is there some pie flavor thread where we can put fixed emojis?
Also another one I found in the same post
The White background was for us dark-mode users IIRC.
-
@tsaukpaetra said in Discussion of NodeBB Updates:
The White background was for us dark-mode users IIRC.
It came from at least Discourse time when there was no dark mode, and IIRC it was just there because to remove the background. There are plenty of other emojicons that are naturally invisible or almost-invisible on a dark theme (, etc)
Besides, all the cool kids* are using emojicon colour inversion userscripts:
e: with pendant inverted
pendant normally invisible
-
@hungrier said in Discussion of NodeBB Updates:
Besides, all the cool kids* are using emojicon colour inversion userscripts:
I just have custom CSS in my profile
.emoji:not(.emoji-fontawesome) { background-color: #DDDDDD; }