Blakeyrat pointing out NodeBB problems
-
@tufty said in Blakeyrat pointing out NodeBB problems:
<sarcasm> much better performance than Discourse.</sarcasm>
E_TOO_MANY_TAGS
-
While we're on that, its "oh so clever" autoclosing of tags doesn't take into account actually closed tags.
<behaviour type="gratuitous" />This is stupid
gives
<behaviour type="gratuitous" />This is stupid
-
@tufty said in Blakeyrat pointing out NodeBB problems:
While we're on that, its "oh so clever" autoclosing of tags doesn't take into account actually closed tags.
Huh? I just meant that you shouldn't put sarcasm tags around text claiming better NodeBB performance than Discourse.
-
@boomzilla they're both fucking awful.
-
@tufty From what I've seen, our NodeBB issues have mainly been system administration issues. I have 99 issues with NodeBB, but performance ain't one.
-
@boomzilla Huh, what kind of dark magic are you using?
For the record, I wasn't making it up that the Recent page took about 17 seconds. After it loaded slow the first time, I hit refresh and kept my eye on the clock.
Even worse, like I posted on Twitter, NodeBB seems to have put ZERO thought into what the client should do if the server goes down. There's no timeouts on anything-- failed posts just have a greyed-out "Submit" button forever, failed queries just have a spinner forever. There's no "server's taking longer than expected" message, there's no "hey server's down, your draft has been saved in your browser's localstorage" mechanism AFAICT. It just completely shits itself.
Sadly that is something Discourse actually did way better than NodeBB does.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Huh, what kind of dark magic are you using?
Linux hardware.
-
most of the afternoon the site was a pile of nginx502s for me.
-
@darkmatter I was moving stuff around to make it easier to change in the future and to get rid of socat. According to NewRelic, there haven't been any problems since I finished that:
-
Here's a fun one:
The order of these posts changes. Originally loopback's post and my answer to it came after my post starting with the Git question on StackOverflow. As soon as I posted my reply to loopback's post, my longer post moved to the bottom of the thread magically.
Now that I've posted this I'm going to check-back to that Status thread to see if the post permanently moved to the wrong location, or if it was just a client-side thing.
EDIT: it was just a client-side thing.
-
@blakeyrat When I was reading that thread, your post with the Git question showed up about 70 posts from the end (42375 or so). As I was reading it it disappeared and I assumed it had been Jeffed.
-
@blakeyrat Bizzarre things seem to happen when it tries to stream posts in and you're not looking at the very last post. I've seen my post in a long thread (say, number 1,000) show up immediately after posts 1-10 when I scrolled up to reference something.
-
@tufty said in Blakeyrat pointing out NodeBB problems:
While we're on that, its "oh so clever" autoclosing of tags doesn't take into account actually closed tags.
That tag wasn't closed. No one is using XHTML any more.
<tag />
does not count as a closed tag. Deal.I agree with tag closing being annoying, but, on a general note, can we stop this XHTML thing already? It's not valid HTML5, never was, never will be. The browsers may tolerate it, but I don't. Stop writing broken HTML and expecting it to work!
Ok, I done with offtopic bitching, back to legit issues.
-
In HTML 4, <foo / means <foo> (which leads to
meaning
> and <title/hello/ meaning <title>hello</title>). Browsers did a very poor job of supporting this and the spec advises authors to avoid the syntax.
-
@Yamikuronue
Looks like according to the linked spec, writing<hr/>
is perfectly OK in HTML 5, after all!
-
https://what.thedailywtf.com/topic/19454/nodebb-updates/57
No human-readable changelog?
-
@blakeyrat major changes since the incremental stuff I've been applying:
- Your selection ignores leading and trailing spaces when applying bold/italics/whatever
- Global moderators can see the ⋮ icon on deleted posts
- The plugin updater only logs success after checking installed plugins, not before.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
Your selection ignores leading and trailing spaces when applying bold/italics/whatever
That's nice.
This is a sentence *used *for testing.
Nope. No worky.
-
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
@blakeyrat major changes since the incremental stuff I've been applying:
- Your selection ignores leading and trailing spaces when applying bold/italics/whatever
- Global moderators can see the ⋮ icon on deleted posts
- The plugin updater only logs success after checking installed plugins, not before.
Works for me. Maybe needs a refresh?
-
@ben_lubar Ok.
I refreshed then tested this again.
Oh weird. It didn't prompt me to refresh, I guess was the bug. I do refresh when it prompts me.
Still has some pretty stupid behavior, though. Look where the selection ended up after using the bold button on the word "prompts" there:
Also undo doesn't work with the Bold or Italics buttons. Or the keuybs**.
(That read "keyboard shortcuts" before I foolishly tried to undo a control-B.)
So once again, nobody fucking tested any fucking functionality. Sigh.
-
@blakeyrat would you like me to rewrite your browser so that undo works differently? I thought people didn't like when websites changed browser behavior.
-
@blakeyrat Testing the undo key, the undo key is control-z, nobody fucking tests anything at all, do ayty?
Wow. I can't even figure out what undo is doing. It's not simply undoing my typing while ignoring the asterisks, where did the Y come from?
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
would you like me to rewrite your browser so that undo works differently? I thought people didn't like when websites changed browser behavior.
Don't bullshit me, I know perfectly well that it's possible for a web app to modify a text field in such a way that undo still works correctly. I use like 5 web apps EVERY DAY that do it correctly.
I'm not as dumb as you think I am.
-
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
would you like me to rewrite your browser so that undo works differently?
I don't think this will require a rewrite. But yes, download Chromium and fix all it's annoyances for us.
when you finish with this you could make eclipse behave more like visual studio
-
@Onyx said in Blakeyrat pointing out NodeBB problems:
The browsers may tolerate it, but I don't. Stop writing broken HTML and expecting it to work!
1998 just called and said "awww, shit. That still happens?"
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Don't bullshit me, I know perfectly well that it's possible for a web app to modify a text field in such a way that undo still works correctly. I use like 5 web apps EVERY DAY that do it correctly.
Not modifying the text field should result in it working correctly. Ripping out the undo and replacing it with Frankenstein's monster to make it work correctly would be . You shouldn't have to do that; it's a signal that you're .
Anyway, Ctrl-Z appears to work perfectly fine for me. What did you do that it doesn't?
-
@anotherusername Hit Ctrl+B. Then hit Ctrl+Z.
-
@RaceProUK estst**
-
-
@anotherusername You can't see it, therefore it isn't an issue? Great logic there.
Tip: if both me and Blakey say something is a bug, then that's pretty much peer-reviewed-journal level proof it's a bug
-
@RaceProUK said in Blakeyrat pointing out NodeBB problems:
You can't see it, therefore it isn't an issue? Great logic there.
He didn't say that, he just demonstrated not being able to reproduce it.
-
Sometimes I visit those dumb "someone upvoted your comment" notification only to find that the post in question has no upvotes. WTF?
-
@blakeyrat they upvoted your post and then un-upvoted your post.
-
@ben_lubar Possibly, but wouldn't that remove the notification?
Also I'm pretty sure aliceif wouldn't do that.
-
@ben_lubar Or someone downvoted it.
-
@blakeyrat it doesn't because if it removed the notification you could get that notification again and that could be used for harassment.
-
@ben_lubar Whatever. I don't want the notification at all. "Harassment" would be strong, but "spam" is more accurate.
-
@blakeyrat it'd be much worse if they could make the notification sound go off thousands of times by unliking and liking a post.
-
@ben_lubar There's a sound?
Wait a minute, upvotes cause notifications and downvotes don't? WTF. Oh well, I don't give a shit about score. BenL program it to give all my posts -99 points.
-
@loopback0 Looks like I upvoted a post that had a score of -1.
-
@aliceif Mystery solved!
-
@ben_lubar Fucking Intercourse! I'ma kill em!
-
@blakeyrat It's too bad he didn't stick with that username past the migration.
-
The home page and threads load quickly.
My notifications are infinite spinner, either through the notifications menu or by going to the "view all notifications" page.
-
The "new topics" number needs a refresh before it changes.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
sound
Any website that makes a sound is
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
thousands of times
Isn't the a rate limit on this?
-
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
sound
Any website that makes a sound is
To be fair, it is an opt-in user setting.
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
thousands of times
Isn't the a rate limit on this?
Who do you think we are? Jeff?
-
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
Any website that makes a sound that isn't specifically designed to is
FTFY (Fixed that for Youtube) :D