People up: Freso, reosarevok, bitmap, zas, ruaok, yvanzo, iliekcomputers, Mr_Monkey, CatQuest – anyone else, please let me know explicitly ASAP.
2018-11-26 33016, 2018
Freso
We start off in .ee, reo go!
2018-11-26 33016, 2018
Freso
reosarevok says:
2018-11-26 33016, 2018
Freso
"""
2018-11-26 33016, 2018
Freso
This week I worked a bit more on converting RG pages to React and on MBS-9899. The former is waiting for some bitmap code to get merged first, but otherwise hopefully ready for review, and the latter I'm still finishing.
2018-11-26 33016, 2018
Freso
Additionally, I started porting reports to React as a thing to do while waiting for feedback on more important bits, have converted all up to label reports, but that means there are quite a few left still.
2018-11-26 33016, 2018
Freso
Other than that, I dealt with a few GCI tasks and quite a few support emails and did a fair amount of editing, as usual.
I made more progress on pr #737 for the the React relationships display. discovered some more bugs in the relationship editor changes while testing things, and fixed them
2018-11-26 33048, 2018
bitmap
fixed all the test failures except one I'm working on rn, then it should be done, I hope...
2018-11-26 33050, 2018
CatQuest
🍻
2018-11-26 33024, 2018
bitmap
did some code review but wasn't very productive at the end of the week, since it was thanskgiving and I was with family for a few days
2018-11-26 33008, 2018
bitmap
not much else to mention I think, so fin... iliekcomputers?
2018-11-26 33022, 2018
iliekcomputers
hi!
2018-11-26 33029, 2018
Freso
(People still up: Freso, ruaok, Mr_Monkey, CatQuest – anyone else, please let me know explicitly ASAP.)
2018-11-26 33000, 2018
iliekcomputers
Let's see, fixed a bunch of bugs that Sentry uncovered in ListenBrainz's RabbitMQ setup.
2018-11-26 33011, 2018
iliekcomputers
of course, those fixes uncovered more bugs =)
2018-11-26 33020, 2018
iliekcomputers
I was just working on them right now.
2018-11-26 33052, 2018
iliekcomputers
other than that, I created a local dev docker environment for `listenbrainz-recommendation-playground`.
2018-11-26 33009, 2018
iliekcomputers
and started some work on writing listens from ListenBrainz to our spark cluster.
2018-11-26 33037, 2018
iliekcomputers
Other than that, we moved labs.acousticbrainz.org to our infrastructure, so MeB hosts it now.
2018-11-26 33049, 2018
iliekcomputers
fin.
2018-11-26 33055, 2018
iliekcomputers
ruaok: go
2018-11-26 33000, 2018
ruaok
k
2018-11-26 33020, 2018
ruaok
I did more planning on LB and helping with labs.
2018-11-26 33044, 2018
ruaok
I've also started doing some tidying of internal papers and also keeping up on reviews and contracts.
2018-11-26 33007, 2018
ruaok
before the end of the year I hope to catch up on some year end reports -- those tend to drag out far too long. :(
2018-11-26 33034, 2018
ruaok
but I'm excited that the business world is slowing down a bit with anticipation of the holidays. that gives me more time to tinker with LB and the likes.
2018-11-26 33040, 2018
ruaok
fin. Mr_Monkey!
2018-11-26 33045, 2018
Mr_Monkey
Hello !
2018-11-26 33021, 2018
Mr_Monkey
Last week I enjoyed mentoring more GCI tasks, continued testing and finally merged my search page improvements PR now ready to be deployed, and fixed an issue with the entity deduplication feature reported by CatQuest.
2018-11-26 33024, 2018
Freso
(Only myself and CatQuest left for reviews. Last call to get in on the fun! :))
2018-11-26 33055, 2018
Mr_Monkey
Like the week before, I also continued work on the entity merging tool, the ongoing schema changes and entity renaming, and our Docker setup and files.
2018-11-26 33033, 2018
bukwurm joined the channel
2018-11-26 33049, 2018
Mr_Monkey
That's it for me! Freso ?
2018-11-26 33052, 2018
Freso
🙋
2018-11-26 33003, 2018
Freso
A bunch of GCI, filed MBH-504 on behalf of zas, reviewed and published iliekcomputers' AB blog post.
Is there any update about this? How long may it take to get an answer? Should we do something about it?
2018-11-26 33038, 2018
CatQuest
erh IA
2018-11-26 33019, 2018
yvanzo
CatQuest: it is IA internals.
2018-11-26 33020, 2018
ruaok
is there a way to report this issue? and to whom? google?
2018-11-26 33036, 2018
yvanzo
reosarevok already contacted IA, zas and others interacted with Google transparency report.
2018-11-26 33047, 2018
ruaok
ah, ok.
2018-11-26 33055, 2018
ruaok
hmmm. not sure what else to do.
2018-11-26 33013, 2018
Freso
One thing we could as a hotfix is to remove the "recent covers" from the frontpage.
2018-11-26 33020, 2018
Freso
I think that one is causing the most flags.
2018-11-26 33029, 2018
Mr_Monkey
I was seeing the warnings about two weeks ago, but not since.
2018-11-26 33029, 2018
yvanzo
The main issue to me is about the homepage. Should we temporarily disable CAA images on the homepage for Chrome users?
2018-11-26 33045, 2018
ruaok
I'm ok with that.
2018-11-26 33053, 2018
Freso
(Because it loads so many different ones at once, so there's proportionally bigger chance that it hits a flagged server.)
2018-11-26 33055, 2018
ruaok
this should serve as an impetus for us to improve that page.
2018-11-26 33012, 2018
CatQuest
oh only for chrome users? ok, +1 to that
2018-11-26 33034, 2018
Freso
So resolution:
2018-11-26 33053, 2018
bitmap
at what point would we know it's ok to re-enable them?
2018-11-26 33005, 2018
Freso
Hotfix not showing CAA images (on front page or all of mb.o?) for Chrome-based users, and follow up with IA and Google about progress?
2018-11-26 33012, 2018
ruaok
bitmap: good question. when someone whines? :)
2018-11-26 33020, 2018
CatQuest
whne google/ia tell us problme is solved?
2018-11-26 33026, 2018
yvanzo
reosarevok is the most knowledgeable…
2018-11-26 33029, 2018
CatQuest
or that, yes
2018-11-26 33057, 2018
CatQuest
I'd ay only on front page for now
2018-11-26 33016, 2018
Freso
bitmap: Could be "until further notice" or until we launch site/UX overhaul which will probably have a new front page.
2018-11-26 33020, 2018
bitmap
there doesn't seem to be any indication that google will solve this, but who knows
2018-11-26 33036, 2018
CatQuest
Freso: that seems to be a fine solution
2018-11-26 33056, 2018
Freso
(If problem still exists then, we can see what we'll do about it at that point. That's still some months away at the very least though.)
2018-11-26 33008, 2018
rdswift
Should the notice have a short explanation of the problem / reason?
2018-11-26 33012, 2018
CatQuest
eh. a bit more thna a few
2018-11-26 33022, 2018
CatQuest
jup, deff
2018-11-26 33028, 2018
CatQuest
possibly a blogpost
2018-11-26 33058, 2018
reosarevok
Put something down there that says "We can't show you covers because Google is being stupid"
2018-11-26 33005, 2018
reosarevok
On Chrome. Only more nicely written
2018-11-26 33006, 2018
CatQuest
:D
2018-11-26 33021, 2018
bitmap
also, if we remove them it'd be hard to tell when it's working again. but it might be the best option for now...
2018-11-26 33029, 2018
Freso
I can try and write up an announcement blog post for when the hotfix is ready to go live.
2018-11-26 33053, 2018
Freso
bitmap: If we only remove them from the front page, people will still intermittently run into issues on release etc. pages.
2018-11-26 33021, 2018
bitmap
alright
2018-11-26 33042, 2018
rdswift
Freso, that could be explained in the notice.
2018-11-26 33055, 2018
reosarevok
I don't like the idea but if there's no chance Google does shit all, it's probably the least bad thing
2018-11-26 33059, 2018
Freso
rdswift: I will write about that in the post.
2018-11-26 33046, 2018
Freso
So, 2nd attempt at resolution:
2018-11-26 33047, 2018
yvanzo
reosarevok: Any update from your IA contacts? Would be nice to support their requests to Safe Browsing somehow.
2018-11-26 33024, 2018
Freso
1) We make a hotfix for mb.o front page and replace "recent covers" with a note that says that we don't currently show them to Chrome users.
2018-11-26 33049, 2018
Freso
2) We(/I) write a blog post with more details and background so people know what's up.
2018-11-26 33005, 2018
CatQuest
and a link to the blopost in the note on the frontpage too i say
2018-11-26 33013, 2018
Freso
3) We monitor the situation of people running into them on release etc. pages as well as try to follow up with IA and Google.
2018-11-26 33015, 2018
Freso
Sounds good?
2018-11-26 33036, 2018
reosarevok
yvanzo: nothing at the moment
2018-11-26 33036, 2018
yvanzo nods
2018-11-26 33038, 2018
bitmap
sure
2018-11-26 33040, 2018
ruaok has no issues
2018-11-26 33045, 2018
Mr_Monkey
:+1::skin-tone-3:
2018-11-26 33057, 2018
CatQuest
else in 3-4 weeks we are gonna get people on chrome making tickets and comments ala "i nat see covers on the front page, it says there problem, what is it"
2018-11-26 33014, 2018
CatQuest
so ye +1
2018-11-26 33020, 2018
reosarevok
The way they spoke about it was basically "Google doesn't tell us shit about what is causing the info so we can't fix much"
2018-11-26 33025, 2018
Freso
Alright.
2018-11-26 33031, 2018
Freso
Let's conclude the meeting on that note then.
2018-11-26 33033, 2018
rdswift agrees with the proposed resolution.
2018-11-26 33037, 2018
Freso
Thanks for your time everyone. :)
2018-11-26 33039, 2018
Freso
</BANG>
2018-11-26 33015, 2018
yvanzo
reosarevok: Would massively reporting error to Safe Browsing help?
