Blakeyrat pointing out NodeBB problems
-
@darkmatter NOtifications.
-
Nice notification there.
-
@darkmatter said in Blakeyrat pointing out NodeBB problems:
it sent me a notification telling me that you responded, and a "1" very briefly appeared in the box.
so notifications only seem to be very partially neutered.We seem to have different experiences of what part is neutered. For me, the number in the red box (sometimes) increments when the toaster pops up, but it refuses to tell me what the notifications are.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
You did not agree with me that it was a bug. You "explained" it away by saying that notifications are off, without bothering to engage enough neurons to realize that if notifications really are off showing me the red 1 is a goddamned bug.
You toxic fucking moron.
@darkmatter said in Blakeyrat pointing out NodeBB problems:
that you entirely forgot what it's like to have someone agree?
Something like that.
-
@ben_lubar disabled the part of the code that returns the notification list as it seemed to be causing the cooties.
Now you're in the loop.
-
@HardwareGeek said in Blakeyrat pointing out NodeBB problems:
increments when the toaster pops up, but it refuses to tell me what the notifications are.
now mine are doing that too. if i stumble onto something that was a notification, it apparently triggers the cleanup too... so I had 5 at one point. now i'm back to 2. previously I was already in the topic that the notification came from, so it just went to 1 and then back to none immediately thereafter.
it's a notifications scavenger hunt game now. or i could just mark them all as read.
-
@darkmatter Please see previous post.
-
Preview is busted.
> try > > this
try
this
In the preview, there's no blank line between "try" and "this", in the published post there is.
-
Can repro:
-
Gosh. It's almost as if relying on unnecessary javascript shenanigans to make your forum system "modern" not only breaks usability and accessibility, but also fucks stability up the asshole.
After our experience with Discourse, who could possibly have predicted that?
-
So now the forum runs like crap and I have no notifications. This is definitely forward motion. Maybe in a couple days we can get it to spit out Nazi slogans sometimes in addition to that.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Maybe in a couple days we can get it to spit out Nazi slogans sometimes in addition to that.
If it can stay up for long enough.
-
Given what it does to my CPU when I switch to the tab "running" it, may I suggest
Arbeit macht cooties
-
https://www.youtube.com/watch?v=PGNiXGX2nLU
I'd say watching this forum trying to load a thread reminds me of this song, but the problem is the song is only about 3:15 long and the forum's spinner can go an order of magnitude longer than that.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
EDIT: you're also making the strong assumption that "advanced' users keep their browsers maximized all the time, and "naive" users do not, which is a crazy bullshit assumption to be making and almost certainly DEAD wrong.
In my experience, it's generally the opposite. Newbs and people who aren't comfortable with computers want everything full-screen, and they then laboriously navigate via the taskbar their 5 Excel windows, 8 Word ones, a web browser, etc., etc.
-
@FrostCat I like my stuff maximized. My main workspace monitors get one bigass window each. And then there's the "distractions" monitor, which gets everything else.
If I had a single large monitor perhaps I'd do things otherwise, but once you go multiple you don't go back.
-
@Weng That reminds me; I really need to get a second monitor at work
-
@tufty said in Blakeyrat pointing out NodeBB problems:
Gosh. It's almost as if relying on unnecessary javascript shenanigans to make your forum system "modern" not only breaks usability and accessibility, but also fucks stability up the asshole.
Except not, apparently. Looks like it was an issue with I/O and the server we had provisioned.
-
@blakeyrat You could always replace the spinner with an embed of meatspin․com. That's got an endless loop of dead or alive, and, as a bonus, will offend pretty much everyone apart from @Fox.
-
@boomzilla So turning off notifications was turning stuff off randomly, and the fact it temporarily stopped the problem was just fortuitous, then?
-
@tufty Not that I'm aware. IIRC it was just a squeaky wheel of I/O at the time. @ben_lubar had been looking for
socket.io
stuff that was taking a long time and that bit stood out.
-
@Weng said in Blakeyrat pointing out NodeBB problems:
My main workspace monitors get one bigass window each. And then there's the "distractions" monitor, which gets everything else.
I do this too.
-
Goddamned, I thought notifications were turned back on. NOW why the fuck are they off?
-
@Weng said in Blakeyrat pointing out NodeBB problems:
@FrostCat I like my stuff maximized. My main workspace monitors get one bigass window each. And then there's the "distractions" monitor, which gets everything else.
That's great. The problem is if you maximize this app, the paragraphs become super-fucking-wide and nearly impossible for me to track my eye across.
Yes, yes, go ahead and tell me how I'm a stupid idiot for not being able to read wide paragraphs, lalala.
AND the font is super-small. Fortunately if I zoom in the font becomes bigger, but to get a big font and paragraphs that aren't a half-mile long, the only solution is to resize the window so it's in mobile-mode.
I mean goddamned, Discourse got like 50,000 things wrong, but even they got "don't make your paragraphs a half-mile long" correct.
-
@blakeyrat Oh and about a minute after I posted that, they just magically turned back on. Whee. Yo-yo them right up and down. Who needs "reliability", it's for sucks.
-
-
This post is deleted!
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
The problem is if you maximize this app, the paragraphs become super-fucking-wide and nearly impossible for me to track my eye across.
QFT. I complained about this on Ben's test forum, seems like no one else gives a shit.
-
@blakeyrat Or you could use Firefox with NoSquint, which gets you independent text and overall zoom remembered per-site.
NoSquint does nothing you couldn't also do with Stylish, but it does fix 90% of what my eyeballs find to complain about on the Web without needing to roll my own CSS.
-
@blakeyrat Good point. I do like 99.95% of my foruming from mobile, so I didn't notice.
However, the alternative is setting a maximum width, which leaves giant white bars everyone likes to complain about. Or columnar layouts, which no actual human being is capable of using. Or resizing text to hilarious sizes, which is clearly stupid.
-
This post is deleted!
-
@Weng said in Blakeyrat pointing out NodeBB problems:
However, the alternative is setting a maximum width, which leaves giant white bars everyone likes to complain about. Or columnar layouts, which no actual human being is capable of using. Or resizing text to hilarious sizes, which is clearly stupid.
Or simply not putting my desktop computer in tablet mode, simply because I used the "zoom" feature of my browser.
That's all I've ever asked for.
-
Fuck this broken shit:
Even if I resize the composer AS HIGH AS IT GOES it still refuses to draw a scrollbar and let me see what I'm typing.
Do you think maybe a single feature here could have had maybe 57 milliseconds of QA before being released? FUCK this broken-ass shit.
Why the fuck is EVERYTHING broken ALL THE TIME. I'm just trying to enter text into a webpage. Somehow I managed to do that in fucking 1997 without major problems.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Why the fuck is EVERYTHING broken ALL THE TIME.
Technical debt comes with a punishing interest rate.
-
@blakeyrat Just right click -> inspect element -> overflow:auto
-
@JazzyJosh said in Blakeyrat pointing out NodeBB problems:
@blakeyrat Just right click -> inspect element -> overflow:auto
How about just right click -> Fuck You -> NodeBB Developers -> Your Product Is BROKEN SHIT!
-
@NedFodder said in Blakeyrat pointing out NodeBB problems:
I complained about this on Ben's test forum, seems like no one else gives a shit.
CBA to find where I originally posted it now, but I've added this to stylish:
div .content { max-width: 100ex; }
There are actual built-in ways to select skins and styles. Not sure what the best way to include something like that would be or even the mechanism for updating that stuff (nothing obvious in the admin area).
You may recall that we had a widescreen version on discourse, though it wasn't the default.
-
@blakeyrat Did you miss your
I agree, that's broken as shit.
-
@JazzyJosh said in Blakeyrat pointing out NodeBB problems:
I agree, that's broken as shit.
Then stop fucking defending it as if it's all ok that nothing here fucking works right.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
it's all ok that nothing here fucking works right.
Lots of stuff works right for me. Now do your fox impression and imagine I said something else!
-
@boomzilla said in Blakeyrat pointing out NodeBB problems:
max-width
That was literally the very first thing I did when I installed stylish. Blakey's right, it's ridiculously bad UX to have text blocks wider than that. This needs to be fixed in the core CSS, not just on our site. (I CBA to get a github account or I'd raise the issue myself.)
-
@boomzilla said in Blakeyrat pointing out NodeBB problems:
CBA to find where I originally posted it now, but I've added this to stylish:
And that does... what?
-
@blakeyrat You're trying to fix a concrete problem in a single use case, for which the correct answer is a "fuck you give me desktop" setting, which my bootstrap guy tells me shouldn't even be hard. So that problem is now solved, aside from the actually getting someone to care enough to implement it.
I've moved on to philosophizing over the generalized problem of responsive UI. Nobody likes defined maximums because they're ugly. Unbounded maximums are also ugly.
-
@Weng said in Blakeyrat pointing out NodeBB problems:
@blakeyrat You're trying to fix a concrete problem in a single use case, for which the correct answer is a "fuck you give me desktop" setting, which my bootstrap guy tells me shouldn't even be hard.
Ok...
@Weng said in Blakeyrat pointing out NodeBB problems:
So that problem is now solved, aside from the actually getting someone to care enough to implement it.
So my problem is solved except it's not solved at all? What the fuck are you talking about?
@Weng said in Blakeyrat pointing out NodeBB problems:
I've moved on to philosophizing over the generalized problem of responsive UI. Nobody likes defined maximums because they're ugly. Unbounded maximums are also ugly.
I don't want philosophy, I just want readable text. Christ.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
@boomzilla said in Blakeyrat pointing out NodeBB problems:
CBA to find where I originally posted it now, but I've added this to stylish:
And that does... what?
It solves the issue for me of post text stretching across the page.
@Weng said in Blakeyrat pointing out NodeBB problems:
"fuck you give me desktop" setting, which my bootstrap guy tells me shouldn't even be hard
How not hard? Did he give any specifics? CSS / responsive design / bootstrap ain't my thing, so I'd be interested to hear how, even in general terms.
-
@blakeyrat I may be turning into a manager. Weep for my branez.
-
@blakeyrat I was never defending it
-
@boomzilla Why would he give specifics, I'm damn near a manager. I'll ask.
-
Tried to add an image to a post by drag-and-dropping. The browser instead navigated to the image file, and my post was lost forever because the "back" button didn't have the composer open.
Seriously. This is almost as bad as the Discourse "one new bug per-post" golden standard!
And of course when I try it now, it works fine. So it apparently just happens randomly? Either fucking way, MY POST IS DELETED! THIS SHITTY SOFTWARE IS DELETING MY POSTS!
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
my post was lost forever because the "back" button didn't have the composer open
Oh no! I wrote something in my notebook and then when I closed it I couldn't see the stuff I wrote because it wasn't open!
@blakeyrat did you even try to open the composer?