Skip to main content
replaced http://blog.stackoverflow.com with https://blog.stackoverflow.com
Source Link

As this thread has been locked and abandoned, I've raised this issue in a separate post.


I was dismayed to find that badge progress is unavailable for tag badges1.

When I heard of the badge-tracking feature, I was excited to begin tracking my progress toward the gold javascript badge:

So, I clicked the cog in the badge widget to configure my Next Badge...

... only to find that my desired badge was unavailable:

Kendra notes that, according to the blog postthe blog post:

Once you’ve earned all the privileges, the “next privilege” bar automatically starts tracking your progress toward your closest tag badge (or another one of your choosing).

So, tag badges aren't treated like other badges; you have to earn 20k rep before tracking them... in a separate widget... which is both unexpected and disappointing.

I imagine that design discussion went something like this:

Engineer: Are we really going to put all these tag badges in the unfiltered select your next badge view? That's going to cause a performance hit.
Designer: That, and it's really going to clutter the view. By the way, I need something to put in the next permission space once a user has all permissions. I hate wasted space...
Unicorn: Guys, guys... two birds with one stone! We'll track tag badges in the space used for next privilege... and since they'll need 20k rep, that's only like 1% of our users who will ever potentially see it! Performance hit averted and, as a bonus, we can promote this feature as a "reward" for high-rep users. It all hangs together so perfectly! #guitar-riff #rainbow-trail

Unicorn's solution, while certainly expeditious and spin savvy, leaves a bit to be desired. I'd suggest one of the following:

  • Add some UI cue which indicates to the user that suddenly tag and non-tag badges will be treated differently... you know... just for this aspect of the site... for some unknown reason.
  • Simply add tag badges to the whole badge-tracking feature instead of setting them apart. Maybe filter by favorite tags or offer a 6th tab? I personally don't care that I won't have a next permission to track at 20k. There will still be plenty of badges... in the badge tracking UI. Just put a "you're awesome" sticker in the next permission slot.

1 I'm referring to my profile on stackoverflow (not a child meta site) in case that's not clear from the javascript tag. I only have ~18k rep.

As this thread has been locked and abandoned, I've raised this issue in a separate post.


I was dismayed to find that badge progress is unavailable for tag badges1.

When I heard of the badge-tracking feature, I was excited to begin tracking my progress toward the gold javascript badge:

So, I clicked the cog in the badge widget to configure my Next Badge...

... only to find that my desired badge was unavailable:

Kendra notes that, according to the blog post:

Once you’ve earned all the privileges, the “next privilege” bar automatically starts tracking your progress toward your closest tag badge (or another one of your choosing).

So, tag badges aren't treated like other badges; you have to earn 20k rep before tracking them... in a separate widget... which is both unexpected and disappointing.

I imagine that design discussion went something like this:

Engineer: Are we really going to put all these tag badges in the unfiltered select your next badge view? That's going to cause a performance hit.
Designer: That, and it's really going to clutter the view. By the way, I need something to put in the next permission space once a user has all permissions. I hate wasted space...
Unicorn: Guys, guys... two birds with one stone! We'll track tag badges in the space used for next privilege... and since they'll need 20k rep, that's only like 1% of our users who will ever potentially see it! Performance hit averted and, as a bonus, we can promote this feature as a "reward" for high-rep users. It all hangs together so perfectly! #guitar-riff #rainbow-trail

Unicorn's solution, while certainly expeditious and spin savvy, leaves a bit to be desired. I'd suggest one of the following:

  • Add some UI cue which indicates to the user that suddenly tag and non-tag badges will be treated differently... you know... just for this aspect of the site... for some unknown reason.
  • Simply add tag badges to the whole badge-tracking feature instead of setting them apart. Maybe filter by favorite tags or offer a 6th tab? I personally don't care that I won't have a next permission to track at 20k. There will still be plenty of badges... in the badge tracking UI. Just put a "you're awesome" sticker in the next permission slot.

1 I'm referring to my profile on stackoverflow (not a child meta site) in case that's not clear from the javascript tag. I only have ~18k rep.

As this thread has been locked and abandoned, I've raised this issue in a separate post.


I was dismayed to find that badge progress is unavailable for tag badges1.

When I heard of the badge-tracking feature, I was excited to begin tracking my progress toward the gold javascript badge:

So, I clicked the cog in the badge widget to configure my Next Badge...

... only to find that my desired badge was unavailable:

Kendra notes that, according to the blog post:

Once you’ve earned all the privileges, the “next privilege” bar automatically starts tracking your progress toward your closest tag badge (or another one of your choosing).

So, tag badges aren't treated like other badges; you have to earn 20k rep before tracking them... in a separate widget... which is both unexpected and disappointing.

I imagine that design discussion went something like this:

Engineer: Are we really going to put all these tag badges in the unfiltered select your next badge view? That's going to cause a performance hit.
Designer: That, and it's really going to clutter the view. By the way, I need something to put in the next permission space once a user has all permissions. I hate wasted space...
Unicorn: Guys, guys... two birds with one stone! We'll track tag badges in the space used for next privilege... and since they'll need 20k rep, that's only like 1% of our users who will ever potentially see it! Performance hit averted and, as a bonus, we can promote this feature as a "reward" for high-rep users. It all hangs together so perfectly! #guitar-riff #rainbow-trail

Unicorn's solution, while certainly expeditious and spin savvy, leaves a bit to be desired. I'd suggest one of the following:

  • Add some UI cue which indicates to the user that suddenly tag and non-tag badges will be treated differently... you know... just for this aspect of the site... for some unknown reason.
  • Simply add tag badges to the whole badge-tracking feature instead of setting them apart. Maybe filter by favorite tags or offer a 6th tab? I personally don't care that I won't have a next permission to track at 20k. There will still be plenty of badges... in the badge tracking UI. Just put a "you're awesome" sticker in the next permission slot.

1 I'm referring to my profile on stackoverflow (not a child meta site) in case that's not clear from the javascript tag. I only have ~18k rep.

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

As this thread has been locked and abandoned, I've raised this issue in a separate post.


I was dismayed to find that badge progress is unavailable for tag badges1.

When I heard of the badge-tracking feature, I was excited to begin tracking my progress toward the gold javascript badge:

So, I clicked the cog in the badge widget to configure my Next Badge...

... only to find that my desired badge was unavailable:

Kendra notes that, according to the blog post:

Once you’ve earned all the privileges, the “next privilege” bar automatically starts tracking your progress toward your closest tag badge (or another one of your choosing).

So, tag badges aren't treated like other badges; you have to earn 20k rep before tracking them... in a separate widget... which is both unexpected and disappointing.

I imagine that design discussion went something like this:

Engineer: Are we really going to put all these tag badges in the unfiltered select your next badge view? That's going to cause a performance hit.
Designer: That, and it's really going to clutter the view. By the way, I need something to put in the next permission space once a user has all permissions. I hate wasted space...
Unicorn: Guys, guys... two birds with one stone! We'll track tag badges in the space used for next privilege... and since they'll need 20k rep, that's only like 1% of our users who will ever potentially see it! Performance hit averted and, as a bonus, we can promote this feature as a "reward" for high-rep users. It all hangs together so perfectly! #guitar-riff #rainbow-trail

Unicorn's solution, while certainly expeditious and spin savvy, leaves a bit to be desired. I'd suggest one of the following:

  • Add some UI cue which indicates to the user that suddenly tag and non-tag badges will be treated differently... you know... just for this aspect of the site... for some unknown reason.
  • Simply add tag badges to the whole badge-tracking feature instead of setting them apart. Maybe filter by favorite tags or offer a 6th tab? I personally don't care that I won't have a next permission to track at 20k. There will still be plenty of badges... in the badge tracking UI. Just put a "you're awesome" sticker in the next permission slot.

1 I'm referring to my profilemy profile on stackoverflow (not a child meta site) in case that's not clear from the javascript tag. I only have ~18k rep.

As this thread has been locked and abandoned, I've raised this issue in a separate post.


I was dismayed to find that badge progress is unavailable for tag badges1.

When I heard of the badge-tracking feature, I was excited to begin tracking my progress toward the gold javascript badge:

So, I clicked the cog in the badge widget to configure my Next Badge...

... only to find that my desired badge was unavailable:

Kendra notes that, according to the blog post:

Once you’ve earned all the privileges, the “next privilege” bar automatically starts tracking your progress toward your closest tag badge (or another one of your choosing).

So, tag badges aren't treated like other badges; you have to earn 20k rep before tracking them... in a separate widget... which is both unexpected and disappointing.

I imagine that design discussion went something like this:

Engineer: Are we really going to put all these tag badges in the unfiltered select your next badge view? That's going to cause a performance hit.
Designer: That, and it's really going to clutter the view. By the way, I need something to put in the next permission space once a user has all permissions. I hate wasted space...
Unicorn: Guys, guys... two birds with one stone! We'll track tag badges in the space used for next privilege... and since they'll need 20k rep, that's only like 1% of our users who will ever potentially see it! Performance hit averted and, as a bonus, we can promote this feature as a "reward" for high-rep users. It all hangs together so perfectly! #guitar-riff #rainbow-trail

Unicorn's solution, while certainly expeditious and spin savvy, leaves a bit to be desired. I'd suggest one of the following:

  • Add some UI cue which indicates to the user that suddenly tag and non-tag badges will be treated differently... you know... just for this aspect of the site... for some unknown reason.
  • Simply add tag badges to the whole badge-tracking feature instead of setting them apart. Maybe filter by favorite tags or offer a 6th tab? I personally don't care that I won't have a next permission to track at 20k. There will still be plenty of badges... in the badge tracking UI. Just put a "you're awesome" sticker in the next permission slot.

1 I'm referring to my profile on stackoverflow (not a child meta site) in case that's not clear from the javascript tag. I only have ~18k rep.

As this thread has been locked and abandoned, I've raised this issue in a separate post.


I was dismayed to find that badge progress is unavailable for tag badges1.

When I heard of the badge-tracking feature, I was excited to begin tracking my progress toward the gold javascript badge:

So, I clicked the cog in the badge widget to configure my Next Badge...

... only to find that my desired badge was unavailable:

Kendra notes that, according to the blog post:

Once you’ve earned all the privileges, the “next privilege” bar automatically starts tracking your progress toward your closest tag badge (or another one of your choosing).

So, tag badges aren't treated like other badges; you have to earn 20k rep before tracking them... in a separate widget... which is both unexpected and disappointing.

I imagine that design discussion went something like this:

Engineer: Are we really going to put all these tag badges in the unfiltered select your next badge view? That's going to cause a performance hit.
Designer: That, and it's really going to clutter the view. By the way, I need something to put in the next permission space once a user has all permissions. I hate wasted space...
Unicorn: Guys, guys... two birds with one stone! We'll track tag badges in the space used for next privilege... and since they'll need 20k rep, that's only like 1% of our users who will ever potentially see it! Performance hit averted and, as a bonus, we can promote this feature as a "reward" for high-rep users. It all hangs together so perfectly! #guitar-riff #rainbow-trail

Unicorn's solution, while certainly expeditious and spin savvy, leaves a bit to be desired. I'd suggest one of the following:

  • Add some UI cue which indicates to the user that suddenly tag and non-tag badges will be treated differently... you know... just for this aspect of the site... for some unknown reason.
  • Simply add tag badges to the whole badge-tracking feature instead of setting them apart. Maybe filter by favorite tags or offer a 6th tab? I personally don't care that I won't have a next permission to track at 20k. There will still be plenty of badges... in the badge tracking UI. Just put a "you're awesome" sticker in the next permission slot.

1 I'm referring to my profile on stackoverflow (not a child meta site) in case that's not clear from the javascript tag. I only have ~18k rep.

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

As this thread has been locked and abandonedlocked and abandoned, I've raised this issue in a separate postseparate post.


I was dismayed to find that badge progress is unavailable for tag badges1.

When I heard of the badge-tracking feature, I was excited to begin tracking my progress toward the gold javascript badge:

So, I clicked the cog in the badge widget to configure my Next Badge...

... only to find that my desired badge was unavailable:

KendraKendra notes that, according to the blog post:

Once you’ve earned all the privileges, the “next privilege” bar automatically starts tracking your progress toward your closest tag badge (or another one of your choosing).

So, tag badges aren't treated like other badges; you have to earn 20k rep before tracking them... in a separate widget... which is both unexpected and disappointing.

I imagine that design discussion went something like this:

Engineer: Are we really going to put all these tag badges in the unfiltered select your next badge view? That's going to cause a performance hit.
Designer: That, and it's really going to clutter the view. By the way, I need something to put in the next permission space once a user has all permissions. I hate wasted space...
Unicorn: Guys, guys... two birds with one stone! We'll track tag badges in the space used for next privilege... and since they'll need 20k rep, that's only like 1% of our users who will ever potentially see it! Performance hit averted and, as a bonus, we can promote this feature as a "reward" for high-rep users. It all hangs together so perfectly! #guitar-riff #rainbow-trail

Unicorn's solution, while certainly expeditious and spin savvy, leaves a bit to be desired. I'd suggest one of the following:

  • Add some UI cue which indicates to the user that suddenly tag and non-tag badges will be treated differently... you know... just for this aspect of the site... for some unknown reason.
  • Simply add tag badges to the whole badge-tracking feature instead of setting them apart. Maybe filter by favorite tags or offer a 6th tab? I personally don't care that I won't have a next permission to track at 20k. There will still be plenty of badges... in the badge tracking UI. Just put a "you're awesome" sticker in the next permission slot.

1 I'm referring to my profile on stackoverflow (not a child meta site) in case that's not clear from the javascript tag. I only have ~18k rep.

As this thread has been locked and abandoned, I've raised this issue in a separate post.


I was dismayed to find that badge progress is unavailable for tag badges1.

When I heard of the badge-tracking feature, I was excited to begin tracking my progress toward the gold javascript badge:

So, I clicked the cog in the badge widget to configure my Next Badge...

... only to find that my desired badge was unavailable:

Kendra notes that, according to the blog post:

Once you’ve earned all the privileges, the “next privilege” bar automatically starts tracking your progress toward your closest tag badge (or another one of your choosing).

So, tag badges aren't treated like other badges; you have to earn 20k rep before tracking them... in a separate widget... which is both unexpected and disappointing.

I imagine that design discussion went something like this:

Engineer: Are we really going to put all these tag badges in the unfiltered select your next badge view? That's going to cause a performance hit.
Designer: That, and it's really going to clutter the view. By the way, I need something to put in the next permission space once a user has all permissions. I hate wasted space...
Unicorn: Guys, guys... two birds with one stone! We'll track tag badges in the space used for next privilege... and since they'll need 20k rep, that's only like 1% of our users who will ever potentially see it! Performance hit averted and, as a bonus, we can promote this feature as a "reward" for high-rep users. It all hangs together so perfectly! #guitar-riff #rainbow-trail

Unicorn's solution, while certainly expeditious and spin savvy, leaves a bit to be desired. I'd suggest one of the following:

  • Add some UI cue which indicates to the user that suddenly tag and non-tag badges will be treated differently... you know... just for this aspect of the site... for some unknown reason.
  • Simply add tag badges to the whole badge-tracking feature instead of setting them apart. Maybe filter by favorite tags or offer a 6th tab? I personally don't care that I won't have a next permission to track at 20k. There will still be plenty of badges... in the badge tracking UI. Just put a "you're awesome" sticker in the next permission slot.

1 I'm referring to my profile on stackoverflow (not a child meta site) in case that's not clear from the javascript tag. I only have ~18k rep.

As this thread has been locked and abandoned, I've raised this issue in a separate post.


I was dismayed to find that badge progress is unavailable for tag badges1.

When I heard of the badge-tracking feature, I was excited to begin tracking my progress toward the gold javascript badge:

So, I clicked the cog in the badge widget to configure my Next Badge...

... only to find that my desired badge was unavailable:

Kendra notes that, according to the blog post:

Once you’ve earned all the privileges, the “next privilege” bar automatically starts tracking your progress toward your closest tag badge (or another one of your choosing).

So, tag badges aren't treated like other badges; you have to earn 20k rep before tracking them... in a separate widget... which is both unexpected and disappointing.

I imagine that design discussion went something like this:

Engineer: Are we really going to put all these tag badges in the unfiltered select your next badge view? That's going to cause a performance hit.
Designer: That, and it's really going to clutter the view. By the way, I need something to put in the next permission space once a user has all permissions. I hate wasted space...
Unicorn: Guys, guys... two birds with one stone! We'll track tag badges in the space used for next privilege... and since they'll need 20k rep, that's only like 1% of our users who will ever potentially see it! Performance hit averted and, as a bonus, we can promote this feature as a "reward" for high-rep users. It all hangs together so perfectly! #guitar-riff #rainbow-trail

Unicorn's solution, while certainly expeditious and spin savvy, leaves a bit to be desired. I'd suggest one of the following:

  • Add some UI cue which indicates to the user that suddenly tag and non-tag badges will be treated differently... you know... just for this aspect of the site... for some unknown reason.
  • Simply add tag badges to the whole badge-tracking feature instead of setting them apart. Maybe filter by favorite tags or offer a 6th tab? I personally don't care that I won't have a next permission to track at 20k. There will still be plenty of badges... in the badge tracking UI. Just put a "you're awesome" sticker in the next permission slot.

1 I'm referring to my profile on stackoverflow (not a child meta site) in case that's not clear from the javascript tag. I only have ~18k rep.

added 105 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 206 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 206 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 43 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
deleted 12 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
edited body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
deleted 2 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 40 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
deleted 5 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 12 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
deleted 2 characters in body; added 15 characters in body; deleted 24 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 102 characters in body; added 32 characters in body; added 12 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 19 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
deleted 6 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 47 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
deleted 81 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 7 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 33 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 517 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
added 8 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
deleted 53 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading
deleted 53 characters in body
Source Link
canon
  • 2.2k
  • 1
  • 24
  • 33
Loading