3 ms·
I think the Caddy mess had a bunch of factors complicating it, and isn't a good comparison. E.g. they promoted themselves as an easy and powerful solution for p
by detaro 8y ago
I think the Caddy mess had a bunch of factors complicating it, and isn't a good comparison. E.g. they promoted themselves as an easy and powerful solution for people that aren't really sysadmin/server types, and then hurt that exact demographic by from one day to the other requiring them to either pay a not-insignificant amount of money or learn how to compile a product they choose because it's really easy themselves. People really don't like bait-and-switch.
- s73v3r_ 8y agoI cannot see someone trying to get paid for their work as a "bait and switch".
- detaro 8y agoThen see it only as "surprising and major change, negating the previous unique selling point, makes people unhappy".
- s73v3r_ 8y agoI can't really see it as that, either. The source is still open, it's free to check out and compile.
- detaro 8y ago> free to check out and compile Which isn't a problem for you and me, but is for the kind of person that was attracted to it because it's easier than nginx+certbot, as I said in my initial comment. I saw 2 major users of it: this kind of user, and people wanting a small simple thing to stick in their container-based setup for HTTPS/reverse proxy duties. The latter more or less automatically updated to container images that do the build instead of loading a binary and didn't have a problem with even having to consider paying. For the first it was a problem, especially since the cost wasn't really in the ballpark of "I'd happily pay that to host a small blog".