nononononono

Stumbled across it in 2017 and created this experiment, https://twitter.com/dsvensson/status/1097072994478944256

Just to push home the awesomeness of crazy music nerds that together create MusicBrainz, please have a look at these two examples:

1. Number of releases per album individually tagged: https://musicbrainz.org/release-group/f5093c06-23e3-404f-aea...

2. The amount of metadata for an album: https://musicbrainz.org/release/b84ee12a-09ef-421b-82de-0441...

When you get used to this kind of high quality metadata, it's just so so sad to see how companies like Spotify treat metadata. As an example, look up Bob Marley & The Wailers on Spotify and try to find original releases, and then compare that to the list found here:

https://musicbrainz.org/artist/c296e10c-110a-4103-9e77-47bfe...

...and the sad part is that the metadata is freely available, with a permissive license.

...preferrably running in a virtualized environment in a closed network so that they don't hog bandwidth off the Internet.

"It's only through God's mercy that we are not under their rule now."

Great way of robbing the people who put their lives to save you of their contribution.

Thanking god for a series of events is nothing more than ignoring reality. A series of events happened, and that's that.

So what decent release tarball storage services are there today if github's autogenerated release tarballs don't do it for you?

Please read the commit log of LibreSSL and try not to face-palm. I think you will fail. The code quality they're up against is very often stuff you expect to find at thedailywtf.com. It must always be ok to criticize (even in the form of mocking) bad code as long as the criticism comes with well written patches. OpenSSL should embrace the help they get for the greater good.