Replying to Avatar Water Blower

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 nostr:npub1kmwdmhuxvafg05dyap3qmy42jpwztrv9p0uvey3a8803ahlwtmnsnhxqk9 nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm, zap.stream by nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 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.

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...

Reply to this note

Please Login to reply.

Discussion

No replies yet.