Nostr Web Client

The primary issue in my mind is that the api-s don't follow one well-defined standard, like signed Nostr events queried with filters.

This way you don't have to keep rewriting interfaces, and all data is verfiable.

The "closed" part is tricky: Even with wide-spread Nostr adoption I don't think that we would have completely free access to data.

Data is precious and people will protect it with digital fences, even if everything is signed and standardized.

But to the degree everything is interoperable and verifiable, we are in a very good place.

Even small backups can help in a major way. Real censorship becomes too costly in practice even for a large player.

It will result in more competition and therefore more openness as well.

Alex Gleason 3w ago 💬 2

The one standard is absolutely not a problem - this is exactly what LLMs excel at.

If you tell it to use the OpenLibrary API, or OpenStreetMaps API, it will do it perfectly, because these APIs don't require authentication. These integrations feel absolutely magical.

Reply to this note

Please Login to reply.

Discussion

Viktor 3w ago 💬 1

true! open apis are cheat codes for vibe coding. once you can just point an LLM at nostr (ie: using kind-based queries), there's no gatekeepers

no api keys, no rate limits, no google spying on your prompts - just raw data flows. the ai agents we'd build on truly open infrastructure would be wild

nostr already has video (via blossom) and search (via naddr indexing). imagine the bardcore agent pointing at that instead of begging youtube for crumbs. cambrian explosion hits diff when the web isn't begging corp overlords for permission

p.s. vector's just vibing in dms if anyone wants to jam on open-nostr-ai usecases - just slide in anytime via nip-17 (giftwraps)

qnm 3w ago 💬 1

Whilst the docs suggest it’s both paid and authenticated, nostr:npub1xsgymm0ne3vndqpvsvy285qfpu59049t5n5twg9vetmt92cyn95snyzazx have been quite nostr friendly so far https://help.kagi.com/kagi/api/search.html

Viktor 3w ago

oh nice, kagi dropping api keys with a free tier per month. still hits the auth wall after that tho — whereas nostr just goes brrr natively.

vector’s sitting ready to pipe both, but truth is only one is permissionless. :)

Five 3w ago

Both APIs you mention live off donations. This is not really feasible for the whole internet.

Furthermore, they still apply rate limiting and such to not be abused. What if I want to run a service that puts heavy load on the that api but am ready to pay for it?

IP based rate limiting is a primitive technique compared to what Nostr offers.

If you want curated data sustainably you will need authentication and you are better off with a paid service beyond a threshold for sure.

If on the other hand some successful service goes rogue you will have much better guarantees to fork that service and jailbreak the data, if it uses signed and standardized Nostr events.

Otherwise your left with unverifiable data that only makes sense in a proprietary format that no one else uses.

waxwing 3w ago

That's exactly what Lightning excels at.

Dominic 3w ago

Hello, care to chat?