:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
Keep dreaming.
About using a better forum platform?
Filed under: That makes Discourse a nightmare, right?
-
Friends! Help! A guinea pig tricked me!!
-
-
Well, that's just rude.
-
@loopback0 (quoting meta.discourse.org) said:
it is a platypus, and not the good kind.
... there's only one kind of platypus. Unless you count [extinct ones known only from the fossil record][1].
[1]: https://en.wikipedia.org/wiki/ObdurodonAnd male platypuses have a venomous spur. How can that not be the
goodawesome kind?
-
Agreed.
-
Popular browser on a popular device? Nah Jeff, can't see why there's an expectation for that to be supported.
Stop spoiling our ivory towers with your pesky reality, you naysayer!
-
I wasn't banned ;) guess I ditched their crappy software earlier enough to dodge the banstick.
-
I don't think I'm banned yet. But I don't want to enable Javascript to find out:
-
@Lorne_Kates said:
I don't want to enable Javascript to find out:
I'm guessing I'm not banned either, but it's too toxic a place for me to even open the email notifications it sends me from time to time. After all, it's just one more nonsense spammer…
-
@Lorne_Kates said:
I don't think I'm banned yet. But I don't want to enable Javascript to find out:
I think you're "good."
-
I have my work IP banned there, but I can still access at home. I use a different username there, so they would have to do some work to catch me.
-
That 'L' looks like it is off center
-
Holy off-centre typography, Robin! Quick, to the B
atikecaveshed!
-
I'm still good but only because I wasn't memorable enough to Jeff.
Probably because everything that came out of my mouth was toxic hellstew and therefore irrelevant because
-
That 'L' looks like it is off center
You just inspired some subtle trolling at a certain other forum
-
We would have gotten away with our lack of testing, too, if it weren't for those meddling users...
-
Not done with the Roboto font. Disliked.
-
Why are those avatars round? What kind of fucking retarded design decision is that? Who came up with that dumb fuckery?
-
@Lorne_Kates said:
dumb fuckery?
-
And Jeff comes through with a classic solution. "I don't think wee should allow tags with quotes in them."
It sounds like sql injection, but it's probably a lot more stupid than that.
-
And Jeff comes through with a classic solution. "I don't think wee should allow tags with quotes in them."
Right. Because the single quote character is completely different from the apostrophe which is used in many legitimate words (and also apparently in many Lojban words).
And yes, I did just imply that Lojban words are not legitimate.
-
Added benefit: tags of #you'redoingitwrong are also banned.
-
Is he insane? There are languages where single quotes are important.
-
It's Jeff, you have to ask?
-
-
I think they've finally replaced Jeff with a bot.
foreach topic in topics { if topic.title kinda-like '$1 with $2 causes $3' and is_bad_thing($3) { reply("I don't think we should allow $2 in $1"); } }
Tag name with single quote causes server error!
I don't think we should allow single quote in tag name.
Username with underscores makes user unmentionable!
I don't think we should allow underscores in username.
Username with non-ASCII letters causes server to crash!
I don't think we should allow non-ASCII letters in username.
Password with numbers causes server to succumb to Zalgo!
I don't think we should allow numbers in password.
-
Password with numbers causes server to succumb to Zalgo!
I don't think we should allow numbers in password.Reminds me of that YAML config file issue ...
-
I think they've finally replaced Jeff with a bot.
foreach topic in topics { if topic.title kinda-like '$1 with $2 causes $3' and is_bad_thing($3) { reply("I don't think we should allow $2 in $1"); } } ```</blockquote> Jeff with Discourse development causes bad software!
-
Discourse development with Jeff causes bad software.
I don't think we should allow Jeff in Discourse development.
There we go, reads correctly now.
-
Jeff with Discourse development causes bad software!
I don't think we should allow Discourse development in Jeff.
-
Discodevs will spend time not coding features, but implementing that code. With additional code after reply
AddToUserToxicity($user->ID, 1) If (UserToxicity($user->ID) > $JeffBabyWhinyThreshold) { DiscoBanComplete($user); } // BAN the fucking user // BAN his IP // BAN his entire IP block // BAN every user who ever came in from that IP block RECURSIVELY!!!!! function DiscoBanComplete($user) { discoban($user); discoAnonymizeUser($user); foreach($ip in $user->LoggedIPs) { discoBan($ip); discoBan(GetIPBlockFromIP($ip)); foreach($moaruser in GetUsersWhoEverUsedThatIPBlock(GetIPBlockFromIP($ip))) { if(! $moaruser->IsBanned) { DiscoBanComplete($moaruser); } } } }
-
function DiscoBanComplete() { foreach($user in getAllUsers()) { if ($user->username != "codinghorror") { discoban($user); discoAnonymizeUser($user) } } }
There, all optimized.
-
Oi! That code's readable, but we all know that DishCoarse is written in Ruby which makes readability into something unreadable…
-
Is he insane? There are languages where single quotes are important.
Languages other than a proper subset of English?
Reminds me of that YAML config file issue ...
Eh?
-
@aliceif said:
Reminds me of that YAML config file issue ...
Eh?
If I'm not mistaken, @aliceif is referring specifically to the database password. That can't contain a pound sign (#) because their YAML parser sees it as a comment and ignores everything after it.
The response to that bug was, of course, "don't use a # in your database password".
-
If I'm not mistaken, @aliceif is referring specifically to the database password. That can't contain a pound sign (#) because their YAML parser sees it as a comment and ignores everything after it.
/me reads spec
I see..
What're the odds a misplaced space could do the same because it's tokenizing incorrectly? Or a single quote or a double quote or…The response to that bug was, of course, "don't use a # in your database password".
-
What're the odds a misplaced space could do the same because it's tokenizing incorrectly? Or a single quote or a double quote or…
Any sane YAML implementation will allow you to use single or double quotes to, uh, quote a string value which contains problematic characters, but apparently if you're , then it's not clear whether those quotes are part of the password or not. Much simpler just to start banning stuff....
-
Any sane YAML implementation will allow you to use single or double quotes to, uh, quote a string value which contains problematic characters, but apparently if you're , then it's not clear whether those quotes are part of the password or not. Much simpler just to start banning stuff....
Indeed. So not so much a YAML config file as a DAML config file. Because of course it has to be that little bit different.
-
I don't think we should allow Jeff in Discourse development.
There we go, reads correctly now.
Still looks off.
I don't think we should allow Jeff in
Discoursedevelopment.That's better.
-
Actually, it was the SMTP password:
https://meta.discourse.org/t/bug-smtp-password-field-does-not-escape-comment-sign-hash/23344
-
-
Bug: SMTP password field does not escape comment sign (hash)
Fucking hell, Jeff really was acting persistently dense there.
-
So it USED to work-- and then they discobroke it in an update-- which means it'll crash an unknown number of critical components (silently)-- and then refused to fix it?
The AristocratsDiscourse!
-
And that whole issue would not exist if they had a graphical installer ...
Filed under: [INB4 lynched](#tag), [people who are willing to hand-edit config files in a weird docker app can't possibly know what quotes mean](#tag), [JDGI](#tag)
-
This is probably old news but I don't use mobile TDWTF that often.
"So, what's wrong with that, it looks like a nice responsive layout that's the proper width for the displ--"
PS: My phone jellypotatoed and the browser crashed so I had to finish posting this from desktop.
-
-
Oh. That's a little disappointing, I was hoping it was a real DiscoWTF.
-
I saw it on Discourse Default last time I cared to look.
-
I saw it on Discourse Default last time I cared to look.
I've probably confused it with something else then.