# Pre-RFC: User namespaces on crates.io

**URL:** <https://internals.rust-lang.org/t/pre-rfc-user-namespaces-on-crates-io/12851>\
**Category:** Web Presence\
**Created:** [August 7, 2020, 12:05pm UTC](https://internals.rust-lang.org/t/pre-rfc-user-namespaces-on-crates-io/12851 "2020-08-07T12:05:02Z")\
**Posts on this page:** 1\
**Showing post:** 39

<div class="post-metadata">

**Author:** ![bascule](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/bascule/32/3057_2.png) [@bascule](https://internals.rust-lang.org/u/bascule)\
**Post date:** [September 3, 2020, 6:54pm UTC](https://internals.rust-lang.org/t/pre-rfc-user-namespaces-on-crates-io/12851/39 "2020-09-03T18:54:22Z")

</div>

> [@anon2808951](#):
>
> Especially as it prevents accumulating knowledge gained with previous efforts and means that newer proposals are often a step back, or try to re-litigate problems that were already solved before.

Usually when one of these namespacing pre-RFCs is posted, someone helpfully posts a summary of previous relevant work in that area. I guess that didn't happen in this issue.

Here is a list from ~1 year ago on a namesquatting-related thread, but it also includes several pre-RFCs on namespacing as namespacing is often suggested as a solution for namesquatting:

> [@Pre-RFC: Formal squatting policy on crates.io](https://internals.rust-lang.org/t/pre-rfc-formal-squatting-policy-on-crates-io/11302/3):
>
> Previously on crate squatting: Some Pre-RFCs to deal with it Some related incidents

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-user-namespaces-on-crates-io/12851)._
