Re:Our experience launching a paid, proprietary product on L...
by s73v3r_ on Monday July 23, 2018 @12:46PM
(#17593926)
I cannot see someone trying to get paid for their work as a "bait and switch".
[ Parent
| on HN ]
Re:Our experience launching a paid, proprietary product on L...
by detaro on Monday July 23, 2018 @02:43PM
(#17594835)
Then see it only as "surprising and major change, negating the previous unique selling point, makes people unhappy".
Re:Our experience launching a paid, proprietary product on L...
by s73v3r_ on Monday July 23, 2018 @03:28PM
(#17595229)
I can't really see it as that, either. The source is still open, it's free to check out and compile.
Re:Our experience launching a paid, proprietary product on L...
by detaro on Monday July 23, 2018 @03:46PM
(#17595381)
> 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".