No. git is not going to be replaced in the next 20 years.
There’s something here, right?
- nostr git hosting is incentivized by nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m with bounty
- CRDT collaborative editing contemplated by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 (https://habla.news/fiatjaf/Zih6ZDW1_63L3QUIaK8BU)
- Gitbutler trying to reform git commercially: https://youtu.be/MRcmnUwrP8A?feature=shared
nostr could simplify git collaboration with the virtual branches approach Scott is pursuing, no?
Discussion
I’m not postulating the replacement of git. But it was designed to be decentralized. Like the internet (Cloudflare) it ended up being used in hyper-centralized manner (GitHub). We use git differently than it was designed. And it’s often cumbersome to work with because of that. I imagine that Scott’s virtual branches approach (continuously rearranging changes for smoother integration) would be especially interesting to be done over nostr. It’s like integrating git patches via mailing list, but with smoother automation.
Do you have like “Nip-Arabic” on GitHub or something?! There is a problem while posting in Arabic because it can become unreadable on many relays as if the language is not recognized by the protocol and I think that could have kept Arabic speaking user away from joining Nostr.
Can you tell more about that? I don’t think Arabic languages should be a problem. JSON is always formatted in UTF-8 which supports all known symbols and also writing from right to left.
It happens when posting in two languages (English and Arabic). The posts look okay before actually posting them then they change when I click post; rendering the Arabic parts unreadable on many relays. Only on Plebstr the Arabic parts are appearing as they should be and the same parts are unreadable on all the other relays including Nos.social and Primal.
It seems that the text format is not kept when posting in two languages and that the posts are considered in English so the direction of the Arabic text is changed to its opposite direction to match the direction of the English text.
So maybe it’s necessary for the “new post” area to have features to format the text and that the format is kept while sharing it between different relays.
Maybe the “new post” area should be like “new message” area of an email where more options are available to format the text and it’s possible to include more than one language simultaneously so that everything is kept the way it was typed once posted.
You are referring to individual implementations of the nostr protocol. The protocol itself is not causing your issue, because Unicode itself should take care of text direction (see https://www.unicode.org/faq/bidi.html). You need to either have a look at relay or client implementations themselves.
Thanks for your reply. Anyways, if there is a problem at the relays, would it be useful to generate a solution within the Nostr protocol so that it’s easily or auto-implemented.
Why don’t most search bars have bidirectional text implemented, Google included?! Why does Plebstr “new post” dev have bidirectional text implement while that’s not the case for other relays?!