Nostr Web Client

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.

Reply to this note

Please Login to reply.

Discussion

corndalorian 2y ago

What about a TIDAL browser extension? They sign in with their email/password and it contains their nsec (like nos2x) and allows them to sign into other Nostr clients and manage their lightning wallets or whatever other features you give them?

Derek Ross 2y ago

I'll tell you what Jack. If TIDAL gets Nostr support, you have yourself a new customer.

Do TIDAL artists have a backend management system? If so, maybe turn this into a social media / nostr client portal for them? It would be a custom client built for TIDAL artists, allowing them to create public channels for their music, band, album, new release, etc. It would be a way for them to reach their fans and fans could directly tip via Lightning their favorite artists. This follows the TIDAL goal or mission I believe, right? 🧠

jack 2y ago

Correct

Derek Ross 2y ago

My consulting fee on this is simple. Google Home / Assistant support for TIDAL 😉

oldpatrickulrich 2y ago

I have to assume by the number of Google Homes you have that you sub to YouTube Premium. If Tidal added support for nostr & added casting would you cancel Premium or just sub both?

Derek Ross 2y ago

I would in a heartbeat. I can't take away the #1 way my family listens to music without replacing it. Sure, they could cast from their phones in the meantime, but we're all used to using our voices and prefer that way most of the time.

oldpatrickulrich 2y ago

If you'd asked me 3 years ago I would have still stuck it out with Goog because of the ad-free YouTube. Unfortunately that's becoming a non issue since most of my content creators have been booted/left YouTube anyway. I think I'd make the jump too now especially if Tidal works well with Android Auto.

Derek Ross 2y ago

I thought it did work with Android Auto. I signed up for the trial, I'll go test later.

Sophia 2y ago

pretty please 🙏 :)

pcdkd 2y ago

Agreed. Very much in alignment.

Couple of challenges:

- tech/private key literacy (it’s more the managers who need to buy as they’d be using it everyday)

- contracts/deals relating to catalog monetization (will need to update TIDAL supplier deals to include monetization via these channels, and the suppliers will want a cut from their artist)

- merch makes sense but more and more 360 deals see labels running that too

- TIDAL will need to start with direct deals and prepare for major label push back

Shawn 2y ago

Do you see a first killer app that would compel them? That seems crucial. Is it co-writing, tour or session management, something else?

jack 2y ago

We have a use case to start with. And nostr will help us get there faster I think.

corndalorian 2y ago

Also, as a musician I am absolutely pumped to see this being talked about 💜

jack 2y ago

❤️

Brisket 2y ago

This is one of the most beautiful things about Nostr.

It teaches people about private key management without the financial risk. It subtly teaches people to feel comfortable custodying bitcoin.

If you're going to be monetising your content, you'd better do some 'research' first though.

I'd not be looking for ways to hide the private key, public key magic. Let them become comfortable with it.

Enki 2y ago

Oooh seems interesting.

Cameri🐦‍🔥 2y ago

NIP-26 delegation would be the simplest approach. Minds.com does it.

DETERMINISTIC OPTIMISM 🌞 2y ago

Use email/pw, but let them export their pk for client portability.

fiatjaf 2y ago

Use a custodial keypair (C) for each. If it happens that at any point they decide to create their standalone keypair (S) outside of TIDAL, you allow them to "adopt" the custodial key from the standalone key using NIP-26 delegation.

If someone is following C, their client that supports NIP-26 should be able to recognize that S->C, so they should automatically associate both and also follow S.

After some time, the user should be able to exit TIDAL completely and just use S (although TIDAL could also let them export C just in case).

I am not sure there aren't problems with this approach, but sounds like it could work.

jack 2y ago

🙏🏼🙏🏼🙏🏼

Melvin Carvalho 2y ago

And tidal users get nip5 validation

eee8f902... 2y ago

For a more UX based solution, Bitcoin Design guide has this interesting concept called "Upgradeable wallet": https://bitcoin.design/guide/upgradeable-wallet/

As the user's funds/income grow (and the importance of non-custodial key management increases) they get upgraded through various stages of "progressive security"

Edward Snowden 2y ago

#[0]

Edward Snowden 2y ago

#[0]

Edward Snowden 2y ago

#[0]

petri 2y ago

#[0]