All open source software has leadership whether you recognise it or not.
The question is, is this leadership more of a risk than it is a benefit.
An anarchic leadership reduces the risk of things changing too fast that only large corporations can keep up.
But it also increases the risk of paralysis and implementing ideas that almost everyone agrees is best, because no one has the power to pursue anything decisively.
We think our way of doing things allowed us to design things from first principles and have a very minimalist and well reasoned architecture.
If you listen to us more often, you might be convinced that we are very protective of the simplicity of the core protocol, pushing most of complexity to higher layers or optional APIs, exactly because we want to build one foundational layer on top of another, as opposed to spontaneous house of cards.
Nuh 🔻
npub1jv…s7yqz
2024-10-30 06:36:13
in reply to nevent1q…2jpn
Author Public Key
npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqzPublished at
2024-10-30 06:36:13Event JSON
{
"id": "436f3c81f669abd304cf2025d1520905bc63b6d5483aa320402f8959b052f9ff",
"pubkey": "930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9",
"created_at": 1730270173,
"kind": 1,
"tags": [
[
"p",
"e8ed3798c6ffebffa08501ac39e271662bfd160f688f94c45d692d8767dd345a"
],
[
"e",
"3b9d4b3da98238b4d5570f9a750f7f0b883e271631384ba84a8b4d1574264cdd",
"wss://nos.lol",
"root"
]
],
"content": "All open source software has leadership whether you recognise it or not.\n\nThe question is, is this leadership more of a risk than it is a benefit. \n\nAn anarchic leadership reduces the risk of things changing too fast that only large corporations can keep up.\n\nBut it also increases the risk of paralysis and implementing ideas that almost everyone agrees is best, because no one has the power to pursue anything decisively. \n\nWe think our way of doing things allowed us to design things from first principles and have a very minimalist and well reasoned architecture. \n\nIf you listen to us more often, you might be convinced that we are very protective of the simplicity of the core protocol, pushing most of complexity to higher layers or optional APIs, exactly because we want to build one foundational layer on top of another, as opposed to spontaneous house of cards.",
"sig": "d61ec26585a4e3d777389f429c96b042ce711b244140779237521e3b575f444c533b92f70d437f262e2cb871ff872fdebd86f39824d54723d654021a447461e5"
}