I keep getting into situations where someone gets reported that would just require a quick email to defuse / improve
2024-11-25 33023, 2024
reosarevok[m]
But I cannot write because it's a temporary mail, which also explains why they ignore edit notes, etc
2024-11-25 33030, 2024
LupinIII
hm
2024-11-25 33032, 2024
mayhem[m]
do it.
2024-11-25 33035, 2024
reosarevok[m]
So I end up having to block the users, and everyone else is posting into the void
2024-11-25 33039, 2024
LupinIII
yea i mena, yea
2024-11-25 33010, 2024
reosarevok[m]
I think it was tykling (IRC) who mentioned there are some good lists of temporary providers that could be used for that, any chance you can point me at those? :)
2024-11-25 33021, 2024
reosarevok[m]
Since it seems mostly people are fine with the idea
2024-11-25 33031, 2024
monkey[m]
Temp emails users are rarely good news.
2024-11-25 33036, 2024
monkey[m]
IMO
2024-11-25 33045, 2024
mayhem[m]
very anti-community
2024-11-25 33002, 2024
aerozol[m]
I support them for some purposes, but not MeB accounts
2024-11-25 33005, 2024
reosarevok[m]
I mean, there's a genuine case of the user who comes, wants to check what the hell but is scared of getting spammed / scammed. But we don't do that, so... I think it's fair
2024-11-25 33007, 2024
LupinIII
that
2024-11-25 33006, 2024
monkey[m]
Creating a free email account somewhere from a no-temp-email-provider is very easy and quick, there's always that for those who insist.
2024-11-25 33010, 2024
reosarevok[m]
Ok, I'm not hearing any reasons why this is a terrible idea, so no rush with it but I'll put it on my list
2024-11-25 33026, 2024
reosarevok[m]
Next!
2024-11-25 33043, 2024
LupinIII
there's more?
2024-11-25 33045, 2024
reosarevok[m]
docker-server-configs (@mayhem)
2024-11-25 33049, 2024
mayhem[m]
hiya!
2024-11-25 33055, 2024
monkey[m]
But wait, there's more!
2024-11-25 33004, 2024
mayhem[m]
so, the LB team has been pretty poor about updating the docker configs before updating containers.
2024-11-25 33031, 2024
monkey[m] guilty
2024-11-25 33033, 2024
mayhem[m]
which makes it hard to find out which image of a container should be running. I even found an image running that had no reference in docker-server-configs at all.
2024-11-25 33048, 2024
mayhem[m]
this is a recipe for disaster. or disaster during disaster recovery.
2024-11-25 33018, 2024
mayhem[m]
I dont think we should really attempt to solve the problem here and now, but I would love to see if people have thought about this and how we could improve it.
2024-11-25 33047, 2024
mayhem[m]
LB uses github for building docker images, so there is likely a way that we could automate this, but...
2024-11-25 33051, 2024
mayhem[m]
it smacks of effort.
2024-11-25 33014, 2024
mayhem[m]
zas: or atj : have you given this any thought?
2024-11-25 33017, 2024
reosarevok[m]
I'm pretty sure we also forget sometimes in MB, it's not always obvious :)
2024-11-25 33042, 2024
reosarevok[m]
(but our stuff changes relatively rarely so we haven't gotten into significant trouble yet...that we know)
2024-11-25 33057, 2024
mayhem[m]
ours are constantly changing, so its a real issue for us.
2024-11-25 33035, 2024
mayhem[m]
well, if no one has any thoughts on this, I will start thinking about what we could do to automate this process.
2024-11-25 33047, 2024
aerozol[m]
Dumb question sorry, is this a technical question or more of a process question?
2024-11-25 33057, 2024
mayhem[m]
a technical process question. :)
2024-11-25 33014, 2024
mayhem[m]
perhaps I should've asked this question in a smaller group -- it doesn't concern the whole team.
2024-11-25 33018, 2024
monkey[m]
the workflow that automatically builds a docker image on release publish, in LB repo, can be set up to hit a webhook somewhere, for example\
2024-11-25 33038, 2024
mayhem[m]
yeah, but where do we store that info?
2024-11-25 33006, 2024
mayhem[m]
anyways, seems like that now is not the right time. let me think about it and then I'll pick it up again with zas/atj.
2024-11-25 33010, 2024
mayhem[m]
back to you reosarevok
2024-11-25 33016, 2024
reosarevok[m]
Thanks!
2024-11-25 33028, 2024
reosarevok[m]
Those are all the topics, but I'm going back for a second to the emails one
2024-11-25 33037, 2024
reosarevok[m]
I just remember we want to move to MeB accounts soon anyway
2024-11-25 33056, 2024
reosarevok[m]
Would it make sense to just have this be a baked-in requirement for the new MeB account system?
2024-11-25 33004, 2024
reosarevok[m]
Or is it far enough that I should implement it in MB first?
2024-11-25 33019, 2024
LupinIII
the emails.. oh the no -temp email
2024-11-25 33035, 2024
LupinIII
i mena it's fine ot implement that right now i think
2024-11-25 33053, 2024
LupinIII
unless it's HUGE work
2024-11-25 33006, 2024
LupinIII
and will require hax later
2024-11-25 33029, 2024
aerozol[m]
You’re dealing with the fallout reo (new spam/sockpuppet accounts being created) so you might be the best person to decide?
2024-11-25 33034, 2024
mayhem[m]
reosarevok[m]: probably close enough to do in MeB.
2024-11-25 33036, 2024
LupinIII
if it's easy to do I say just od it asap
2024-11-25 33054, 2024
mayhem[m]
then again, it doesn't sound like a BIG task.
2024-11-25 33057, 2024
reosarevok[m]
Who'd work on that on MeB, lucifer?
2024-11-25 33018, 2024
reosarevok[m]
I could coordinate with him so we implement it in a way that works for both cases so we don't reinvent the stuff soon later
2024-11-25 33019, 2024
aerozol[m]
time spent implementing the block vs time spent moderating temp email account sockpuppets
2024-11-25 33053, 2024
reosarevok[m]
I made MBS-13835 as a MBS ticket for now, but whoever would look into this for MeB, talk to me and we can look at it for a moment at some point :)
aerozol: hellooooo! The flairs on LB are about ready to be released. If you want to do a blog post etc. about it we can wait for the final merge to coordinate the release
2024-11-25 33028, 2024
mayhem[m]
as an explicit action, rather than an automated action.
2024-11-25 33039, 2024
mayhem[m]
people can still forget, but its muuuuch easier than the current process.
2024-11-25 33044, 2024
aerozol[m]
woohoo! Keen. I would love to grab some screenshots, are flairs up anywhere?
2024-11-25 33053, 2024
LupinIII
erhm i'm still not showing on that page tho
2024-11-25 33002, 2024
mayhem[m]
anyways, off to catch some noms now.
2024-11-25 33040, 2024
monkey[m]
aerozol: not at the moment but I can put it up in the coming days. Cna also take screenshots if you'd like
2024-11-25 33000, 2024
aerozol[m]
Sorry to be cross-talking like this, but mayhem fyi I think all I need to setup those accounts is the login and pw for whatever email we are using for those socials. I think twitter@meb which is pretty funny and we should keep. If there’s no further authentication I can get cracking once I have the login 🤞
2024-11-25 33012, 2024
aerozol[m]
That would be great thanks monkey
2024-11-25 33033, 2024
monkey[m]
A gif would be best, I'll see what I can do
2024-11-25 33002, 2024
aerozol[m]
ooh
2024-11-25 33020, 2024
aerozol[m]
Good idea
2024-11-25 33046, 2024
mayhem[m]
aerozol: what exactly do you need from me?
2024-11-25 33007, 2024
aerozol[m]
I think I just need the login/pw of the twitter email, then I can make new accounts today
2024-11-25 33024, 2024
aerozol[m]
If there’s further authentication needed to login I might ping you again after your noms
2024-11-25 33013, 2024
bitmap[m]
<BobSwift[m]> "I'm guessing that if the merge..." <- the images are still available under the old mbid at the archive (`/details/mbid-$old_mbid` should work). we also have the failed "copy-image" events stored which can be requeued if the archive ever fixes the issue (though we probably wouldn't be able to mass-requeue them, as some have likely been copied over manually at this point)
2024-11-25 33033, 2024
BobSwift[m]
Okay, but sounds like finding them requires some extra work by the users (even it it's not much). That was the point I was trying to make.
2024-11-25 33034, 2024
aerozol[m]
I guess I’m hoping that IA fixes this soon and then we can put together a little info pack/message for those who want to help move images? With links etc (or how to easily generate the links)
2024-11-25 33051, 2024
aerozol[m]
Or do you think we should be letting users know now bitmap (that the images aren’t being moved)
2024-11-25 33014, 2024
bitmap[m]
yeah, I was wondering if we should set a global banner message for now, and perhaps add a warning the merge page in case the issue persists. do you have another idea?
2024-11-25 33051, 2024
aerozol[m]
A global banner sounds perfect for now. Can’t miss it, and users can hide it
2024-11-25 33030, 2024
aerozol[m]
Might be good to include what you expect/want users to do, e.g. migrate the images manually
2024-11-25 33018, 2024
bitmap[m]
<BobSwift[m]> "Okay, but sounds like finding..." <- you're right, it's not obvious at all how to get the old MBID either (it's not available from the merge edit once it passes). you have to go in the edit history and view the raw edit data of the "add release" edit (for the removed release)
2024-11-25 33040, 2024
bitmap[m]
<aerozol[m]> "Might be good to include what..." <- how does this sound: "Images are currently not being copied over after event or release merges. For now, please make sure to upload any images that should be kept to the merge target beforehand."
2024-11-25 33041, 2024
aerozol[m]
Looks good!
2024-11-25 33040, 2024
BrainzGit
[bookbrainz-site] 14dependabot[bot] opened pull request #1141 (03master…dependabot/npm_and_yarn/elastic/elasticsearch-8.16.2): chore(deps): bump @elastic/elasticsearch from 5.6.22 to 8.16.2 https://github.com/metabrainz/bookbrainz-site/pul…
2024-11-25 33042, 2024
BrainzGit
[bookbrainz-site] 14dependabot[bot] closed pull request #1139 (03master…dependabot/npm_and_yarn/elastic/elasticsearch-8.16.1): chore(deps): bump @elastic/elasticsearch from 5.6.22 to 8.16.1 https://github.com/metabrainz/bookbrainz-site/pul…
2024-11-25 33018, 2024
zas[m]
mayhem: sorry, I was cooking, and missed your question. And to be honest I don't understand what's the exact issue. The normal and safe process should be: build the image, update docker-server-configs, and deploy. But sometimes that's not very practical. How are your images built for LB right now?
2024-11-25 33038, 2024
mayhem[m]
Via GitHub. And everyone skips the docker server configs step
2024-11-25 33005, 2024
mayhem[m]
If people don't follow the process, the process is broken.
2024-11-25 33013, 2024
zas[m]
Well, if we don't have the correct version of an image in docker-server-configs, it could be an issue if we need to redeploy on another server. It happened to me to forget to commit changes regarding image versions or the like. But to me that's clearly a process issue.
2024-11-25 33045, 2024
zas[m]
For example, for picard-website, the image is built via a hook, tagged version, then the scripts should be updated to use this version. Though I usually deploy manually for testing, and only update scripts afterwards, I guess you do more or less the same.
2024-11-25 33030, 2024
zas[m]
With current setup, I don't see much solution to this, but being rigorous. On the long term, we should move to some container orchestration system and stop to do manual deployment.
2024-11-25 33032, 2024
aerozol[m]
Hey mayhem do you want to create the Bluesky accounts the “proper” way, using our domains, like you did with MeB and LB?
2024-11-25 33051, 2024
aerozol[m]
If so is it worth me creating accounts the pleb way/will it migrate stuff over?
2024-11-25 33015, 2024
mayhem[m]
<aerozol[m]> "Hey mayhem do you want to create..." <- Yes. But that can be done after the fact
2024-11-25 33053, 2024
aerozol[m]
Cool, I'll truck on
2024-11-25 33040, 2024
prout has quit
2024-11-25 33053, 2024
prout joined the channel
2024-11-25 33016, 2024
bitmap[m]
zas: hey, when you have time can you help with updating the CAA index queue alert on https://stats.metabrainz.org/d/000000075/alerts-c… ? previously it came from rabbitmq, now it needs to be queried from postgres
2024-11-25 33032, 2024
aerozol[m]
Okay, we now have Bluesky & Mastodon accounts for MetaBrainz, MusicBrainz, ListenBrainz & BookBrainz (just the Mastodon BB account still needs email verification)
2024-11-25 33030, 2024
aerozol[m]
I have updated the descriptions for the X accounts to say “Follow us on Mastodon and/or Bluesky.” but will come up with a witty graphic as our last post (to pin to the top). The Austrian airline one is great!
2024-11-25 33041, 2024
aerozol[m]
If you have ideas for gfx hit me peeps
2024-11-25 33001, 2024
mayhem[m]
wait, are you struggling to summon snark???
2024-11-25 33048, 2024
aerozol[m]
Haha! Maybe I’ve been trying to be clever when I should be letting the snark flow
2024-11-25 33003, 2024
mayhem[m]
let it flow. don't hold back.
2024-11-25 33017, 2024
mayhem[m]
bonus points for making it X related.
2024-11-25 33053, 2024
mayhem[m]
maybe for my personal I account I could use something like... "I prefer X in other activities in my life. 3 times as much even!"
2024-11-25 33006, 2024
mayhem[m]
needs to be wittified, but hey, its late.
2024-11-25 33015, 2024
mayhem[m]
"eXceptional toXicity, wholesale disrespect and attacking kindness does not align with our values."
2024-11-25 33037, 2024
mayhem[m]
"hate speech is not our jam"
2024-11-25 33057, 2024
aerozol[m]
“Share data, share kindness, never enshittify.”
2024-11-25 33017, 2024
aerozol[m]
Since you’re up mayhem can you verify the bb bluesky email? bitmap couldn’t find it either. bb @ meb.org
2024-11-25 33027, 2024
aerozol[m]
Then I can get it all done
2024-11-25 33013, 2024
mayhem[m]
I have no bluesky emails.
2024-11-25 33007, 2024
mayhem[m]
the twitter@ email is working, at least for me. did you just receive a test email from me?
2024-11-25 33007, 2024
aerozol[m]
Ah when I go to send a email to that address it pops up with Nicholas’ name so, I’ll wait for monkey
2024-11-25 33043, 2024
mayhem[m]
or reo. we gots two of them.
2024-11-25 33050, 2024
aerozol[m]
Yeah that one works. We’ve only been using that one for the MeB accounts so far
2024-11-25 33006, 2024
Kladky has quit
2024-11-25 33023, 2024
mayhem[m]
ok, let me check bb@ as well.
2024-11-25 33054, 2024
mayhem[m]
I can't find a record of bb@
2024-11-25 33053, 2024
mayhem[m]
where did that come from?
2024-11-25 33001, 2024
mayhem[m]
yep. bb@ didn't exist. it does not. request another email confirmation and you should be good to go.
2024-11-25 33007, 2024
aerozol[m]
From the syswiki as the email for the Twitter X account
