Collecting ideas on comment moderation. Not policy ideas but how to deal with the before and after.
https://github.com/peterwilsoncc/rapid-comment-moderation/issues/1
Archives: Notes
-
Half way through a first round interview with a recruiter she abruptly called it off and told me it was hopeless.
I’d never get the job, there was no point continuing the interview.
The dumb twenty-six year-old in the room, got up disheartened and prepared to leave.
The recruiter handed me a pen & piece of paper and told me we’d start again same time next week. Next week I’d come prepared & on the paper would be all the things I’d ever done in tech.
There would be no “I kind of can do…” or “I’ve tinkered with…” In their place there would be definitive statements “I can do…”
like an idiot, I cancelled the following weeks interview via email a few days later – a dumb twenty-six year old not realising she saw potential I didn’t.
When imposter syndrome hits, I often think of the recruiter and whether it would still be hitting if I’d taken her up on her offer.
Probably. Best I can do is try and adopt some advise I half listened to as a dumb twenty-six year old. Following through and getting all the advice would have been a good idea.
-
writing a post on my phone over breakfast. http://www.whatdomobileuserswanttodo.com
-
Severely looking forward to @krogsgard‘s full post on the Pearson/Mullenweg brouhaha.
-
WordPress’s plugins SVN has a ticketing system & I’ve been closing them syncing Github commits. Oops.
https://plugins.trac.wordpress.org/ticket/19#comment:7 -
Four years since my first WordPress props. It broke backward compatibility and remains in core. https://core.trac.wordpress.org/ticket/18018
-
It must be said, despite sweary rants giving him every reason not to be, @markjaquith is incredibly responsive.
https://core.trac.wordpress.org/ticket/22889 -
Hmm, unblessed => punt it => committed and screw progressive enhancement in the 7 hours Aus was sleeping. https://core.trac.wordpress.org/ticket/22889
Back in the day it was decided comment replies were core functionality. It either is or it isn’t, not some half assed enhancement.
This commit essentially says comment replies are no-longer core functionality. Clicking reply “too early” can currently explode JavaScript.
Result: on a large comment thread, attempting to reply to a comment can kill the feature all together even for users running JavaScript.
On an ideal network this is fine, most people are not on ideal networks. Fuck, parts of Florida are stuck on shitty 2G connections.
A three year old ticket with negative usability implications should not go from comatose to punted to committed over the course of a night.
-
@cnn oh my god, ISIS have invaded North Melbourne #omgisis

-
For your podcatcher, audio of Mark Scott’s talk last night. https://huffduffer.com/peterwilsoncc/244826
-
Official status as @Joy949 volunteer came through last night following @AviOnJOY‘s successful goading.
@pwcc I’d love to dare you to try and achieve that with a complex WordPress theme and lots of plugins. I can’t even get close. :(
— Djelibeybi (@Djelibeybi) May 31, 2015
-
Looks like @Yoast SEO auto-updated, wondering if it’s @WordPress or @mediatemple. It’s pathetic an XSS fix was in a feature release.
-
Quark developer @maddisondesigns has suggested widening the scope of WordPress customizer improvements.
http://maddisondesigns.com/2015/06/lets-talk-about-the-wordpress-customizer/ -
The @linkedin iOS app now shows the anti pattern trying to trick you into giving up your contacts on every open. Dick move deleted.
-
Wind turbines: quieter than an asthmatic’s wheeze.
How loud is a wind turbine? pic.twitter.com/vHPN1nd0vk
— Bob Earth (@bobearth) June 11, 2015
-
Any chance of a WPSEO 2.1.2 with just the XSS fix @yoast? I’d rather wait for 2.2 bug fixes.






