NodeBB Updates
-
I'll be posting reasons for instance restarts here from now on.
-
Applying fix for duplicate replies:
-
Updated to the latest git master of nodebb-plugin-youtube-lite.
-
-
-
add allowed HTML tags to the composer help box
-
Disabled
nodebb-plugin-question-and-answer
so @blakeyrat would stop bothering me about it.
-
-
No restart, but if you're wondering why you have a lot of unread topics it's because I set the timeout to 90 days (up from 2 days).
-
We are currently being attacked by several "SEO" bots. I've blocked a few of them in nginx, but there's still a lot of requests going through.
-
-
Sorry about that, @Mafia-Players. I don't think it affected anyone else.
-
-
Now it supports all kinds of fucked up titles!
https://github.com/RaceProUK/nodebb-plugin-composer-default/pull/1
-
I added
hljs
to the list of allowed classes on<code>
, but that doesn't seem to have done anything.
-
Also re-enabled iframely.
-
-
disabled iframely
-
You can now upload gifs.
Images load without JavaScript.
-
More jellypotato fixes.
-
Fixed an exploit where someone could crash my HTML cleaner by posting a deeply nested tree of disallowed elements.
-
Better mobile composer CSS
-
Still no idea what's causing the cooties.
-
Disabled notifications. Let's see if that stops the cooties.
-
@ben_lubar They're sort of disabled. I keep getting the numbers showing up. But nothing is there.
-
Ok, disk problems should be much less now. Notifications hack removed.
-
https://what.thedailywtf.com/topic/19533/youtube-thumbnails
also updated some sso plugins to the latest version.
-
notifications re-disabled.
-
hopefully less jellypotato
-
No restart right now, but if there aren't any major cooties by the time I wake up tomorrow, I'll re-enable notifications. Hopefully the problem was 100% caused by bots and the notifications taking 90 seconds to load was just a symptom of the database having trouble keeping data in cache.
-
Notifications re-enabled.
-
Disabled the 503 page.
-
We're back on 4 nodes.
-
-
re-enabled iframely
-
re-added the hack that fixes iframely links.
-
-
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Didn't we at one point fix it so the name of the thread remained on screen as you scrolled down in desktop mode? Because that no longer works. The header of the site stays put, but the thread title is not present in it.
-
@ben_lubar Manually applied a correction to the fix.
-
-
iframely updated to 0.6.10.
-
@ben_lubar manually applied https://github.com/NodeBB/nodebb-plugin-iframely/pull/18
-
Blacklisted codepen.io oneboxing.
-
Created new @TDWTF-NodeBB-Development group.
-
-
Also re-applied the PR from and so commas will work in titles again.
-
I updated
nodebb-plugin-mentions-emoji
to setwidth="20"
,height="20"
, andclass="not-responsive"
, so those will be skipped by the jellypotato hack. I didn't restart the server, so anything that was in the post cache will still have resizing emoji, but new posts and posts that get pushed out of the cache will be less jittery.
-
also fixed a Signature Guy exploit.
-
redis caused cooties. restarted redis.