Repository navigation
Labeler rate limits: a raise path for high-volume mechanical labelers #5888
80sFauxstalgia
started this conversation in
Protocol (atproto)
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The docs put labeling services at 5 labels/s, 10,000/hour and 100,000/day. The relay page says its default limits "can be raised" on request; the label limits page does not say either way.
Some useful labelers are mechanical and high-volume. An alt-text labeler that labels every media post lacking alt text is one: counting a recent 7-day window on the firehose, about 506,000 media posts a day had no alt text (74.5% of media posts; peak hour 29,708, about 8.3/s). At 100,000 a day such a labeler covers about 1 in 5 eligible posts, and a hide-by-default accessibility label that misses 80% of posts does not serve its purpose.
Would Bluesky consider a documented raise path or a tier for labelers that compute labels only from record fields (no media fetches, no content judgment, no backfill), perhaps with published coverage stats? Happy to share ingestion numbers. If yes, the rate-limits page could say so, like the relay section does.
I opened bluesky-social/bps-website#55 to add the same note to the rate-limits page.
All reactions