{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiazst7rxl5uxfqzgegmnnty6a2p26t6xxksnbzxyxfwd6bwqxokt4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mjppzvx7nwb2"
  },
  "path": "/t/request-provide-an-official-way-to-deprecate-a-crate-not-yank-yank-is-stupid/24174#post_14",
  "publishedAt": "2026-04-17T18:09:54.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I think this should work like \"last seen online\" status in messenging apps: _some people would like to share this, others would find it annoying._ In consequence, the crate author could opt in to setting such status information on their crates, but they shouldn't be forced. The opt-in could be the same as the first time you press a \"this is still maintained\" button on a particular crate. (And you should be able to change your mind and opt out again later.)\n\nEmail reminders should be a separate opt-in; I believe it's only acceptable to send each crate author an email unmasked for _once_ (once per person not per crate), the first time one of their crates (that they have opted in to share a status in the first place, as described above) is about to become considered \"old\".\n\nThat email can then contain a section like \"This is a _one-time demonstration_ of the crate grace window notification feature. **Click here** if you do want to receive this kind of email again in the future.\"\n\nI believe the email opt-in should be per-user, whereas the setting of whether to share any status information should be per-crate.",
  "title": "Request: Provide an official way to *deprecate* a crate. NOT yank. Yank is stupid"
}