Unpopular opinion:
Treating Nostr as a collection of "Nostr" clients that talk to each other, rather than a communication protocol that allows any clients to talk to each other, is holding back adoption because you are trying to force users to immediately change interfaces and workflows, instead of just co-opting the data transfers on the backend.
If you get people moving their data over Nostr, then you can create new Nostr-native clients to handle that data in some novel way, to add value.
Don't put the cart before the horse.
Get the data first.
Integrate, then build.
#devs #Nostr
Laeserin
npub1m4…jc2jl
2024-08-18 05:59:21
Author Public Key
npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jlPublished at
2024-08-18 05:59:21Event JSON
{
"id": "13faf45f1e404fba0fa505aae519a920bef39997a9e602cfa62c9a47a44681e4",
"pubkey": "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319",
"created_at": 1723960761,
"kind": 1,
"tags": [
[
"t",
"devs"
],
[
"t",
"nostr"
]
],
"content": "Unpopular opinion: \n\nTreating Nostr as a collection of \"Nostr\" clients that talk to each other, rather than a communication protocol that allows any clients to talk to each other, is holding back adoption because you are trying to force users to immediately change interfaces and workflows, instead of just co-opting the data transfers on the backend.\nIf you get people moving their data over Nostr, then you can create new Nostr-native clients to handle that data in some novel way, to add value.\n\nDon't put the cart before the horse.\nGet the data first.\nIntegrate, then build.\n\n#devs #Nostr",
"sig": "5c8c35b815faa21b3929022660b2c59aa14bd47151855ce472bacf6d9becc39f75d5aa1be6e4ea1fb27a79d196cdb8ce542dabfda799df72f9d79936c9b601ba"
}