# Pre-RFC: crate creator rate limiting in docs.rs

**URL:** <https://internals.rust-lang.org/t/pre-rfc-crate-creator-rate-limiting-in-docs-rs/15518>\
**Category:** tools and infrastructure\
**Created:** [October 26, 2021, 7:02pm UTC](https://internals.rust-lang.org/t/pre-rfc-crate-creator-rate-limiting-in-docs-rs/15518 "2021-10-26T19:02:23Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![ckaran](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@ckaran](https://internals.rust-lang.org/u/ckaran)\
**Post date:** [October 26, 2021, 8:54pm UTC](https://internals.rust-lang.org/t/pre-rfc-crate-creator-rate-limiting-in-docs-rs/15518/19 "2021-10-26T20:54:50Z")

</div>

> [@mathstuf](#):
>
> Sure. I'm saying that reporting such behavior to GitHub is likely to get their abuse team on the case and shut down the backing GitHub accounts too (that is, `crates.io` is not necessarily on its own when dealing with account abuse).

Yup, and as long as they have GitHub accounts, that'll be a good way to handle it. But as @kornel [pointed out in the other topic](https://internals.rust-lang.org/t/docs-rs-build-prioritization/15511/8), you don't need a GitHub account to publish to [crates.io](http://crates.io) (and thence to docs.rs). So relying on GitHub's policies won't solve it.

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-crate-creator-rate-limiting-in-docs-rs/15518)._