BC TECH
Saved by @Mollyycolllinss

Elastic didn't really relicense ElasticSearch. It forked it.

🧵 A thread.

1/18

 There's a lot of talk in the open source community about the cost of forking.

2/18
- "Forking is best avoided."

- "Forking is a last resort option."

- "Forking is like a nuclear weapons. It's a defensive threat."

3/18
Forking is seen as impractical and extremely expensive.

And that's a Really Good Thing(tm).

It's a forcing function for figuring out solutions that are broadly acceptable across the community.

4/18
The thing is, the cost of forking is mostly a function of three things:

1⃣ the size of the community that you can bring along with you,
2⃣ whether you need to rename your fork (who owns the trademark), and
3⃣ how much infrastructure you need to rebuild.

5/18
When that "community" is your employees, when you own the trademark, and control the infrastructure, then forking is really cheap. You just tell your employees to now contribute to your new fork, and you're done.

6/18
So the whole forcing function that the threat of forking has on the community is essentially lost. You don't get your way, and you fork.

7/18
Of course, with GPL, you can't just fork and close-up the source code, unless you've secured re-licensing right from all of your contributors. This is why the GPL+CLA combo is so prevalent with FOSS vendors.

8/18
With permissive licenses, there is no such need. You can literally embed the software into anything that is proprietary. As long as you give proper attribution and keep the open source license around FOR THAT PART OF THE CODE ONLY.

9/18
No one can stop me from forking Node today and releasing it as proprietary software.

10/18
What I can't do however is:

1⃣ move all of its community to contribute to my proprietary fork overnight,
2⃣ use the "Node" trademark, and
3⃣ leverage all of the existing infrastructure that isn't mine.

11/18
So the problem with Elastic forking ElasticSearch isn't the CLA, or its new license.

It's that it:

1⃣ *is* the community,
2⃣ owns the trademark, and
3⃣ controls the infrastructure.

12/18
So from the very start, none of what would have made forking costly was ever an issue for Elastic. At any point in time, Elastic could have forked at practically zero cost.

Of course, that's a powerful weapon and an incredible power imbalance in a community.

13/18
A key element of community stability (the shared threat of forking) was lacking from the get go.

The lack of open governance, of community trademark ownership, and of a genuine community of contributors beyond Elastic employees, are at the heart of the problem.

14/18
Folks like @beep and @adactio have started calling this "nominally open source."

I think it's more "Schrödinger open source."

Despite the license, you don't really know whether it is open source or not until you open the envelope and find out the cat is dead. 😿

15/18
With that framing in mind, ElasticSearch was never really open source. It was always in this unstable, "quantic" state of being both open and close, up until a decision was made and it was no longer open.

16/18
I've said it before and I'll say it again. We really need to start looking beyond licensing to understand open source and really assess the risk of buying into an open source project.

https://t.co/wuUJMh1RtX

17/18
Licensing clearly is a factor, but community health, governance, and trademark ownership are just as important.

It's time we truly recognize this.

18/18

More from Tech

Jared Spool
Jared Spool
@jmspool
A common misunderstanding about Agile and “Big Design Up Front”:

There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.

You’re allowed to think about a desired outcome from the beginning.

It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.

It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.

It’s not BDUF if you help every team member know what success looks like.

Agile is about reducing risk.

It’s not Agile if you increase risk by starting your sprints with complete ignorance.

It’s not Agile if you don’t research.

Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.

It would be a mistake to assume this research should only be done by designers and researchers.

Product management and developers also need to be out with the team, conducting the research.

Shared Understanding is the key objective


Big Design Up Front is a thing to avoid.

Defining all the functionality before coding is BDUF.

Drawing every screen and every pixel is BDUF.

Promising functionality (or delivery dates) to customers before development starts is BDUF.

These things shouldn’t happen in Agile.
TECH
Patrick McKenzie
Patrick McKenzie
@patio11
Most software founders, particularly in B2B, need to get radically better at sales. @Steli , who is the best person for explaining the scrappy stages in the beginning and then building out a team with scripts and processes, wrote a guide to:

For technical founders it is irrationally, obscenely hard to reverse years of programming (ba dum bum) that sales is a value-destroying activity. Sales is CLEARLY a value-creating activity, contingent on you have a value-creating product.

The world will not drop what they are doing to adopt your work. This is particularly true in B2B, where simply building a better mousetrap won't overcome the activation energy required to get people with additional non-mice problems to prioritize changing mousetraps today.

This is very non-obvious for founders because founders are not often people who *want* to be sold to. We often come from a background where trying out tools is a bit of a fun hobby. We like looking at all the options, making charts, and ripping out partially complete tests.

"This week I unsuccessfully trialed four software options for automating that thing that has been killing us. Our actual production process remains the same as last week. Don't worry; this was a great use of time." is not a thing you want to write in a progress report to manager.
TECH
Advertisement
Novid Houellebecq (That's Hollaback)
Novid Houellebecq (Tha...
@GarouGothic
I want to explain what happened to tumblr overnight. And why Twitter as reached it's dream (or have come ever so close to it)

Yahoo, who bought Tumblr years ago, used to have a huge adult presence on the early net. They allowed adult groups and what not.

However, people and bots (just like now) misused the service, and Yahoo were forced to make a choice. They made private the groups (and later closed them down and sold some of it to other companies) and then ended their chatrooms on yahoo messenger...

after a incident with one of the chatrooms vid cams. The damage was done, Yahoo Messenger lost a lot of people - and with the closing of the groups - backpage and Craigslist came more important.

Now backpage is no more and Craigslist is slowly passing away. Tumblr had a semi strong community, but once 2014 came around and both porn, and political bots exploded the quality started to go down,
TECH
sumitgarg.eth
sumitgarg.eth
@sumitupgarg
I read two-and-a-half decades worth of Jeff Bezos’s Amazon shareholder letters.

It’s like a mini MBA.

Here I’ve pulled out a free guide for startups, investing, marketing, and “web3”🧵

(It’s a thread, not an ebook)


First, why the focus on web3?

It’s the mid 90’s. A 30-year-old Jeff Bezos is trying to raise money for Amazon. And investors are wondering,

“What’s this internet thing?”

Fast forward, the year is 2022, and folks today are wondering,

“What’s web3?”

Now, a little background…

In 1994, Bezos quit a well paying job to start Amazon.

It wasn’t an easy decision. But Bezos used his famous “regret minimization framework.”

In other words, he didn’t want to be 80 and regret not doing what he really wanted to do.

But what did he want?

Bezos didn’t set out to disrupt retail from the outset.

He simply wanted to come up with a business idea based on the internet and then let the internet grow around it while he kept working on it.

Today, that idea is worth $1.7 trillion and counting.

Moving on to the lessons…

Each year since 1997, Bezos has written an annual letter to Amazon shareholders.

These letters reveal a great deal of lessons and secrets behind his massive success.

So what are they?
STARTUP , TECH
Ameya
Ameya
@Finstor85
After getting good feedback on yesterday's thread on #routemobile I think it is logical to do a bit in-depth technical study. Place #twilio at center, keep #routemobile & #tanla at the periphery & see who is each placed.


This thread is inspired by one of the articles I read on the-ken about #postman API & how they are transforming & expediting software product delivery & consumption, leading to enhanced developer productivity.

We all know that #Twilio offers host of APIs that can be readily used for faster integration by anyone who wants to have communication capabilities. Before we move ahead, let's get a few things cleared out.

Can anyone build the programming capability to process payments or communication capabilities? Yes, but will they, the answer is NO. Companies prefer to consume APIs offered by likes of #Stripe #twilio #Shopify #razorpay etc.

This offers two benefits - faster time to market, of course that means no need to re-invent the wheel + not worrying of compliance around payment process or communication regulations. This makes entire ecosystem extremely agile
TECH

You May Also Like

Vibhu Vashisth
Vibhu Vashisth
@VIBHU_Tweet
शमशान में जब महर्षि दधीचि के मांसपिंड का दाह संस्कार हो रहा था तो उनकी पत्नी अपने पति का वियोग सहन नहीं कर पायी और पास में ही स्थित विशाल पीपल वृक्ष के कोटर में अपने तीन वर्ष के बालक को रख के स्वयं चिता पे बैठ कर सती हो गयी ।इस प्रकार ऋषी दधीचि और उनकी पत्नी की मुक्ति हो गयी।


परन्तु पीपल के कोटर में रखा बालक भूख प्यास से तड़पने लगा। जब कुछ नहीं मिला तो वो कोटर में पड़े पीपल के गोदों (फल) को खाकर बड़ा होने लगा। कालान्तर में पीपल के फलों और पत्तों को खाकर बालक का जीवन किसी प्रकार सुरक्षित रहा।

एक दिन देवर्षि नारद वहां से गुजर रहे थे ।नारद ने पीपल के कोटर में बालक को देख कर उसका परिचय मांगा -
नारद बोले - बालक तुम कौन हो?
बालक - यही तो मैं भी जानना चहता हूँ ।
नारद - तुम्हारे जनक कौन हैं?
बालक - यही तो मैं भी जानना चाहता हूँ ।

तब नारद ने आँखें बन्द कर ध्यान लगाया ।


तत्पश्चात आश्चर्यचकित हो कर बालक को बताया कि 'हे बालक! तुम महान दानी महर्षि दधीचि के पुत्र हो । तुम्हारे पिता की अस्थियों का वज्रास्त्र बनाकर ही देवताओं ने असुरों पर विजय पायी थी।तुम्हारे पिता की मृत्यु मात्र 31 वर्ष की वय में ही हो गयी थी'।

बालक - मेरे पिता की अकाल मृत्यु का क्या कारण था?
नारद - तुम्हारे पिता पर शनिदेव की महादशा थी।
बालक - मेरे उपर आयी विपत्ति का कारण क्या था?
नारद - शनिदेव की महादशा।
इतना बताकर देवर्षि नारद ने पीपल के पत्तों और गोदों को खाकर बड़े हुए उस बालक का नाम पिप्पलाद रखा और उसे दीक्षित किया।
ALL
Greta Musk
Greta Musk
@GretaMusk
🚔 HUGE #Tesla SERVICE PROBLEMS THREAD🚔

You might remember my 3 prior threads on how
TESLA. TREATS. ITS. CUSTOMERS. LIKE. TRASH.

Here's the 4th installment.
@tomkeinan @jonsey_lisa @jwmooc @tchanpoker @bryanthediamond @EconomicManBlog
$TSLA $TSLAQ 1/22


Welcome to Greta's 4th edition of #Tesla customers getting used and abused. Because that's the Elon Musk way.
@coffeebreakls @KocgibiHarun @omaragha @JayGhahari
$TSLA $TSLAQ 2/22


"The best service is no service." - Elon Musk a.k.a. #SpaceKaren
@briansaziz @FarSha998899 @thinktankfour @Billoday1
#Tesla $TSLA $TSLAQ 3/22


These #Tesla customers represent just the very tip of the iceberg. They are ones who have Twitter, have decided to complain about their #TeslaServiceIssues publicly, and were found by yours truly.
@yanismydj @hajelatweets @AlanHeldman @francislongo5 $TSLA $TSLAQ 4/22


Dear #Tesla customers: In California, if your vehicle has been out of service for >30 days total, it's a lemon. You can get punitive damages and attorney's fees. Don't sit around and take Elon's abuse. @13arm13arm @cecimar12 @richardson_skip @shootinglee $TSLA $TSLAQ 5/22
TECH
Advertisement
Ramblings of a Sikh
Ramblings of a Sikh
@RamblingSingh
1/ Jassa Singh Ahluwalia & his role in the history of Shri Harmandir Sahib (A Thread)


2/ Jassa Singh was born in 1720/21 at a village called Ahlu in the Lahore District of Punjab.


3/ Jassa Singh was educated in Delhi, in Persian, Arabic & more, under the care & supervision of Mata Sundari Ji.

Mata Sundari Gurdwara in Delhi.


4/ In 1733, Jassa Singh's mama, Thag Singh (ਤਾਗ ਸਿੰਘ), requested Mata Sundari Ji's permission to take Jassa Singh back to Punjab.


5/ At first Mata Ji refused but eventually gave permission for Jassa Singh to go with his mama, giving Jassa Singh a blessing and weapons, informing him, it was now the right time to take up arms.
HISTORY
Marc K\xf6hlbrugge
Marc Köhlbrugge
@marckohlbrugge
💬 I often get Q’s like these:

How did you get your first customers for WIP? How did you grow BetaList’s traffic? Etc.

Makers are looking to reverse-engineer success. I see it everywhere.

I don’t think it works that way and the answers to those questions are mostly useless. 💥

I have built dozens of different products over the last couple of years. The vast majority failed. 😭

Surely if I know the answers to these questions, but still fail over and over again, these answers aren’t that useful. 🤷‍♀️

So what’s a better question to ask? 🤔

99.9% of the questions I receive are about the products that did well. In a way that makes sense, because we quickly forget about those that didn’t succeed.

🧠 This is known as survivorship bias.

Focusing on what survived, while ignoring what made it survive in the first place.

The real question, what you really want to know, is this:

What makes @WIP, @BetaList, and to some extent @AllStartupJobs succeed where my countless other attempts failed?

What separates a failed product 👎 from a successful product 👍?

Honestly, I don’t know. I wish I did.

It’s like Steve Jobs said “I’ll know it when I see it.” 👀

Same is true when we make products. We don’t know upfront what will work. But once we see an inkling of a product that does have potential, it’s not that hard to spot.
STARTUPS
JayneshKasliwal
JayneshKasliwal
@JayneshKasliwal
ULTIMATE GUIDE TO 21 and 200 Moving Average
SUNDAY THREAD 🔖
A trend Following System That will Help You Improve Trading immensely.

RETWEET AND SHARE 🔄
@kuttrapali26 @AmitabhJha3
#stocks #StockMarket
1/n

Moving averages
EMA and SMA
1. Exponential Moving Average (EMA) is similar to Simple Moving Average (SMA), measuring trend direction over a period of time.
2. However, whereas SMA simply calculates an average of price data, EMA applies more weight to data that is more current
2/


21 EMA : SHORT TERM TREND
1. Calculates the Average Price of past 21 days
2. A stock above 21 ema is in strong momentum , which will give pullbacks to 21 ema again and again.
3. Stock above 21 ema should never be shorted so as to stay with the trend
3/n

3. A stock which moves 10-15% above 21 ema will be too extended and hence will generally pullback
Stocks take dynamic support on 21 ema
4. You can Short only if its too extended like 15 to 20% from 21 ema ( Not advised )
#ADANIPOWER:
#pnbhousing
4/n


1. Whenever 21 ema is sloping upwards its called uptrend
2. Whenever 21 ema is sloping downwards its called dowtrend
3. Whenever 21 ema is sideways its called consolidation
⏫Buy in uptrend
⏬Sell in downtrend
Examples:
5/n
MOVINGAVERAGES , MOVING AVERAGE 20021 , ALL