The 3rd party services were part of the early Twitter success when the API was open and it was an open field for innovation and experimentation providing utiilty and value for end users.
Nostr has the openness but the hurdle to start development is pretty high at the moment. There are plenty of nips and existing repos but the documentation and getting started easiness is not there. For existing devs who been around the knowledge is implicit. Thats not the case for newcomers, and it’s rarely made explicit.
The dev friendliness is not in the level where the libraries and tools are supporting newbies to experiment and test quickly.
For example, comparing how quickly you can do stuff to ATProto is one reference point: https://skyware.js.org/guides/bot/introduction/getting-started/
Some of the (obvious) issues are:
- easy authentication on multitude of devices (especially on Mobile; again here ATProto has a pretty nice app password solution)
- media storage
- the ecosystem costs issue (who pays for relays, storage etc)
There are a lot of individiual projects but when you look across categories and across the user value chain (starting from the client, moderation tools, content sources (algos), relays, storage etc.) the integration is not smooth.
petri / Petri Kajander
npub1us…nn3mj
2024-04-13 16:52:10
in reply to nevent1q…0uq6
Author Public Key
npub1ust7u0v3qffejwhqee45r49zgcyewrcn99vdwkednd356c9resyqtnn3mjPublished at
2024-04-13 16:52:10Event JSON
{
"id": "e3f5d677981564524d15a92a8c7168ae013b04b4f0973b7074a1a2e033dcd6e6",
"pubkey": "e417ee3d910253993ae0ce6b41d4a24609970f132958d75b2d9b634d60a3cc08",
"created_at": 1713019930,
"kind": 1,
"tags": [
[
"e",
"2f7ed1ab5f2395f075784021822e36083dabe02e5bb68f902c001068ed5e4c3b",
"",
"root"
],
[
"p",
"82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "The 3rd party services were part of the early Twitter success when the API was open and it was an open field for innovation and experimentation providing utiilty and value for end users.\n\nNostr has the openness but the hurdle to start development is pretty high at the moment. There are plenty of nips and existing repos but the documentation and getting started easiness is not there. For existing devs who been around the knowledge is implicit. Thats not the case for newcomers, and it’s rarely made explicit.\n\nThe dev friendliness is not in the level where the libraries and tools are supporting newbies to experiment and test quickly.\n\nFor example, comparing how quickly you can do stuff to ATProto is one reference point: https://skyware.js.org/guides/bot/introduction/getting-started/\n\nSome of the (obvious) issues are:\n - easy authentication on multitude of devices (especially on Mobile; again here ATProto has a pretty nice app password solution)\n - media storage\n- the ecosystem costs issue (who pays for relays, storage etc)\n\nThere are a lot of individiual projects but when you look across categories and across the user value chain (starting from the client, moderation tools, content sources (algos), relays, storage etc.) the integration is not smooth.",
"sig": "650acb6b3c0d6c5d54ec41c310e3f5c60253d577b8541b038c2318e9f4f536613d06778c0dc34244f6cd182e07dde471eba7ec5692439ce57cc414dfdf6b3c86"
}