#metabrainz

monkey: before I forget, and I will bring it up tomorrow, akshaaatt made some good points about how we’ve named stuff in LB. I would be in favour of renaming ‘profile’ in the sidebar to dashboard, and ‘dashboard’ in the secondary nav to ‘profile’

aerozol: :P

monkey: for the top listeners of this album, that should be based on release groups too?

I think so, lucifer

makes sense 👍

Yes

I think in general you've started a migration to RGs across LB, as the representation of "the album" which is how we choose to represent it on the website

Unless we specifically need to differentiate between releases, the answer is probably always going to be RGs > releases

yvanzo: mayhem: any dislikes about the last version here? MBH-542. If not, I will start the journey of making the final files, then nagging mayhem to update the wiki files again (sorry!! hope you can remember how), and rustling up whoever can update Discourse and Jira

MBH-542: Replace wiki favicon with updated MB logo https://tickets.metabrainz.org/browse/MBH-542

aerozol: No, thanks.

mayhem: If you remember (or not) how ^ but don't want to spend time with this, just drop me a line; I now have access to the wiki instance and it's documented in our sysadmin stuff.

mayhem, monkey, aerozol: not sure if this has come up before but how about adding a YIM-like share button to pin, review and recommend a recording modals.

lucifer: yes, more share buttons!

yvanzo: yes, please do take care of that. I remember how, but I have loads of other (stupid) stuff on.

aerozol: all good with those versions, looking good.

[musicbrainz-server] 14reosarevok merged pull request #2679 (03master…MBS-12658): MBS-12658: Convert user ratings summary to React https://github.com/metabrainz/musicbrainz-serve...

np

mayhem: The page with the funny donation prompt I was talking about: https://react.gg/visualized#more

(scroll to the very bottom of the page)

cute.

the hard sell is a bit passive aggressive for my taste, but ok.

I like that the intermediate sell is "Drop your email below or you and your entire family tree will be cursed 🫶."

I actually like the hard sell more than the "help us blah blah" stuff Wikipedia and the like have, but of course it doesn't scale great for multi-person companies :D

gah. pr LB#2453 is a BEAST!

LB-1042: Add release group entity stats: https://github.com/metabrainz/listenbrainz-serv...

I'll continue on that tomorrow.

reosarevok: so, about the data-sets page...

as you recall, the board suggested that we should put all of our data behind a soft-sign-up-wall.

which on the surface is a quick and easy thing to do and then when you dig deeper, it gets hairy fast.

first: Our FTP sites are not hard to find, so we can't really go "hide" them. (we could, but is not our speed)

which then means that we need to be a sincere about what we're doing.

second: what about musicbrainz-docker that does the automatic downloading?

third: our doc pages are all over the place when it comes to linking to our download sites.

The doc pages we should just fix, those are a mess anyway

yes, those are a bulk of the work, I think.

and this is where I could use help from the MB team, but I am painfully aware of the upcoming schema change.

If someone then shares the link, so what

agreed.

As we said, the goal is not to get everyone, but to get most people to know and care

yep.

The docker question... that I don't know

lets stick to the docs for sec...

At the very least, if we change nothing, then we should have the docker README mention "hey, could you sign up here? it'd be helpful"

Ok, docs :)

docs pages lead to the dataset pages on meb, which then requests users to sign-up and the data sets page, post sign-up or post sign up skipping then links to FTP?

Yes

I think so

ok, that makes sense to me.

We can have anchors on the dataset pages if we want to go straight from doc page to the appropriate section for the dataset sign up

yep.

how about getting those pages updated?

do you have time to work on that considering the schema change is coming?

(about what I would expect from universal)

Probably, yes

great, that would be of immense help to me.

then I can focus on the meb.org work.

I think for the musicbrainz-docker side of things we could so something simple like:

in the beginning of the process show some text: "By using musicbrainz-docker you acknowledge that you should support or project. Before proceeding, please sign-up with us here: [link]."

and then two buttons: "[ I signed up] [I lied about signing up]"

yvanzo: ^^

mayhem: we still need to talk to bitmap about potentially splitting the JSON dumps, btw (that probably requires at least a test run with a split to see if it takes even longer than the absurdly long pretty-much-a-full-day it already does with one dump)

yep. we're all around now, so when the three of us are present lets do that.

reosarevok: do you think you could get the doc revamps done by the end of next week?

Yes, I don't think that'd be too problematic

The JSON thing, that's more questionable

(if it works well at first test, then probably, if not, then probably not)

I think the JSON fix should be left for post schema change.

but please carry out the doc work before the end of next week.

Ok, I'll make myself a ticket and check the docs that need updating

thank you!

I'll chat with yvanzo about the mb-docker bits.

When do we do the same for the API? :p

when we have API keys?

Does http://ftp.musicbrainz.org/pub/musicbrainz/genp... still make sense to keep, really? :D

(checking mentions of FTP in our docs)

lolno

(that's linked from https://musicbrainz.org/doc/Fingerprinting#PUID)

https://musicbrainz.org/doc/Changed_MBID_Feed "Status: In May, 2016 this service became unavailable. Plans to resume it are being discussed (as of March 2017)."

I have no memory of any of that, I'm going to assume we don't currently provide this and are not planning to or?

both super old. nuke with prejuidice

Dunno if there's more stuff in http://ftp.musicbrainz.org/pub/musicbrainz/ that is no longer needed

I'd suggest nuking data.classic , but people will shoot me I am sure.

In any case, I expect other projects are still linking to the FTP server since that includes tons of other stuff

But I can change https://musicbrainz.org/doc/MusicBrainz_Databas... and https://musicbrainz.org/doc/Development/JSON_Da... at least

let me clean up some things.

ha, mbtagger from 2003!!!

reosarevok: how about ngs/orpheus ?

https://tickets.metabrainz.org/browse/MBS-13033 that seem right to you, mayhem?

MBS-13033: Point to Datasets page for dump downloads rather than FTP

I don't remember what ngs/orpheus is

BBC orhpheus.

uh, I read in the newspaper that some parts of chatgps-4 had accived some kind of level of intelligence and that actually interests me

like it could use uh idk how to translate from norwegian but "sunn fornuft" like "reason" and logic and like human levels of figuring out ideas

that was weird

I hope we skip decades of AI being usefull slave bots and go directly to artificials being peopel in their own rights. beause that'll skip a lot of annoying and horrible stuff

:D

:D :D

aerozol: check figma

i found updated version of the icons library

theres also a figma plugin for that

RemixIcons

mayhem: I expect it's not needed? We could archive the copy somewhere local and take it off ftp

bitmap: we still need to look at how to do the JSON dumps stuff, but mayhem suggested maybe it should be a post-schema-change project :)

I'm ok with that - we could then combine it with looking into making it faster anyway, which was already in the plan

seems like a good plan.

monkey: ended up not talking today, what about tomorrow?

I should be around most of the day

(off for a couple hours maybe around 10-12 or so your time since I'm getting a tick-borne encephalitis vaccine refresher)