Is there a reason you’re stanning so hard for ZBD? Surely they can defend their own practices. Why are you?
nostr:npub1earna05hx6ax38r33h3atmecjzdu547m8suw87w70aw6mlyga4hsqcja5j won't be the only Nostr client to custody keys for users. Even if ZBD plans on allowing users to export their keys at a later date, at some point we will most likely see another Nostr client that won't allow this. They may even clearly state this in their business model. The beauty of Nostr is that it's truly open. That means any client can be built in any shape or fashion that fits their user's needs. The free market will prevail here though, I think. Users will want to try other experiences and advocate for their clients to allow them to do this. And if they don't, those clients may not make it. Freedom and user choice will prevail.
Discussion
I don't have anything else to do at the moment and I wish for people to hold everyone to the same standards.
The pitchforks are already out. What other clients are doing this?
Plenty of clients don't support all features of Nostr. Did you know that Damus doesn't support GiftWrapped messages, Communities, and plenty of other NIPs!? Damus doesn't support exporting your NSEC though.
I kinda assumed freedom to change clients was already the standard.
It generally has been. I remember saying back in January that some day we could see Twitter add Nostr support. They'd generate an npub for every user and they'd just be using Nostr and not even know it. They'd custody keys and manage them on the backend. We're actually seeing that scenario now. My bad for putting that out into the ether, I guess. 🤣🤣 But seriously, of Nostr and open and people can do what they want, them a client treating exporting their nsec as a feature should be okay too. Not all clients will be exactly the same. Not all clients will be for everyone.
What you’re describing is more like mostr.pub where fediverse users are writing events with nsecs tied to their Mastodon accounts. I don’t know much about how that works though, but I’m pretty sure nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 isn’t sitting on a pile of nsecs.
I highly doubt he's personally messaging everyone on Mastodon and providing them with their NSEC 🤣
No, they can’t login using it either but I think nobody has the nsec as it’s probably generated cryptographically and never stored anywhere. Someone correct me if I’m wrong please.
@npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6
Twitter could and I hope does exactly this. Then I will charge Elon 10 BTC for the idea and send it all to Nostr devs.
Twitter would probably not do this because then it would have to support an open standard where they can’t police the content.
Oh they absolutely could. They could run their own relay and indexing service and control all content which goes in and out. It wouldn't be a vanilla experience, but it's how they would probably integrate Nostr.
But if an X user’s note ends up stored on a relay that doesn’t support delete, it’s stuck out there in the wild.
That's something they'll have to come to terms with and give users a choice to opt-in. I assume it will a check box. "Participate in Nostr: your Tweets will be sent to Nostr. Please note that doing so, your Tweets on Nostr may not be able to be deleted from all Nostr servers."
I don’t see it happening under the current regime.
Why would they? What on earth is in it for Twitter to add Nostr? What does it offer that their closed platform does not? Surely Twitter already has more than 300 Bitcoin bros arguing about nsec custody already?