So has the same issue when doing the open signer app button but bunker worked!

i see you're using my new nostrconnect login workflow. hell yeah!

NGL not sure what to do with the manual bunker option? Its one of those "and at this point im afraid to ask" sorta situation.... 😳🙈

Ill look into importing. But why arent tracks being automatically imported? Is it to associate the uploader npub (that would make sense). What prevents another user from claiming someone else's feed?

Apologies if the answers are obvious if I just try it... I have amber installed but trying to login it says no signer extension found. Not keen on yolo'ing my nsec

to be automatically imported, relays would need to know all the feeds. Nothing prevents a user from claiming someone else's feed. But the same is true with podcast: anyone could mirror a feed and swap out the wallet addresses. This is a shared responability between publisher and audience: audience needs to verify, publisher needs to provide means of verification. In that particular context, i believe nostr has a greater chance, because cryptographic verification mechamisms are built in the protocol. But we'll only ever know what really works once we blow up and we start having big stars pulling in big figures.

there are two slightly more mature clients i recommend you try:

nodecast.xyz

nostria.app

don't raw dog your nsec though. Like ever. Extension, amber, or throwaway keys! 😅💜

Ill look into importing. But why arent tracks being automatically imported? Is it to associate the uploader npub (that would make sense). What prevents another user from claiming someone else's feed?

Apologies if the answers are obvious if I just try it... I have amber installed but trying to login it says no signer extension found. Not keen on yolo'ing my nsec

This looks great!

Have you considered API with podcast index to pull existing feeds? Your library is understandably sparse but there's thousands of tracks available on the podcast index (which includes the entire wavlake library and 2x more tracks on #demu).

An immediate issue we would face is duplication. To distribute our full catalog on your platform, we'd be duplicating feeds. We are already using the same rails for our existing feeds so it would make more sense to import an existing feed vs creating new ones.