I'm reminded of how common it is for people who are uninvolved in implementing services that use the Internet, to say things like "I don't use the Internet on my phone, only Facebook". Nostr might well find a similar long-term pervasion, however you must determine when constructing your message: how important is the fact of message getting to you thanks to some specific protocol, relative to your message itself?
If your audience are tool-builders and community engineers, then it is defensible to add the cognitive overhead of naming a protocol they might never have encountered before, and including some evangelism about why it is important... however, if you're using a tool already built, and your message will reach an audience already there, then the cognitive burden might be an irrelevant distraction.
A similar discussion could be made about IPv4 and IPv6; sure, more and better services can be deployed on IPv6... although too much information about an improved technology drowns the prospective customer. Someone else who does not burden them with the cognitive load, and performs the developer advocacy with developers alone, might ultimately cause a much larger adoption effect.
I'm reminded of how common it is for people who are uninvolved in implementing services that use the Internet, to say things like "I don't use the Internet on my phone, only Facebook". Nostr might well find a similar long-term pervasion, however you must determine when constructing your message: how important is the fact of message getting to you thanks to some specific protocol, relative to your message itself?
If your audience are tool-builders and community engineers, then it is defensible to add the cognitive overhead of naming a protocol they might never have encountered before, and including some evangelism about why it is important... however, if you're using a tool already built, and your message will reach an audience already there, then the cognitive burden might be an irrelevant distraction.
A similar discussion could be made about IPv4 and IPv6; sure, more and better services can be deployed on IPv6... although too much information about an improved technology drowns the prospective customer. Someone else who does not burden them with the cognitive load, and performs the developer advocacy with developers alone, might ultimately cause a much larger adoption effect.