On a personal opinion (I don't represent my employer), the new license affects both behemoths like AWS and smaller providers like Aiven alike. It may be a bargaining chip for the business, a trojan horse or it may backfire; only time will tell. I think many HNers know first-hand how hard it is to balance business and open source. It is a sign of health that the community is concerned and the best way to ensure an open platform going forward imo.
The summary is that we're committed to open source software and this change won't affect our users. We'll follow-up with a more details about our plans in early January.
I thought the FAQ said you wouldn't refer to it as such:
> Because of this, we will not refer to the Confluent Community License or any code released under it as open source.
IMO it’s a deliberately deceptive technique to try to confuse the market and dilute open source.
I think you mean "dilute Open Source" with capitals :P
More seriously: most terms dilute over time, and it takes a lot of effort to prevent that. I wouldn't assume every instance is malicious
Source available. Your license is not open source as understood by OSI or free software as understood by FSF.