Oddbean new post about | logout
 Here is my proposal for a 30 minutes talk about a better way to develop Nostr softwares in general, contrary to mainstream nostr believes.

https://github.com/nostrworld/nostriga/issues/13

“Nostr Native” vs “Nostr Integrated”

Nostr Native is applications that builds 95%+ features with Nostr relays only.

Nostr Integrated is applications that builds its own system and only integrate with Nostr for parts that make sense.

I will use case studies such as @geyser @Alby, zap.stream by @Kieran as “Nostr Integrated” applications and most other Nostr clients as “Nostr Native” applications.

I will argue that “Nostr Integrated” is the better way build applications.

I will then dive deep into how blowater.app transform from “Nostr Native” to “Nostr Integrated” and promote a little bit about my new project https://github.com/BlowaterNostr/relayed at the very end.

Please vote for me!

I believe this talk will be very insightful for developers and users. 
 I like this idea. We need to promote more of integrating existing applications/services to leverage nostr where it makes sense. This is part of the ethos behind Corny Chat (nostr integrated)

 
 Please 👍 in the Issue so that Nostriga organizers know you want it. 
 Native / relays only. Even Native-- remove as many features as possible. Make it really simple and robust.  
 nostr only vs nostr as social layer, seems like a nice spitch. But my note is how can you developers build together? The answer is nostr, I don't know.  
 Please 👍 in the Issue so that Nostriga organizers know you want it. 
 Love it. I don't think we need another 500 nostr social clients. We need apps that integrate parts of nostr that are useful for them. Maybe some social aspects, maybe some "other stuff" aspects, like nip90. 
 Please 👍 in the Issue so that Nostriga organizers know you want it. 
 Good distinction and sounds like an interesting perspective 
 Please 👍 in the Issue so that Nostriga organizers know you want it. 
 At this moment i do not have a plan to be there. I wish you well 
 I think “Nostr Integrated” has far more potential. I am experimenting using #nostr relays for a push notification service and backend api orchestration. 
 Yes, yes, and YES! "Nostr bros" want nostr to be the end-all, be-all of everything ever. And because of that the scope bloat is unreal. 
 Concept ACK.

This was something I struggled to get clarity on, when first learning about Nostr. 

Nostr is marketed as permissionless, and so developers are more or less free to implement integrations, as they see fit.

This can be confusing, as questions arise like.. 'should I store large amounts of arbitrary application data myself, on private infrastructure, or is it acceptable to burden relays with this task'.

Obviously there are no set in stone answers to many of these questions, but to at least have a discussion around 'best practises' would be very helpful, especially for the newcomers...