rdswift: not really, it seems tickets exist, and patches are welcome ;)
rdswift
Okay, thanks.
zas
it should be noted there's a command line option to select a different config file
and there's a ticket somewhere about "profiles"
rdswift
Thanks again. I responded in the discussion with this information.
candyman joined the channel
candyman
hey I'm trying to do some setup/eval of MB and I'm not sure if I'm taking the right route to achieve my goals...
anyone around that could answer a few basic questions?
Cyna
reosarevok: Is there some other way i can write this ```IF !edit.display_data.begin_date.is_empty ```
reosarevok
candyman: yes, ask
Cyna: I can check in a bit
Cyna
sure thanks
candyman
so the application I'm building is going to both need to pull artist genres (tags) rapidly, and will also be producing new data in the form of artists and their associated genres
reosarevok
Cyna: that means " return !(defined $self->year || $self->month || $self->day);" (so it's empty if it's missing those three) FWIW
candyman
so my 1st thought is that I would use the musicbrainz-api to both submit new data and pull new data rapidly
Cyna
If possible, is there an easy to understand answer
😅
candyman
however the rate-limiting info says that only python-musicbrainz/0.7.3 gets a special limit of 50/sec - would that be true of the node version 'musicbrainz-api' as well?
that is, my application - if implementing the musicbrainz-api - could pull at 50/sec?
reosarevok
candyman: I didn't even know we allowed someone to use 50/sec - I thought it was 1/sec for everyone
Its functioning perfectly now I'm adding flow to it
reosarevok
candyman: how are you planning to do it? :)
(say, if you get "Nirvana", how will you map it to the right Nirvana artist)
candyman
magic. no lol unfortunately Echonest's Rosetta stone isn't a thing anymore - so resolving Spotify -> MB has been hard but not impossible. I look at their albums and such
Songkick fortunately uses MusicBrainz ids so I can map directly a lot of the time
reosarevok
I mean, for some artists we might have the Spotify ID on our side for example, but sadly we don't have anywhere as many as I'd like
candyman
right. but assuming I could figure out that link, sounds like setting up a server - which OMG
the indexing has ended, dear lord that took some time
I as of just now have a server setup w/out replication
reosarevok
Setting up a server might be the easiest way, yes, unless you can figure good ways of doing cache on your side
candyman
alright so part 2 (sorry, you've been a great help, theres no part 3)
reosarevok
Is this supposed to be mostly for yourself, or a bigger service? :)
candyman
I don't plan on distributing the service super widely, a passion project
reosarevok
If you're going to hammer your own server yourself (or with some friends) it probably doesn't matter, but if it'll be a bigger thing you're likely to want some caching anyway :)
Part 2? :)
candyman
I feel that, thank you. I have an idea already for how to cache the event lookups - just let people 'think' their looking at live data...
reosarevok
Tbh we don't get new tags that often, at least not yet
Although we'd love to change that, heh. Maybe if ListenBrainz takes off :)
Cyna: re: props, what do you have now?
candyman
anyways, the new data that I submit. I find that Spotify and MB don't have any genre info, but I manage to figure it out some new genres from other sources
reosarevok
Look at the display_data, you'll need to give that proper types.