no, it's not like that, lightning addresses also use this, it's borrowed from email and that was originally borrowed from ... i forget... maybe telnet
protocol://username:password@address
this is the basis of it, i think there is an RFC for it and all
in http, this has generally equated to username:password being parsed into http headers in some way in the request, iirc
for humans to read it, what you have proposed is fine, but for web servers you have to say where that username is going, and i say a path prefix is the simplest
you presumably would do it with subdirectories right? this is the standard for http file servers, and git servers are literally this, each subdiretctory.git is literally a folder, and inside it is what in the "not bare" version on your system when you "git clone" if you add the extra part `--bare` to the git clone command it puts it in the format that the http git service is expecting, on the client side
so you see what i'm saying, you have to define a route remapping, and for clarity of implementation, you should recommend a preferred method
