[listenbrainz-android] 14dependabot[bot] opened pull request #619 (03dev…dependabot/gradle/dev/androidGradlePlugin-8.13.1): Bump androidGradlePlugin from 8.5.2 to 8.13.1 https://github.com/metabrainz/listenbrainz-androi…
2025-11-19 32352, 2025
_BrainzGit
[listenbrainz-android] 14dependabot[bot] opened pull request #620 (03dev…dependabot/gradle/dev/org.mockito.kotlin-mockito-kotlin-6.1.0): Bump org.mockito.kotlin:mockito-kotlin from 5.4.0 to 6.1.0 https://github.com/metabrainz/listenbrainz-androi…
[listenbrainz-android] 14dependabot[bot] opened pull request #622 (03dev…dependabot/gradle/dev/hiltNavigationCompose-1.3.0): Bump hiltNavigationCompose from 1.2.0 to 1.3.0 https://github.com/metabrainz/listenbrainz-androi…
2025-11-19 32330, 2025
_BrainzGit
[listenbrainz-android] 14dependabot[bot] opened pull request #623 (03dev…dependabot/gradle/dev/com.google.devtools.ksp-2.3.2): Bump com.google.devtools.ksp from 2.0.0-1.0.23 to 2.3.2 https://github.com/metabrainz/listenbrainz-androi…
2025-11-19 32332, 2025
_BrainzGit
[listenbrainz-android] 14dependabot[bot] closed pull request #606 (03dev…dependabot/gradle/dev/com.google.devtools.ksp-2.3.0): Bump com.google.devtools.ksp from 2.0.0-1.0.23 to 2.3.0 https://github.com/metabrainz/listenbrainz-androi…
2025-11-19 32333, 2025
_BrainzGit
[listenbrainz-android] 14dependabot[bot] opened pull request #624 (03dev…dependabot/gradle/dev/com.patrykandpatrick.vico-compose-2.4.0-alpha.1): Bump com.patrykandpatrick.vico:compose from 2.0.0-alpha.22 to 2.4.0-alpha.1 https://github.com/metabrainz/listenbrainz-androi…
2025-11-19 32335, 2025
_BrainzGit
[listenbrainz-android] 14dependabot[bot] closed pull request #607 (03dev…dependabot/gradle/dev/com.patrykandpatrick.vico-compose-2.3.0-alpha.2): Bump com.patrykandpatrick.vico:compose from 2.0.0-alpha.22 to 2.3.0-alpha.2 https://github.com/metabrainz/listenbrainz-androi…
basically just an endpoint on MB that will be called whenever a user is created/modified/deleted in MeB
2025-11-19 32347, 2025
bitmap[m]
was also working on the login/session handling code and found out it's a mess and we have four unused DBDefs options related to sessions
2025-11-19 32324, 2025
bitmap[m]
I still have some doubts about how to handle sessions, but we should probably have yvanzo and lucifer in the discussion
2025-11-19 32319, 2025
reosarevok[m]
Seems good
2025-11-19 32310, 2025
reosarevok[m]
If there's anything I can help with, let me know, but for the bigger discussions it'd be good to have the whole team indeed
2025-11-19 32355, 2025
reosarevok[m]
I've kept working on the label form, and today I've spent most of the time updating dependencies, since we had last done that widely in June
2025-11-19 32338, 2025
reosarevok[m]
After that I expect I'll keep working on the label form, I have a general idea how to do the bits that are missing although I'm sure I'll want some opinions at some point :)
2025-11-19 32352, 2025
bitmap[m]
I saw, thanks for looking into that
2025-11-19 32311, 2025
bitmap[m]
unfortunately I did not get a chance to look into the ArtistCreditEditor stuff last week
2025-11-19 32344, 2025
reosarevok[m]
No worries, the oauth stuff takes priority
2025-11-19 32305, 2025
reosarevok[m]
Once that is done, we can look through all the React stuff (my forms, serial-ata's area form, and the external links)
2025-11-19 32312, 2025
bitmap[m]
yep, sounds good
2025-11-19 32324, 2025
bitmap[m]
reosarevok: have you noticed more support requests for people not receiving verification emails lately?
2025-11-19 32333, 2025
reosarevok[m]
Yes, I was literally going to bring that up :D
2025-11-19 32350, 2025
bitmap[m]
(just saw the latest email)
2025-11-19 32301, 2025
reosarevok[m]
I'm not sure if something with the new richer email is triggering the spam filter more often?
2025-11-19 32316, 2025
petitminion joined the channel
2025-11-19 32328, 2025
bitmap[m]
that's what I was wondering. in all of the cases I checked, the emails are actually being sent out, so
2025-11-19 32319, 2025
bitmap[m]
it might help to ask people to confirm whether it was in their spam folder
<bitmap[m]> "reosarevok: have you noticed..." <- Uh oh
2025-11-19 32343, 2025
op3kay[m]
no worries, take your time. i just wasn’t sure if i needed to make any changes :)
2025-11-19 32345, 2025
Jade[m]
Jade[m]: It could be that the junk that mjml generated makes it have too high a similarly to newsletters that get immediately junked
2025-11-19 32323, 2025
Jade[m]
The junk being the outlook compatibility code
2025-11-19 32324, 2025
julian45[m]
also: what is the email address under which things are being sent, and through what email server? there are a number of ways we might accidentally be impairing our own compliance w/ spf/dkim/dmarc, which could cause clients to be less happy with the email
2025-11-19 32338, 2025
julian45[m]
*
2025-11-19 32316, 2025
bitmap[m]
looks like they go through one of our exim relays and then smtp-relay.gmail.com (from our noreply address)
2025-11-19 32306, 2025
bitmap[m]
Jade[m]: do you know if there's a way to configure that? if so we can test whether removing it helps
2025-11-19 32357, 2025
julian45[m]
<bitmap[m]> "looks like they go through one..." <- oh ok, that should generally be fine; i would have been more worried if, say, we were sending them directly from MBS using an email like "noreply@verifications.musicbrainz.org"
2025-11-19 32357, 2025
julian45[m]
(would fail most email safety checks since not an allowed host, no known mail servers configured in DNS nor dkim keys set up for that domain, etc.)
2025-11-19 32347, 2025
bitmap[m]
yeah they are sent from the same noreply@musicbrainz.org address and exim relays as before so I don't think anything changed in that respect
2025-11-19 32327, 2025
Jade[m]
<bitmap[m]> "do you know if there's a way..." <- There isn't, I would have to redo the template without MJML
2025-11-19 32343, 2025
Jade[m]
But the templates aren't really complex enough to need it tbh
