Change eth.link to eth.limo and update Locales

ensdomains / ens-app

Legacy ENS manager app

https://legacy.ens.domains/

BSD 2-Clause "Simplified" License

223 stars 267 forks source link

Change eth.link to eth.limo and update Locales #1553

Closed jackson-jackson closed 2 years ago

jackson-jackson commented 2 years ago

Eth.link is down for the foreseeable future, so we need to switch the links to limo and update the Locales.

Issue number

None

Description

I updated all of the locales documents and the two js docs that resolve the link.

List of features added/changed

Update locales with new .limo links.
Update the front end to display and link to .limo instead of .link on the details page.

How Has This Been Tested?

I tested locally.

Screenshots (if appropriate):

Checklist:

[ x ] My code follows the code style of this project.
[ x ] My code implements all the required features.

eth-limo commented 2 years ago

This would be great. Right now every .link URL is broken and it really impacts user experience.

makoto commented 2 years ago

@eth-limo how does .limo issue ssl certificate to subdomains like a.b.matoken.eth (or app.ens.eth.limo for the real example) ? Currently https://github.com/ensdomains/ens-app/blob/62ee94b6052c1a5135385e5c4febd37f3de9edcc/src/components/SingleName/ResolverAndRecords/Certificate.js#L3 part checks if the parent b.matoken.eth if the parent doesn't issue wildcard certificate to its subdomains then makes POST request to request the certificate. Do you have similar method to request cretifcate for subdomains or you have other ways to work around?

eth-limo commented 2 years ago

@eth-limo how does .limo issue ssl certificate to subdomains like a.b.matoken.eth (or app.ens.eth.limo for the real example) ? Currently

https://github.com/ensdomains/ens-app/blob/62ee94b6052c1a5135385e5c4febd37f3de9edcc/src/components/SingleName/ResolverAndRecords/Certificate.js#L3

part checks if the parent b.matoken.eth if the parent doesn't issue wildcard certificate to its subdomains then makes POST request to request the certificate. Do you have similar method to request cretifcate for subdomains or you have other ways to work around?

So we now automatically generate subdomain certificates on the fly whenever an HTTPS request is made to a subdomain. It takes about 30s-1m to issue and then the request is unblocked and forwarded to the content. We do not require any kind of provisioning workflow, as everything is on-demand.

LeonmanRolls commented 2 years ago

@jackson-jackson Thanks very much for your contribution, I branched off from it and added some more changes here #1554 . Will close this one.