Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I think this guy has the right idea but may be confused about how `git` works: every repo you `git clone` is an entire copy of the repo and all of its history, completely stand alone.
You can never lose your work as long as you retain a copy of the repo. You can never lose other people's work as long as you retain a copy of their repo. `cargo` does not require crates.io, can use other registries when they come into being, and can refer to modules by file path or by `http` uri.
However, he is trying the tact of talking about how crates.io uses GH's oauth; this is a clever thing to do since it ties explicit ownership of the repo to the user. There is nothing stopping crates.io to also use other ouaths the same way, as all of the major GH alternatives also support oauth and can be used for this purpose.
Crates.io most likely doesn't want to handle internal auth, as this becomes a maintenace nightmare for a 3? person team. Since the team is also small, adding other oauth->proof of repo onwership backends is presumably on their todo list but something they can't commit to.
Good news, though: https://github.com/rust-lang/crates.io (and they accept PRs)