For adjunct pieces such as web app authentication, including some common features such as user sign up via email or phone, recover a password, multi-factor auth, social sign in, and the like, there's not yet a good solution (AFAIK).
I will gladly donate money toward developers working on this, especially if it's something simple such as Elixir Phoenix `mix phx.gen.auth` doing a one-time setup with good defaults, then fully customizable.
But if someone wants to take up the project I don't mind donating the code.
If anyone ever saw my version years ago[1], it's effectively Jelly 2.0.
I re-purpose abandoned code all the time. It's not a moral failing to release unfinished code, especially if you label it as such.
I’ll consider dropping it later tonight or this weekend.
Are you looking for a framework-agnostic solution here, or one Really Good Solution for the leading framework (whichever that may be)?
It's used by at least Actix-web, Tide, Hyper, and Warp. Generally, this crate's types aree re-exported from the main framework so you can avoid adding extra dependencies to your application, but AFAIK the compiler can "see through" the type alias to see that the types are the same.
I think the older generations of web frameworks (like Iron, Nickel, and Gotham) might not have leveraaged the http crate, so your point still stands.
It not help rust still lack the "#1" in some key areas but maybe what we need is to people to voice the interest here.
I'm in the fence about doing something that could be the "auto-admin" alike django, and the maintenance cost is what make me doubt this. In the other hand, maybe following the model of tailwindcss with a full open source + a very nice styling to get the proper founding will help (and btw, i plan to use tailwind)