> Please note that Apple Music and iTunes Music data will be migrating away from the Enterprise Partner Feed (EPF). Starting July 16, 2024

Simply sharing metadata, related artists, genres, etc would create a pretty interesting ecosystem[1].

[1]: https://everynoise.com/

Every Noise was created by a former Spotify employee.

He's a former Spotify employee now, but he was a Spotify employee when he made it. I think it hasn't been updated since he lost his data access.

I have a lot of respect for Glenn McDonald for spam fighting all these years on Spotify, but we can go better than PCA for mapping music these days. Any neural embedding model is going to produce more meaningful axes. In fact Spotify had an intern who did just that, just before the launch of Discover Weekly: Sander Dieleman. Along with Aäron van den Oord he was snapped up by Deepmind after their Spotify internship. Those two guys were (and are) wildly good at what they do.

I think this is too much credit given for emotional labor. NY has an intrusive din and these people live in their cars all day. They evolve toward chronic irritation alleviated with impotent shows of force.

Would love to see this show up on homebrew!

Oooh, that's a nice idea! We'll look into doing that!

Making a homebrew recipe is super easy, and you can definitely find an example to draw from that's "shaped" like your app. Highly recommend.

Alternatively for Mac,

https://github.com/halo/LinkLiar

^ seems like the way to go. open source and more features.

> "Cheaper/easier" is what creates consequences, not "new".

Nuclear bomb?

Imagine if they were cheaper and easier to manufacture

Are you going to offer a web embeddable version of the Live offering?

It's something we are considering. What use cases do you have in mind?

Mostly personal/art projects for now, but willing to pay.

Just added a signup at the bottom of the technical report: https://lemonslice.com/live/technical-report

Had a hard time parsing this, assumed "breeder" was the role of a human ranch hand, and you were telling them about family trivialities ("bull") so they felt included and soothed. Theory really fell apart around the time you started giving them corn and "sweet feed".

No pretty sure this is just talking to a bull.

It's a boy cow.

interesting to see what accents do and do not work

The eternal red flag of a DB UI that tries to support wildly different backends explains a lot of the problems. Many sane and powerful Postgres features can't be used because Directus also needs to support SQLite, for example. Views not properly supported, search features inadequate, graphql DSL with arbitrary limitations, a lot of weird or dysfunctional relational patterns when something much simpler would do... it's a parallel, inferior system on top of stock pg that is very frustrating when used at some depth.