Meta.d is sad
-
Refactor topic performance to support topics with 100k posts+ without serious performance impact
So, I guess somebody with money hit the barrier too, and Jeff is like "OH YES YES OF COURSE TOP PRIORITY NUMBER ONE".
-
Abillity for groups to have a "group owner" than can add and remove people from the group
If groups had any meaningful role, this would be a useful thing.
Fix topic splits having owner of person who split the topic
Ah, that's another good one. It's always kind of confusing having the topic owner not being the OP. (I think this one was reported, as alluded to by @onyx.)
-
Wonder if here is a paying customer...
-
Yeah but he's a developer. What do developers know about this stuff?! </s>
OPEN YOUR TAGS
-
-
https://meta.discourse.org/t/composer-button-bar-looks-disabled/33215/6?u=sdertvgsedrtfvcswe
This one appears to have been mega-jeffed:
Edit: :Hanzo:'d, but I'm leaving it for the discoterm.
-
-
github highlight
"My software doesn't work? Who cares?"
I mean, this is unquestionably a bug.
-
Also, I probably managed to get myself banned too, because I replied to the highlight thread, "This seems kind of a harsh response to a bug report."
-
Also, I probably managed to get myself banned too, because I replied to the highlight thread, "This seems kind of a harsh response to a bug report."
Still there from what I can see, and Jeff's last post was more than half an hour after yours.
Also, Jeff really needs to hire someone to interact with customers for him, and then back the hell off. If CDCK fails, the problem is almost certainly going to reduce to his craptastic customer interaction skills.
-
The larger progress bar might be useful, but they'll probably fuck it up.
Adjust right gutter
Make progress bar larger
to do so, shrink down any useless, un-needed cruft.Here you go:
http://i.imgur.com/f2bs7h0.png
Filed under: If this image breaks Discourse I'm sorrynotsorry
-
show ... other relevant UI elements
I thought Jeff's modus operandi was to remove all the relevant UI elements, hide the semi-relevant ones, and make the remaining, irrelevant ones as confusing as possible.
-
-
Also, Jeff really needs to hire someone to interact with customers for him
On the contrary. The CEO should be the sole public face of the company and the sole point of contact for all customers. This is would certainly increase the likelihood of a good outcome for all concerned.
-
Also, Jeff really needs to hire someone to interact with customers for him, and then back the hell off. If CDCK fails, the problem is almost certainly going to reduce to his craptastic customer interaction skills.
What @HardwareGeek said.
<rant>
Seriously though, you're absolutely right. Discourse honestly wouldn't be nearly as bad as it is if it wasn't for the fact that Jeff continuously uses the "Doing It Wrong", "NOTABUG", etc replies and bikesheds literally all the time. I imagine the other devs (No need to @mention summon them here since that really probably won't help...) probably have a hard time putting up with it - I know I would. Jeff should understand (given that it's a nominally open-source project) that shitting on users of his own software, on its own public support forums, even if they aren't paying customers, will drive people away.
Yes, we poked the bear. A lot. We trashtalked the hell out of him. We even made personal assaults on his character and ability to code. We still do (moreso now that this has happened). We made fun of his design decisions. Hell, we even ganged up on some of the other devs on numerous occasions. And we aren't a paying customer. But we still interacted. We still participated. Many of us were very civil and never got close to an argument with him. Others did, sure. But he banned the entire forum. Including contributors. Including those of us who found expoits. Major ones that, had we not found them, could have shut the project down (Imagine a big name like Imgur, Cisco or one of their other big customers getting themselves XSS'd. That would not go over well). Yes, we're a toxic hellstew of a community. But we tried to get along. I had no personal gripe with him. Now I do.
This whole debacle is just ridiculous. The fact that anyone thinks it's OK to do that is outrageous. He will get himself in trouble if he continues to do this kind of thing. They have built, in many ways, a fantastic platform. It has glaring flaws. But as our search for forums to use has proved pretty well, making a good forum is really hard. But the attitude from the developer
sis unacceptable. Plain and simple.</rant>
-
Cisco
Yeah, just checked that.
An XSS on an official Cisco forum would go over about as well as... well... yeah.
-
But we tried to get along. I had no personal gripe with him. Now I do.
Indeed. I had at worst a neutral attitude towards him until Discourse, and even until recently it wasn't really negative (although I did poke him once..). I kinda like Discourse, despite its flaws, and if it weren't for Jeff would wish it well. But with him? Nope. Should I ever be in a position to advise someone on working with Jeff or using Discourse, the answer would be a very emphatic "NO". And that "Everybody Panic!" .gif as a public response to a bug report on Discourse's home forum would be exhibit A for why. As well as the fact that he so acrimoniously parted with his free QA team because he got pissy about our bug reports not turning a profit.
-
An XSS on an official Cisco forum would go over about as well as... well... yeah.
Hmm, have they fixed that latest fa-spin exploit, yet?
-
They've fixed it. No idea if it's been pushed out to everyone though...
-
They've fixed it. No idea if it's been pushed out to everyone though...
Say, now that we're off support and effectively on a fixed version-- I wonder which one, in the end, has more site-breaking bugs? Discourse or CS?
-
@Lorne_Kates said:
effectively on a fixed version
We can still upgrade versions at will. We just can't submit bug reports or have any input.
-
Filed Under: No I wasn't being subtle
Understatement of the week, when your email address includes
fuckjeff
.{removed image with email address} -bz
No it doesn't warrant understatement of the month award, that's too prestigious
-
@rad131304 said:
Filed Under: No I wasn't being subtle
Understatement of the week, when your email address includes
fuckjeff
.No it doesn't warrant understatement of the month award, that's too prestigious
Evidently subtlety is not his strong suit...
-
Should I ever be in a position to advise someone on working with Jeff or using Discourse, the answer would be a very emphatic "NO".
I might be willing to work with him (he's still better than a few of the managers here) but only if he has no administrative or otherwise privileged access. Like that, an adult would always be able to slap him down and keep the peace.
-
Paging @beetlejuice and @bloody_mary ...
-
-
@loopback0 said:
Fix topic splits having owner of person who split the topic
Oh, that was a bug?!
Not when we reported it IIRC.
I notice that they're fixing that but not the useless broken notification you get from splitting a topic.
-
I notice that they're fixing that but not the useless broken notification you get from splitting a topic.
And clicking the reply notifications that bring you to the original thread. Unless they fixed that already?
-
I don't think so.
-
sams is as quick as him with the ban hammer, he took seconds to vaporize mr candlejack. of course it was a joke account, but he didnt even count to 10 before nuking him from orbit, ip and everything else
-
I'm pretty sure his celebrity status would let him go unchecked in almost any business he is. And this IMHO is the problem. He is not really a bad person, if you try to account for the damage fame does to someone, and having noone to call him out.
-
-
He is not really a bad person
Jeff Atwood might not be when he's away from a computer (none of us will know either way) - but @codinghorror is.
-
> Refactor topic performance to support topics with 100k posts+ without serious performance impact
Ahhahaaaaha. Aha. Ha.
Seriously? After all the "you're doing it wrong" and "show me a real Dicksauce instance with threads over 10000" and all the hate we got over /t/1000?
YOU. FUCKING. ASSHOLE.Either (as already suggested) a paying customer suddenly has found out that Dicksauce runs like shit with bigger threads, or some DiscoDev did not want to let "our" improvements go to waste. Or both.
-
Either (as already suggested) a paying customer suddenly has found out that Dicksauce runs like shit with bigger threads
This.
Especially the one who got a 260k ish topic which Discourse can't even open any more.
-
-
Surprised you're avoiding the banhammer...
-
Surprised you're avoiding the banhammer...
Call it a passive-aggressive game of chicken.
But this badge. At first I was like "let's just paste without comment lol". Then I had a sip of coffee.
Okay, let's see if I can parse this.
- Likes are a feature of Discourse. They're supposed to measure the worthiness of a post.
- But they aren't important enough to give you a UI to see your most liked posts.
- Because that would gamify the discussion. So likes aren't a measure of worth.
- Unless it's a like from a Discodev on a BUG REPORT, which in their eyes are the least useful discussion that could be had (on their bug tracker).
- But this grants a BADGE. Which are gamifications of a discussion.
- So it's a reward for a earning a single useless point on a type of discussion they hate!
- and the cherry on top? The bug reported was a trivial keyboard shortcut in a fucked up implementation of a shitty WYSIWYG markup code that the Discodev team both ACKNOWLEDGE and****strong text insist is NOT_A_BUG-- but rather than closing, they liked and granted an award.
-
@Lorne_Kates said:
The bug reported was a trivial keyboard shortcut in a fucked up implementation of a shitty WYSIWYG markup code that the Discodev team both ACKNOWLEDGE and****strong text insist is NOT_A_BUG-- but rather than closing, they liked and granted an award.
Stuff like this is how the discodevs show their dissent from Jeff. It's generally subtle and you rarely see any pushback once He's spoken, except from @sam.
-
@Lorne_Kates said:
but rather than closing, they liked and granted an award.
Normally they do both ...
-
Jeff deleted my comment in the Github highlight topic.
ETA: Holy shit, I'm pretty sure I liked the OP and that's gone now too.
-
Surprised you're avoiding the banhammer...
Yeah, I'm annoyed. @Lorne_Kates has been far more "toxic" than I (take it as a compliment) yet he's unbanned and I, as a mere lurker who hadn't posted in months at least, probably longer, was banned with the rest of the group.
-
Yeah, I'm annoyed. @Lorne_Kates has been far more "toxic" than I
Dude, you're the one who created /t/1000! That's like the most toxic thing evar!
-
Dude, you're the one who created /t/1000! That's like the most toxic thing evar!
Apparently it's only toxic because we didn't pay for the right to make a giant topic.
-
To be fair, it's more than just a giant topic.
-
t/1000 could be solved in dishorse by making a reply act as a "reply as a linked topic" after some determined number of replies. This new linked topic can carry some information, so we can click anywhere on this chain of linked topics. The topic list could show just the first topic in a chain.
In the bottom of the topic these links could be identified by numbers, like:
1 2 3 4 5 6 7 (if you're in the 4th topic of the chain)
-
I think Jeff banned someone for suggesting that once...right after Jeff suggested /t/1000 was too long and needed to be split into multiple targets.
-
t/1000 could be solved in dishorse by making a reply act as a "reply as a linked topic" after some determined number of replies.
https://what.thedailywtf.com/t/topagination-suck-it-dicsourse/1889?u=boomzilla
-
I think Jeff banned someone for suggesting that once...right after Jeff suggested /t/1000 was too long and needed to be split into multiple targets.
I suggested it, and the post got Jeff'd but my account didn't.
-
blakeyrat is right.
Nobody ever learns from history.TOPAGINATION, LOOK IT UP!