Tobias Bieniek
Tobias Bieniek
> Would you prefer I implement the new co-owner email as a background job? whatever you prefer/is easier. we don't have strong reasons yet to prefer one over the other.
> the S3 bucket is not publicly reachable (yet) this has been fixed last week and the archive is now publicly available at https://static.crates.io/archive/version-downloads/ :)
The `links` column in the database exists at this point and has already been backfilled. The remaining issue is that the `version` model of the API already contains a `links`...
> More serious suggestion: `links_to_library`? `lib_links`?
https://github.com/rust-lang/rfcs/pull/3660 proposes a way for crate authors to delete their crates (and then be able to reregister them, potentially with underscores instead of hyphens or vice-versa). It seems unlikely at...
with https://github.com/rust-lang/crates.io/pull/9064 we now have per-crate RSS feeds, that can be followed as desired. while those are not emails, they achieve a similar result. we are unlikely to implement email...
the extra complexity and the fact that we have a limited budget for sending emails
we've implemented explicit cache invalidation a while ago, so this is probably not strictly needed anymore :)
FWIW we now have `has_lib` and `bin_names` columns in the database that would potentially allow us to implement a lib/bin filter for the search, if there is enough interest.
it would probably be better to work with our daily database dump instead of regularly querying the API for this information. also, whether a crate version contains a lib or...