[jonathanoliver]

I'm confused. If telemetry is an option and you can opt out, why not just do that? Also, because everything is open source, you're welcome to inspect the source to verify that it's behaving as expected and not reporting telemetry. You mentioned that you're not a Go programmer and/or you don't have time to do this...okay, so pay someone else who is a Go programmer to do this for you. Or is any software that costs money too much?

Matt has a right, as the creator of that work, to ask for some form of compensation for the portion of his life invested into the project. It's a completely fair and reasonable request. If you're set on avoiding any form of compensation (financial or otherwise), then you don't have any rights to demand anything from him. Just go use nginx and be done with it.

[neflabs]

You're conflating two issues. If Matt wants money, we're happy to pay. That's a separate issue from telemetry.

We don't want a) a sole developer making decisions which the community has rejected, and b) software which sends telemetry by default.

[gus_massa]

> a) a sole developer making decisions which the community has rejected

Have you run a poll to be sure that >50% of the community rejects the change? Anyway, online polls are not reliable, it's difficult to be avoid sock puppets, people that don't use the software, ensure that people that disagree with your proposal care to vote, ...

Just make a fork and if most of the community agree with you, your fork will be most popular and shadow the original.

[jonathanoliver]

If Matt feels that having telemetry on by default is the form of compensation he would like for his time/investment, I don't see that as a problem.

I can see that different people would take exception to that which is why there's an off switch for telemetry.

If you're having a difficult time accepting that telemetry exists at all, then I'm almost certain Matt would be happy to create a non-telemetry version for paid subscribers.