> crates.io is moving away from GitHub-only authentication

Crates.io has not moved away from Github-only authentication, and got into the habit of yelling at people who complained about it.

> crates.io's attachment to GitHub is a fact about crates.io specifically, not the Cargo crate registry protocol

Is this just trivia you wanted to share? I feel like I covered it in the second sentence of the comment you're replying to.

> Cargo's support for Git repositories is generic across Git and has nothing to do with GitHub specifically

I'm looking to compile Rust projects from the semi-standard commonly-used crates. I do not want a Github account.

> Radicle offers nothing to a crate registry that a Git remote doesn't

Radicle offers peer-to-peer hosting that does not require a Github account.

> none of this has anything to do with the GPL.

Radicle is a project being built in Rust that partially reimplements git. Git is GPL-licensed, Radicle is MIT-licensed.

> It feels like you're just listing off things you like and don't like aesthetically.

I am unconcerned about your feelings. What I was saying is that I would like a peer-to-peer hosted, namespaced code repository that mirrors (or replaces) crates.io, and I do not want a github account to be necessary to use it.

> They have nothing to do with each other structurally.

I have no idea what "they" is referring to in this sentence.