As an interesting aside… If someone contributes code for a feature that ends up in the commercial product, are they stuck with the options of paying the annual per license fee, or compiling their own code to get the feature?
Basically, yes.
We Should Ditch Nginx
171–176 of 176 posts
Re: We Should Ditch Nginx
#172Earlier quoted context omitted.
I don't disagree, but my point is that the code people freely contributed prior to this change is still freely available to the public. If they are rejecting patches for features that impinge on their enterprise offerings and you have an issue with how the project is run now, you are welcome to not contribute, fork, or use another project.
>If they are rejecting patches for features that impinge on their enterprise offerings and you have an issue with how the project is run now, you are welcome to not contribute, fork, or use another project. Which is precisely what is being argued.
No, you were insinuating they had an obligation to provide monetary compensation to the people who contributed code to the open source product when they sold licenses to the closed source product.
Re: We Should Ditch Nginx
#173Earlier quoted context omitted.
To the NSA, presumably: http://exiledonline.com/read-yasha-levines-introduction-to-t...
To be 100% clear: we have never been asked or ordered to share log data with the NSA. We've not participated in any program like PRISM and would fight vigorously if we ever were. We do receive law enforcement requests on occasion, typically to determine who owns or hosts a site behind our network. When we've received law enforcement requests for customer data (e.g., account information like the email address of an ac…
Sure, but why should I have any reason to believe you?
If you had been served with a national security letter, you would be obligated to lie about it.
Plus, you have a pretty significant financial incentive to lie about how great Cloudflare is, with no downside, since you're not under oath on HN. And even if you were, officials who have lied about the extent of surveillance programs while under oath haven't been prosecuted.
Representatives of Facebook lied. Ditto with Google. Etc, etc, etc.
Re: We Should Ditch Nginx
#174Earlier quoted context omitted.
To be 100% clear: we have never been asked or ordered to share log data with the NSA. We've not participated in any program like PRISM and would fight vigorously if we ever were. We do receive law enforcement requests on occasion, typically to determine who owns or hosts a site behind our network. When we've received law enforcement requests for customer data (e.g., account information like the email address of an ac…
Sure, but why should I have any reason to believe you? If you had been served with a national security letter, you would be obligated to lie about it. Plus, you have a pretty significant financial incentive to lie about how great Cloudflare is, with no downside, since you're not under oath on HN. And even if you were, officials who have lied about the extent of surveillance programs while under oath haven't been pros…
No. National security letters can act as gag orders, obligating you not to talk about their existence but you're never required to lie and say you have never been served a letter.
In that case, you can be cagy (as Google has I believe) and say something on the lines of "I can neither confirm nor deny receiving a NS letter" which of course is double speak for "I have one, and I can't talk about it directly".
Re: We Should Ditch Nginx
#175Earlier quoted context omitted.
This part of FOSS culture I really dislike as a developer. Many people seem to consider an offence that other developers need to make a living, instead of being grateful of being able to sell stuff using software they haven't paid a dime for. Then become outraged when the developers come to the conclusion that the baker won't sell bread for pull requests. This is what moved me into the direction of suggesting dual li…
What you are suggesting is the part of a greedy FOSS project. One that enjoys the external open source contributions, yet still charges for features in the software. It's disgusting and an insult to your contributors, unless you pay them all money as well. There is nothing wrong with making money, but don't to it with sleazy tactics like this that put you in a conflict of interest. Charge for support or a hosted vers…
> What you are suggesting is the part of a greedy FOSS project. One that enjoys the external open source contributions, yet still charges for features in the software. It's disgusting and an insult to your contributors, unless you pay them all money as well.
Just for the records: http://www.ohloh.net/p/nginx http://www.ohloh.net/p/nginx/contributors/summary
Indeed there are useful patches/bugfixes from the community, however nginx has always been almost a "one-man operation".
To the best of my knowledge, syslog code in nginx plus isn't based on any 3rd party work too.
Re: We Should Ditch Nginx
#176It's $1350/server per year to pay for the feature. You mention in your post: "Our noble HTTP server". Wait. Not plural? I know that a that is a fair bit of money for a bootstrapped startup, but if you are anticipating enough traffic that the syslog feature is an issue, AND you have at least three floors of offices (as mentioned in your blog post), then maybe your OPEX prioritization is a bit off, and you should just…
Yes, $1350/server per year * 100 VMs which just broker requests from clients to php-fpm. Totally reasonable. /s For that price, they could pay someone who's sole job is to maintain a private fork with the feature. It's not like they can submit it back since nginx would reject an enterprise competing patch, but at least they would have the functionality and the benefit of another dev on hand.
So is that about the pricing or the closed source? Would it be different if the pricing was something else? Just curious. Also, like quite a few people pointed out, why not request "the best pricing" given certain deployment scenario?