Skip to main content
16 events
when toggle format what by license comment
Jun 3, 2020 at 13:30 history edited CommunityBot
Commonmark migration
Mar 20, 2017 at 10:31 history edited CommunityBot
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Apr 24, 2014 at 13:50 history edited CommunityBot
Migration of MSO links to MSE links
Jun 17, 2013 at 17:33 comment added Deer Hunter @Jaydles - nice to know that. This answer is now my personal record for no. of downvotes, let's see how it goes.
Jun 17, 2013 at 17:15 comment added Jaydles StaffMod Screenshot fixed. Regarding the other issue, I do think second person sounds less condescending, but we'll take a look at the tradeoffs.
Jun 16, 2013 at 15:55 comment added Adam Lear StaffMod @DeerHunter Yeah, that's a fair point. We could do better with responding to feedback during major rollouts.
Jun 16, 2013 at 4:49 comment added Deer Hunter @AnnaLear - Err.. how does one make sure he's not beating an already fixed UI bug? That is, getting feedback on submitted bugreps is quite valuable, yet I find it is done rather informally - a sea of comments and no links to resolutions, even "Not a Bug (TM)". In the usual course of meta-work, there are resolutions on questions, but with grand rollouts we are reluctant to post separate bugreps and unceremoniously dump all the stuff (impressions and reproducible faults) into one question's space. Possibly an area for improvement.
Jun 16, 2013 at 4:38 comment added Adam Lear StaffMod Far as the "unclear what you're asking" wording goes... yeah, I'm not a big fan of that either. My personal preference would be for "unclear what is being asked here" as the least awkward option. I'll bring it up internally on Monday and see where we land on that.
Jun 16, 2013 at 4:37 comment added Adam Lear StaffMod This post being here is a call for feedback and review that you're asking for. The changes haven't yet been rolled out to the entire network, and rolling out to MSO first to work out any leftover bugs or make last-minute adjustments based on community feedback is how we roll out most of our features.
Jun 16, 2013 at 4:04 comment added Deer Hunter @AnnaLear - thanks, I found that it was an artefact from testing while doing a sample flagging here at mSO. On UXSE and others - review is off-topic there, as well, was referring to checking corner cases there. The introduction of controversial interface changes with glaring omissions becomes a trend lately, could have been avoided by offering the design for review through mSO before rolling out. Yannis had a valid point on personal pronouns but there was no reaction.
Jun 16, 2013 at 2:30 comment added Adam Lear StaffMod On another note, proofreading is off-topic on English SE itself. :) Folks who frequent UX, English, and any other site are more than welcome to participate here to help design and grow the network.
Jun 16, 2013 at 2:29 comment added Adam Lear StaffMod "About on-topic" is just an artefact from the test server that made it into a screenshot. What happens in reality is that the default off-topic close reason pulls the right phrasing from site settings. So, here on MSO it is "This question does not appear to be about Stack Overflow of the Stack Exchange engine that powers the Stack Exchange network, within the scope defined in the FAQ." (Though we should probably kill that comma before "within".)
Jun 16, 2013 at 2:26 history edited Adam LearStaffMod CC BY-SA 3.0
Fixed formatting to make the answer more readable and make the quotes and emphasized parts more clear
Jun 15, 2013 at 7:27 comment added Deer Hunter @Werner - based on the picture presented in the question - think this needs to be edited. The choice of personal pronouns to refer to the OP as "you" is consistently wrong throughout the reason page. You may be right in that the involvement of Graphic Design, UX and English should be discussed in a separate question.
Jun 15, 2013 at 7:19 comment added Werner This seems primarily opinion-based...
Jun 15, 2013 at 6:07 history answered Deer Hunter CC BY-SA 3.0