The consensus on that list is that License Zero violates certain tenets of the Open Source principles, and as such software released under a License Zero license is not open source software. By extension, this means that getting to work full time on License Zero software means that you’re not working full time on open source software.
> FreeDB avoids this problem by supporting multiple entries for any given disc.
FWIW, something somewhat similar to this will Soon™ be part of MusicBrainz too: https://tickets.metabrainz.org/browse/MBS-4501 – you might want to read through there and maybe even put your own thoughts about what it can be used for in a comment on that ticket.
> MB […] used to have rules specifically banning anything except Camel Cased English Literary Title style
Just out of curiosity: When was this? I’ve been involved with MusicBrainz since summer of 2006 (ie., for over 10 years) and this hasn’t been the case for as long as I’ve been around.
… And I think this has exactly been @bunderbunder's argument from the start? That the "definition" put forth by threeseed is naïve and could at best be usable on an amateur level, but as soon as you start having money involved, you really want a more in-depth/verbose/specific definition (like the one the OSI provides), rather than simply being "I can read (and thus modify) the source."
Note that our current search server software is in "minimal maintenance" mode. We're working on a replacement which will hopefully allow for a lot of improvements to search rankings etc., but a lot of other things have higher priority (like actually being able to serve requests in spite of getting hammered by bots and spammers).
Of course, MusicBrainz is an open source endeavour. The old search server maintainer was a volunteer from the community. If you believe you can do a better job at running our search server, please join us in #metabrainz at Freenode and introduce yourself.
LinkedBrainz is not something that the MetaBrainz team is directly involved with, however, according to themselves, «[they are] back, if basic for now.»
We may never have the stats Spotify has, but we are trying to get listening information via the in-development ListenBrainz: https://listenbrainz.org
I'm not sure when/if we'll be able to tie it in with MusicBrainz directly, but for someone like exogen, ListenBrainz may be a good basis to figure out relative popularity of various Recordings/Tracks regardless.
Thanks! Looks like it's a fairly old post (and thus working with an old version of the schema), but still interesting to see how it's being used "out there". :)
Are you aware of the AcousticBrainz[1] and (upcoming/in-development) ListenBrainz[2] projects? We at MetaBrainz (the organisation behind MusicBrainz and the other *Brainz projects) really hope that the combination of data MusicBrainz, AcousticBrainz, and ListenBrainz will enable powering a lot of open recommendation engines. :)
Libre.FM sets out to be a ~1:1 (open) "clone" of Last.FM (or least the AudioScrobbler part of Last.FM), while ListenBrainz aims to improve on Last.FM/AudioScrobbler. E.g., the AudioScrobbler protocol only allows for a given subset of metadata items to be submitted, while ListenBrainz's native API allows you to submit basically all the data you have on the file.
Compare http://www.last.fm/api/show/track.scrobble 's 7 item specific metadata fields (artist, track, album, trackNumber,
mbid, albumArtist, duration) to https://listenbrainz.readthedocs.io/en/latest/dev/json.html#... - as ListenBrainz is part of the MetaBrainz "umbrella", one of our own main highlights is that we can now actually submit all MBIDs associated with a file, not just the Recording MBID (ie., Artist MBID(s), Release MBID, Release Group MBID, Track MBID, Work MBID(s), possibly Label MBID(s), etc., etc.), but also stuff like language, performers, AcoustIDs, ...
Also, ListenBrainz is linked up with MessyBrainz[1], which should work as a buffer to have even listens submitted without MusicBrainz identifiers be able to eventually get linked up to the MusicBrainz database.
> which is why I export in mp3 as well as wav; wav for higher quality, and mp3 for labeling purposes; I could probably just use flac but compressed audio like mp3 also has the benefit of being less space intensive
You could replace the WAVs with FLACs and save a bunch of space on that account. Maybe enough that you realise you don't need to keep both lossless (WAV/FLAC) and lossy (MP3) copies around. Since FLAC is lossless, it will have the exact same audio quality as the WAV files they'll be sourced from. (And, as you mention, FLAC supports tags directly.)
It would be completely against the spirit of the project to close in on itself, and as Leo_Verto mentioned, also pretty hard. With the core data available as CC0 and all the source code needed to run the servers, anyone could legally take all the data and set up a "LibreMusicBrainz" in some hours in the unlikely event that the MetaBrainz Foundation (the organisation created to support MusicBrainz and the other *Brainz projects) should ever flip.
Unauthenticated search is still possible and allowed, just as long as you use a proper User Agent string. See https://musicbrainz.org/doc/Development/XML_Web_Service/Vers... "Do I need an API key?" and "Do I need to provide authentication?" (In fact, I don't think there is a way to do authenticated searches.)