Hey Nostr, Here is a deck I prepared for doing a presentation in my office. We have a tech talk session and I am planning to present Nostr there. Your feedback and suggestions are most welcome. #AskNostr
https://url.thaliyal.com/nrLfW
#GrowNostr
Discussion
This is great!
There are a few minor spelling and typographic errors sprinkled through it. Might want to do an editing pass.
Slide 12 characterizes NIP-07 as "Browser extension integration" but NIP-07 is not nearly so broad. It is only for "Browser extension signing of events," or could just be listed as "Browser extension signing" in a presentation format, since the presenter can elaborate on what it means.
Slide 15 characterizes everything as public unless encrypted. That is not necessarily the case any longer. Everything is as public as the relay it is stored on. So we have a spectrum of privacy levels available, depending on how a given relay restricts read access, and whether notes are stored as plain text or encrypted. For instance, I administer a private community relay. Only npubs that are whitelisted can read from it or write to it. However, it is stored as plain text, so it is not as private as it could be, but it is more private than storing the same notes on a public relay. I could also choose not to have that relay accessible over clearnet, and only give the folks I want to have access to it the onion address, or have it only be a local relay, accessible by my family on our local network, or remotely using Tailscale. Lots of options for enhancing privacy at the relay level these days.
Slide 21 suggests one client each for iOS, Android, and Web. If I may be so bold, I would suggest replacing Snort with Jumble. Reason: Jumble is a better showcase of Nostr's core architecture, because it puts relays front and center. You still have the standard follow feed, but you can also look at a feed of all notes on a particular relay, and create relay sets that show you all notes from more than one relay in a unified feed. I also find Snort to be slow and buggy these days.
FANTASTIC JOB, though!
Thank you very much for your invalueable feedback.
I will update the deck with these comments addressed.
I myself have used Nostr only for about a month or so. My ignorance is evident :) and I have duly called that out in the deck as well!!
Incredibly well done for being so new to Nostr! You definitely grokked the fundamentals and the value of this protocol!
Of course, ChatGPT for organizing the content. And prepared notes based on what I learned in the short period!
Meanhile, I am setting up a little NIP-05 service on https://phostrich.com. And attempting a relay based on Laravel Reverb 😉 . Those learnings were to base for taking up this tech talk session.
This is why Nostr is ACTUALLY decentralized, instead of just LARPing about it; devs that are brand new to the protocol can just jump in and start building on it right away, without a massive learning curve.
Can't wait to see what you build! Maybe one day it will make it into one of my nostr:npub1rsv7kx5avkmq74p85v878e9d5g3w626343xhyg76z5ctfc30kz7q9u4dke.
That is pretty good, I don't have any suggestions or complaints.
Going to mention things as soon as i come across them in the slide deck, so might be a messy string of comments:
Slide 4, the table, last row on censorship resistance: content being hard to erase is half the story; semi-frictioneless restaurarion is the other half (does not need to be on the slide, but do mention it)
NIP stands for 'Nostr Implementation Possibilities' ; its a small little semantic thing where the protocol as such is not 'improved', but rather implemented in various ways
Thats about it actually, looks good. Thank your for your efforts and good luck on the presentation
Sure. Thank you. Let me read more and internalize it myself.
And il throw these in the mix as well, because they are short :)