Vote of No Confidence
-
-
Personally, I love Markdown.
@Lorne_Kates Looks like we've got ourselves a live one!
-
pms_per_day
Do all women get that or just cis-?
-
@CalvinSmith said:
Personally, I love Markdown.
@Lorne_Kates Looks like we've got ourselves a live one!@CalvinSmith sounds like a manufacturer of knock off underwear.
-
should still just work
Discourse philosophy: Anything your browser will simply do on its own must be hijacked and reimplemented in the most complicated and fragile way possible.
-
should still just work.
Discourse.
Discourse philosophy:...
Yeah, I walked right into that, didn't I?
I also apparently tried posting into a cootie storm. Thanks "502 OK"!
-
Ooh, I wonder:
- Hello
- ...
maybe?
- Test?
- Test
- Ha.
- This is just bad.
-
-
No comment necessary:
-
That last spike is almost like a middle finger from Dischorse.
-
contents under a <details> tag without a <summary> tag should still just work.
It's part of their Firefox polydisco. A real polyfill knows this, but third-party dependencies besides Ember, jQuery, JSMarkdown, oEmbed, and... all the other third party dependencies, of which there are dozens ... anyway, Doing It Wrong™.
-
The new notifications list first gets filled with dupes and then spends a few seconds de-duping when you open it.
Now that's how you make something look performant!
-
Your post came up while I was reading the thread, but the notification doesn't go away.
If I click it, it focusses and flashes your post, but the notification is still blue.
Edit: it went away when I posted.
-
[poll]
-
is this broken?
- of course it is
- and how
[/poll]
-
-
It was broken in a different way in preview. </surprise>
-
-
Personally, I love Markdown.
You may have Discourse Syndrome …
The Endless Scroll thing is terrible, though.
But it's hard to say.
-
Anyone notice the delete button highlights a bright, eye-catching, encouraging green? It's like Discourse knows whatever you posted is crap, so you might as well delete it...
-
Anyone notice the delete button highlights a bright, eye-catching, encouraging green? It's like Discourse knows whatever you posted is crap, so you might as well delete it...
It's been green for a while, but it seems brighter now.
-
Love happens when you click the 2nd arrow.
-
Oh - and they stop working after you look at the "n Replies"!
-
Entered on post 1411, scrolled down to the end of the thread, ended up at post 1410.
The jellypotato on mobile is worse than ever, the performance went to shit, viewing raw takes multiple seconds, the new notification menu is buggy and terrible, whispers are like the most retarded feature ever, and I'll probably find two or three more problems before I end and submit this post, if it even lets me do that.
Can't we, I don't know, rollback this update or something? If we're gonna stay with unsupported, buggy, hostile software, I'd rather have a version that actually mostly works. We can even keep that XSS, it's not really abusable anyway.
-
The jellypotato on mobile is worse than ever,
Quoted for truth. Discourse on mobile is
differenta lost cause.
-
Ever since Discourse was updated
Still haven't got a good reason why we did that.
tell me how Sam is God among software developers!
No. If I did, I would be lying.
The update doesn't seem to helped performance:
Did anyone think it would?Another tab-related bit of Discuntery.
You're doing it wrong. Stop using tabs. Read one thread at a time like Jeff intended!!!!
@CalvinSmith said:
Personally, I love****strong text Markdown.
@Lorne_Kates Looks like we've got ourselves a live one!FTFY
Can't we, I don't know, rollback this update or something? If we're gonna stay with unsupported, buggy, hostile software, I'd rather have a version that actually mostly works. We can even keep that XSS, it's not really abusable anyway.
There literally aren't enough likes to give to this.
And now before I post-- ctrl-a ctrl-c because surely Discourse will fuck up.
-
The first rule of Civilized Discourse -- the era of Silent Movies had the most civilized discourse...
-
Can't we, I don't know, rollback this update or something?
From a thread on Meta.D that I saw before it was ruthlessly murdered, yes we can roll back to 1.4 (no database schema changes), but we have to do so by hand.
-
a thread on Meta.D that I saw before it was ruthlessly murdered
Not a popular update then, eh?
-
@abarker said:
On an unrelated note, is quote reply broken for anyone else? It keeps failing for me, almost like it's trying to make a trip to the server.
It is taking several seconds to open the editor for me. This one was only about 3 seconds, but the last one took long enough that I had highlighted the text to try again before it finally opened.
I kept getting timeouts (well, Chrome asking "Can I kill this tab(set)? Please? Pretty please? Oh, the agony!") until I disabled HTTPS Everywhere for WTDWTF, and now it's all speedy (relatively) again. So while this update fixed the most recent script injection, they may have belgiumed up HTTPS stuff. Or it might just be my computer at the moment, but I thought I'd share anyway.
Edit: actually, not for WTDWTF, but for discourse.org in the HTTPS Everywhere dialog. I've re-enabled it for now, so I guess I'll find out whether that was it or not.
-
@Lorne_Kates said:
And now before I post-- ctrl-a ctrl-c because surely Discourse will fuck up.
Just like the good old CS days
Also, adding my vote of no confidence.
-
@Lorne_Kates said:
Filed under: I'm sure Jeff put a random-bug in when current user == lornekates. But since he's a shitty coder, he forgot that string comparison includes underscores.
I'm starting to believe that they really have something like:
if(wtdwtf) activateMoreBugs();
somewhere in the code
-
Anyone notice the delete button highlights a bright, eye-catching, encouraging green? It's like Discourse knows whatever you posted is crap, so you might as well delete it...
@PJH stylesheeted that, I think.
-
@Lorne_Kates said:
Still haven't got a good reason why we did that.
Because this version is basically 1.4-stable, if I understood things correctly.
-
I'm starting to believe that they really have something like:
if(wtdwtf) activateMoreBugs();
somewhere in the code
Even if that's the case I'm amazed they are managing to produce them at the rate we're finding them.
-
-
i said dismiss post not dismiss topic!
Are you sure your buttons are in the right order? At least the text on the buttons.
That's what got us banned. Pointing it out that is.
If the function doesn't actually match the text, you might want to file a bug report over on meta.d...
@aliceif said:
stable
I'm sure I saw the horse running ->> that way. With a battery and a stapler.
Given it was away from Discourse, I'm not sure about the correctness...
Anyone closed the doors yet?
-
Edit: actually, not for WTDWTF, but for discourse.org in the HTTPS Everywhere dialog. I've re-enabled it for now, so I guess I'll find out whether that was it or not.
Looks like their new "CDN" isn't up to the load. Strange...
Side note: Posting from Windows Phone. No weird selection behavior, no top-of-the-thread rocket, just Works (TM). I like it.
Edit: Actually, only edits do that, and only if you never touch the text area. New posts destroy something, so I get a blank page, even if I go back. Hard refresh sometimes fixes. Not always. And posting from the subway? That's different. Fuck this.
-
@Yamikuronue said:
Anyone notice the delete button highlights a bright, eye-catching, encouraging green? It's like Discourse knows whatever you posted is crap, so you might as well delete it...
@PJH stylesheeted that, I think.
Indeed:
nav.post-controls button.delete:hover{ background:#33CC33; color:#fff }
-
That last spike is almost like a middle finger from Dischorse.
[Code]
//09/19/2015 Jeff A: "fix" for tdwtf (fuck those guys)
if (Request.URL.Contains("thedailywtf"))
{
Thread.Sleep(Math.Rand() *1000);
}
[/code]
-
-
That code is too well-written and not surrounded in puddles of edge cases, poor design decisions, and security issues.
-
I'm sure I saw the horse running ->> that way. With a battery and a stapler.
Given it was away from Discourse, I'm not sure about the correctness...
If it was running away from Discourse, it was correct. If it was running toward Discourse, OTOH, it's probably been grazing on locoweed.
-
I mean, look at their customers; if they're providing them with the same hands-on service, and providing advice on how to build/foster a community, then it's a huge value.
Are their customers aware that they've been shipping XSSable code as late a one month ago? I mean, I'm pretty sure you're not going to be able to access actually critical stuff from their forum box but I'm not sure (as someone else mentioned) that e.g. Cisco would be happy with someone XSSing their customers who are looking for support.
bangate
Can we please stop calling everything *gate
FFF why can't I just minimize the edit window by dragging the split panel to the bottom? Why must I click the down arrow?
Filed Under:
Uploading...
-
Cisco would be happy with someone XSSing their customers who are looking for support.
I think Cisco are safe for now.
-
That code is too well-written and not surrounded in puddles of edge cases, poor design decisions, and security issues.
It would be the one thing the DiscoDevs could get right.
-
-
Horses run into fires...
-
-
Security through cooties.
The Discopædia thread is that way :arrow-right: :arrow-left:
Edit, Fucking emoticon lookup is broken on mobile, and I cannot be arsed to fix it.
-
Feel free to cite me!
-