From b63e9c6ae7753058ca8551d0dcff9b964536be5f Mon Sep 17 00:00:00 2001 From: Tobias Bieniek Date: Tue, 7 Nov 2023 10:41:38 +0100 Subject: [PATCH] Integrate "crates.io Policy Update" RFC see https://github.com/rust-lang/rfcs/pull/3463 --- app/components/footer.hbs | 2 +- app/templates/data-access.hbs | 2 +- app/templates/policies.hbs | 274 ++++++++++++++++------------------ 3 files changed, 133 insertions(+), 145 deletions(-) diff --git a/app/components/footer.hbs b/app/components/footer.hbs index e25435dc090..4f8c37c73e9 100644 --- a/app/components/footer.hbs +++ b/app/components/footer.hbs @@ -22,7 +22,7 @@

Policies

+ +

We recognize that not all nudity or content related to sexuality is obscene. We may allow visual and/or textual + depictions in artistic, educational, historical or journalistic contexts, or as it relates to victim advocacy. In some + cases a disclaimer can help communicate the context of the project.

+ +

Violations and Enforcement

+ +

crates.io retains full discretion to take action in response to a violation of these policies, including account + suspension, account termination, or removal of content.

+ +

We will however not be proactively monitoring the site for these kinds of violations, but instead relying on the + community to draw them to our attention.

+ +

While the majority of interactions between individuals in the Rust community falls within our policies, violations of + those policies do occur at times. When they do, the crates.io team may need to take enforcement action to address the + violations. In all cases, content and account deletion is permanent and there is no basis to reverse these moderation + actions taken by the crates.io team. Account suspension may be lifted at the team's discretion however, for + example in the case of someone's account being compromised.

+ +

Credits & License

+ +

This policy is partially based on + + PyPI’s Acceptable Use Policy and modified from its original form.

-

Security

- -

- Cargo and crates.io are projects that are governed by the Rust Programming - Language Team. Safety is one of the core principles of Rust, and to that end, - we would like to ensure that cargo and crates.io have secure implementations. - To learn more about disclosing security vulnerabilities, please reference the - Rust Security policy for - more details. -

- -

- Thank you for taking the time to responsibly disclose any issues you find. -

- -

Crawlers

- -

- Before resorting to crawling crates.io, please read - Accessing the Crates.io Data. -

- -

- We allow our API and website to be crawled by commercial crawlers such as - GoogleBot. At our discretion, we may choose to allow access to experimental - crawlers, as long as they limit their request rate to 1 request per second or - less. -

- -

- We also require all crawlers to provide a user-agent header that allows us to - uniquely identify your bot. This allows us to more accurately monitor any - impact your bot may have on our service. Providing a user agent that only - identifies your HTTP client library (such as "request/0.9.1") increases the - likelihood that we will block your traffic. - - It is recommended, but not required, to include contact information in your user - agent. This allows us to contact you if we would like a change in your bot's - behavior without having to block your traffic. -

- -

- Bad: "User-Agent: reqwest/0.9.1"
- Better: "User-Agent: my_bot"
- Best: "User-Agent: my_bot (my_bot.com/info)" or "User-Agent: my_bot (help@my_bot.com)" -

- -

- We reserve the right to block traffic from any bot that we determine to be in - violation of this policy or causing an impact on the integrity of our service. -

+

Licensed under the + Creative Commons Attribution 4.0 International license.

\ No newline at end of file