Visually I think of it like those stat charts in an rpg like this:

https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcTHtWQ8CbE4a9gvbdzvIV3AP5KpdCa9QT6f9AvBT6hu0g&s=10

With each variable being some genre or tag or artist or whatever. Basically create a matrix variable and that serves as an npubs unique music wot score. A bot can log activity similar to how nostr:nprofile1qqs0q5wwke7qr4j7d4sk37dmf4mzytzy2r59w47f8yc6627rzm9urjcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq3samnwvaz7tmhv4kxxmmdv5hxummnw3ezuamfdejsstjm9w bot listens for boosts.

The closer the score the closer the style preference. You then extrapolate suggestions based off similar tracks that haven't been interacted with.

Reply to this note

Please Login to reply.

Discussion

I see your point with all of this but you're trying to interpret data that doesn't exist.

We need ways for people to listen to this music before we can worry about seeing what your friends are listening to.

That said my app stablekraft.app does have some Nostr stuff added to it. Status updates for what your listening to, favorites (bookmarks) that are stored on Nostr and I use the metadata proposal that nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2 uses with Fountain when a user sends a boost and those even show up in Fountain b/c its the same spec.

https://primal.net/merryoscar/open-podcast-payments-with-bitcoin-and-nostr

Podcasting 2.0 uses GUIDs to identify items and thats how Fountain knows what song or album I'm Boosting.

https://nostrhub.io/naddr1qvzqqqru7cpzpauj9g9dk0aymkj7aj4x9ahhaes4nal4tcyqxe5xc68qswpvx3ugqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqqpdcnqamgdenxxcttv4nqzlljwj

We now have a couple decent options available. I agree we still need more ways to listen but a huge part of retaining users (its not enough just to attract first timers) are vital ancillary features like new music suggestion. Tbh i think thats essential in this age of music if you want to attract and retain most modern users.