#metabrainz

/

      • mayhem
        and today I descended into accounting hell working out the finances from the last quarter and paying people.
      • I'm quite curious to get our half way through the year report card and see how it stacks up to the plans made in january.
      • fin. Arsh, go!
      • arsh
        Hi everyone
      • Last week I continued progress on my GSOC project for artist similarity graph
      • Made small adjustments to achieve the right balance of things
      • Most of time went into fixing the scaling function for the graph and setting up the colors for the same
      • Overall I am happy to learn many new things
      • thats it from my side
      • go jasje:
      • jasje
        hello everyone
      • just finished phase 1 of my gsoc project yesterday
      • reosarevok
        Still on my list today: akshaaatt, riksucks, ShivamAwasthi, vscode, pixelpenguin
      • jasje
        trying to brush up any remaining edges or any better ways to route state
      • also practicing my xml skills again
      • thats it for me
      • akshaaatt: go
      • akshaaatt
        Hi Everyone!
      • I did the usual PR reviews and thought about a few things
      • Other than that, my head has been spinning for the last week for so with the amount of continuous learning and management of things.
      • Or*
      • That’s pretty much it for now. Go pixelpenguin !
      • jasje
        +1
      • pixelpenguin
        HI Everyone
      • I am inching closer towards trying to make progress before the mid term evaluation
      • I tested the implemented query changes in data set hostler repo this week i.e Converting models in queries to pydantic type. With that I also migrated one of the api query in listen brainz repo, most of the api's left in it which should follow the same pattern.
      • That's it from my side, vscode_ please go
      • vscode_
        Hell everyone!
      • hello*
      • I continued working on Apple Music integration
      • I have fixed the preview playing issue and addressed to most of the comments on PR
      • facing some issues with refresh token
      • as apple does not provide them
      • but I was looking at the chat and saw the doc by Lucifer
      • hopefully we will be able to overcome that
      • still working on error handelling and stuff
      • that's it from my side
      • shivamAwasthi:
      • go
      • ShivamAwasthi
        hi
      • last week I worked on creating middleware for privilege-based access to routes
      • I also started writing tests for the same, but wasn't able to make as much progress as I wanted to because I went on a mini-trip with family.
      • This week, I aim to finish writing tests for these routes, as well as complete the work on Admin Logs page.
      • that's it for me! riksucks: go!
      • TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | BookBrainz: #bookbrainz | Channel is logged; see https://musicbrainz.org/doc/IRC for details | Agenda: Reviews, MBS-13146: reCAPTCHA (yvanzo), ORG-51: Google Fonts (ruaok), LLM policy (aerozol/reo)
      • reosarevok
        Let's wait a minute or two for riksucks and move on otherwise :)
      • riksucks
        Hi!
      • Nothing much to update, reviewed vscode_'s PR and working closely with him for shipping it
      • Fin.
      • reosarevok
        Thanks all for the reviews!
      • yvanzo: MBS-13146 ?
      • BrainzBot
        MBS-13146: Registration form may not conform to the GDPR https://tickets.metabrainz.org/browse/MBS-13146
      • yvanzo
        Our current use of reCAPTCHA in MB has been questioned with respect to the GDPR.
      • Basically alternatives are cookie-free captchas, honey pot, nonce, and form delay.
      • These can be used together too.
      • mayhem
        I can't say the last three are clear to me.
      • yvanzo
        I don’t really have any question now I made some research about those.
      • Is it alright to move away from reCAPTCHA?
      • Extra question: Should we move away from captcha at the same time?
      • reosarevok
        I don't think we have any reasons to want to stick with recaptcha if we can move away
      • yvanzo
        You have 1.5 minutes.
      • mayhem
        I would prefer we moved away from anything that people might consider a privacy issue. within reason.
      • reosarevok
        I have no idea what any other options than a captcha look like
      • monkey
        Agreed
      • reosarevok
        (and as mayhem said, the names don't say too much)
      • mayhem
        because, if its a privacy issue, it will keep coming up and taking our time.
      • reosarevok
        Would it be possible to have a small explanation of each type and examples for next meeting?
      • mayhem
        so, lets rip the bandaid off and move away from recpachate and (forshadowing) google fonts non self hosted.
      • yvanzo
        mayhem: the captcha alternatives are more respectful of privacy and more accessible too.
      • mayhem
        reosarevok: +1
      • yvanzo
        The issue with reCAPTCHA was that the cookie was both a security feature AND a marketing feature.
      • mayhem
        sneaky as ever.
      • reosarevok
        The other captcha yvanzo shared in the ticket is supposed to set no cookies *and* have some sort of plan for nonprofits
      • Pratha-Fish
        hey reosarevok available for a few minutes? :D
      • zas
        If we can use alternatives, I don't see any reason to stick to recaptcha
      • reosarevok
        We could ask for how that works
      • Pratha-Fish: after the meeting, yes :)
      • (still going)
      • ApeKattQuest
        as long as i don't have to slect bridges, that stud¨ff is annoyng and SIHT
      • mayhem
        I think it would be good to research further and even point out plausible examples of each.
      • Pratha-Fish
        reosarevok: oops. didn't realize. Can you please ping me once done
      • yvanzo
        I mentioned in comments two alternative captchas to look into.
      • ApeKattQuest
        as long as i don't have to select bridges, that stuff is annoying and SHIT
      • mayhem
        so that we could have a look.
      • reosarevok
        ApeKattQuest: don't burn your bridges
      • ApeKattQuest
        la
      • yvanzo
        We can also drop captchas but for doubtful (greylisted) IP blocks (hosting providers...).
      • mayhem
        well, identifying shit has always been about training AI, so yes, please lets move away
      • reosarevok
        yvanzo: yeah, the captcha alternates are already there :) If you could explain a bit the non-captcha options (if you feel they are good) we could discuss them better (either today or next time)
      • mayhem
        next meeting. we have a lot more on today.
      • reosarevok
        Easiest probably to expand on non-captcha ones (are they worse than captcha?)
      • And email the legit captcha guys asking for pricing for non-profits
      • ApeKattQuest
        +1
      • yvanzo
        reosarevok: "explanation of each type" of techniques (beyond captcha)?
      • reosarevok
        Yes, and why they're better or worse
      • mayhem
        yep, at everything reosarevok says
      • reosarevok
        (short thing, anyway, to get a small idea, no need for an essay)
      • yvanzo
        They do not require any third-party.
      • It will become technical then.
      • mayhem
        even better.
      • we're good with technical. :)
      • reosarevok
        Well, some of you are :p But yes
      • yvanzo
        Right but it doesn't really require everyone then.
      • reosarevok
        I think we're all in agreement we can get rid of recaptcha, anyway
      • ApeKattQuest
        +11
      • mayhem
        I've heard no dissent.
      • yvanzo
        OK, I will approach MTCaptcha about their plans for non-profit reosarevok mentioned.
      • reosarevok
        Next step can be a meeting talk or an implementation detail in MBS, but I expect we'll want at least lucifer and mayhem in this talk too
      • Since we're planning to move the stuff to MeB anyway
      • yvanzo
        Otherwise, for other techniques it’s mostly down to code review.
      • mayhem
        good plan.
      • reosarevok
        yvanzo: thanks! :) Any more questions today or should we move on for now?
      • yvanzo
        By the way, we already have CSP nonce since 2020.
      • Yes, please :)
      • reosarevok
        mayhem: ORG-51!
      • BrainzBot
        ORG-51: Review Google Fonts usage in context of GDPR https://tickets.metabrainz.org/browse/ORG-51
      • mayhem
        Google Fonts is basically the same sort of question: Google hosted Google Fonts are basically a GDPR violation.
      • so, can anyone see a reason why we should not self host the google fonts our projects use?
      • ApeKattQuest
        we should.. host thme ourselves?
      • no problem from me
      • monkey
        👍
      • mayhem
        I see no bandwith issues. we have staticbrainz.
      • reosarevok
        Is that allowed by the Google ToS?
      • If yes, go for it?
      • I don't know what the conditions are :)
      • ApeKattQuest
      • mayhem
        I'll check, but i believe so.
      • reosarevok
        (I assume automatically if Google made it they want ad money, but :D )
      • mayhem
        ok, I'll double check and then open tickets for the various projects.
      • reosarevok
        (maybe it's fully open)
      • mayhem
        monkey: does BB use GF?
      • reosarevok
        +1
      • monkey
        Yes
      • mayhem
        I think everyone does. ok, everyone gets a ticket.
      • back to you reosarevok
      • ApeKattQuest
        you get a tikcet and you get a ticket!
      • reosarevok
        Yay, tickets
      • Ok, last bit for the day!
      • mayhem gro
      • mayhem
        not even worth a whole groan
      • reosarevok
        LLM policy (2)
      • aerozol sent me a summary:
      • '''
      • The community feedback is all collected at: https://community.metabrainz.org/t/llm-ai-code-...
      • ApeKattQuest
        a): why have we started calling AI bots LLMS
      • reosarevok
        UltimateRiff posted a very useful poll, which had 22 responses: 63%: A, Allow no LLM, 27%: B, Allow some LLM, 9%: C, Allow all LLM
      • There was some interesting discussion, but the poll should be enough to deduce the feeling of the community.
      • The community shared no substantial feedback re. whether we address this in the MeB Code of Conduct, or on a per-project basis (one comment in favour of MeB-wide/CoC).
      • The goals of this (final?) LLM meeting topic should be to pick one of the options (A, B or C), and to raise any comments that you want taken into account re. guideline wording.