The IP address comes from the web browser. There is no server component to this.
Here's the draft of our trademark policy: https://therootcompany.com/legal/#trademark
Essentially the rule is "attribute, but don't confuse". We'd very much appreciate it if you'd let people know that you're using Greenlock and link back to the repo, but the name of and images on your site shouldn't lead someone to believe that it is "Greenlock".
This still relies on pkijs, but this week I'm hoping to overhaul it so that it doesn't. I may be able to use help on that. I've sent you an invite to our Keybase channel.
Three things:
1. The IP address comes from the web browser. There is no server component to this.
2. Here's the draft of our trademark policy: https://therootcompany.com/legal/#trademark
Essentially the rule is "attribute, but don't confuse". We'd very much appreciate it if you'd let people know that you're using Greenlock and link back to the repo, but the name of and images on your site shouldn't lead someone to believe that it _is_ "Greenlock".
3. This still relies on pkijs, but this week I'm hoping to overhaul it so that it doesn't. I may be able to use help on that. I've sent you an invite to our Keybase channel.
I'm considering self-hosting this. Could someone repeatedly make failed requests and get my IP ratelimited?
Three things:
The IP address comes from the web browser. There is no server component to this.
Here's the draft of our trademark policy: https://therootcompany.com/legal/#trademark
Essentially the rule is "attribute, but don't confuse". We'd very much appreciate it if you'd let people know that you're using Greenlock and link back to the repo, but the name of and images on your site shouldn't lead someone to believe that it is "Greenlock".
This still relies on pkijs, but this week I'm hoping to overhaul it so that it doesn't. I may be able to use help on that. I've sent you an invite to our Keybase channel.
Okay, cool.