Who will get to push the code to another server? jb55 (npub1xts…kk5s)'s main branch which contains 1 commit ahead of yesterday's last commit for everyone, or mine, which contains 2 other separate commits than his?
Without a centralized origin which purpose is to retain the source of truth for all collaborators and mitigate conflicts, you can't efficiently work in a multi team, distributed setup.
Which comes back to my initial point. Yes, it's a step in the right direction to not depend on 3rd party services that might go away tomorrow. BUT. That doesn't negate the need for a centralized master repository. Which makes the entire network still centralized. Distributed. But centralized.
The only difference is that now the central location is not Github anymore, but jb55 (npub1xts…kk5s)'s repo. What happens if that goes down? Or something else happens?
bogdanzurac / Bogdan Zurac
npub1k5…wjkdv
2023-07-04 21:31:20
in reply to nevent1q…etp0
Author Public Key
npub1k5a4y6yfarc8p62xq0uae8jf3aa25mm5eptc20ysyfp0766ypmjsswjkdvPublished at
2023-07-04 21:31:20Event JSON
{
"id": "404523d144b80593a7bff5f2ee08b70a55d9921fdb340ecd4d6def4ec1c13c8e",
"pubkey": "b53b526889e8f070e94603f9dc9e498f7aaa6f74c857853c902242ff6b440ee5",
"created_at": 1688506280,
"kind": 1,
"tags": [
[
"e",
"096a9d87e145717db19c1c6fe9f64d4cf3ec0c031bc07919701f326fb9696d33"
],
[
"e",
"bfa27c4b86865ceed4869f1d03d1eddcdd2fb35d51fe03825c3e42c4463cb2a4"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"00000000827ffaa94bfea288c3dfce4422c794fbb96625b6b31e9049f729d700"
]
],
"content": "Who will get to push the code to another server? nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s's main branch which contains 1 commit ahead of yesterday's last commit for everyone, or mine, which contains 2 other separate commits than his?\n\nWithout a centralized origin which purpose is to retain the source of truth for all collaborators and mitigate conflicts, you can't efficiently work in a multi team, distributed setup.\n\nWhich comes back to my initial point. Yes, it's a step in the right direction to not depend on 3rd party services that might go away tomorrow. BUT. That doesn't negate the need for a centralized master repository. Which makes the entire network still centralized. Distributed. But centralized.\n\nThe only difference is that now the central location is not Github anymore, but nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s's repo. What happens if that goes down? Or something else happens?",
"sig": "1ceb6192cbc1cf28d9483e7ecc080a60a155e04c3fac50c99ea14449de5114d3c3410b3294dcdc1ec4f2d6864c6b920f71b845f321831399f30c102ba9d1739a"
}