Inspired by Jeff's answer here,

I thought this was already discussed in the comments to the blog post announcing the feature [...]

Yeah, reading the blog is one thing, but digging through a forum-like comment-tail when we could actually use the SE engine and simply vote on the most relevant things, I ask why discuss at the blog when there is a tag here? Why not make a mod-only tag for entries duplicating the blog entry (or soft-linking to its contents)?

  • 2
    That's a really good point. Many of the SE users don't know about the SO blog at all.
    – C. Ross
    Oct 7, 2010 at 12:35
  • 2
    +1 because this might get more people involved in the Meta sites.
    – Jon Seigel
    Oct 19, 2010 at 16:53

2 Answers 2


I don't really see the point of this request; the blog is the blog, and meta is meta.

  1. If I want detailed feedback on a topic with voting from the insider community I will open it on meta.

  2. If I want to broadcast a message to the wider stackexchange.com audience, I will post it as a blog entry.

In some blog entries I do both things, but generally they serve different purposes.

  • as I mentioned in the request, there are sometimes trails of comment leading to some new feature or other thing and it would be nice to understand their development (and maybe vote for/against it directly) without the whole noise around. I mean, re 1: You can say you don't want detailed feedback and still you may get some, and then it might also be helpful for you to see votes on how serious you should take it. Re 2, why not use the Inbox for big announcments anyway? Feb 24, 2011 at 11:13
  • oh well, at least there is a flashy red "new" button at the bottom indicating the age of the most recent blog post now (though I'd prefer it to vanish when I clicked it once) Mar 31, 2011 at 13:00
  • 1
    But blogs are (now?) used for more things then SE announcements (many sites have their own blogs). Sep 20, 2012 at 21:56

An easier solution would be to disable blog comments, then re-post blog entries as a "question" on meta.

However, that's a horrible abuse of the Q&A model, so a new type of post would be required, something which doesn't allow answers and is otherwise geared for "announcements" — it would require commenting at 1 rep, for example. You would benefit from the users of the SE site voting, responding, using notifications, etc. — even fixing typos (if they have 2k rep) in the post. This type of post would only be needed on meta sites, and should probably be restricted to moderators/admins.

  • I don't think a meta.SO [discussion] is much different from what we both are basically asking for. Minor stuff like "this sucks" as comments, relevant suggestion on what to improve or "why this is really great (TM)" as answers. And as @Simon stated, meta's comment rep requirement is already 1rep Oct 25, 2010 at 11:13
  • I don't see why answers can't be used, other than them being called "answers". People can comment with 1 rep on MSO.
    – Gelatin
    Oct 25, 2010 at 11:14
  • @Simon I see we agree :) Oct 25, 2010 at 11:14
  • @Simon: I was thinking of announcements on other meta sites, where you cannot comment with 1 rep. For example, blog.SF on meta.SF.
    – Gnome
    Oct 25, 2010 at 11:17
  • @Tobias: I think, when explicitly not asking a question, explicitly breaking with the Q&A model would work better than trying to jam a square peg in a round hole. The best uses of meta.SO still ask questions, with the [discussion] tag as a necessary evil to meet the "1 required tag" requirement when the others don't apply. The SO blog posters appreciate reactions and comments, but they are rarely asking questions, or at least that's my impression.
    – Gnome
    Oct 25, 2010 at 11:22
  • @Roger Pate: but how likely is someone with < 50 rep on SF to read its blog? Also, that is the only example since there only are the blog and SF's blog Oct 25, 2010 at 11:23
  • 1
    @Tobias: So you think moderators/admins of the other sites will never want to make an announcement besides the "system message banner" — which is only a single line, doesn't allow feedback, and evaporates with no public trace? An explicit "blog post" type would allow other uses that also don't fit the Q&A model.
    – Gnome
    Oct 25, 2010 at 11:25
  • @Roger Pate: ok, I didn't see it from that point, but this is a different issue. I am only talking about the big blog announcing SE stuff in general, for which a migration to meta.SO would not yield these problems. But if you [feature-request] a blog-type post, I'll probably +1 it Oct 25, 2010 at 11:39

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .