- @JMV1070 what was Collie doing in the 'ville? in reply to JMV1070 #
- @justintadlock ping @westi? He may have an idea about why P2 is causing problems on the make.wordpress site. in reply to justintadlock #
- @justintadlock I'm not seeing anything in spam or awaiting moderation… Hopefully you copy/pasted your comment? in reply to justintadlock #
- @JMV1070 awesome! That kind of thing never took place when I lived there… in reply to JMV1070 #
- Does the new-in-#wordpress 3.1 Admin Bar cause display issues for your Theme? Fix using the CSS class body.admin-bar. h/t @markjaquith in reply to markjaquith #
- @technosailor unless you have to fly to get there, in which case just leave them off. It will make it easier for the TSA. in reply to technosailor #
- @wptavern looks like a scraper. See the notice at the end of this post: http://wpnewswire.com/seo-optimization/ in reply to wptavern #
- @pwilson24 way to throw Adrian Klemm under the bus there, Belickick! in reply to pwilson24 #
- @ryancduff @tommccammon I call shenanigans. Clearly, if true, TSA would be making use of the equally wonderful Facebook Groups "feature". 😉 in reply to ryancduff #
- @ewerickson just between us "Taliban" Family Men: he didn't miss the point; he was a troll. Don't sweat it. in reply to ewerickson #
- @nathanrice then perhaps the powers-that-be should stop opening old wounds just to further petty grudges? How does that help the community? in reply to nathanrice #
- @yoast @Skitzzo I guarantee it doesn't hurt @pearsonified. It only hurts the soon-to-be erstwhile happy users of PressRow on WPCOM. in reply to yoast #
- @yoast @Skitzzo if true, that's dumb, psychotic, and suicidal in reply to yoast #
- @bgardner they have nobody to blame but themselves. For all the complaints about @pearsonified being a jerk, this move is childish. in reply to bgardner #
- @andrea_r well down here, I'm grilling some pork steaks! in reply to andrea_r #
- @carlhancock @skitzzo @yoast @pearsonified but the bottom line is: WPCOM is a service. If you want control, move to self-hosted #wordpress in reply to carlhancock #
- @andrea_r the real question for me is: what to make for dinner for my wife's birthday tomorrow? in reply to andrea_r #
- @yoast @Skitzzo if only. in reply to yoast #
- @andrea_r not with a 3yo and an almost 2yo… not exactly relaxed/romantic. Besides, I like to cook. 🙂 in reply to andrea_r #
- @zamoose @carlhancock nope; WPCOM this time: http://bit.ly/drSdbk Cutline Part 2: Screwing Over Happy PressRow Users for Pettiness & Grudges in reply to zamoose #
- @zamoose @carlhancock and the misinformation and @pearsonified FUD in that forum thread from people defending the move is utterly astounding in reply to zamoose #
- "But that doesn’t mean I’m disloyal to this president" – thanks for the Twitter-friendly, Obama-loyalty soundbite, @clairecmc! #
- @zamoose knew for a while that it was coming. Matt announced it weeks ago. It's foolish, petty, and counter-productive. in reply to zamoose #
- @nacin but the Theme can be updated. The FUD should be water under the bridge by now. It's the WPCOM PressRow users who are unhappy, not me in reply to nacin #
- @nacin I think it's a bad leadership decision borne out of a petty grudge, which I think is unhealthy for the project. in reply to nacin #
- @nacin Just make Pilcrow a better Theme than PressRow, and let the latter fade away quietly. Why raise hackles? Just move on. #okimdone 🙂 in reply to nacin #
- @zamoose but existing users are happy (being forced to change Themes). They are the ones hurt, not the developer. in reply to zamoose #
- @nacin does that mean we can start enforcing obsolescence requirements?!? 😀 I'm all for suspending obsolete, no-longer-supported Themes! in reply to nacin #
- @zamoose you know I have no complaints about ensuring Theme code is current. It's forcing users to switch Themes that is a problem. in reply to zamoose #
- @zamoose agreed. Now, to see that same theory applied to ALL Themes available on WPCOM… in reply to zamoose #
- @zamoose they tried that with Coraline. It didn't turn out so well. in reply to zamoose #
- @technosailor @Otto42 I thought it was "fail early, fail often"? in reply to technosailor #
- @nacin and props for the advanced warning, and being up-front about the reasons. Both are good moves. in reply to nacin #
- @devinsays I don't expect us to get the green light on that anytime soon. I was just busting @nacin's chops for opening the door 😉 in reply to devinsays #
- @wptavern write good content, and I'd read it at WTLC or WPT. 😉 in reply to wptavern #