#musicbrainz-devel

love this

ianmcorvidae: I created PR as before, so feel free to share feedback there

navap, bitmap: Can I please get access to https://github.com/musicbrainz/picard-plugins ?

so I can create a master branch, and then fork and send a PR.

could someone add some categories to http://blog.musicbrainz.org/2014/07/07/server-u..., please?:)

Mineo: done

dankesehr

Hi. I am trying to install musicbrainz server on Centos 6.4 and was wondering if there are separate instructions for it

dufferzafar: You've got access

navap: thanks.

Someone else did it actually, bitmap perhaps

Sang: I think the musicbrainz-server repository has some instructions in it?

Sang: Anyway, you will probably be in for less pain if you go for using a virtual image instead.

oh, yeah, I did when I woke up and forgot to mention here

Ok I think I am close. We use EC2 instances and try to stick with Centos as much as possible

so the current issue that I am facing is probably to do with a required module

Compilation fails at this line: use MusicBrainz::Server::Validation qw( encode_entities );

Does that ring a bell on what I must be missing

ianmcorvidae: ^

no.

(that module itself is part of our codebase, so you're not missing it, presumably it's something else it's including or such)

Ok Thanks. I was misreading the error. There was stuff about unicode above it which I fixed by doing this: cpanm Unicode::ICU::Collator so, moving on

I think I may have found the first album I really want to write a review of on CB :)

let your critique freak flag fly

indeed :)

heh, god I'm wordy

oh well, it's designed for reading :P

you've just realised? :P

no, just reminded by that pesky Preview tab :P

:D

less than 1000 words, I guess, but :P

... dammit

overran the review length, heh

Gentlecat: is there a specific reason for the particular review length limits that CB has? I really don't want to trim this down 1300 characters :P

though I guess it'd help my wordiness :P (anyway https://gist.github.com/ianmcorvidae/e50147290f... XD)

that seems like a reasonable length of review

yeah

6411 characters, max is 5000 right now

I guess it's 5090 if you remove all the links, but :P

I mean, it should be possible to at least have a few sentences for each track, plus an intro and closing paragraph

er, or maybe 5150. vim and wc seem to count things differently

wc might not count unicode characters properly

or vim might, yeah

wc might count characters with the -m option, but the gnu coreutils are notoriously bad at that sort of thing :/

passing through binary bytes properly, sure, but handling unicode, not so much :)

evening folks

MB went with Gandi for SSL, is that right?

hi ocharles

and yes afaik

kepstin-laptop: spotify also sucks for things like canada!

hum. I'm in charge of getting ssl for work tomorrow, and I feel like chemistry dog with this stuff :)

I like Gandi as a company, so I'm inclined to go with them - MB hasn't had any problems of browser acceptance, afaik

yeah, they're pretty reliable

their certs are signed by comodo, IIRC

yea, warp would know :)

my thoughts exactly XD

ianmcorvidae: i think that's right, yea

an ev wildcard is reasonable affordable

also, we're going to be trying linode for hosting... which will be interesting :)

generally the rules with SSL are, unless you're a bank don't bother with an EV cert probably, and as far as configs, https://github.com/ioerror/duraconf has some reasonable info, and use https://www.ssllabs.com/ssltest/analyze.html to check your setup

kepstin-laptop: sure, but this is a business that can afford to go a bit further

ianmcorvidae: all good info, thanks!

duraconf is pretty hardcore about secure ciphers, so you may need to add more (IIRC it only allows PFS ciphers, for example)

those configs are especially useful

depending what you're looking at supporting, etc.

duraconf also turns on HSTS, which you may or may not need or care about

(if you want to support non-ssl, you definitely *don't* want it, anyway)

heh, the ssllabs test is kind of fun; kepstin.ca gets an A+ right now.

we may actualy want hsts

we are very websocket heavy, and proxys tend to fuck them up pretty consistently

e.g., the entire site is unusable on EE's mobile network atm becaus they strip out the "Upgrade" header

thanks guys!

yeah, obviously I don't know your needs :) so just trying to give general warnings

heh, good job

yea, appreciated :)

I have nothing to add, ianmcorvidae covered everything interesting and more.

well, I feel like i'll only be leaving with more questions

but what else would I expect :)

heh

:D

good ol' security/crypto

ocharles: the ssllabs thing is good to check when it's all set up.

and MB too, probably, we're bad about that I guess :P

oh, if you want HSTS, also note that you can fairly easily add yourself to browser lists of HSTS sites with pull requests (I believe at least chrome/FF have established processes for this), though I haven't researched it deeply

wow, today I learned that one of the guys who started studying here in ilmenau with me is now winning one stage of the tour de france after another