Blakeyrat pointing out NodeBB problems
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
@blakeyrat did you even try to open the composer?
I guess I'm a stupid retardo who doesn't know how to open it without replying to something. Let me guess, there's some vaguely-geometric widget somewhere in a light-grey-on-slightly-darker-grey color-scheme with no tooltip?
LOOK! The bug is simple: I hit "back", I wasn't taken back to where I was before. SIMPLE. Do not make things more complicated than that. I can make it even simpler: Back button doesn't work. IT NO WORKY.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
I guess I'm a stupid retardo who doesn't know how to open it without replying to something.
It's amazing that people have trouble using things because they refuse to click the button that does the thing they want and is labeled the thing they want.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
It's amazing that people have trouble using things because they refuse to click the button that does the thing they want and is labeled the thing they want.
Screenshot the button labeled "open composer". I am too stupid to see it. Remember I'm an idiot dummy moron.
Of course your whole post is besides the point. The point is: THE BACK BUTTON DOESN'T FUCKING WORK!
-
@blakeyrat add this to your stylish:
[component="post/reply"]:after, [component="topic/reply"]:after { content: ' or open composer'; }
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
add this to your stylish:
I'll just choose to read that as, "I, Ben Lubar, was completely wrong and stupid when I said that there was a button in the UI labeled 'open composer', and I am deserving of all possible mockery for such statement. Also I am still too stupid to acknowledge that the real bug here is that the back button doesn't work."
-
@blakeyrat Do you want to reply or not?
-
@ben_lubar Ok: I don't use stylish.
I'm getting sick of people responding to my legitimate bugs with dumb workarounds.
Now go ahead and tell me how it's just perfectly fine hunky-dory that the Back button doesn't work! That's what people want man! You're just a clueless old loser to expect browser features to work!
-
@blakeyrat is the bug you're trying to report that the "reply" button's caption describes an action instead of the result of one of the steps in that action?
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
@blakeyrat is the bug you're trying to report that the "reply" button's caption describes an action instead of the result of one of the steps in that action?
No; the bug is, AS I'VE SAID LIKE 4 TIMES NOW, that the Back button doesn't work.
YOU'RE the one who brought up all the shit about the invisible magical "open composer" button. Not me.
-
@blakeyrat The drop zone for the image is small and has no visible borders.
It's a rectangle (about 140px × 180px) around the "Drag and Drop images here" text.
-
@Weng said in Blakeyrat pointing out NodeBB problems:
If I had a single large monitor perhaps I'd do things otherwise, but once you go multiple you don't go back.
I use two monitors at work. The only things I maximize are Outlook, which I leave on the secondary one, and most RDP windows. Everything else I prefer to run windowed.
-
@FrostCat said in Blakeyrat pointing out NodeBB problems:
I use two monitors at work. The only things I maximize are Outlook, which I leave on the secondary one, and most RDP windows.
I have two monitors at home, and the only things I maximize are videos and one Chrome window that has way too many tabs open; I can't find the tab I want unless I maximize it, then I restore it to normal size.
-
@aliceif how's the new CSS?
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
How about just right click -> Fuck You -> NodeBB Developers -> Your Product Is BROKEN SHIT!
Translation into Hu-mon: "Goddamnit I will suffer and make everyone else miserable rather than expend an iota of effort on workarounds!"
Having said that, there's all kinds of things need to be fixed. I bet @blakeyrat's alter ego doesn't like this when he posts on, say, Shamus Young's blog.
-
@boomzilla said in Blakeyrat pointing out NodeBB problems:
Now do your fox impression and imagine I said something else!
He already did. You even quoted him doing it.
I'm just reminding you because a person your age might've forgotten it in between hitting Reply and typing your reply.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
I'm getting sick of people responding to my legitimate bugs with dumb workarounds.
So are people.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
So my problem is solved except it's not solved at all? What the fuck are you talking about?
Do you ever briefly run out of outrage?
If you used Stylish to set that up locally, it'd be solved for you, but it can't be fixed properly until the NodeBB devs fix it in the product.
-
@FrostCat said in Blakeyrat pointing out NodeBB problems:
If you used Stylish to set that up locally, it'd be solved for you,
Except it wouldn't because I don't have a "locally", I use this site on tons of different PCs.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Except it wouldn't because I don't have a "locally", I use this site on tons of different PCs.
Sucks to be you, I guess.
I limit it to two, and I set up the rule on both. If I'm on a different machine I try to stay off this forum.
-
@ben_lubar Nah, I agree with this too. Pressing the back button should bring you to your previous state
-
-
OneBox plugin is still ridiculously broken and should be removed, and whoever asked for it to be put back should die in a fire because seriously
-
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.
-
-
Wow the flagging UI is broken. I guess hitting "offensive" is a submit button? WHICH MAKES THE DIALOG DISAPPEAR? Does my custom text get erased or submitted? I have no idea. There's no confirmation or anything.
If the "Spam" and "Offensive" buttons are submits, is the "Flag" button at the bottom a submit? Who fucking knows. Which of those buttons sends my text and which do not? Who fucking knows. Who designed this shitty UI? Oh I know the answer to that one: a moron.
This isn't NodeBB's problem but the "great" thing on this forum about trying to get the moderators attention to do something is that usually a moderator is the cause of the problem in the first place. Come on, Boomzilla, you should know better than to let my videos thread turn into a gun control debate. Seriously.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Come on, Boomzilla, you should know better than to let my videos thread turn into a gun control debate.
It's hard to distinguish topics when there is no topic title at the top
-
@Luhmann said in Blakeyrat pointing out NodeBB problems:
It's hard to distinguish topics when there is no topic title at the top
Strangely there is one in mobile view. (But it disappears when you scroll down, so you have to scroll up a notch to see it.)
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
@Luhmann said in Blakeyrat pointing out NodeBB problems:
It's hard to distinguish topics when there is no topic title at the top
Strangely there is one in mobile view. (But it disappears when you scroll down, so you have to scroll up a notch to see it.)
Or hope someone uses quoates
-
-
The topic title thing still doesn't work properly. I had to go to the top of the topic and back down for it to show in this one.
-
@loopback0 I fixed @barisusakli's fix.
-
@ben_lubar Ah - I misunderstood your previous update post.
-
@loopback0 hmm, even that isn't fixing it... Weird.
-
@ben_lubar well it seemed to be working for me, but I've just gone into a topic and it's not appeared.
-
@loopback0 it works on the initial page load, but not in some other case I haven't nailed down yet.
-
@ben_lubar I had to refresh and now I see the title. (64-bit linux chrome 49).
Oh, yeah...I said that and then I went to another topic and it disappeared.
-
hidden topic titles: worst feature ever.
even worse than...
-
NodeBB doesn't grey-out the Edit button, even for posts I don't have permissions to edit. (Specifically, a post I made that is over 1 week old.)
The error message for this is particularly stupid:
ERROR
You are only allowed to edit posts for 604800 second(s) after postingBut I'm kind of ok with the dumb error message, since if the error message ever appears to the user, that's obviously a bug somewhere else.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
604800 second(s)
Is there no middle ground between Discourse's overly eager rounding to large units and nodebb's love for seconds?
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Come on, Boomzilla, you should know better than to let my videos thread turn into a gun control debate.
It wasn't a gun control debate, you dummy. A couple of jokes were cracked.
I forgot for a moment which thread it was or I would've stopped sooner. You'll notice as soon as I read your complaint I asked to move the posts.
-
So, after all those many years of complaining about how broken Community Server was, the forum software has been changed, twice, and both them are worse than Community Server. I feel like I'm being trolled.
http://i.imgur.com/zvHA5Ay.jpg
-
@El_Heffe you're free to troll anyone here, except for our greatest troll. don't take on him
-
@El_Heffe We could still migrate to Telligent ...
-
Quality.
The avatar gets shrunk too tiny, but it's this:
-
@aliceif said in Blakeyrat pointing out NodeBB problems:
Is there no middle ground between Discourse's overly eager rounding to large units and nodebb's love for seconds?
I think it looks better as
ERROR
You are only allowed to edit posts for 0.01917808219* year(s) after posting
*0.01912568306 year(s) if it's a leap year
-
Error: forum noworky this morning, not even a nice error message. Instead I got plaintext reading this:
502 Bad Gateway
nginx/1.4.6 (Ubuntu)And then undoubtedly a long HTML comment present specifically because if those nginx people ain't gonna show a friendly error message than, by gummit, ain't nobody else gonna show one either! It's not good enough that our open source webserver is shitty and breaks all the time, it needs to actively sabotage other programs in the process!!! OPEN SORESSSSQ!!!
-
https://what.thedailywtf.com/topic/19634/why-tipping-is-a-scam/64
YouTube onebox plugin still INCREDIBLY broken.
And it's not turned off because...?
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
And it's not turned off because...?
It's better than not having it.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
breaks all the time
I've had nginx break precisely 0 times on me, and I don't think it's broken here at all either (although maybe it did under Discourse, who knows...).
But please, do continue your fact-free open soresssssq hate. Don't mind the facts or truth or anything bothersome like that...
Filed Under: What does 502 mean again?
-
@blakeyrat is it the one that doesn't fit the width on my phone screen, and instead of resizing just get cropped?
I'm all for disabling it too, all it's doing for me is causing more jellypotato.
-
I see this forum is running at super speed again. Loading the Recent page only took about 17 seconds. Zoom, whoosh, speed of light.
-
@blakeyrat I think the phrase you're looking for is something along the lines of
<sarcasm> much better performance than Discourse.
And I discovered a new bbhtmarkcode bug and some discodiscoverable behaviour posting that. Source was :
> <sarcasm> *much* better performance than Discourse
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Either fucking way, MY POST IS DELETED! THIS SHITTY SOFTWARE IS DELETING MY POSTS!
Finally the move has started paying off! Thank you, @julianlam and @ben_lubar, keep up the good work.