Blakeyrat pointing out NodeBB problems
-
@Polygeekery said:
Case in point, the browser zoom bullshit.
What bullshit? It's a valid bug. It's making the site extremely difficult to use on my laptop RIGHT NOW THIS INSTANT.
-
@blakeyrat said:
it's still broken that turning on zoom makes the width WIDER. For me it's not 992 pixels, it's more like 1200. Which is RIDICULOUSLY wide for a browser.
Do you even know how browser zoom works? Also, FFS, your problem was that you were running browser zoom while also not running your browser in full screen.
Learn how Stylish works and use it instead. Devs cannot design specific to each person. Change the site to suit your needs if necessary.
-
@Polygeekery said:
That may solve the problem, but it also falls under "unsolicited advice"
I don't have insane shoulder aliens, so I'm not opposed to the principle of unsolicited advice, because sometimes, you get some that's good (or so I presume in this case, since I don't use FF).
-
@Polygeekery said:
If everyone did only that...why the fuck have forums?
I guess there's no reason at all. Now that you've realized that, you can leave this one and never come back.
-
@blakeyrat said:
I guess there's no reason at all. Now that you've realized that, you can leave this one and never come back.
No. I am not the one who is ranting and raving about how we should not discuss things on a discussion forum. Because I am not fucking retarded.
-
@Yamikuronue said:
Oh yeah, FYI, @blakeyrat don't kill yourself, your cat would miss you.
He's not going to kill himself, this is just a ploy, like the time he trial-ballooned calling me a stalker. Remember that the guy accusing others of being stalkers is still gratuituously insulting RaceProUK to this day for an argument over a year ago.
-
@blakeyrat said:
It's a valid bug.
The zoom thing is that it doesn't actually show on the page what it's navigating to? I was looking into that bit of the code, because it seems odd that it always shows down towards the bottom (in my unzoomed experience). I'd expect it to be up top, which makes more sense, and should work zoomed or unzoomed.
I think there maybe an offset involved, but I haven't gotten fully to the bottom of it.
-
@boomzilla said:
But I've never claimed to be some crack QA person. Or even really a "web" developer.
That's exactly what you just tried to disagree with me on!
Me: "Nobody's responsible for QA"
You: "Nuh-uh!"
Me: "What about (thing that obviously wasn't QAed)
You: "Well I'm not a QA person"You're just talking in circles.
-
@boomzilla said:
The performance didn't seem to be a problem like it was with Discourse, so it didn't seem to be an issue.
To be fair, reloading the linked thing on every keypress is not really a good thing.
-
@FrostCat said:
He's not going to kill himself
I don't like to leave even idle threats out there without a counter, just in case. It can be... no, you know what, there's no end to this sentence that doesn't end up with me being mocked or reviled, so call it a personal quirk.
-
@blakeyrat said:
It's a valid bug.
Deliberately-designed behavior is never a bug. Doesn't the underside of your bridge miss you?
-
@boomzilla said:
When you start discussing a topic, people are going to discuss it.
See now I suspect you're being dense on purpose, like you usually assume I'm doing. But in case you're not:
Discussion != unsolicited advice
-
@blakeyrat said:
See now I suspect you're being dense on purpose, like you usually assume I'm doing. But in case you're not:
Discussion != unsolicited advice
This is getting painful. You are the Hispanic chick from "White Men Can't Jump".
-
@Polygeekery said:
Also, FFS, your problem was that you were running browser zoom while also not running your browser in full screen.
Those are two UTTERLY unrelated features. Is there some kind of implicit assumption that if I'm doing one, I'm also doing the other? Why?
-
@blakeyrat said:
That's exactly what you just tried to disagree with me on!
No. You said that no QA at all was done. Which is obviously wrong given the number of issues that have been filed (mostly after the switch, but not entirely). I'm saying that while I can certainly find some issues, my domain knowledge of things web related isn't anything like comprehensive, and anyways, no one is claiming that any sort of exhaustive testing has been done here on TDWTF.
The YT problem, from my POV, was performance, which didn't seem to be a problems with the combination of iframely and the composer. I certainly wasn't worried about a DoS of fucking youtube!
-
@Polygeekery said:
Learn how Stylish works and use it instead.
Actually, the thing NodeBB does when you narrow your window is not the most intuitive. I'd rather see the site do what every other website does, which is drop the preview area under the composer area, rather than switch to mobile view.
Since I'm not an asshole like @blakeyrat, I won't say it's retarded behavior or pretentiously call "things that don't work the way I want them to" a bug, but it's not the best way of doing things.
-
@Polygeekery said:
Learn how Stylish works and use it instead. Devs cannot design specific to each person. Change the site to suit your needs if necessary.
The mobile mode thing can't be fixed, as Ben L told me, it's all implemented in CSS. There's no way to override the behavior.
-
@Yamikuronue said:
no, you know what, there's no end to this sentence that doesn't end up with me being mocked or reviled, so call it a personal quirk.
Well, then I can be mocked or reviled with you. I will leave it out there also...blakey if you need or want human help with your depression we can set aside whatever-the-fuck our differences are and anyone here will help you with your depression and suicidal tendencies. The offer is there, if you want help.
-
@Polygeekery said:
I am not the one who is ranting and raving about how we should not discuss things on a discussion forum. Because I am not fucking retarded.
But you do think discussion and unsolicited advice are the same thing.
-
@blakeyrat said:
You're just talking in circles.
Truly, you have a dizzying intellect.
"I really like this site because I come back every day for a heaping helping of abuse, but if I helped offer this thing others have told me is called 'constructive criticism', then the site might get fixed and I would have to come up with a new excuse to be an asshole to everyone."
-
@boomzilla said:
The zoom thing is that it doesn't actually show on the page what it's navigating to?
There's a LOT of zoom-related bugs, and we've added a new one just today or yesterday. (By highlighting "go to" posts with an underline instead of a border, you virtually guarantee the underline will be outside the window every single time. Unless it happens to be the bottom-most one.)
-
@Yamikuronue said:
I don't like to leave even idle threats out there without a counter, just in case. It can be... no, you know what, there's no end to this sentence that doesn't end up with me being mocked or reviled, so call it a personal quirk.
I'm not going to mock you at all for it! Normally you'd be right. Occam's Razor, however, suggests that in this case, what might normally be a cry for help is probably just another troll tactic. It's not as if people haven't done it before.
Besides, what you did is probably "unsolicited advice" anyway, and we all know how Voldemort feels about that.
-
@boomzilla said:
I certainly wasn't worried about a DoS of fucking youtube!
Well you're certainly correct when you say you're not a QA person, because that was the MOST IMPORTANT ISSUE of the previous implementation and the FIRST thing that should have been tested.
But fine. Sure. There has been some QA. Like maybe 1/50th the amount there should have been. Conceded.
-
@boomzilla said:
I certainly wasn't worried about a DoS of fucking youtube!
What about a soi-disant DoS of the Supreme Court website?
I mean, it's not actually a YT issue per se--any linked site that can get oneboxed will get hammered. Crankyrat's right that iframely isn't ready for prime time because of that misfeature.
-
@blakeyrat said:
The mobile mode thing can't be fixed, as Ben L told me, it's all implemented in CSS. There's no way to override the behavior.
In my limited experience with Stylish, you can, in fact, override CSS.
I don't know enough about the guts of NodeBB to know if that's true in this case. In any event, I wouldn't want to suggest you try and see if you can do it, because that'd be unsolicited advice.
-
@blakeyrat said:
But you do think discussion and unsolicited advice are the same thing.
Shoulder aliens!
Note I'm not acting like you and calling you a liar.
-
@FrostCat said:
I mean, it's not actually a YT issue per se--any linked site that can get oneboxed will get hammered. Crankyrat's right that iframely isn't ready for prime time because of that misfeature.
Yeah, obviously this is an issue. But I assumed it would be pulling stuff from cache and that it was a performance problem, not a DoS problem. In fact, it took a while before those extra network requests were even showing up in my browser tools, so from all appearances, it was pulling from cache and there was no observed potential for DoS.
-
@boomzilla said:
But I assumed it would be pulling stuff from cache and that it was a performance problem, not a DoS problem.
In hindsight, you can usually tell something's not coming from cache by observing the behavior. A PDF (for example) that's coming from cache should render instantly. If you can see it pop in and then render, it's probably not coming from cache.
Regardless, the fact that the content is apparently being created and destroyed with each keystroke, as evidenced by the way it keeps appearing and disappearing seems highly non-optimal! But since I don't do a lot of front-end web stuff I don't keep up with the technology.
-
@FrostCat said:
In hindsight, you can usually tell something's not coming from cache by observing the behavior. A PDF (for example) that's coming from cache should render instantly. If you can see it pop in and then render, it's probably not coming from cache.
Right, but it seemed pretty smooth when I was testing it. And even my tooling said it wasn't coming across the network!
-
@FrostCat said:
I don't know enough about the guts of NodeBB to know if that's true in this case.
Nor do I. Nor do I want to spend my time learning this shit just to work around their bug. It's their bug, not mine.
-
@boomzilla said:
Right, but it seemed pretty smooth when I was testing it. And even my tooling said it wasn't coming across the network!
Well clearly you're a stupid poopyhead who should've known you hadn't tested it enough, and then found and fixed the bug in this shitty open sores software!
-
@FrostCat said:
I don't have insane shoulder aliens
And a majority of my shoulder aliens claim to be sane!
-
@blakeyrat said:
I already told** Ben L over *chat, but the security cert for forums.thedailywtf.com domain is invalid.
....Ben Lover?
-
@blakeyrat said:
Ok if people (moderators no less) are going to just turn this thread into trash so early, nevermind.
NodeBB is perfect, there are absolutely no flaws, Blakeyrat is just a super mental idiot moron dumbshit for not instantly getting it or telepathically knowing that the window size dictates whether or not you get a full-screen editor.
The term used in England is "mental midget".
-
@blakeyrat said:
Nor do I want to spend my time learning this shit just to work around their bug. It's their bug, not mine.
Well, not that this is advice or a suggestion, mind, because heaven forbid someone give you same unsolicited and you run the risk of finding your day minimally improved, but if I frequent a site and the font's too small, I spend a couple minutes in the inspector seeing if I can adjust the CSS to make the text bigger, or not fucking grey on grey in some twee font because I hate everyone whose life-crystal's gone red, and if I can fix it, I'll spend another couple minutes in Stylish trying to make a rule to apply my fix. And then, especially if it's a site I read every day, my reading experience is improved every day from then on.
But you should keep suffering and not try to improve your own UX. All those other assholes should just know they're making your life miserable.
Especially don't go tell them, either.
-
@Nagesh said:
The term used in England is "mental midget".
See? There we go, this is the kind of thing I'm looking for.
-
@FrostCat said:
ut if I frequent a site and the font's too small, I spend a couple minutes in the inspector seeing if I can adjust the CSS to make the text bigger,
You can do what you like.
I just hit control-+ a couple times.
I personally think my way's easier.
-
@blakeyrat said:
I just hit control-+ a couple times.
Oh, that fixes light grey on grey text, and eliminates stupid font choices by the web designer? Awesome!
-
@FrostCat said:
Oh, that fixes light grey on grey text, and eliminates stupid font choices by the web designer? Awesome!
In those cases, I simply don't visit the site. They obviously didn't want readers, so why not make them happy?
-
It's stupid that to "mark all as read" in the unread posts page you have to scroll back to the top of it. You can't mark all as read after scrolling down to take a look at all the thread titles.
-
@Yamikuronue said:
To be fair, this is a problem I have in real life. A friend will say something like "OMG I hate my car, it can't drive in snow!" and I start explaining how they can pump the brake pedal to regain traction when all they actually wanted was a place to vent.
That's fine occasionally, but if a friend of mine continually vented and never wanted any advice on how to improve things, I would make a point of spending as little time with them as possible.
-
@antiquarian Pretty sure that one version of that arrangement is called a wife?
-
@darkmatter said:
Pretty sure that one version of that arrangement is called a wife?
Which is just one more reason that I don't have one.
-
@blakeyrat said:
It's stupid that to "mark all as read" in the unread posts page you have to scroll back to the top of it. You can't mark all as read after scrolling down to take a look at all the thread titles.
This is I where I agree with you. "Mark all as red" should be at the bottom.
-
@Nagesh said:
This is I where I agree with you. "Mark all as red" should
be at the bottomalways be visible.FTFY.
-
@Tsaukpaetra said:
@Nagesh said:
This is I where I agree with you. "Mark all as red" should
be at the bottomalways be visible.FTFY.
Always visible is annoying.
-
@Nagesh said:
Always visible is annoying.
Any more annoying than always visible post actions?
What about an always visible bar at the top with buttons you're probably going to rarely use?
-
@Tsaukpaetra said:
@Nagesh said:
Always visible is annoying.
Any more annoying than always visible post actions?
What about an always visible bar at the top with buttons you're probably going to rarely use?The bar is very much usable. I am always clicking on it "baar-baar"
-
-
@Tsaukpaetra "Access to the Web page you are trying to visit has beer"? And they're blocking it? How cruel!
