#metabrainz

sorry for all the picard dev spam :p

dev spam is best spam =)

[picard-plugins] phw opened pull request #184: Work & Movement (2.0...workandmovement) https://git.io/fpuuC

reosarevok: Ping?

<BANG>

It's Monday! In fact, it's

Hah :)

People up: Freso, reosarevok, bitmap, zas, ruaok, yvanzo, iliekcomputers, Mr_Monkey, CatQuest – anyone else, please let me know explicitly ASAP.

We start off in .ee, reo go!

reosarevok says:

"""

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.

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.

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.

MBS-9899: Recording and recording artist tags/genres missing in JSON WS https://tickets.metabrainz.org/browse/MBS-9899

"""

zas: Go!

zas says:

"""

This week, I fixed few more issues related to discourse upgrade.

Also deployed a bunch of system upgrades on almost all servers.

I went through options we have for backups.

Picard PRs reviews, we plan to release 2.1.0 before end of December.

"""

yvanzo: Go!

Hi!

Merged more contributions by GCI students, thanks to them! Added more tasks in return, thanks to Freso!

Pursued converting MB user stuff to React, got stuck with autocompletion in hydrated React component.

Took a look at PgBarman documentation. Plus usual PRs and tickets review, support, and so on.

Finito, bitmap?

hey

what is PgBarman?

It is for backups :)

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

fixed all the test failures except one I'm working on rn, then it should be done, I hope...

🍻

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

not much else to mention I think, so fin... iliekcomputers?

hi!

(People still up: Freso, ruaok, Mr_Monkey, CatQuest – anyone else, please let me know explicitly ASAP.)

Let's see, fixed a bunch of bugs that Sentry uncovered in ListenBrainz's RabbitMQ setup.

of course, those fixes uncovered more bugs =)

I was just working on them right now.

other than that, I created a local dev docker environment for `listenbrainz-recommendation-playground`.

and started some work on writing listens from ListenBrainz to our spark cluster.

Other than that, we moved labs.acousticbrainz.org to our infrastructure, so MeB hosts it now.

fin.

ruaok: go

k

I did more planning on LB and helping with labs.

I've also started doing some tidying of internal papers and also keeping up on reviews and contracts.

before the end of the year I hope to catch up on some year end reports -- those tend to drag out far too long. :(

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.

fin. Mr_Monkey!

Hello !

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.

(Only myself and CatQuest left for reviews. Last call to get in on the fun! :))

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.

That's it for me! Freso ?

🙋

A bunch of GCI, filed MBH-504 on behalf of zas, reviewed and published iliekcomputers' AB blog post.

MBH-504: Switch to using native Let's Encrypt Discourse setup https://tickets.metabrainz.org/browse/MBH-504

I enabled tag filtering from the front page of the forums this week too, after a request from the users.

Seems to work pretty nicely.

Other than that, being around and about, handling flags and reports, etc.

fin.

CatQuest!

Still working on tasks and tickets.

that's it. fin.

Oh hey! Happy belated birthday Freso !

Alright. No more people on my list of reviewers.

yvanzo added a last-minute agenda item, so…

yvanzo: Chrome phishing warning!

Ok!

oh shi, that thing

It is about the security warning issued by Chrome (and other browsers using Safe Browsing service) about musicbrainz.org.

More specifically, it issues a warning for cover art images hosted on some Internet Archive servers.

The topic is two weeks old already at https://community.metabrainz.org/t/phishing-war...

do we know *which* IE server exactly

Is there any update about this? How long may it take to get an answer? Should we do something about it?

erh IA

CatQuest: it is IA internals.

is there a way to report this issue? and to whom? google?

reosarevok already contacted IA, zas and others interacted with Google transparency report.

ah, ok.

hmmm. not sure what else to do.

One thing we could as a hotfix is to remove the "recent covers" from the frontpage.

I think that one is causing the most flags.

I was seeing the warnings about two weeks ago, but not since.

The main issue to me is about the homepage. Should we temporarily disable CAA images on the homepage for Chrome users?

I'm ok with that.

(Because it loads so many different ones at once, so there's proportionally bigger chance that it hits a flagged server.)

this should serve as an impetus for us to improve that page.

oh only for chrome users? ok, +1 to that

So resolution:

at what point would we know it's ok to re-enable them?

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?

bitmap: good question. when someone whines? :)

whne google/ia tell us problme is solved?

reosarevok is the most knowledgeable…

or that, yes

I'd ay only on front page for now

bitmap: Could be "until further notice" or until we launch site/UX overhaul which will probably have a new front page.

there doesn't seem to be any indication that google will solve this, but who knows

Freso: that seems to be a fine solution

(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.)

Should the notice have a short explanation of the problem / reason?

eh. a bit more thna a few

jup, deff

possibly a blogpost

Put something down there that says "We can't show you covers because Google is being stupid"

On Chrome. Only more nicely written

:D

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...

I can try and write up an announcement blog post for when the hotfix is ready to go live.

bitmap: If we only remove them from the front page, people will still intermittently run into issues on release etc. pages.

alright

Freso, that could be explained in the notice.

I don't like the idea but if there's no chance Google does shit all, it's probably the least bad thing

rdswift: I will write about that in the post.

So, 2nd attempt at resolution:

reosarevok: Any update from your IA contacts? Would be nice to support their requests to Safe Browsing somehow.

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.

2) We(/I) write a blog post with more details and background so people know what's up.

and a link to the blopost in the note on the frontpage too i say

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.

Sounds good?

sure

:+1::skin-tone-3:

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"

so ye +1

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"

Alright.

Let's conclude the meeting on that note then.

Thanks for your time everyone. :)

</BANG>

reosarevok: Would massively reporting error to Safe Browsing help?

thank you freso!