Blakeyrat pointing out NodeBB problems
-
This post is deleted!
-
@fbmac except that in this case, it's a really good product...
-
When you go to edit a post, then cancel that edit, the caption in the confirmation dialog is, "are you sure you want to discard this post?" when it should be "are you sure you want to discard these edits?" or something equivalent.
Taken literally, I'd never hit "yes" because when I'm editing a post OF COURSE I DON'T WANT TO DISCARD THE POST WHAT KIND OF A FUCKING STUPID QUESTION IS THAT, WHO WROTE THAT DIALOG AN UTTER MORON IDIOT?!
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
When you go to edit a post, then cancel that edit, the caption in the confirmation dialog is, "are you sure you want to discard this post?" when it should be "are you sure you want to discard these edits?" or something equivalent.
Taken literally, I'd never hit "yes" because when I'm editing a post OF COURSE I DON'T WANT TO DISCARD THE POST WHAT KIND OF A FUCKING STUPID QUESTION IS THAT, WHO WROTE THAT DIALOG AN UTTER MORON IDIOT?!
-
@boomzilla Oh right, I'm insane and illiterate for pointing out obvious bugs in products. Forgot for a second.
Thanks for contributing to this thread.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Thanks for contributing to this thread.
Happy to help.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
@boomzilla Oh right, I'm insane and illiterate for pointing out obvious bugs in products.
Are you purposely whooshing the meaning ?
hint: it is about your overly aggressive ^ n tone in commenting nodeBB bugs
I'm glad that apparently the nodeBB devs don't squirm through this forum except when invoked with the '@' incantation.
-
@cabrito It's not overly aggressive. Some dude set out to write the copy in that dialog and didn't do his fucking job. It's exactly as aggressive as it should be IMO.
If you don't want to be yelled at for having stupid bugs even a 5 year old could identify, don't have stupid bugs even a 5 year old could identify.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
It's exactly as aggressive as it should be IMO.
-
@anotherusername said in Blakeyrat pointing out NodeBB problems:
whether they're read or unread
I've said this before and I'll say it again. This is a stupid, stupid, dumb, idiotic design. Once I've read a notification, I DON'T NEED TO SEE IT ANYMORE. Keeping those 10 slots filled with notifications I've already acted up defeats the entire purpose of having a quick-access limited-info notification area.
Then again that is the theme for NodeBB overall: Information density is abysmally low. User interaction cues are non-existent. Everything is laid out jumbled, haphazard, inconsistent, non-discoverable. Every UI element is "flat" so there are no borders or alignment to partition information.
I've put in several stylish styles to make it sane, but there's somethings a client-side css can't fix.
AND EVERY REPLY BOX STILL HAS THAT GODDAMN RED BOOB USELESSLY TAKING UP SPACE!
-
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
AND EVERY REPLY BOX STILL HAS THAT GODDAMN RED BOOB USELESSLY TAKING UP SPACE!
Just think of all the useful things you could do with ALL THOSE PIXELS!
-
@loopback0 said in Blakeyrat pointing out NodeBB problems:
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
AND EVERY REPLY BOX STILL HAS THAT GODDAMN RED BOOB USELESSLY TAKING UP SPACE!
Just think of all the useful things you could do with ALL THOSE PIXELS!
-
@Lorne-Kates Why has your red boob had an enlargement? What browser are you running?
-
@RaceProUK said in Blakeyrat pointing out NodeBB problems:
Why has your red boob had an enlargement?
Yeah, nurse that kid already!
-
@RaceProUK said in Blakeyrat pointing out NodeBB problems:
@Lorne-Kates Why has your red boob had an enlargement? What browser are you running?
Some obscure little browser called Firefox.
CSS is hard, apparently.
http://i.imgur.com/stAhYI6.png
.taskbar .navbar-nav li a { animation-duration: 1s; animation-fill-mode: both; animation-name: bounceIn; border-radius: 50% 50% 50% 50%; font-size: 13px; height: 50px; padding: 3px 15px; width: 50px; }
Also, opeing up Firefox makes the page go into a quas-mobile view. I can't see what I'm typing right now. By "firefox" i meant firebug, ie a docked window taking up a bit of vert space.
-
@Lorne-Kates Firefox supports all those CSS properties properly though, so fat the whuck is going on?'Cause I ain't got a clucking fue.
-
@Lorne-Kates FF on the left, Chrome on the right:
-
Is
box-sizing: border-box;
supported by Firefox?
-
@Lorne-Kates AH! You have
box-sizing: content-box
. Is it being set by some plugin? It should bebox-sizing: border-box
.
-
-
@RaceProUK hmm... @Lorne-Kates, are you using a version of Firefox before 29?
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
@RaceProUK hmm... @Lorne-Kates, are you using a version of Firefox before 29?
What was the last one that ran on OS/2 Warp, or whatever OS he's using?
-
@loopback0 said in Blakeyrat pointing out NodeBB problems:
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
AND EVERY REPLY BOX STILL HAS THAT GODDAMN RED BOOB USELESSLY TAKING UP SPACE!
Just think of all the useful things you could do with ALL THOSE PIXELS!
I could actually use the scroll bars on the preview:
-
Medium.com onebox also does DoS spam while you're typing your post. Thus says this insane and illiterate person.
I guess that was fixed only for YouTube? Because that makes more sense than fixing every site simultaneously.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
@RaceProUK hmm... @Lorne-Kates, are you using a version of Firefox before 29?
22, the last non-retarded version I would tolerate.
And hey, look at this:
<a style="background-color: red; position: absolute;height:50px;width:50px;display:block;right:0px;top:0px;color:white;text-align:center;font-weight:bold;font-size:2.5em;line-height:1.4em;border-radius:25px;z-index:99999">+</a>
http://i.imgur.com/FNNF20A.png
In 15 seconds I was able to make it work even in my "ancient" browser using "old" techniques. But no, let's reinvent the wheel for a shitty piece of UI that interferes with user input and has absolutely no useful purpose other than RED BOOB.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
I guess that was fixed only for YouTube? Because that makes more sense than fixing every site simultaneously.
Yes and yes. I won't bore you with details you're not interested in.
-
@boomzilla We need to turn off that plugin or feature until it works. Seriously.
DoSing other sites makes us into an asshole site, we're fucking malware until that bug is fixed.
-
-
@boomzilla It's indistinguishable from an actual denial of service attack, yes.
The intent isn't present, but their network intrusion system doesn't have a function to measure "intent". All it sees is, "this asshole is DoSing me!"
-
@blakeyrat Wait a minute. Did you...make your browser bigger?
-
@boomzilla I have a different monitor setup at work.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Oh right, I'm insane and illiterate for pointing out obvious bugs in products.
No, that's not why.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
It's exactly as aggressive as it should be IMO.
And do you do this with your coworkers?
-
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
absolutely no useful purpose other than RED BOOB.
Isn't that enough?!
-
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
[Firefox] 22
-
Mousing over a block of text in the chat view causes some widgets to appear on the right. This has two problems:
-
Touchscreen interfaces (whether mobile or desktop or whatever) don't have a concept of "mouse over", so those features are invisible to them
-
It causes the text in the post to reflow which is extremely weird and distracting when you're just trying to use the UI
-
-
Then why is the dialog still there, you piece of dog ass shit?
-
@blakeyrat how do you know I'm not one of your alts?
-
It's impossible to type *) without it turning into this retarded smiley. (That's an
*
followed by a)
) Trying to "escape" either character with a backslash does nothing.
-
@blakeyrat
*)
?
-
@PleegWat Fuck off, you know what I mean.
Explain to me why
*\)
shouldn't "break" the smiley match. Why are we turning *) into a smiley anyway? What fucking emotion is that supposed to represent? Being a douche?
-
@blakeyrat It's
:wink:
. I agree the discourse way of breaking with backslashes was handy, but in most cases if you type combinations like that you want code anyway?Also *) works. (That's
*­)
).
-
@PleegWat said in Blakeyrat pointing out NodeBB problems:
. I agree the discourse way of breaking with backslashes was handy, but in most cases if you type combinations like that you want code anyway?
No, I was using a footnote. Why the fuck would
*)
necessarily be code? That's a very common way of denoting footnotes.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
It's impossible to type without it turning into this retarded smiley. (That's an * followed by a )) Trying to "escape" either character with a backslash does nothing.
*) might not be impossible in some states.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Mousing over a block of text in the chat view causes some widgets to appear on the right. This has two problems:
-
Touchscreen interfaces (whether mobile or desktop or whatever) don't have a concept of "mouse over", so those features are invisible to them
-
It causes the text in the post to reflow which is extremely weird and distracting when you're just trying to use the UI
I pointed that out a while ago (in the midst of the Ben-planning chat). Glad to know horrible UI and UX cues are still the norm.
-
-
*) might not be impossible ever
-
@Lorne-Kates The NodeBB chat stuff needs to die. Somehow discourse mostly got it right, except that you couldn't get to your damn PM section if you had a large amount of posts and stuff because you couldn't reliably get to your profile without timing out on the server.
Somehow their laziness overcame their urge to be clever shedders and they just reused most of the infrastructure they already had for written communication.
-
@boomzilla said in Blakeyrat pointing out NodeBB problems:
The NodeBB chat stuff
Works for its intended purpose, which is basically an in-forum IRC-style chat. It's no substitute for private messages, but then I don't think it's meant to be.
-
@RaceProUK said in Blakeyrat pointing out NodeBB problems:
@boomzilla said in Blakeyrat pointing out NodeBB problems:
The NodeBB chat stuff
Works for its intended purpose, which is basically an in-forum IRC-style chat.
Which doesn't work for the actual needed purpose: a private discussion.
With the chat, I can't view history, bookmark, like or link to any particular chat, search the chats, and I also STILL can't figure out the UI of the /chat page.
I mean, it'd be great if NodeBB already had a pre-built way for users to have asynchronous, chronological, full-featured discussions-- maybe like some sort of "forum" that they could re-use the logic of, but just with the addition of making the messages private. I don't know if NodeBB includes that sort of discussion feature. Does it?
-
@Lorne-Kates Short of getting Ben to set up private categories, not yet. And yes, I want proper PMs as much as anyone else.