is this the first mention of AB in the non-academic press?
2018-05-16 13657, 2018
alastairp
hah, cool!
2018-05-16 13659, 2018
alastairp
it might be
2018-05-16 13620, 2018
alastairp
of course, they're making this claim based on the assumption that our features are robust :)
2018-05-16 13625, 2018
ruaok
this brings an interesting question....
2018-05-16 13631, 2018
ruaok
DING! THAT!
2018-05-16 13647, 2018
ruaok
You'd hope they made same sanity checks along the way....
2018-05-16 13657, 2018
ruaok tweets
2018-05-16 13630, 2018
alastairp
trying to work out what it takes to get a publication here
2018-05-16 13609, 2018
Leo_Verto
ruaok: we could ask them to make a guest blog post!
2018-05-16 13649, 2018
ruaok
Leo_Verto: that is a great idea. I really appreciate you volunteering to contact them with that offer. so kind of you!
2018-05-16 13625, 2018
Leo_Verto
I can do that but remember when I told you I wouldn't need another password reset for my meb email address? Well I kinda managed to overwrite my password database with an older version :P
2018-05-16 13648, 2018
reosarevok
Oooh, neat
2018-05-16 13653, 2018
reosarevok
The article, not Leo_Verto's mess :p
2018-05-16 13659, 2018
ruaok
Leo_Verto: lol, ok hang on.
2018-05-16 13615, 2018
Leo_Verto
Shuh, reo :P
2018-05-16 13650, 2018
github joined the channel
2018-05-16 13650, 2018
github
[listenbrainz-server] mayhem closed pull request #406: LB-354: Allow deletion of user accounts (production...allow-user-deletion) https://git.io/vpyJU
2018-05-16 13650, 2018
github has left the channel
2018-05-16 13601, 2018
bukwurm joined the channel
2018-05-16 13612, 2018
ruaok
iliekcomputers: hmm. not sure where we should be merging stuff to right now. we've got some things headed to production, others to master. but we're not 100% that we can get the spotify stuff debugged in time, so I don't want to be too agressive in merging just yet.
2018-05-16 13616, 2018
ruaok
thoughts?
2018-05-16 13650, 2018
UmkaDK has quit
2018-05-16 13600, 2018
UmkaDK joined the channel
2018-05-16 13639, 2018
iliekcomputers
ruaok: I'm thinking the delete user stuff and GDPR should go to production as it needs to be fast tracked. then, I'll do a merge with master.
2018-05-16 13601, 2018
ruaok
ok, sounds good.
2018-05-16 13639, 2018
ruaok
and the number of small details that we need to handle on the spotify front worries me -- let's keep working, but consider that it might not happen for our mini release for the 25th.
2018-05-16 13648, 2018
iliekcomputers
The Spotify stuff is a bigger so should probably be in master. I don't have access to Spotify so it is hard to actually test the code out.
2018-05-16 13616, 2018
ruaok
doh.
2018-05-16 13639, 2018
iliekcomputers
I'll focus on the one remaining GDPR pr till then
2018-05-16 13608, 2018
iliekcomputers
Regarding that, the logging out everyone once for GDPR seems like a good idea to me.
2018-05-16 13630, 2018
iliekcomputers
But I was wondering, for how long do we show the banner? Until the user has responded?
2018-05-16 13638, 2018
iliekcomputers
rsh7: hi, thanks for your PR on BU, I'll take a look today. Do you have plans on what other entities you want to add to BU?
2018-05-16 13619, 2018
iliekcomputers
I think we could co-ordinate with kartikeyaSh and see what entities he needs and divide work accordingly maybe
2018-05-16 13644, 2018
rsh7
hi iliekcomputers! Yeah, I am thinking to add release entity also. And I need to add more information to recording dict (in continuation to already open PR in BU).
I'm tending towards getting feature parity with current AB while using the two methods first, so try to work towards that.
2018-05-16 13622, 2018
iliekcomputers
If we only need track number and track length and we get that from recordings, then no need to get more info for now, we'll add stuff as we need it.
2018-05-16 13602, 2018
iliekcomputers
But, please take a look and see if other track info is needed in other places once.
2018-05-16 13643, 2018
CatQuest
uhm hi. cna i be exempt from the banner and the logging out? i've been following laong all the time i know aobut sutff :D
2018-05-16 13636, 2018
rsh7
iliekcomputers: okay!
2018-05-16 13616, 2018
ruaok
iliekcomputers: ok, given that you're busy the next few days, I would suggest that we simply not attack the Spotify release for the GDPR release. we're capable of doing releases fast, so lets take advantage of that.
2018-05-16 13605, 2018
github joined the channel
2018-05-16 13605, 2018
github
[listenbrainz-server] paramsingh opened pull request #410: Keep track of when a listen was inserted into influx. (production...track-inserted-time) https://git.io/vpdpV
2018-05-16 13605, 2018
github has left the channel
2018-05-16 13627, 2018
D4RK-PH0ENiX has quit
2018-05-16 13645, 2018
github joined the channel
2018-05-16 13645, 2018
github
[listenbrainz-server] paramsingh closed pull request #405: Keep track of when a listen was inserted into influx. (master...influx-track-inserted-time) https://git.io/vprva
2018-05-16 13645, 2018
github has left the channel
2018-05-16 13604, 2018
iliekcomputers
ruaok: okay, good idea. Only thing left is the notice then.
2018-05-16 13620, 2018
ruaok
oh, right notice.
2018-05-16 13628, 2018
ruaok
I was not thinking of a banner.
2018-05-16 13643, 2018
ruaok
given that we agreed to log users out, then we could display a "acknowledge GDPR" message with the "OK, I agree" tickbox next to it on the login screen. maybe add a big fat notice to make it clear.
2018-05-16 13605, 2018
ruaok
and then don't let them in until they choose ok or "take me the deletion page".
2018-05-16 13615, 2018
iliekcomputers
Ahh
2018-05-16 13620, 2018
iliekcomputers
nice
2018-05-16 13629, 2018
drsaunder has quit
2018-05-16 13657, 2018
github joined the channel
2018-05-16 13657, 2018
github
[listenbrainz-server] mayhem closed pull request #410: Keep track of when a listen was inserted into influx. (production...track-inserted-time) https://git.io/vpdpV
2018-05-16 13657, 2018
github has left the channel
2018-05-16 13647, 2018
ruaok
Leo_Verto: alastairp: we chatted about the GDPR during the board meeting yesterday and Matthew chimed in on a few things. Generally he agrees that our current actions are on the right track and have the right level of concern behind them.
2018-05-16 13610, 2018
Leo_Verto
that's good to hear :D
2018-05-16 13639, 2018
ruaok
I feel so lucky that our community has such high standards -- makes GDPR relatively easy for us.
2018-05-16 13623, 2018
Leo_Verto
I'd say the fact that MeB doesn't collects a massive amount of user data makes it also pretty easy :P
2018-05-16 13650, 2018
Leo_Verto
"Datensparsamkeit" at it's best
2018-05-16 13659, 2018
ruaok
exactly. the high standards have always made it clear that we should not collect too much data.
2018-05-16 13624, 2018
ruaok
ein sehr deutsches wort....
2018-05-16 13648, 2018
Leo_Verto
"data economy" ist halt einfach nicht ausdrucksstark genug
2018-05-16 13622, 2018
ruaok
stimmmt
2018-05-16 13641, 2018
D4RK-PH0ENiX joined the channel
2018-05-16 13649, 2018
ruaok
what do people think about adopting a policy that does not use gendered speech in our code?
2018-05-16 13619, 2018
ruaok
I'm not picking on iliekcomputers, but seeing this code made me think about it:
they have a webhooks system, where they will ping you (as a website which uses oauth) if the user changes their consent for medical data (heart rate) or deletes their account
2018-05-16 13628, 2018
ruaok
great. that is generally a great trend -- and also the same method we use for deleting MB accounts
2018-05-16 13642, 2018
Leo__Verto joined the channel
2018-05-16 13610, 2018
Leo__Verto
I suppose iliekcomputers is following the approach of just alternating pronouns? I wonder, is that more common in academia than using singular they? I've seen it in quite a few papers
2018-05-16 13612, 2018
ruaok
likely. but with code things can get wonked out on the balance of he vs she. that can lead to a clear bias, which can be... troublesome. we can avoid all of this by using non-gendered speech.
2018-05-16 13648, 2018
Leo__Verto has quit
2018-05-16 13641, 2018
ferbncode has quit
2018-05-16 13641, 2018
akhilesh has quit
2018-05-16 13657, 2018
darkhorse has quit
2018-05-16 13615, 2018
rsh7 has quit
2018-05-16 13622, 2018
iliekcom- has quit
2018-05-16 13651, 2018
iliekcom- joined the channel
2018-05-16 13635, 2018
ferbncode joined the channel
2018-05-16 13641, 2018
UmkaDK
Guys, I'm trying to port the latest production build to our infrastructure. All is working well apart from the renderer. For some reason the renderer is trying to load common.css instead of common-ae6d8d9ce7.css
