Discourse DMZ



  • @Matches said:

    My point was it works fine for the topic list. What's different about the profile page that it causes a crash?

    I would venture a bet it's a view over several tables with a bad join/bad index which is causing it to appear unresponsive to the browser, and cause the crash. (Think 'not responding' winform application that doesn't take advantage of background threads properly)


    Don't think so. AJAX calls are asynchronous. A bad join would cause a time-out (and perhaps crash the backend) but the browser shouldn't really notice.

    So if an AJAX-driven front-end crashes the browser, the front-end is responsible.

    Loading a 100 posts shouldn't stress the browser. Loading a 100 posts 100 times shouldn't stress the browser.

    Unless of course the front-side Javascript takes too long to update the DOM or the memory consumption of the average post is beyond what's acceptable.

    And just to rub it in: this behaviour has only been observed with Discourse. I can't recall Facebook or Twitter having similar problems with Infiniscroll tm.



  • @eviltrout said:

    User streams just dump in the dom forever.

    Why? Honestly, why? As I've said before:

    • you unload from the DOM in topics
    • Facebook doesn't seem to have that problem although they also just dump into the DOM forever.

    This really puzzles me, because I don't understand why you have a problem just with user streams.



  • @faoileag said:

    Then do it. It shouldn't be too difficult - you already can filter search to only take into account a single topic, so adding a filter for a specific user should be a matter of minutes. Just a changed WHERE clause.

    But that would be admitting that paging fits into the Discourse world in some way. And once there's a chink in that armor, we will press the advantage until paging is optional throughout Discourse. Jeff would not allow us such an advantage.


  • Discourse touched me in a no-no place

    @faoileag said:

    Why? Honestly, why? As I've said before:

    • you unload from the DOM in topics
    • Facebook doesn't seem to have that problem although they also just dump into the DOM forever.

    This really puzzles me, because I don't understand why you have a problem just with user streams.


    What's more, unloading makes sense in user streams. They've just got to take the stuff they've already got working in topics and put it to use in the one place where it is exactly the right thing. Seriously, a user event stream is where all sorts of sites already use unloading; adding it will surprise no-one at all. (Except one or two of the pedants here, but whatever.)

    Better searching would be good too, but not keeling over in a heap takes precedence over that.


  • Banned

    @tufty said:

    Yeah, ha ha ha. Dismiss serious points in a flippant manner.

    @tufty said:

    It's about Discourse being broken on a level that's beyond mere bugs. It's about issues that Jeff will never grok, can never accept as being issues, because they go against his conviction that Discourse is better than any other forum software, despite admitting that he never uses forum software.

    I think it was Robert McNamara talking about the Vietnam war. He was asked something along the lines about why it went so badly. He explained both parties were fighting different wars. US was trying to "stop communism" or whatever and the Vietnamese were fighting for independence.

    You disagree with Discourse on a fundamental level. What seems to be motivating you is

    • Publicly embarrass team
    • Sling poo at my co-founders
    • Learn us how to build software

    What is motivating us is

    • Make Discourse awesome

    So there is a fundamental different war being fought I don't see it as one there is any point engaging in.

    @tufty said:

    And above all, get yourself a decent bug tracker.

    Others raised this as well. So I will entertain your trolling.

    Cause bugtrackers magically fix bugs. Like this one

    We tried GitHub issues, the fragmentation meant bugs on GitHub issues were getting forgotten and ignored.

    I review https://meta.discourse.org/category/bug?status=open&order=likes on a regular basis and don't feel any immediate need for anything better. We respond better than may huge companies do and overall do no allow bugs to go ignored.

    Nonetheless, I can hear the echoing people on TDWTF at the back of my head saying I am sitting on my chair wrong and not touch typing correctly cause I am an idiot.



  • @sam said:

    Make Discourse awesome

    When are you gonna get started on that?

    Great goal, but I don't see how the last year of "make Discourse annoying" is contributing towards it.


  • Winner of the 2016 Presidential Election

    @faoileag, @tufty

    I am kind of with @Sam on this matter. I mean, it's fine to be disgruntled and a bit dismissive about discourse and probably some trolling is always in order.
    But in this topic @eviltrout came out, asked why Discourse is getting that much hate in this forum, agrees that some things could have been better and you guys still keep trolling / ridiculing him.

    He can't magically fix what has been done, neither could you. I don't know, let time do its thing for a bit. But don't shoot the guy who asked for valid feedback. Even if he is the Co-founder.

    Filed under : [Do what you want but don't make me agree with people please.] (#tag)


  • Banned

    Come on @blakeyrat you can do better than that, where is the CAPS LOCK.



  • @sam said:

    What is motivating us is

    • Make Discourse awesome
    It's not just a different war as you see it though; there's also a fundamental disagreement as to what "awesome" means. Like the Discourse attitude is "infiniscroll is awesome", but there are plenty of people here that feel that infinite scrolling precludes being awesome, and plenty more (like me) who feel like while it doesn't absolutely preclude being awesome, it's at least a barrier to it. So we feel like the Discourse policy is to pick & implement a non-feature, notice that non-feature breaks a bunch of stuff that have a normally-perfectly-good implementation in the browser (e.g. in-page search), spend a bunch of effort doing an incomplete job reimplementing those broken things, and then say "1.0 guys!"

  • :belt_onion:

    @sam said:

    Cause bugtrackers magically fix bugs. Like this one

    I think your problem is that your bug submission is now 404 not found thanks to jeff deleting things:
    https://meta.discourse.org/uploads/meta_discourse/1491/a8f7fc731167dfe6.png


  • Banned

    ... or me having no spot to uploading an image on their bug tracker, so I upload it in the composer on meta... and our regular job that deletes old orphan images deleted it,

    Regardless, there is a live working repro there.



  • "Jul 24, 2013"

    Good luck finding a bug report from July 24th, 2013 using your current method of tracking bugs.


  • Banned


  • :belt_onion:

    By the way - click your link, then click the Dicsourse Logo icon and behold... All categories supposedly showing, nothing but bug category visible on the front page. It says it's sorted by topic, but I have no idea how so because it appears to just be randomly ordered topics out of the bugs category. I assume it is a flaw in it keeping some sort options due to the link you posted having passed in sql sorts. Re-sorting by topic or anything else fixes the list.



  • @sam said:

    - Publicly embarrass team

    • Sling poo at my co-founders
    • Learn us how to build software

    No. We were in the early days quite happy to offer our thoughts and insight and generally help you guys make it more awesome than it was - despite our objections on things like infiniscroll.

    The problem is when your co-founders starting being pissy with us about it. We're not regular mortals. We're not people who are swayed by shiny or spiffy. If you're going to throw software at us - people who write software ourselves - expect to be called out on bugs.

    And when we raise bugs, we appreciate being taken seriously because we know we don't have to bother spending time and effort using the skills that normally make us money.

    So when we raise bugs and get passive-aggressive and aggressive-aggressive bullshit for our trouble, don't expect to get a free pass because spiffy and shiny don't appease us.

    So Github wasn't the right tool for you. Fine, that happens. But trying to bastardise a bug tracker out of a forum is not a clever idea, no matter how good the forum is because a forum IS NOT A BUG TRACKER.

    This is the reason we give you the bile we do - it's kindness. It's a cruel form of kindness but all the time we spit bile it's because on some level we care.

    When we stop giving you grief, that's when you should really worry.



  • I'm swayed by shiny.



  • You might be swayed by it but I've seen enough of your posts to know that it doesn't sway you very far.



  • I haven't seen any shiny yet.



  • I thought Discourse was kind of shiny personally, but then again my expectations are limited by those crusty old fuddy-duddy PHP toxic hellstew 1990s era forums, WTF would I know?

    I'm like a forum redneck.



  • Turn your monitor brightness down.



  • Why?



  • Whitespace != shiny, you're just confused by the brightness.



  • No, to be fair there are some shiny semi-cool things in Discourse, like copy/pasting an actual image to initiate an upload. Very convenient to screengrab a bug, crop the crap and then paste it into a new topic.

    But shiny things do not make a forum software.



  • You know the best feature of CS that we're missing is how you could change the subject per-post instead of the entire topic just having one.



  • I've never been sold on how useful that feature actually is, generally, but I can see the use for places where the topic lurches out the door, down the street and into the bar, like it does here with alarming familiarity.


  • :belt_onion:

    I assume this is the same as the bug you're talking about:
    http://what.thedailywtf.com/t/opera-chrome-has-scrolling-issues-in-textbox/2857

    It happens in Opera as well, so I'm guessing it's a general Blink engine problem with the scrollbar movement related to the cursor. Probably a massive overhaul to fix with very little gain, because who puts a 30px border-top on a textbox element (oh right, discourse). I can't recall ever seeing that bug in the wild before outside of this forum.


  • :belt_onion:

    It happens when you do padding-top:30px and then overlay something on top of that 30px of padded space too. Interestingly hitting page up instead of arrow up on the keyboard causes it to scroll to the right place (in both scenarios).



  • @blakeyrat said:

    You know the best feature of CS that we're missing is how you could change the subject per-post instead of the entire topic just having one.

    Remember when CS stopped accepting posts so we had to put the entire message in the title?



  • @abarker said:

    faoileag said:

    Then do it. It shouldn't be too difficult - you already can filter search to only take into account a single topic...

    But that would be admitting that paging fits into the Discourse world in some way.


    I didn't mean the paging - I don't really mind one way or other. I meant search filtered only on posts by a specific user.



  • @Matches said:

    "Jul 24, 2013"
    Good luck finding a bug report from July 24th, 2013 using your current method of tracking bugs.

    @sam said:

    https://meta.discourse.org/category/bug?order=activity&ascending=true&status=open

    That link is a very good example of why Discourse as a bug tracker is a bad idea, especially since it seems to be directed at @Matches suggestion to look for a bug created on a specific date.

    • The list is ordered by activity, not by creation date, and since activity can mean anything from post to like, that order is useless
    • Even if the list were ordered by creation date, you would still have to mouse-over on every activity activity indicator to find the bug created on 2013-07-24.

    Now, if for the bug category only you could customize the columns to show creator and creation date, fine. But such a customization is probably not possible with the current state of Discourse.



  • @sam said:

    You disagree with Discourse on a fundamental level.

    Certain elements of Discourse, yes.
    @sam said:
    Publicly embarrass team

    I don't need to do that, Jeff does it just fine, and you seem to be back to following suit.
    @sam said:
    Sling poo at my co-founders

    Just wiping it off my face and slinging it back, mate.
    @sam said:
    Learn us how to build software

    I'll ignore the grammar, assuming it's meant to be amusing.

    Oddly enough, there is a significant element of that. I've personally been developing software for well over 30 years, and to my eyes you're Doing it Wrong™. I'm not the only one who thinks that, either, and in this forum you have a community with getting on for thousands of years of software development experience.

    @sam said:

    I don't see it as one there is any point engaging in. … I will entertain your trolling.

    I'm not trolling. I'm still raising bugs. I've got loads of them. You'll also note that I treated the data leak issue you had in a responsible manner. So, y'know, fuck you.

    @sam said:

    Nonetheless, I can hear the echoing people on TDWTF at the back of my head saying I am sitting on my chair wrong and not touch typing correctly cause I am an idiot.

    Sometimes, you need to listen to the voices in your head. Sometimes that orphanage does need to be burned down at 3AM.

    Oh, and

    @sam said:

    Make Discourse awesome
    … is about the most cuntish mission goal I've ever seen since Google's

    Don't be caught beingEvil

    It's about as stupid as your "rainbows" bullshit. But doesn't answer this question:
    http://what.thedailywtf.com/t/this-topic-has-nothing-to-do-with-pjh-updating-discourse/2914/503


  • ♿ (Parody)

    @tufty said:

    @sam said:
    What is motivating us is

    Make Discourse awesome


    … is about the most cuntish mission goal I've ever seen since Google's

    Obama's "Don't do stupid shit" has them all beat.


  • Discourse touched me in a no-no place

    @boomzilla said:

    @tufty said:
    … is about the most cuntish mission goal I've ever seen since Google's

    Obama's "Don't do stupid shit" has them all beat.


    Way to go picking something that is both lacking in vision and a total failure for its proponent in the first place.


  • Trolleybus Mechanic

    @boomzilla said:

    Obama's "Don't do stupid shit" has them all beat.

    @dkf said:

    Way to go picking something that is both lacking in vision and a total failure for its proponent in the first place.

    I find that it is at the same time the most laudable aim and hardest to achieve.

    Ceterum: it is my belief that anyone with visions should consult a psychiatrist.



  • I hear shaman are familiar with visions.



  • @sam said:

    What is motivating us is

    • Make Discourse awesome

    I actually do believe you mean that.

    However, to make it awesome you first need to understand what awesome is. And that there are degrees of awesomeness.

    It is not the same if someone whose internet experience boils down to using facebook exclaims "Wow, awsome, look, it has Infiniscroll tm!!11eleven" and if a seasoned developer says "Wow, awsome, best piece of software I've ever come across!"

    Those two examples mark the end points of a range. It is up to you and your co-founders to decide where Discourse should reside within that range.

    This is a community of seasoned developers, and it is telling you that so far they see Discourse at the other end of the spectrum. Or perhaps even beyond that, because facebook has far fewer issues than Discourse.

    To illustrate my point, I make a point:

    • <- a point.

    Why is the -translated into a bullet point here but not in your quote, although the markup is identical?

    So, if you really want to make Discourse awesome, listen to this community.

    Yes, it is far more difficult to achieve that kind of awesomeness. But it is worth it. Because somewhere out there might sit a lonesome developer, who looks at Discourse, looks at all the criticism this community hurls at Discourse and thinks "I can do better than that!".

    Facebook was not the first social networking site. But they did things right enough to outgrow competitors. Or to put it more bluntly: "What is this "MySpace" thing you keep talking about?"

    Filed under: just my 2% on that since I thought a bit about it during the day.



  • @GOG said:

    Ceterum: it is my belief that anyone with visions should consult a psychiatrist.

    We had a chancellor once who told people that. He was replaced in mid-parliamentary term by a guy who had the vision that the country needed an "intellectual-moral about-turn".


  • Trolleybus Mechanic

    That's how it usually turns out, yes.


  • Discourse touched me in a no-no place

    @blakeyrat said:

    You know the best feature of CS that we're missing is how you could change the subject per-post instead of the entire topic just having one.

    "Reply as new post? "

    Fairly certain that'll be the answer...



  • Yup, it's not civilised to have per-post subjects 😛



  • It's more civilized to have several sidebars in the same post when a secondary topic comes up and no indication it's a side bar, for sure.



  • @PJH said:

    @ChaosTheEternal said:
    cc @PJH if you wanna drop this in to fix issues with quote replying not working.

    Remind me Monday if I haven't done it by then.


    Here's your reminder, and here's the CSS again:

    .fa-quote-right { display:none; }
    .quote-button:before {
        content: "\f10e";
        font-family: FontAwesome;
    }
    

  • Discourse touched me in a no-no place

    @ChaosTheEternal said:

    ```css
    .fa-quote-right { display:none; }
    .quote-button:before {
    content: "\f10e";
    font-family: FontAwesome;
    }

    
    Confirmed fixed in FF35 and Chrome 37.0.2062.94.

  • Banned

    Hey guys, I hope you had a good weekend! I had food poisoning and then had to prepare for an ember tutorial thing I'm doing next weekend so I haven't had time to catch up but I still plan on going through all those bugs early this week.

    (I have some security/major issues to fix first, such as making ridiculously long posts)

    <3 <3 <3



  • @GOG said:

    Ceterum: it is my belief that anyone with visions should consult a psychiatrist.

    Anyone without visions should consult an optometrist.


  • ♿ (Parody)

    @HardwareGeek said:

    Anyone without visions should consult an optometrist.

    Probably a waste of money. Get a dog.



  • Email display on the profile is now removed.


  • Banned

    I did an initial pass on the bugs. Some were fixed, some we are well aware of already. But there are about a dozen I have to look at more closely and seem legit.

    Tomorrow I plan to check for duplicate topics on meta and see how many were reported there (and possibly closed?).

    There's a bunch of good stuff that we will fix for sure, thanks. More to come soon.


  • ♿ (Parody)

    @eviltrout said:

    More to come soon.

    Indeed. I've posted two new ones on meta.d today.



  • @boomzilla said:

    I've posted two new ones on meta.d today.

    For someone who purports to hate open source, you sure seem to be helping a lot.

    Mind you, 2 new bugs is only half the bugs we're finding daily, so hey.


Log in to reply