FYI
nostr:note18z7rqv87qt0nu3v0rajf4ghnrqcnnc3ujgeqy3zswgs2nwh3nq3qmwhnlh
nostr:note1822pz2c4p2c4flgdha47jgfrzzf7xqasa7pu7mczacgp2yw4gvqs9m39xx
Discussion
Be the change you want to see - and fork
nostr:note1sdv4kqa3yy9e2e9mxzllqkedgjd262l0c5r9plnmf2s2ddtyfx6s2wx93a
It seems great to be open to forks and suggest that as a way to deal with all the requested toggles and such but really, what are the chances to beat the network effect of an already established client like Amethyst? Even when Nostr itself kind of fixes the walled gardens problem, the network effect is still very much in play here.
Everyone said this about Twitter… now everyone is saying it about Damus and Amethyst. We shall see. 🧿 It’s easy to forget that it’s only been a few months.
That is very true. Althought Damus and Amethyst are technically not forks of Twitter, they only have very similar UI. Forking a project to tweak a few parameters and expecting everyone else to follow is much more unprobable than getting a chunk of Twitter users to switch to your app with a fundamentally different approach to social media at the core.
I guess relays could share with others if you updated your tree, so it could be similar.
The time it takes to turn your OS into a tree is far too long though lol… maybe in the future when consumer hardware is faster, then it may likely be possible.
Whoops I replied to the wrong post here lol…
True, forking Amythest may not yield much fruit… but a new multiplatform client may. 🍇
Has anybody build a successful product from a fork that is core to the product?
Maybe it's a way to start something but wouldn't being on a passenger seat on somebody else's journey a shaky way to build your product.
Thanks for including notes from both sides here. It's really important these days.
My Bluesky usage have gone almost to the Amethyst level (I don't have an Android phone).
note1t7c49703xep6f4u9whaczutxxe7sg6u50l0caclanl6zg20z8jpse8skzl