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

Update:
George Edisons comments appear to explain most issues raised here (if not all), so I reformulated the question to reduce the noise and allow for an answer accordingly. I have considered to delete the question instead, but apparently it triggered one user to assess and resolve the lack of private API badge assignment to him, so there appear to be some useful outcome of my procrastinations at least ;)

Background:
I have been looking at this topic with the assumption that the private API beta worked just like the Stack Exchange 2.0 private betas, where all activities are at the target host starting from day one and only the access barrier is lowered over time. However, if I read things correctly now, the private API beta has been hosted on a separate site, which got migrated to Stack Apps later on with manual steps involved.


After one issue of reputation inflationreputation inflation via multiple badge assignment has been resolved recentlyhas been resolved recently, I'm again confused by this topic due to the introduction of the latest procrastination playground - the new per-site reputation leagues do show for example:

Maybe the whole registration/membership has been reset after the private beta and the badges are triggered by the next visit only, but this doesn't explain the API Evangelist badges and could qualify as a confusing bug in the 'member for' display at least. Besides, looking at the API Evangelist badgesAPI Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

Is it possible to get this explained/sorted without dissecting any case individually?

Update:
George Edisons comments appear to explain most issues raised here (if not all), so I reformulated the question to reduce the noise and allow for an answer accordingly. I have considered to delete the question instead, but apparently it triggered one user to assess and resolve the lack of private API badge assignment to him, so there appear to be some useful outcome of my procrastinations at least ;)

Background:
I have been looking at this topic with the assumption that the private API beta worked just like the Stack Exchange 2.0 private betas, where all activities are at the target host starting from day one and only the access barrier is lowered over time. However, if I read things correctly now, the private API beta has been hosted on a separate site, which got migrated to Stack Apps later on with manual steps involved.


After one issue of reputation inflation via multiple badge assignment has been resolved recently, I'm again confused by this topic due to the introduction of the latest procrastination playground - the new per-site reputation leagues do show for example:

  • Sorting by August
  • yields 1 user being rewarded the API Beta badge despite being a member as of Aug 12 only
  • Sorting by June
  • yields 3 users being rewarded the API Evangelist badge, where some don't have any posts before May 21 (start of public API beta) and some don't have any posts at all - see my related question What constitutes 'active participation' in the private API beta?
  • yields 5 users being rewarded the API Beta badge, where some are a member as of May 21 or even June only

Maybe the whole registration/membership has been reset after the private beta and the badges are triggered by the next visit only, but this doesn't explain the API Evangelist badges and could qualify as a confusing bug in the 'member for' display at least. Besides, looking at the API Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

Is it possible to get this explained/sorted without dissecting any case individually?

Update:
George Edisons comments appear to explain most issues raised here (if not all), so I reformulated the question to reduce the noise and allow for an answer accordingly. I have considered to delete the question instead, but apparently it triggered one user to assess and resolve the lack of private API badge assignment to him, so there appear to be some useful outcome of my procrastinations at least ;)

Background:
I have been looking at this topic with the assumption that the private API beta worked just like the Stack Exchange 2.0 private betas, where all activities are at the target host starting from day one and only the access barrier is lowered over time. However, if I read things correctly now, the private API beta has been hosted on a separate site, which got migrated to Stack Apps later on with manual steps involved.


After one issue of reputation inflation via multiple badge assignment has been resolved recently, I'm again confused by this topic due to the introduction of the latest procrastination playground - the new per-site reputation leagues do show for example:

  • Sorting by August
  • yields 1 user being rewarded the API Beta badge despite being a member as of Aug 12 only
  • Sorting by June
  • yields 3 users being rewarded the API Evangelist badge, where some don't have any posts before May 21 (start of public API beta) and some don't have any posts at all - see my related question What constitutes 'active participation' in the private API beta?
  • yields 5 users being rewarded the API Beta badge, where some are a member as of May 21 or even June only

Maybe the whole registration/membership has been reset after the private beta and the badges are triggered by the next visit only, but this doesn't explain the API Evangelist badges and could qualify as a confusing bug in the 'member for' display at least. Besides, looking at the API Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

Is it possible to get this explained/sorted without dissecting any case individually?

Shortened update notice.
Source Link
Steffen Opel
  • 1.4k
  • 8
  • 14

Update:
George Edisons comments appear to explain most issues raised here (if not all), so I reformulated the question to reduce the noise and allow for a realan answer (from George?!) accordingly. I have considered to delete the question instead, but apparently it triggered one user to assess and resolve the lack of private API badge assignment to him, so there appear to be some useful outcome of my procrastinations at least ;)

Background:
I have been looking at this topic with the assumption that the private API beta worked just like the Stack Exchange 2.0 private betas, where all activities are at the target host starting from day one and only the access barrier is lowered over time. However, if I read things correctly now, the private API beta has been hosted on a separate site, which got migrated to Stack Apps later on with manual steps involved.


After one issue of reputation inflation via multiple badge assignment has been resolved recently, I'm again confused by this topic due to the introduction of the latest procrastination playground - the new per-site reputation leagues do show for example:

  • Sorting by August
  • yields 1 user being rewarded the API Beta badge despite being a member as of Aug 12 only
  • Sorting by June
  • yields 3 users being rewarded the API Evangelist badge, where some don't have any posts before May 21 (start of public API beta) and some don't have any posts at all - see my related question What constitutes 'active participation' in the private API beta?
  • yields 5 users being rewarded the API Beta badge, where some are a member as of May 21 or even June only

Maybe the whole registration/membership has been reset after the private beta and the badges are triggered by the next visit only, but this doesn't explain the API Evangelist badges and could qualify as a confusing bug in the 'member for' display at least. Besides, looking at the API Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

Is it possible to get this explained/sorted without dissecting any case individually?

Update:
George Edisons comments appear to explain most issues raised here (if not all), so I reformulated the question to reduce the noise and allow for a real answer (from George?!) accordingly. I have considered to delete the question instead, but apparently it triggered one user to assess and resolve the lack of private API badge assignment to him, so there appear to be some useful outcome of my procrastinations at least ;)

Background:
I have been looking at this topic with the assumption that the private API beta worked just like the Stack Exchange 2.0 private betas, where all activities are at the target host starting from day one and only the access barrier is lowered over time. However, if I read things correctly now, the private API beta has been hosted on a separate site, which got migrated to Stack Apps later on with manual steps involved.


After one issue of reputation inflation via multiple badge assignment has been resolved recently, I'm again confused by this topic due to the introduction of the latest procrastination playground - the new per-site reputation leagues do show for example:

  • Sorting by August
  • yields 1 user being rewarded the API Beta badge despite being a member as of Aug 12 only
  • Sorting by June
  • yields 3 users being rewarded the API Evangelist badge, where some don't have any posts before May 21 (start of public API beta) and some don't have any posts at all - see my related question What constitutes 'active participation' in the private API beta?
  • yields 5 users being rewarded the API Beta badge, where some are a member as of May 21 or even June only

Maybe the whole registration/membership has been reset after the private beta and the badges are triggered by the next visit only, but this doesn't explain the API Evangelist badges and could qualify as a confusing bug in the 'member for' display at least. Besides, looking at the API Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

Is it possible to get this explained/sorted without dissecting any case individually?

Update:
George Edisons comments appear to explain most issues raised here (if not all), so I reformulated the question to reduce the noise and allow for an answer accordingly. I have considered to delete the question instead, but apparently it triggered one user to assess and resolve the lack of private API badge assignment to him, so there appear to be some useful outcome of my procrastinations at least ;)

Background:
I have been looking at this topic with the assumption that the private API beta worked just like the Stack Exchange 2.0 private betas, where all activities are at the target host starting from day one and only the access barrier is lowered over time. However, if I read things correctly now, the private API beta has been hosted on a separate site, which got migrated to Stack Apps later on with manual steps involved.


After one issue of reputation inflation via multiple badge assignment has been resolved recently, I'm again confused by this topic due to the introduction of the latest procrastination playground - the new per-site reputation leagues do show for example:

  • Sorting by August
  • yields 1 user being rewarded the API Beta badge despite being a member as of Aug 12 only
  • Sorting by June
  • yields 3 users being rewarded the API Evangelist badge, where some don't have any posts before May 21 (start of public API beta) and some don't have any posts at all - see my related question What constitutes 'active participation' in the private API beta?
  • yields 5 users being rewarded the API Beta badge, where some are a member as of May 21 or even June only

Maybe the whole registration/membership has been reset after the private beta and the badges are triggered by the next visit only, but this doesn't explain the API Evangelist badges and could qualify as a confusing bug in the 'member for' display at least. Besides, looking at the API Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

Is it possible to get this explained/sorted without dissecting any case individually?

Reformulated question to address initial misconception regarding the topic at hand.
Source Link
Steffen Opel
  • 1.4k
  • 8
  • 14

Why has What are the mechanics of private API beta badge black market still not been shut down/reputation rewards?

Update:

George
George Edisons comments to my question appear to explain most issues raised here (if not all), so I reformulated the question to reduce the noise and allow for a real answer (from George?!) accordingly. I have considered to delete the question instead, but apparently it triggered one user to assess and resolve the lack of private API badge assignment to him, so there appear to be some useful outcome of my procrastinations at least ;)

please disregard this question for a momentBackground:
I have been looking at this topic with the assumption that the private API beta worked just like the Stack Exchange 2.0 private betas, as unfortunatelywhere all activities are at the target host starting from day one and only the access barrier is lowered over time. However, if I have to leave rightread things correctly now for, the private API beta has been hosted on a road trip - I'll update my questionseparate site, which got migrated to Stack Apps later on Sunday/Monday as appropriatewith manual steps involved.

WhileAfter one issue of reputation inflation via multiple badge assignment has been resolved recently, the root cause has apparently not been tackled yet, as easily seen inI'm again confused by this topic due to the just officially announcedintroduction of the latest procrastination playground - the new per-site reputation leagues do show for example:

  • Sorting by August
  • yields 1 user being rewarded the API Beta badge for 2k reputation despite being a member as of Aug 12 only
  • Sorting by July
  • yields 3 users being rewarded the API Beta badge for 2k reputation, where one is a member as of May 21member as of Aug 12 only - don't know the exact cutoff date, but the Public Beta announcement has been on May 20
  • Sorting by June
  • yields 3 users being rewarded the API Evangelist badge for 4k reputation, where some don't have any posts before May 21don't have any posts before May 21 (start of public API beta) and some don't have anydon't have any posts at all - see my related question What constitutes 'active participation' in the private API beta?
  • yields 5 users being rewarded the API Beta badge for 2k reputation, where some are a member as of May 21 or even June only - again, don't know the exact cutoff date, but the Public Beta announcement has been on May 20member as of May 21 or even June only

There might be several issues involved which might confuseMaybe the whole pictureregistration/membership has been reset after the private beta and the badges are triggered by the next visit only, but something seems wrong here orthis doesn't explain the API Evangelist badges and could qualify as a confusing bug in the 'member for' display at best:least. Besides, looking at the API Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

  • Maybe the cutoff date is a 24 hour window bordering into May 21, which might explain some API Beta badges to be correct, but some of these May 21 cases have been rewarded a API Evangelist badge without any post still.
  • Maybe the whole registration/membership has been reset after the private beta and the badges are triggered by the next visit only, but again, this doesn't explain the API Evangelist badges and would qualify as a confusing bug in the 'member for' display at least.
  • Looking at the API Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

Is it possible to get this shadow economy explained/sorted without dissecting any case individually? ;)

Why has the badge black market still not been shut down?

Update:

George Edisons comments to my question appear to explain most issues raised here (if not all), so please disregard this question for a moment, as unfortunately I have to leave right now for a road trip - I'll update my question on Sunday/Monday as appropriate.

While one issue of reputation inflation via multiple badge assignment has been resolved recently, the root cause has apparently not been tackled yet, as easily seen in the just officially announced new per-site reputation leagues:

  • Sorting by August
  • yields 1 user being rewarded the API Beta badge for 2k reputation despite being a member as of Aug 12 only
  • Sorting by July
  • yields 3 users being rewarded the API Beta badge for 2k reputation, where one is a member as of May 21 only - don't know the exact cutoff date, but the Public Beta announcement has been on May 20
  • Sorting by June
  • yields 3 users being rewarded the API Evangelist badge for 4k reputation, where some don't have any posts before May 21 and some don't have any posts at all - see my related question What constitutes 'active participation' in the private API beta?
  • yields 5 users being rewarded the API Beta badge for 2k reputation, where some are a member as of May 21 or even June only - again, don't know the exact cutoff date, but the Public Beta announcement has been on May 20

There might be several issues involved which might confuse the whole picture, but something seems wrong here or confusing at best:

  • Maybe the cutoff date is a 24 hour window bordering into May 21, which might explain some API Beta badges to be correct, but some of these May 21 cases have been rewarded a API Evangelist badge without any post still.
  • Maybe the whole registration/membership has been reset after the private beta and the badges are triggered by the next visit only, but again, this doesn't explain the API Evangelist badges and would qualify as a confusing bug in the 'member for' display at least.
  • Looking at the API Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

Is it possible to get this shadow economy explained/sorted without dissecting any case individually? ;)

What are the mechanics of private API beta badge/reputation rewards?

Update:
George Edisons comments appear to explain most issues raised here (if not all), so I reformulated the question to reduce the noise and allow for a real answer (from George?!) accordingly. I have considered to delete the question instead, but apparently it triggered one user to assess and resolve the lack of private API badge assignment to him, so there appear to be some useful outcome of my procrastinations at least ;)

Background:
I have been looking at this topic with the assumption that the private API beta worked just like the Stack Exchange 2.0 private betas, where all activities are at the target host starting from day one and only the access barrier is lowered over time. However, if I read things correctly now, the private API beta has been hosted on a separate site, which got migrated to Stack Apps later on with manual steps involved.

After one issue of reputation inflation via multiple badge assignment has been resolved recently, I'm again confused by this topic due to the introduction of the latest procrastination playground - the new per-site reputation leagues do show for example:

  • Sorting by August
  • yields 1 user being rewarded the API Beta badge despite being a member as of Aug 12 only
  • Sorting by June
  • yields 3 users being rewarded the API Evangelist badge, where some don't have any posts before May 21 (start of public API beta) and some don't have any posts at all - see my related question What constitutes 'active participation' in the private API beta?
  • yields 5 users being rewarded the API Beta badge, where some are a member as of May 21 or even June only

Maybe the whole registration/membership has been reset after the private beta and the badges are triggered by the next visit only, but this doesn't explain the API Evangelist badges and could qualify as a confusing bug in the 'member for' display at least. Besides, looking at the API Evangelist badges in isolation yields users with posts after May 20 only and no posts or no activity at all even.

Is it possible to get this explained/sorted without dissecting any case individually?

Added short term notice regarding pending update.
Source Link
Steffen Opel
  • 1.4k
  • 8
  • 14
Loading
Fixed phrasing/typos.
Source Link
Steffen Opel
  • 1.4k
  • 8
  • 14
Loading
Source Link
Steffen Opel
  • 1.4k
  • 8
  • 14
Loading