Putting this out there to see if it sticks (or not).
This is intended to be a (god forbid!) value proposition slide to someone already familiar with Signal and who doesn't really care about the underlying tech.
Discussion
my only gripe is that the position of the line items is confusing.
are the middle ones shared by both? does Safebox not do messaging?
also says "**Yo** have Signal"
Remember when Signal enabled MOB coin on their platform and then did nothing with it? I’d love to see lightning payments in Signal.
The best value proposition for 99,9% of my friends and family would be: "yes" to the question: "is everybody i know using it?"
Most people i know cannot even be bothered to install something other than whatsapp simply because everybody else is already using that. I think they would still use it if they had to turn on their camera and microphone everytime they were using the app and all messages would automatically be forwarded to every intelligence agency that is out there.
Things need to escalate so badly before people would even consider changing it.
Totally agree. It’s the protocol underneath anybody could incorporate or white label into their own app.
As for adoption, I believe it will be an impending crisis that will force it, for example, finding out that an adversarial AI is harvesting your medical data and singling you out to health insurance companies.
I am 100% on board with safebox and looking forward to test it.
I hope things escalate badly soon. People really need a reality shift.
I watched your safebox explainer video and I have a use case.
You mentioned "medical records" and it got me thinking. When you go to a Dr. they ask you to fill out forms. These multiple pages of forms sometimes have you enter name, address, etc, MULTIPLE TIMES.
Using this app, the flow could be:
1. Doctor office says scan this code to fill out the forms.
2. The office has checked off boxes from a pre-determined list of personal info they are requesting, with a time limit on the request. (i need your address for 1 year, etc)
3. Your first time doing this: you will fill in all the data they request, then next time, you will just see a bunch of check boxes of which items they are requesting, and you "approve" or "deny" these requests.
4. So Dr. A needs this info, you enter it. You go to Dr. B, and just approve their request.
5. The app transmits the data they need with no repetition (on the same form, or over multiple dr visits or multiple doctors.)
The durability of the Nostr protocol is fine, but this would need to work even if everyone abandoned nostr, and the only relays were YOU and the doctors office.
Yup. I am 100% certain about #nostr as the authentication and transport protocol. What you are describing are user domain requirements that can be elicited and fulfill through user flows. There might be another infrastructure requirement lurking in there waiting to be discovered. That’s the fun part of this project.