Content
@
https://warpcast.com/~/channel/scoop3
0 reply
0 recast
0 reaction
meta-david 💥| Building Scoop3
@metadavid
QUESTION: Background story: Scoop3 is an onchain podcast player where if you listen to an eligible podcast episode, you will receive loyalty badge (NFT/ERC1155) that signifies you listened to the episode. As you can tell, this connects the podcaster to their audience on crypto rails. Anyway, now the question, if you're a podcast listener, would you rather: A) Receive an ERC1155 that consists of the audio of the podcast episode. You would have to pay (might be per episode, might be monthly, annual, etc.) B) Receive an ERC1155 that consists of just a badge (graphic), but no audio. It'd be a free service though. Would you rather A or B?
1 reply
0 recast
0 reaction
jon
@jonbray.eth
I love this idea so much it depends on the podcast, and whether the badge contains any metadata that links to the episode is the idea that scoop3 would act as a player only, or a wallet also? I'm leaning towards 1155 that contains audio as well, I love the idea of being able to have podcasts in your wallet with all your other NFTs
1 reply
0 recast
0 reaction
meta-david 💥| Building Scoop3
@metadavid
Great feedback regarding metadata — and that’s something we have to look at! Scoop3 is a player. You can use your existing wallet or it can make one for you if you don’t have one (the general idea was to abstract out the blockchain as much as possible). I like the idea of having the audio file too, but coming across some roadblocks storage space affecting the cron job, so trying to see how people feel. :)
1 reply
0 recast
1 reaction
jon
@jonbray.eth
abstracting out blockchain as much as possible is awesome. as much as I love to see fully onchain stuff, it can make for a worse UX for an app like this now I'm kind of leaning the other way, especially if scoop3 is just the player and the main source for finding the podcasts. if audio NFTs were more of a standard, and already something many people have in their wallets to begin with when they connect to scoop3 then it would make a lot of sense but at the end of the day, having just an 1155 badge still gives you all of the composability benefits of the other option without additional cost to the user if I was building it, I'd probably go for 1155 badges -> get the app fine tuned -> later on, start introducing audio NFTs good luck with debugging that cron job, and looking forward to seeing how this turns out!
0 reply
0 recast
1 reaction
