Problem
Currently we block all webpages because of phishing problems on the gateway URL, but when using ENS service if you put a hash there, it will go to the this link for example
https://api.gateway.ethswarm.org/bzz/11b2d24c52e021fd5ec1dfdee602d6b46c2f6b6b90c13c8687bd560c6154d628/
Which will be forbidden by default. So basically you can't connect any website on swarm to ENS.
Even if you go and solve this with your own node and gateway, you can't connect it to ENS as it will always go to our gateway which is blocked.
Solution
We need a public whitelist service, where users can apply to get whitelisted through a form, and we approve manually hashes for them, which can then be served from our gateway. It should be served from "gateway.ethswarm.org" but also "bzz.link," which is much nicer. We should use bzz.link as the default on ENS as it looks more professional.
Problem
Currently we block all webpages because of phishing problems on the gateway URL, but when using ENS service if you put a hash there, it will go to the this link for example
https://api.gateway.ethswarm.org/bzz/11b2d24c52e021fd5ec1dfdee602d6b46c2f6b6b90c13c8687bd560c6154d628/
Which will be forbidden by default. So basically you can't connect any website on swarm to ENS.
Even if you go and solve this with your own node and gateway, you can't connect it to ENS as it will always go to our gateway which is blocked.
Solution
We need a public whitelist service, where users can apply to get whitelisted through a form, and we approve manually hashes for them, which can then be served from our gateway. It should be served from "gateway.ethswarm.org" but also "bzz.link," which is much nicer. We should use bzz.link as the default on ENS as it looks more professional.