Psi

@equinusocio yeah exactly - if we create repositories all over the place people get overloaded with notifications. That's part of the problem with the multiple repositories thing :/

WIP PR here https://github.com/resonatecoop/tracks-api/pull/38

Opened an issue on `tracks-api` for this https://github.com/resonatecoop/tracks-api/issues/24

Note that the second two items are blocked by not knowing what the id is of an album on the track. https://github.com/resonatecoop/tracks-api/issues/24

Yep!

https://github.com/resonatecoop/beam/blob/main/src/components/common/Button.tsx#L63 They are currently rounded. I guess you're asking for more rounded?

Hmm, works for me:  I'm wondering: do you have stream running locally? I'm wondering if we have to change the port for the electron client.

I think we'd need a way to find top tracks for a tag, which might mean implementing the same `plays` filter on the `tag/:tag` endpoint as exists on the `/tracks/latest`...

This looks like it won't be possible until we use the oauth2 api stuff.

It's possible with the API beam has since switched to! (v3). Though I'm not sure what I documented above is what that API is. It kind of looks like that's...