I’d have no problem hosting it, and I certainly have the infrastructure, but unfortunately, I’m in the US and have a domain with a TLD owned by Google, who very much could take it down.
I don’t think people will want to memorize an IP. I also host many services, so I have to use a domain so that my reverse proxy can use the Host HTTP header to properly route the request and execute the proper middlewares. No domain also means no TLS, which is not a good idea.
Same. And if there’s not one, we should find someone to host one.
We must extended the grad
Mastograd.
Gradodon
So cool, no words 🤣
I’d have no problem hosting it, and I certainly have the infrastructure, but unfortunately, I’m in the US and have a domain with a TLD owned by Google, who very much could take it down.
use direct ip connect
I don’t think people will want to memorize an IP. I also host many services, so I have to use a domain so that my reverse proxy can use the Host HTTP header to properly route the request and execute the proper middlewares. No domain also means no TLS, which is not a good idea.