We recently announced a license change.

Blog: https://t.co/DwokGSwilX

FAQ: https://t.co/FCrovhQ0J0

We’ve also clarified the license change here: https://t.co/Cbnk3wlr77

I wanted to share why we had to make this change. (1 of 22)

This was an incredibly hard decision, especially with my background and history around Open Source. I take our responsibility very seriously. (2 of 22)
And to be clear, this change most likely has zero effect on you, our users. It has no effect on our customers that engage with us either in cloud or on premises. Its goal, hopefully, is pretty clear. (3 of 22)
So why the change? AWS and Amazon Elasticsearch Service. They have been doing things that are just NOT OK since 2015 and it has only gotten worse. If we don’t stand up to them now, as a successful company and leader in the market, who will? (4 of 22)
Our license change is aimed at preventing companies from taking our Elasticsearch and Kibana products and providing them directly as a service without collaborating with us. (5 of 22)
Our license change comes after years of what we believe to be Amazon/AWS misleading and confusing the community - enough is enough. (6 of 22)
We’ve tried every avenue available including going through the courts, but with AWS’s ongoing behavior, we have decided to change our license so that we can focus on building products and innovating rather than litigating. (7 of 22)
AWS’s behavior has forced us to take this step and we do not do so lightly. If they had not acted as they have, we would not be having this discussion today. (8 of 22)
We think that Amazon’s behavior is inconsistent with the norms and values that are especially important in the open source ecosystem. Our hope is to take our presence in the market and use it to stand up to this now so others don’t face these same issues in the future. (9 of 22)
In open source, trademarks are considered a great and positive way to protect product reputation. They have been used and enforced broadly. They are considered sacred by the open source community, from small projects to foundations (Apache) to companies (RedHat). (10 of 22)
So imagine our surprise when Amazon launched their service in 2015 based on Elasticsearch and called it Amazon Elasticsearch Service. We considered this to be a pretty obvious trademark violation. NOT OK. (11 of 22)
I took a personal loan to register the Elasticsearch trademark in 2011 believing in this norm. Seeing the trademark so blatantly misused was especially painful to me. Our efforts to resolve the problem with Amazon failed, forcing us to file a lawsuit. NOT OK. (12 of 22)
We have seen that this trademark issue drives confusion with users thinking Amazon Elasticsearch Service is actually a service provided jointly with Elastic, with our blessing and collaboration. This is just not true. NOT OK. (13 of 22)
When the service launched, imagine our surprise when the Amazon CTO tweeted https://t.co/R10MINaWUA that it was released in collaboration with us. It was not. Over the years, we have heard repeatedly that this confusion has persisted. NOT OK. (14 of 22)
When Amazon announced their Open Distro for Elasticsearch fork, they used code that we believe was copied by a third party from our commercial code and provided it as part of the Open Distro project. NOT OK. (15 of 22)
We believe this further divided our community and drove additional confusion. More on this here: https://t.co/HKuMOgsHAO NOT OK. (16 of 22)
Recently, we found more examples of what we consider to be ethically challenged behavior. We have differentiated with proprietary features, and now see these feature designs serving as "inspiration" for Amazon, telling us their brazen behavior continues. NOT OK. (17 of 22)
We are happy to collaborate with cloud service providers, including Microsoft, Google, Alibaba, Tencent, Clever Cloud, and others. We have shown we can find a way to do it. We even work with other parts of Amazon. We are always open to do it, it just needs to be OK. (18 of 22)
I believe in the core values of the Open Source Community: transparency, collaboration, openness. Building great products to benefit users across the world. Amazing things have been built and will continue to be built using Elasticsearch and Kibana. (19 of 22)
And to be clear, this change most likely has zero effect on you, our users. And no effect on our customers that engage with us either in cloud or on premises. (20 of 22)
We created Elasticsearch; we care about it more than anyone else. It is our life’s work. We will wake up every day and do more to move the technology forward and innovate on your behalf. (21 of 22)
Thanks for listening. If you have more questions or you want more clarification please read here https://t.co/FCrovhQ0J0 or contact us at [email protected].

Thank you. It is a privilege to be on this journey with you. (22 of 22)

More from For later read

This response to my tweet is a common objection to targeted advertising.

@KevinCoates correct me if I'm wrong, but basic point seems to be that banning targeted ads will lower platform profits, but will mostly be beneficial for consumers.

Some counterpoints 👇


1) This assumes that consumers prefer contextual ads to targeted ones.

This does not seem self-evident to me


Research also finds that firms choose between ad. targeting vs. obtrusiveness 👇

If true, the right question is not whether consumers prefer contextual ads to targeted ones. But whether they prefer *more* contextual ads vs *fewer* targeted

2) True, many inframarginal platforms might simply shift to contextual ads.

But some might already be almost indifferent between direct & indirect monetization.

Hard to imagine that *none* of them will respond to reduced ad revenue with actual fees.

3) Policy debate seems to be moving from:

"Consumers are insufficiently informed to decide how they share their data."

To

"No one in their right mind would agree to highly targeted ads (e.g., those that mix data from multiple sources)."

IMO the latter statement is incorrect.
I should mention, this is why I keep talking about this. Because I know so many people who legally CAN'T.

How do I know they have NDAs, if they can't talk legally about them? Because they trusted me with their secrets... after I said something. That's how they knew I was safe.


Some of the people who have reached out to me privately have been sitting with the pain of what happened to them and the regret that they signed for YEARS. But at the time, it didn't seem like they had any other option BUT to sign.

I do not blame *anyone* for signing an NDA, especially when it's attached to a financial lifeline. When you feel like your family's wellbeing is at stake, you'll do anything -- even sign away your own voice -- to provide for them. That's not a "choice"; that's survival.

And yes, many of the people whose stories I now know were pressured into signing an NDA by my husband's ex-employer. Some of whom I *never* would have guessed. People I thought "left well." Turns out, they've just been *very* good at abiding by the terms of their NDA.

(And others who have reached out had similar experiences with other Christian orgs. Turns out abuse, and the use of NDAs to cover up that abuse, is rampant in a LOT of places.)

You May Also Like

🌺कैसे बने गरुड़ भगवान विष्णु के वाहन और क्यों दो भागों में फटी होती है नागों की जिह्वा🌺

महर्षि कश्यप की तेरह पत्नियां थीं।लेकिन विनता व कद्रु नामक अपनी दो पत्नियों से उन्हे विशेष लगाव था।एक दिन महर्षि आनन्दभाव में बैठे थे कि तभी वे दोनों उनके समीप आकर उनके पैर दबाने लगी।


प्रसन्न होकर महर्षि कश्यप बोले,"मुझे तुम दोनों से विशेष लगाव है, इसलिए यदि तुम्हारी कोई विशेष इच्छा हो तो मुझे बताओ। मैं उसे अवश्य पूरा करूंगा ।"

कद्रू बोली,"स्वामी! मेरी इच्छा है कि मैं हज़ार पुत्रों की मां बनूंगी।"
विनता बोली,"स्वामी! मुझे केवल एक पुत्र की मां बनना है जो इतना बलवान हो की कद्रू के हज़ार पुत्रों पर भारी पड़े।"
महर्षि बोले,"शीघ्र ही मैं यज्ञ करूंगा और यज्ञ के उपरांत तुम दोनो की इच्छाएं अवश्य पूर्ण होंगी"।


महर्षि ने यज्ञ किया,विनता व कद्रू को आशीर्वाद देकर तपस्या करने चले गए। कुछ काल पश्चात कद्रू ने हज़ार अंडों से काले सर्पों को जन्म दिया व विनता ने एक अंडे से तेजस्वी बालक को जन्म दिया जिसका नाम गरूड़ रखा।जैसे जैसे समय बीता गरुड़ बलवान होता गया और कद्रू के पुत्रों पर भारी पड़ने लगा


परिणामस्वरूप दिन प्रतिदिन कद्रू व विनता के सम्बंधों में कटुता बढ़ती गयी।एकदिन जब दोनो भ्रमण कर रहीं थी तब कद्रू ने दूर खड़े सफेद घोड़े को देख कर कहा,"बता सकती हो विनता!दूर खड़ा वो घोड़ा किस रंग का है?"
विनता बोली,"सफेद रंग का"।
तो कद्रू बोली,"शर्त लगाती हो? इसकी पूँछ तो काली है"।
Fake chats claiming to be from the Irish African community are being disseminated by the far right in order to suggest that violence is imminent from #BLM supporters. This is straight out of the QAnon and Proud Boys playbook. Spread the word. Protest safely. #georgenkencho


There is co-ordination across the far right in Ireland now to stir both left and right in the hopes of creating a race war. Think critically! Fascists see the tragic killing of #georgenkencho, the grief of his community and pending investigation as a flashpoint for action.


Across Telegram, Twitter and Facebook disinformation is being peddled on the back of these tragic events. From false photographs to the tactics ofwhite supremacy, the far right is clumsily trying to drive hate against minority groups and figureheads.


Declan Ganley’s Burkean group and the incel wing of National Party (Gearóid Murphy, Mick O’Keeffe & Co.) as well as all the usuals are concerted in their efforts to demonstrate their white supremacist cred. The quiet parts are today being said out loud.


The best thing you can do is challenge disinformation and report posts where engagement isn’t appropriate. Many of these are blatantly racist posts designed to drive recruitment to NP and other Nationalist groups. By all means protest but stay safe.