Can we reveal the bug category to all since it's post v1 now?

Matches

The bug category had more posts than meta. That should be top ranked in disco searches.

PJH

Well the only reason it was hidden was, at the time, it rather dominated the most-recent-posts list to google and those not logged in (with the potential of scaring new users away.) - see no reason why it shouldn't be demoted now...

Matches

That's right, prepare them good and proper to be dominated by bugs.

PJH

@PJH said:

see no reason why it shouldn't be demoted now...

Except it's just brought a whole new category of posts into the 2^n badges count it appears...

Kuro

Yay, I got a new badge. Don't take it away from me now!

Also: Why is bug excluded from 2^n anyway? Not only are bug-reports usually at least mediocre-quality posts. The topics in there derail at the same speed as everywhere else. Excluding them seems odd!

Filed Under: Free the Bug-Category from it's shackles!

Matches

They were in a 'private' category, all of which were excluded and non Google indexable.

PJH

@Kuro said:

Also: Why is bug excluded from 2^n anyway?

It was restricted to TL1 and above. Any restricted category gets excluded - it wasn't anything about the fact it was a bugs category.

Matches

You could have had an in b4 fail there my friend, so close, yet so far.

Kuro

That excuse would count if I didn't know you controlled the badge-query. Or is there a general "you can never include private-categories in anything ever"-rule in the code?

Filed Under: WHERE category.privacy != 'private OR category.name == 'Bug'

Arantor

I don't care, I'm still free
You can't take the ~~sky~~ 2^12 badge from me (for now)

Matches

Simplicity.

PJH

@Kuro said:

That excuse would count if I didn't know you controlled the badge-query.

The table I run the query against is actually a convenient view (created, I'm guessing from the name badge_posts, specifically for post related badges) - the basis of which I've not even considered looking at yet; I'm assuming it's a join against at least three tables - and it simply doesn't include posts that are in restricted categories.

Changing the query to either

specifically include posts not in that view or
re-create the view locally to include restricted

would make them even more complicated than they are at the moment.

Ok - here's the definition of badge_posts:

 SELECT p.id, p.user_id, p.topic_id, p.post_number, p.raw, p.cooked, p.created_at, p.updated_at, p.reply_to_post_number, p.reply_count, p.quote_count, p.deleted_at, p.off_topic_count, p.like_count, p.incoming_link_count, p.bookmark_count, p.avg_time, p.score, p.reads, p.post_type, p.vote_count, p.sort_order, p.last_editor_id, p.hidden, p.hidden_reason_id, p.notify_moderators_count, p.spam_count, p.illegal_count, p.inappropriate_count, p.last_version_at, p.user_deleted, p.reply_to_user_id, p.percent_rank, p.notify_user_count, p.like_score, p.deleted_by_id, p.edit_reason, p.word_count, p.version, p.cook_method, p.wiki, p.baked_at, p.baked_version, p.hidden_at, p.self_edits
   FROM posts p
   JOIN topics t ON t.id = p.topic_id
   JOIN categories c ON c.id = t.category_id
  WHERE c.allow_badges AND p.deleted_at IS NULL AND t.deleted_at IS NULL AND NOT c.read_restricted AND t.visible;

Arantor

That makes my recent receipt of 2^12 interesting, I could have sworn more of my posts were in that thread, or in restricted boards but I guess not.