:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
>395 enhancements
I could also tell you how many UX tweaks we’ve gone through (204)
Since the "UX tweaks" are listed independently of the "enhancements," I infer that none of the UX tweaks actually enhanced Discourse.
-
-
1265 bugs got squashed
But how many got the Jeff treatment?
Well, banning all of TDWTF also jeffhole'd their bug reports. Which is every bug we've ever reported. So 1265-- actually seems way too low.
-
The @aliceif way:
a.mention { animation: omgrainbows 0.5s infinite; } @keyframes omgrainbows { 0%, 100% {color: #7ccdea;} 16% {color: #0074D9;} 32% {color: #2ECC40;} 48% {color: #FFDC00;} 64% {color: #B10DC9;} 80% {color: #FF4136;} }
-
@accalia, new feature for Clown Vomit Mode?
-
Holy shit
-
-
Maybe for a:hover?
-
Welp, this is embarrassing. I put the code into the Chrome Inspector to see what would happen for really reals, browsed around some more and forgot Discourse is one of those SPA bullshit-fests, so it's still live when I look at other threads.
-
-
Here, try this CSS reset:
a.mention { position: relative; color: black !important; animation: ka-chunk 3s infinite; } @keyframes ka-chunk { 0%, 80%, 100% { left: 0; } 98% { left: -50px; } 99% { left: 5px; } }
-
* { position: relative; color: black !important; animation: ka-chunk 3s infinite; } @keyframes ka-chunk { 0%, 80%, 100% { left: 0; } 98% { left: -50px; } 99% { left: 5px; } }
-
*twitch*
* { position: relative; color: black !important; animation: ka-chunk 3s infinite; } @keyframes ka-chunk { 0%, 80%, 100% { left: 0; } 98% { left: -50px; } 99% { left: 5px; } }
FTFY
-
-
-
Some levels of evil right there.
-
I see mentions got bikeshedded.
Gray on gray. Yesss.
Why don't you just do
* { color : #888888 !important; background-color : #888888 !important; }
and be done with it?
-
Make one of those #888889 for contrast and you're golden.
-
Make one of those #888889 for contrast
No! We can't allow such a bright, garish shade of blue. It needs to be a proper gray: #898989.
-
That contrasts too much with #888888, we can't use that!!
-
If we limit the contrast in value, then we get a distracting amount of color saturation. If we mute the color, we get too much contrast in the value. I guess the only solution is to remove the @mention feature entirely.
-
I guess the only solution is to remove the @mention feature entirely.
That seems reasonable. I mean, do users really need to be able to mention each other?
-
It only causes server problems processing all those mentions, we probably should remove it after all.
-
That seems reasonable. I mean, do users really need to be able to mention each other?
I miss this feature frequently on phpBB, but "Jeff giveth and Jeff taketh away" so might as well accept its transience.
Filed under: starholes
-
I would like to remove [the similar topics toaster] as it pops up on the right side of the composer. (On top of Preview section). I am on a lower resolution screen.
As a quick solution, you could just add the following as a css addition:
We really should add a site setting for this, cause its so wasteful to be running an expensive query to calculate information we are not displaying.
I don't think people should be hiding this, so penalizing them for doing so is fine by me..
-
And re-bikeshedded. Twice.
-
Someone needs to sell them this:
https://what.thedailywtf.com/t/how-can-this-be-so-wrong-aka-the-discopocalypse-thread/51117/1654?u=aliceif
-
Jeff is being a total prick, as we've grown to expect from him, but I can sort-of understand where he's coming from. He has a certain vision for what discussion platforms should look like in 2016, and he wants his software to enforce that. There's nothing wrong with having a certain view on things and sticking to it.
Now, if only Jeff knew how to communicate with his audience instead of going full-on Mao on them...
-
Someone needs to sell them this:
It'll save them some bikeshedding time. The CSS changes its own colour.
-
He has a certain vision for what discussion platforms should look like in
20162026,FTFJeff…
-
@AlexMedia said:
He has a certain vision for what discussion platforms should look like in
201620262023,FTFJeff…
FTFIR
Though I suppose it wouldn't be too absurd to assume that Discourse is the Forum for Ten Years From Right This Very DiscoMinute.
-
Okay, I realize now why the "show username instead of long name" bug has bugged me so much. I can't be DiscoArsed to search for the exact convos, but the summary was basically:
(Alex) Discourse can't have spaces in usernames.
But CS, a 200 year old forum, can do it. FFS, YOUR username has a space in it, Alex Papadimoulis
(Blakey) FFS, my Windows username RIGHT NOW has a space in it
YOU ARE ALL DOING IT WRONG! NO SPACES! USE THE LONG NAME TO DISPLAY YOUR NAME WITH A SPACE
But that's the hand full of liquid poop we were dealt. So I dutifully put "Lorne Kates" into all the name fields. And I guess for a while it worked. I do recall at some point, shortly before the bug was found, thinking "huh, am I seeing Lorne_Kates? Whatever."
So when this bug WAS found-- well, surely it'll be fixed, right. Because The Exalted Prolapsed Colon-Man said this is his vision and THE RIGHT WAY OF DOING IT. But nope
THIS IS AS EXPECTED EVEN THOUGH IT NEVER WORKED THIS WAY BEFORE AND THE BUG WAS INTRODUCED BY THE COCK TEAM FUCK YOU
So yeah-- even when you DO do it the way, he might revise history at any moment and tell you to fuck off.
Fuck this whole forum software with an "A Year Vision"
-
That seems reasonable. I mean, do users really need to be able to mention each other?
It occurs to me that probably 90% of Discofunctionality could be safely removed entirely if users weren't allowed to log in at all. Just think how civilized it could be then!
Filed under: maybe then there would finally be time enough to make "quote reply" work sanely on mobile...
-
-
At this point, are Whisper bugs basically buy one get three free?
-
I'm betting CLOSED_AS_DESIGNED.
-
No, it's going to be CLOSED_DOING_IT_WRONG. "You shouldn't add staff color to a whisper, since only staff can see it anyway."
-
I'm betting CLOSED_AS_DESIGNED.
Nah..."We'll fix this in $future_release."
##$future_release notes
...
fix whispers
...
-
-
Gray on gray. Yesss.
Interesting, we're getting some of that on the project I'm working on. Looks horrid.
-
Atwoodian support... 7 replies, 0 help for the customer, 4 coats of paint on the bikeshed.
Also, including a trailing / on the link for whatever reason (user error, in this case) will break the oneboxer.
-
This isn't even that bad of a reply from Atwood... he acknowledges the problem, tries to give the user some pointers (the 'suspect user' page) and even comes up with some potential solutions for Discourse vNext.
I've seen worse from him.
-
First rule of the Discopocalypse thread: whatever Jeff does, it's .
And I'd say that constantly talking over/around the customer, and not making it clear for like 4 posts that you're positing a way that /users/suspect will eventually be easy delete -- while the customer is wasting time looking for an existing easy delete button on the page -- is not quality support by any standard.
-
It's not top-notch support, but for Jeff's standards it's pretty decent.
Someone really should tell Jeff that he should not be talking to clients. Playing an architect or lead dev is fine, but it's probably best if he delegates client interfacing to someone else.
-
At this point, are Whisper bugs basically buy one get
threefourfree?Duplicated elsewhere, there are a bunch of issues with whispers around counts and unread and stuff.
Snort. "and stuff". Leaking private messages? Meh-- it's just stuff.
-
Atwoodian support... 7 replies, 0 help for the customer, 4 coats of paint on the bikeshed.
I'm not sure what the problem is here. Seems like some decent discussion about a difficult topic. Jeff pointed out some useful things:
/admin/users/suspect
- which I wasn't aware of but is kind of interesting...we have some stuff that look like theirs here, though not so many. At least a couple of them look like novelty accounts.In fact, I just deleted some profile spammers.
-
Seems like some decent discussion about a difficult topic.
The score so far:
Jeff 1
The Rest Of The Thread: 1691
Filed under: Superb Owl
-
Someone really should tell Jeff that he should not be talking to clients.
i tried that,
in response he attempted to ban me from the internet.
-
in response he attempted to ban me from the internet.
And yet you're still here. Another Jeffcess, there!
-
So to even out the Jeffcess in not banning a user for talking about spammers, let's see what else is happening on meta.derp:
https://meta.discourse.org/t/muted-users-still-show-notifications/38965
Hey, remember how we wanted a feature where you could mute a fox user? I guess it exists. And it doesn't work right!
But the real gold in that one is "I have our bots set to muted". At the time of this posting, there are no replies. How much do you want to bet the first response is Jeff having a meltdown at the mention of Bots?
And hey, who wants an information leak while we're at it?
Expected result: UR DOING IT WRONG PEOPLE SHOULDN'T URL!!!!!!!!!
And finally the best for last. Here, just the title first: Occasional blank screen using iPad iOS Chrome
Okay and now some space. Because I know you all already know how this is going to run right?
I mean we all have our assumptions about Jeff and his reactions, right?
About what he thinks about mobile, right?
And surely he wouldn't just be a stereotype, and that easily predictable, right?
Here's the thread:
https://meta.discourse.org/t/occasional-blank-screen-using-ipad-ios-chrome/38774
And the literal quote from Jeff's first response:
Make sure you are using the newest version of Chrome. This isn't a "real" browser on iOS, just a wrapper around either the old and stinky Web Mobile Safari view
Never change, Jeff.