🗣 Things Our Customers Have Said About Discourse Thread
-
Different third, different first.
The :( screen is for all page transitions except topic views.
-
Different third, different first.
The :( screen is for all page transitions except topic views.
i do have to wonder..... whose bright idea was it to issue a 302 redirect to this link on certain errors?
i've landed on it a couple of times due to cooties and it always confuses me because the try again button just pops up a spinner for a while then reloads the page.... go back at least works, as do notifications once the cooties are past, but still why a 302 redirect?
-
why a 302 redirect
I suppose they tried a 602 YADIW response but most browsers are Doing It Wrongâ„¢ when processing that response code.
-
I love the 6xx error codes, my favourite continues to be 666 Evil Inside, though 665 Neighbour of the Beast is fun too.
Serious note: browsers generally treat 6xx however they treat 5xx codes.
-
-
I'd buy that for a dollar.
-
-
Not sure if whoosh.
-
-
i do have to wonder..... whose bright idea was it to issue a 302 redirect to this link on certain errors?
i've landed on it a couple of times due to cooties and it always confuses me because the try again button just pops up a spinner for a while then reloads the page.... go back at least works, as do notifications once the cooties are past, but still why a 302 redirect?
It's not a 302, it's a pushState() followed by replaceState(). The replaceState() wasn't supposed to happen, you're supposed to see the URL of the page you were trying to go to, but whatever. The "try again" does
transition.retry()
. So it's Ember stuff.
-
There should be an emoji for slope shoulders
-
-
Yeah. I get that. Virtually all actually good ideas have to be forced down people's throats against extreme resistance. Force of habit and institutional inertia is what keeps most things going.
<Cant be empty>
-
-
No other forum can fuck up a video being watched by a user who didn't refresh the page after someone added text to the bottom of their post.
<post is not empty>
-
Discourse seems like it's taking the principle of least surprise, and violently raping it in the back alley.
<not empty
-
@Maciejasjmj said:
Discourse seems like it's taking the principle of least surprise, and violently raping it in the back alley.
As evidenced by the random scroll 20-ish posts up-thread experienced when attempting to reply to this very post.
Filed under: Nobody expects the
Spanish InquisitionDiscourse jellypotato.
-
-
-
I'm going to assume that my image is the CLOSED_FIXED version of your image.
Ok, now that we know that what... why?
-
Ok, now that we know that what... why? Oh, wait, we are talking about Discourse. This explains everything!
Filed Under: FTFY
-
does your desktop browser tend to freeze for a second or two when you open a discourse tab?
FUCK THIS SOFTWARE
Â
-
Dammit, got to it before I did
-
-
-
Not yet, but lately there is a 50 / 50 chance when I click any button / control Discourse truffle shuffles to some random location with in the topic. I'm just waiting for it to drop me into another topic before I will allow myself to lose it
-
-
It's worse on mobile. On my iPad, I would be directed about 20 posts up from where I was supposed to be at least 75% of the time.
-
On my iPad, I would be directed about 20 posts up from where I was supposed to be at least 75% of the time.
Currently, Discourse seems to think it is funny to interpret my clicks to select a region to reply to as a command to scroll to the top of the thread by simulating a large stream of Page Up presses or something like that. Because seeing the first post in the slowest way possible is obviously relevant. In the Status thread, that's downright painful…
-
For bonus points, if I hit the address bar to select it, then press Enter, it would reload and 95% of the time then actually end up on the post I wanted it to go to in the first place.
-
Yes, this (or F5 or any equivalent) usually works. Occasionally Discourse serves up a second helping of jellypotato, but it's fairly rare.
-
for the record: this is why I'm really nervous about having a ServiceWorker deliver the initial page load
-
"Why does it still do this?"
The lower-right icon, while I didn't capture the tooltip, is also RPUK.
-
well, isn't that interesting....
-
note that Twitter also gets confused on avatars when you're updating them every 10 minutes. for more information, follow codl on twitter dot com
(ps yes it does update his profile colors)
-
Status: The fuck is this shit:
Warning: you have too many tracked new and unread topics, clear some using "Dismiss New" or "Dismiss Posts"
Since when does forum software complain that you are using it too much?
Empt'y cant be post
-
-
Discourse would be a lot better if it wasn't 30 crappy libraries frankensteined together.
-
-
Anyone have any background info about this fracas? I'm interested for... reasons....
-
He's lightyear on meta.d - there's nothing obvious that's public over there.
-
Basically he was one of the more prominent 3rd party discourse devs, and he posted, in a topic that Sam created about supporting 3rd party discourse development, that it didn't work out the way it was being suggested. The discussion went the way that meta.d discussions go when someone disagrees with a discodev. IMO, he handled himself pretty well, and the discussion ended reasonably peacefully, but then all the posts were jeffed the next day and the op edited by Sam to basically "our way or the highway" before the topic itself was completely jeffed. I actually grabbed most of the posts because I figured it would be jeffed eventually, but I was surprised it was gone the very next day.
-
Inquiring minds would love to know more.
-
Some idiot out there thinks this is a positive. He thinks it is a positive to run software that just fires off updates without even the barest of testing is a positive.
These are the kinds of people that run Discourse. The kind that don't realize that there is zero testing done and he is probably introducing more bugs in a month than his previous phpBB forum had EVER.
-
I actually grabbed most of the posts because I figured it would be jeffed eventually, but I was surprised it was gone the very next day.
Care to post them, for the rest of us to see?
-
These are the kinds of people that run Discourse.
@larsiusprime said:
I update my @discourse forum as many times per MONTH as I have updated my previous phpBB forum EVER. It's sooo much easier.
Is your sarcasm detector broken? Bolded the part that should have told you (or alternatively they weren't and are terrible communicators).
-
Is your sarcasm detector broken? Bolded the part that should have told you (or alternatively they weren't and are terrible communicators).
Well, now I am confused and think that the DiscoDevs sarcasm detector is broken also. I looked over the rest of his Twitter account and it seems to be mostly sarcasm, yet that tweet was retweeted by @discourse themselves, as that is where I found it.
If it was sarcasm, kudos to him for getting them to retweet it.
-
Is your sarcasm detector broken? Bolded the part that should have told you (or alternatively they weren't and are terrible communicators).
I don't think it's sarcasm. I think he's talking about the update process. Which I think is fairly automated (so long as nothing goes wrong, of course). I've no idea about phpBB.
-
I don't think it's sarcasm
OK, if it isn't something intended to be sarcastic then something like "It's SO much easier" gets the right kind of emphasis across much better than dragging it out which implies a very different kind of speech.
But it would explain @discourse retweeting it.
-
I don't see any major difference between the two ways of emphasizing there. Either could be sarcastic or not to my mind.