#metabrainz

yvanzo: Yes, that is exactly what I like to accomplish. But the trained file by Leo_Verto is not present to work on or I didn't find it so far....

Yes, this is why a trainer must be made first.

I can provide the trained model, it might make sense to re-train it on newer spam though.

When Leo_Verto worked on it, he had direct access to privated data. It simplified development, but it also made it difficult ot fully open source it.

We want to avoid this by making everything that is necessary to train a model, but the private data, thus the needed dummy data.

The trainer must be deployed on MeB servers along with the MB DB, so it will have access to private data.

Yes, that is my intention too :) but the model if trained on dummy data would have a very bad foundation from the beggining, unless the dummy data is highly accurate to the real spam.

this brings to my other issue: What I found is that, the data that we keep through online learning is minimal relative to the data the model is trained on. This might not help change the model perception anytime soon. To change this, I want to retrain the model every week/month with new editor data. For this to happen, first we have to send the data for the model to test, send it back to SpamNinja, let them

classify the SB result. Store them back and train the model based on final review.

yvanzo: did I get it correctly in the Muziekweb email that we should also change the cleanup to standardize to .nl?

reosarevok: yup, I think so

Ok

reosarevok: and probably remove language too.

We already do, it seems

diru1100: let's have something based on dummy data that can be retrained with dummy feedback first :)

We can reboot from a rightful model after that, does it make sense?

yes, you want to test out the whole process with dummy data everywhere, first?.

yes :)

reosarevok: could you rebase https://github.com/metabrainz/musicbrainz-serve... when you have a moment ('cause it's still referencing musicbrainz_collate so breaking for me)

Sure

Gimme a sec

ok sure, I can use dummy data and do it np. Which approach do you want me to follow for updating the model? the online learning one or retrain every week/month one? or shall we test both of those as well?

diru1100: online learning at least, both if you feel it could be worth it :)

and if you want to do both, start with the simplest one, so something can be tested sooner.

I think the problem with online learning is that the email and website tokenizers will need to be recreated once in a while to include new spam domains. This automatically invalidates all previously trained models.

bitmap: rebased

thx

Guess I should be rebasing pretty much everything really!

[musicbrainz-server] reosarevok merged pull request #1522 (master…MBS-10839): MBS-10839: Add merge button to recording list in artist overview https://github.com/metabrainz/musicbrainz-serve...

MBS-10839: "Add selected recordings for merging" missing in standalone-only overview https://tickets.metabrainz.org/browse/MBS-10839

[musicbrainz-server] reosarevok merged pull request #1519 (master…MBS-10834): MBS-10834: Account flag to disable writing edit notes https://github.com/metabrainz/musicbrainz-serve...

MBS-10834: New account flag for disabling ability to write edit notes https://tickets.metabrainz.org/browse/MBS-10834

yvanzo: I think I can complete the phase 1 with just dummy data and it doesn't involve any updation methods. I will research which way is better till then and we can go with that?

works for me!

Cool :)

:)

ruaok: Added GET API endpoints too to the PR

ruaok: Mr_Monkey's listens couldn't be reached after 3 pages because of this check. 3 week data is missing but window is 15 days.

yeah, fixing two tests and adding buttons prompting the user to reload with a longer range are the two things left to do.

[musicbrainz-server] reosarevok opened pull request #1530 (master…MBS-10849): MBS-10849: Check for allowNew on AddReleaseGroup https://github.com/metabrainz/musicbrainz-serve...

MBS-10849: Add release group preview on RE shows "This entity has been removed" https://tickets.metabrainz.org/browse/MBS-10849

shivam-kapila: I trust your react skills are better than mine, right? mine are non-existent...

I know react. Can't rate it though.

well, if you're up for helping, we need to add a button...

that gives the user the option to "look harder" for listens.

Hm. I can do that.

ok, in the react props I will pass a new value called "try_harder" (boolean).

if true, show text and a button at the bottom of the listens in the center

"We could not find any more listen, but there may be more."

[ try harder ]

try harder should load the page with the same parameters, but with try_harder=1 as an extra argument.

does that make sense?

Yeah

I will get this done

<3

yvanzo: would like to deploy https://github.com/metabrainz/musicbrainz-serve... today so we don't have to babysit the cron container tonight & over the weekend

bitmap: reviewed

[musicbrainz-server] mwiencek merged pull request #1528 (production…slow-reports): Prevent two statement timeouts in reports https://github.com/metabrainz/musicbrainz-serve...

shivam-kapila: timescale-rebased-again is pushed -- something is making the connection to the db blow up during the integration tests. maybe you have a moment to look at it -- I suspect i'll be afk all day tomorrow.

bitmap, yvanzo: it seems container mb website on ludwig is misbehaving. Can you have a look?

See https://stats.metabrainz.org/d/000000076/mbs-pe...

bitmap, yvanzo: around?

ok, I'll just restart it, logs don't help at all (zilions of "Can't use an undefined value as a subroutine reference at /home/musicbrainz/carton-local/lib/perl5/Plack/Util.pm line 14")

I also restarted the ws container on ludwig, everything is back to normal now, not sure what happened (but it seems both containers were affected)

zas: The Picard docs refer to the following as basic tags, but I haven't yet found a release that will produce them. Do you know if they are still valid, or have they been deprecated? musicbrainz_originalalbumid, musicbrainz_originalartistid, musicbrainz_releasetrackid, originalalbum, originalartist