Nostr Web Client

the nostr booth at nostr:npub167n5w6cj2wseqtmk26zllc7n28uv9c4vw28k2kht206vnghe5a7stgzu3r had a lot of successes

for example, i spoke with a team of German journalists that recognized the importance of decentralized and censorship resistant content. they want to build and/or use an existing platform that uses nostr for their articles.

they had a lot of questions.

i informed them on highlighter, habla, and said that they can use these existing applications, contribute to them, fork them, or build their own.

#grownostr

Sebastix 1y ago

That's why I believe integrating Nostr in existing publishing software (like a CMS) can really make a change for them. With Nostr the content can syndicate in both directions.

In case you didn't know: that's what I'm trying to build in Drupal and have already demonstrated it with some proof of concepts. 🤓 Your content not only lives on your server in your own database, but is also distributed with Nostr to several relays (long-form content is a really good fit for this). Looking forward: imagine what happens if your current website will also act as a Nostr relay..

Reply to this note

Please Login to reply.

Discussion

Derek Ross 1y ago

i think that local relays are great for speed and distributing or broadcasting that content to other relays helps with decentralization. it's a good mix. no one wants a slow website.

Sebastix 1y ago

I know nostr.band is alreadyacts like a client requesting new events from all known relays.

When I post an event to my personal/development relay, it's getting requested and indexed within seconds 😆

So broadcasting content already works in a neat way I must admit even I just broadcast it to one relay.

Derek Ross 1y ago

The outbox model helps here too. I publish to my private relay and it's discovered right away.