/unread wonky layout on mobile


  • Discourse touched me in a no-no place

    0_1461605606338_Screenshot_2016-04-25-18-31-30.png


  • SockDev

    @PJH you're on mobile, that's different, banned, HTH, HAND, etc.



  • @Arantor
    He should have learned by now ... he'll get us all banned before you can say CLOSED_WONT_FIX_AS_DESIGNED



  • @Arantor I feel like we'd be at the NodeBB devs' throats if we hadn't been on Community Server and Discourse first.


  • Discourse touched me in a no-no place

    @ben_lubar said in /unread wonky layout on mobile:

    @Arantor I feel like we'd be at the NodeBB devs' throats if we hadn't been on Community Server and Discourse first.

    Doubt it.

    1. We probably wouldn't have moved over to begin with because NodeBB didn't pretend to be 'Shiney, working, and only a few minor things need sorting out to be production - 1.0 - ready' when it was in fact nothing of the kind as the first few days' worth of XSS exploits were pointed out.
    2. The lead developers attitudes are different between the two products


  • @PJH - If there was one moment in time that pissed you off with Jeff and co. what was that moment? maybe a few? but mainly the straw that broke the camel's back. AND has the user base been affected? I think there was an exodus of some classic users, has that ship righted itself? I'm curious about those things (from your persepective)...I have no loyalties/adgenda...just curious if you don't mind my asking.


  • Discourse touched me in a no-no place

    @Frank said in /unread wonky layout on mobile:

    If there was one moment in time that pissed you off with Jeff and co. what was that moment?

    Most of the older regulars must recall the few times I've mentioned handing in a 'pre-resignation' to Alex. It was basically Jeff's continued insistence on moderation of this forum after being asked to "stop fucking doing it" because he wasn't actually a moderator in the 'job title' sense of the phrase - he merely had those powers and was abusing them to hide/edit/move others' posts to fit his perception of how the forum should be run.

    Last straw was his editing one of my posts which demonstrated a bug, to remove the demonstration of the bug with a "ta-da - no more bug. Don't do that. FIXED_WONT_FIX."

    My pre-resignation was basically a "I'm sick of this - it's him or me" threat to Alex with regards to Jeff's moderation activities.


    And I didn't have a problem with the 'and co.' part of the arrangement - they were OK. It was just the 'Jeff' part.

    https://what.thedailywtf.com/topic/19225/nice-things-in-nodebb/119 touches on it.

    @Frank said in /unread wonky layout on mobile:

    has the user base been affected?

    The initial move over to Discourse (founder's attitude included) was the major reason that most of those that left around that time actually did. Others (like dhromed) were more 'natural' (in particular real-life intruded on dhromed.)

    We picked up other users which made up for the loss. The forums certainly feel busier after the move to DC.



  • @PJH - thanks! this is really good information.


  • Discourse touched me in a no-no place

    @ben_lubar said in /unread wonky layout on mobile:

    I feel like we'd be at the NodeBB devs' throats if we hadn't been on Community Server and Discourse first.

    I dunno. Blakey would certainly froth at the mouth, but that's his thing. Many of the rest of us, even after :doing_it_wrong: started mocking, still managed to be civil after he stopped.

    That the NodeBB devs aren't such obvious assholes helps, too.



  • @FrostCat yeah, but we would have exploded Discourse if we hadn't just moved off of Community Server.

    TDWTF: "running less-bad software than last time, I promise"


  • Discourse touched me in a no-no place

    @ben_lubar I was barely participating around the time the switch happened, but from what I read later, it seemed like initially, most people were happy with Discurse and even the sploit-finding wasn't done to haxxor the site so much as to let the devs know so they can fix it, our resident Dalek[1] obviously excluded.

    [1] anyone seen the Season 10 trailer yet? High-larious. And no hint that Bill's a magical girl.


  • Discourse touched me in a no-no place

    @FrostCat said in /unread wonky layout on mobile:

    most people were happy with Discurse

    For anyone on Chrome, Community Server was really nasty (replying required writing HTML including the annoying bits like <p>). It also had so many security holes that nobody was even bothering to try to plug them. And that's before we get into the sheer fucktarded awfulness of the tagging system. About the only thing going for CS was that it was pretty resource-frugal.

    Discourse fixed a lot that was wrong, but got a lot of other stuff wrong instead. (We swapped literally no support for support by fucktarded arsewipes.)

    If only we could hammer out the problems with NodeBB (or related) going resource-mad, we'd have something reasonable. Or at least it would be a matter of fixing things to mostly monotonically reach reasonable, which is nearly as good. :)


  • Impossible Mission Players - A

    @dkf said in /unread wonky layout on mobile:

    NodeBB (or related) going resource-mad

    I was wondering why the site starts doing it's weird slowdown thing every so often...



  • @Frank said in /unread wonky layout on mobile:

    @PJH - If there was one moment in time that pissed you off with Jeff and co. what was that moment? maybe a few? but mainly the straw that broke the camel's back. AND has the user base been affected? I think there was an exodus of some classic users, has that ship righted itself? I'm curious about those things (from your persepective)...I have no loyalties/adgenda...just curious if you don't mind my asking.

    I'm not PJH (none of us are-- we're all Blakeyrat alts), but for me it was a few things:

    1. The first hints of DiscoDev's "It isn't an obvious bug, you are just doing it wrong" attitude that started to pile the straws on
    2. The fact that literally everything I pointed out months previously about "this will go wrong" came to pass, and that literally zero of the "this needs to be part of the migration" happened
    3. The final straw was one of Jeff's snarky little quips. Not at me, though. Ben had actually gone through all the effort of learning how to create a Discourse plugin (or was it a PR? Can't remember). He'd actually fought the uphill battle to get a Discourse instance running, learn the fucktarded codebase, and apply a patch to a community-desired feature (nested quotes). He was also well on his way to being a Discourse champion-- defending the product, and working very, very hard to make the product better. Jeff's reaction to the PR? Calling it out IN PUBLIC, calling it "yucky", and reverting it back. Not because it didn't work-- but because Jeff thought it looked "yucky". So he managed to insult and degrade a junior developer-- IN PUBLIC-- who was literally the only one doing what no one else would or could do. Fuck that shit. And-- it'd be one thing if he'd reverted a PR I'd submitted-- me, a very vocal antagonist of his. I would even understand him being a dick to me. But to Ben? Yeah. No. That was the irredeemable line that was crossed and was a flock of canaries that proved that this would be Jeff's attitude forever. Fuck that.

  • Discourse touched me in a no-no place

    @Tsaukpaetra said in /unread wonky layout on mobile:

    I was wondering why the site starts doing it's weird slowdown thing every so often...

    I suspect there's a problem with some resources getting held too long in some circumstances. Maybe a leak, maybe just stuff getting tangled. When external conditions are right (i.e., I think it is triggered by some sort of spider, as there's often degraded performance for a while before the service collapses) the system gets in a state where it no longer has enough memory to keep its working set fast (which is a major precondition on getting speed out of Mongo and Redis) and the excrement hits the ventilator.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.