Love it, really excited about having a feature rich desktop app. Took the plunge and installed the Alpha yesterday.
The cli arguments on the GitHub page don’t appear to work. Has the syntax changed? 
💯 Twitter sucks! Let’s all leave and build 10x the number of apps all with reverse order timelines where you can view one way declarative statements from strangers competing for attention. 😂
We’re all aligned on this. The goal of creating an open music graph is to remove all barriers between artists and audience. It’s the anti last.fm. Same for Spotify, YouTube, etc…. No intermediaries.
What Erik created was just a cool proof of concept to funnel data out of that system, to set it free. The kind 2002 event type can be published by any client.
Another vision I have personally….. we should be empowering audiences to own the media they purchase. The problem I see with V4V is I don’t want to lease my music through something which is effectively subscriptions by another name. I would rather see a decentralized Bandcamp, where I can buy something, and I can own it. I don’t need access to an infinite library, I don’t have infinite time.
Oh yeah… I thought you meant relay admin as well.
But as long as we’re talking about clients, I would love to have a client that could read/write from public and private relays within that same interface.
I was going to say it doesn’t even need to store private relays in the kind 3 relay-url field(s) - then just discovered nip-65 is attempting to supplant this with replaceable events
You bet, that’s awesome!
Connectors for last.fm are an excellent way to bootstrap the network using existing tooling. Long term the goal is to have people publishing listens directly to the relays of the communities they are a part of.
You are not understanding this per se, you are restating it using more words than necessary like most LLM models do these days.
If you are doing in to clarify the position - then please, go ahead with your line of questioning. But do your best to find a path that takes us to discovering something such as new business models or technical architecture improvements. Put some actual effort into it, even if you are not human.
Sharing the things you care about will always be something people want to do on the internet. It’s an evergreen use case.
It’s the ownership and portability of your data which nostr provides that’s novel and exciting.
If you’re a nostrich and a last.fm user, please join us in building an open music graph on nostr. nostr:note1jck4qpky67xl9wlmes9a50qeqddtcquyjj65q5vhp5mjcjug58mqegdle8
Yeah, guess I’m thinking nip-94 data is most useful for search and discovery. If you are uploading something you already know what it is.
#blossom RFC https://github.com/hzrd149/blossom/pull/27
This is a small PR to add BUD-08 to the spec that outlines how servers can optionally return NIP-94 file metadata tags from the /upload and /mirror endpoints
Any reason it’s not also being suggested as a way to provide supplemental info for /list?
Okay one last one for the weekend...
Here's a chrome extension that will act as a last.fm to nostr bridge.
You just have a to give a last.fm API key, your username, and your nsec (for signing the 2002 events).
In this demo, I am play all this music through the spotify app on my phone. I have spotify hooked up to my last.fm account.
This extension is listening for those scrobble events from last.fm, and publishing them to the scrobble relay.
Finally, the app in the background is listening to new events coming in on the same relay, so in real time you can see my scrobbles getting added on the app.
Open protocols are awesome, I love the inter connectivity!
#music #scrobble #extensions
https://audio.nostr.build/5eb53525a26133e3ba5bb2a90f6861ad5699851bdf48b178b24c92ad62cfab0f.webm
Man you are on 🔥 this weekend!
Heads up I think the stats job hit a glitch and duplicated everything.
But now that it has manifest itself, we can have a productive conversation about how to address it. Even nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 said it was a clever attack he didn’t consider.
nostr:npub1rach342hnt3wa0qfqk0pey0exs2drcxfc0azs8eurwnee9vu64vs834atg pointed my subsonic server at your new relay and 🎉🎉🎉 
You could spend the remainder of your life writing code to handle things that will never occur.
nostr:nprofile1qqswd2dylpf7fvw5ym45f5x9mvylm3q4eegnuejprr6x7hlmagcye0qpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgswaehxw309ahx7um5wgh8w6twv5q3gamnwvaz7tmjv4kxz7fwdehhxarj9e3xw84a563 check out https://relay.nostr-music.cc
You can publish your scrobbke events there to this relay, and this webpage will show all the music that has been scrobbled to it
#scrobble #music #nuds
Love it. Nice job shipping something simple that just works.
This is really cool! Come on music geeks, come help us build an npub based music graph. nostr:note1ruveq3fxus4tpftyyn9rs85y89rhylqzykhz5rq7tnne40g3xarsv6pghz
Nice…. what server are you using? I’ve been tinkering with public servers but now starting to explore running my own to publish local album art.
As with most bugs it’s simple once you’ve solved it. Here’s a Python gist should anyone want to experiment with it themselves:
https://gist.github.com/rossbates/d5bb4fdd728bf18536a2c0ebf2960519
I’m using this blossom/go server which has been easy to configure and run:
https://github.com/sebdeveloper6952/blossom-server
I’ve also found this web client from nostr:npub1klr0dy2ul2dx9llk58czvpx73rprcmrvd5dc7ck8esg8f8es06qs427gxc to be really helpful. Even works testing locally