Lucifer: my favourite Onion feature!! (regarding the tweet though, the headline for those is always real news, the comments that come with it is the satire)
mayhem: interesting question. I'd say that bits of messybrainz are probably the same, the flask app structure, bits of the ingestion API, and the base flask templates, probably not much more left from that
mayhem: of course, knowing academia, having more than 1 article that reproduces the same work is definitely a good idea!
mayhem
well, its not so much about anything concrete in that paper, but there is a seed thought that turned out to be rather insightful.
alastairp
actually - speaking of that article, I wanted to run some stuff past you today. work out where we should try and get to in the next week or so
mayhem
I'd love that.
in the office today?
alastairp
I teach this afternoon, so it kind of breaks up my day a bit too much. I'll be in next week
mayhem
k.
I'm working on a proof of concept of something, that if it does pan out, could be a bit of a game changer for us.
alastairp
great
mayhem
that would influence this discussion, possibly a lot.
let me keep working for a bit.
this of course was one of those 11pm insights and then you can't stop hacking until 2am...
alastairp
I think the BPM stuff, while useful, is probably pending on getting an interesting dataset of ground truth - that could be either related to us collecting data from users, or somewhere else
mayhem
as are many others yes.
alastairp
one options would be to go ahead and do our plan for running all algorithms, and then get some spotify ids for songs for which there are inconsistencies, and start putting them in front of people
mayhem
which makes me want to focus on BP as a killer experience, complete with data gathering tools
and then build ML tools out.
alastairp
however, I'm not sure exactly what that's going to give us in the long run - as you said, getting candidate bad songs in front of software developers is a good idea. is this process enough?
mayhem
I guess the process is enough if it yields sufficiently clean data. which of course defies definition.
aerozol has quit
alastairp
yeah - and even on my small test of queen, pink floyd, and miles davis we saw stuff which I'd define as not clean data
mayhem
which in all of this makes me want to go back to our roots. have users give us this info.
alastairp
yeah, right
mayhem
what was this guy Bob's name who kept harping that MIR research wasn't any better than a horse could so or so?
I think he's right. 100%.
alastairp
yep - Bob Sturm
mayhem
him.
alastairp
right, his argument was to try and think about things in terms of musical understanding
e.g., want to classify jazz? start looking at instrumentation and chord sequences
of course, that's a difficult task in itself, so...
mayhem
I'm really starting to think that these hard problems "what is jazz" are just pointless to solve. very hard, poor results.
I really think that given a goal in mind (e.g. we want to do recommendations and cross-platform playback) we can find simple solutions that may not even require machine learning. or much fancy stuff at all.
It was mainly for the playstore release process of the app because the process requires us to do 1-2 additional things, which can be missed by someone. But I agree with the point that since we are a few, we don't have to worry about this. However, I will make this point for future devs in the docs in case we expand and multiple people are involved in the process!
monkey
👍
alastairp
in that case, clear documentation is definitely an important part of the release process
and is exactly why we just spent a week doing this, because there are many parts for which only one of us knew how to do something
akshaaatt
Yusss 💯
monkey
I'll add that in some cases it's useful to allow the team access so someone can do a release for you if you're unavailable (provided there's good docs on how to do it)
but do you think there is any way I could have bono to myself for another... half hour to an hour?
lucifer
sure 👍
mayhem
thanks!!
python script at 80% of ram, lol. she's gonna blow capn'!
lucifer
lol
reosarevok
yvanzo, bitmap, lucifer, mayhem: zas asked us to document different bits of docker-server-configs which were not added by him, maybe you can take a look when you have the time :)
mayhem
is there a PR for this project yet or should we start one?
outsidecontext
mayhem: I love the Bad Gateway sign. It's for sure a quiet place 😜
mayhem
yeah. peaceful.
reosarevok
mayhem: nothing yet, I think, because zas just added a basic readme directly for the stuff he knew