> > And as side topic I would like to ask if I can grab lips.scheme.org domain
> > for my implementation.
>
> Yes, absolutely! It would be great to have more implementations.
>
> > I can setup on old domain redirect (it need to be like
> > this) https://node.js.org/ and setup GitHub pages with scheme.org domain.
> > I can setup CNAME on GitHub pages (right now it say lips.js.org) I'm not
> > sure what need to be done in order to make this proper mapping. I would
> > prefer proper name and not redirect like with other implementations.
>
> The proper name, non-redirect solution, requires adding a
> lips.scheme.org virtual host to your web server software and getting a
> TLS/SSL certificate for it. The cert can be completely different from
> your existing cert, or you can add lips.scheme.org as an alias hostname
> onto the existing cert. Let's Encrypt and certbot make this easy but any
> cert provider ought to be able to do it.

If I would need to setup server then it's useless to me, I wanted something
that would not require to pay for anything, so the service will not be lost
after my death. I wanted something that will still exists after I'm dead.

I think that simple redirect is fine then, the problem with domain is that
the only useful if it stick to the address. Right now those two
implementation are kind of use useless (the domain names). If you just want to
have same link to that implementation then setup l.scheme.org with url
shortener would provide the same benefot.

The only benefit I see for domain is SEO and that it looks nice. But just
redirect is kind of pointless.

But if you decide that this is how all implementations will work then I'm
fine with just redirect. But you need to know that it's good only for
scheme.org to organize the structure it probably will of no use for the
implementer, because he will not get even a link to his site so it will not
benefit SEO at all.

--
Jakub T. Jankiewicz, Web Developer
https://jcubic.pl/me