True True
I thought so too, but that doesn't seem to be the case during my daily scrolls in next.nostrudel.
#Blossom servers are gonna have a harder time. Swifties are visual-media-first kind of people.
NIP-05's seem easier indeed, but in practice they're confusing and create more problems than they solve.
1. This new bitcoiner will think it's an email address
2. He will not get why he can't just use his email then
3. Apps spend a significant part of their scarce onboarding UX on introducing NIP-05's (and even prioritize it over Keys)
4. This new bitcoiner now is told to pay for his own NIP-05, because "If you not, people can't find you!"
5. Even if he hasn't left the whole thing yet and pays for his NIP-05, he's gonna be extremely dissapointed and confused when...
Everyone is linking their NPUB in the podcast show notes.
Npubs + Network = good enough.
Other identifiers aren't necessary.
Wikis as a rabbit hole dashboard.
https://cdn.satellite.earth/52acbeb2620d452fa15ba2ec1dc2890a695e3945c0801573ca6dceaa3b80f588.mov
Letting users explore topics in whatever way they prefer is going to be pretty darn useful for onboarding.
Why hardcode explanations of Nostr terminology in your app, when you can let wikis do the explaining for you?
Wikis as a rabbit hole dashboard.
https://cdn.satellite.earth/52acbeb2620d452fa15ba2ec1dc2890a695e3945c0801573ca6dceaa3b80f588.mov
Yes. Zap interactions let's gooooooow!
Zap Mentions / some thoughts on broadcasting zaps...
Today on nostr zaps don't provide a great discovery signal because they are fundamentally reactions which you only see if the event being zapped is in already your feed.
If you don't see the content, you won't see the zap reaction, and therefore you won't get the payment signal that indicates the content is valuable.
Zaps also can't trend on nostr because they can't be liked / reposted / zapped / quoted / replied to.
As a user there is no way for me to broadcast a zap in the same way I would broadcast a kind 1 note. I can share my thoughts on something - but there's no way for me to increase the signal of those words by including a zap alongside them. Examples where you might want to do this include:
- donating to a good cause
- sharing a long form article
- supporting a content creator
- thanking a supporter for a zap
---
Potential Solution - Zap Mentions
I think there is a solution to this that doesn't require a new nip or change to the spec. Zap events could just be embedded in kind 1 notes using the standard NIP-27 nevent1 format.
Clients could give users the option to 'broadcast' their zap within a kind 1 note in certain cases and other clients could render some additional UI to display the zap.
Below is an example zap I just sent to nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s - you will probably be reading this just as nevent1... but it would be trivial for clients to parse this and render the zap in whatever way they choose:
nostr:nevent1qvzqqqpxquqzptjz5ej5jncfssa0n2hjvr8e4jz5tlpequraz2442jekee5243qnr65tnu
Ultimately we don't want users of nostr clients to be forced into a choice between sharing content or zapping it - we want them to be able to do both in one frictionless action and this will generate the most signal and make nostr the most attractive place for content creators.
I would love to hear thoughts on this from client developers / designers - nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc
And if someone wants to try rendering this note in the way I've described please tag me!
Reading my mind sir. #V4V
💯 + let various "derivers" compete
Yup, users aren't capable of making explicit attestations (and don't want that overhead).
Looking at the activity at the community-level is the way.
"Forkable read-only public communities where write-access needs to be granted/payed for" fixes this.