Let’s say we were building something for musicians at TIDAL that sat on top of nostr…

We could run a private relay and hide all key management behind the email/password account system we already have…but if we wanted to enable the musicians to be able to fully participate in the wider nostr ecosystem with their own key pair…what’s the best way to present that? A lot of these people will not be all that tech savvy.

Trying to figure out a safe and effective way to enable them to immediately use best practices for key management. Or some safe custodial model until they want to take it upon themselves.

I think the medium.com replacement is the best strategy moving forward. Preferably keep the two ecosystems slightly separate, with separate clients, unless a client deliberately wants to support both.

I am (kinda) working on something like that, #[3] is too, but we must come up with a nice standard.

One this this "long-form" standard should have is the ability to edit the content.

It is very hard to comment about what John Carvalho says, because I can't ever understand what is his core point.

Overall I think the Slashtags idea of WOT is interesting, but you don't need a fully peer-to-peer thing for it, and I think fully peer-to-peer things will work at scale, plus they're too complex. Their stuff would work better on top of Nostr.

Playing with nutstash.app . I’m not sure why, but I can’t stop throwing sats in there then pulling them back out. Do this enough and eventually I’ll have a good idea.