#It has allowed us, first of all, to keep the service very simple and create a simple API so that developers can build on top of our infrastructure and come up with ideas that are way better than our ideas, "

Sounds pretty much the start of #nostr. How will nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 prevent nostr from having the same fate as twitter, being closed source, having Monopol of one client over the others, full of censorship, etc?

Is it by not attaching IDs to clients/servers?

If #amethyst and #domus and other servers get big enough and merge and find ways to block other clientes, how will this be prevented?

Reply to this note

Please Login to reply.

Discussion

Like when Microsoft does Embrace Extend Extinguish

That is a concern, yes. If any single client gets too big that starts to threaten the protocol.

This could happen if making new clients and servers is too expensive. A way to help that would be to make ready to make new servers and clients.

To achieve this, i Believe creating sdks/libs for the most used backend and frontend languages should help, as they did with Matrix. Then everyone could just import it to to the heavy stuff and then program easily some UI on top.

I believe the most used language is typescript, so I guess this would be the best target for a sdk/lib?

*make it easy to make new clients and servers