#metabrainz

atj: yes. i am looking up the docs as we speak but its somewhere between 30s-60s afair.

lucifer: haproxy has separate timeouts for tunnels but they cannot be used because it is running in tcp mode

as it can't see inside the connection

lol I tried using a twitter "send your thing trough a n ai thing and it will generate a tweet like you" and it came back saying "I wrote too unique for it to emulate me" XD

i see, so any change to timeout would affect traffic at meb-wide level?

lucifer: I'll tweak haproxy, how can I check the impact on lb websockets (I mean the most reliable and quick way) ?

I suspect tcp round robin to be the cause of the issue

zas: i can't think of another way than to manually monitor the LB frontend.

i am around to keep a check on that if it helps

ok, I'll try something, let's see

looks like the default heartbeat in Flask-SocketIO is 25 seconds

zas: bump client timeout to 30s?

atj: I think both client/server timeout are far too low, I'll set them to 150s (from 15s), some set them much higher

deploying

that seems high, can we try something a bit lower rather than going from one extreme to the other?

lucifer: check if it changes anything on your side, within next minutes

Yep, on it mayhem, I've got some even more clever CSS on the way

oh on, not clever css

:D

dangit

ruined my own joke with typo

clever monkey with clever CSS!

also INVOICES PLEASE!

zas: seems to be working fine since 1 min.

Oh yeah

lucifer: yes, I'll check side effects, but it seems much better

!m zas, lucifer, atj

You're doing good work, zas, lucifer, atj!

this must be a great feeling for you two, atj & zas.

well done for such a smooth switchover. I doubt anyone noticed.

mayhem: one day please 😅

oh, ok.

mayhem: yes, quite smooth, but the preparation was a very long process (and we're not over yet)

mayhem: you cna invoice me for 50 kr :D and thne I cna say i'm actually hired. like.. performatory :D

zas: yes, but it shows what badasses you two are!

CatQuest: wait, you're going to pay ME for not working here? cool!

other way around but

:D

it'd be cool to say i legit have a hired job thing

atj: I think new timeout values are balanced between what we had and what is usually recommended, it increased the number of used sockets by 30% only

feel less like a bozo and more liek a regular guy

comes with the benefit of actually being able t to tel lme what to do.. that woudl probably rock for most people here :DDD :P

aerozol: Don't know if you're still up but… your feedback echoes what I was thinking: I guess we should automatically select the first recs playlist when you open the page?

[musicbrainz-server] 14reosarevok opened pull request #2959 (03master…MBS-13111): MBS-13111: Hide list of autoeditor election voters during vote https://github.com/metabrainz/musicbrainz-serve...

monkey: I was just thinking that too, I think so. Then the bottom of the page is always nicely filled

Yus.

Other option is some message along the lines of "select a playlist above…" but I don't see how that would be better

👍

At the compy now, it looks so good. Love the play and save buttons

Is Weekly New Jams a working title? Not very clear to me

Nor to me really. I guess we need to workshop the name. nudge mayhem

"Weekly discoveries"?

I feel like I saw you discussing this, I can’t find it - is new jams things you haven’t listened to before?

Weekly discoveries sounds good already

atj: I'll stop openresty on rex for a while, traffic will be handled by rudi alone during this time. That's in order to ensure everything works as expected in this case.

done

I'm a bit hazy on the details, will discuss with rob and workshop a good name

I'll restart it in 5 minutes

akshaaatt: unit tests for social repository added!

also if you can, please take a look if the tests are being correctly run on the pipeline?

atj: before restarting openresty on rex, I'll also stop haproxy on rex for a while to have the full figure

haproxy stopped on rex

restarting haproxy on rex

restarting openresty on rex

atj: everything looks fine :)

monkey: aerozol : Weekly new jams are tracks that our system thinks you should listen to , but haven't yet.

I'm open for a new name for it.

I think "Weekly discoveries" sums that up pretty well

ofc performance decreases a bit when running on one leg, but nothing unexpected

discoveries is perhaps not the best name. we used that in context of "retrospective of what you've already listened to".

Right. Makes sense. Let me rack my brain a bit

but in fact, you haven't listened to these tracks yet, so they are future discoveries.

There's also the aspect that you might know these songs, but haven't sent a listen for it in the past (or some issue on LB doesn't recognize you did)

In which case it won't be a 'discovery' exactly

zas: 👍

and one gw is able to handle the whole traffic without issues, as planned. Load increased from ~2 to ~3 on rudi, nothing to worry about

yep. subtle, but how do you get that into a short pithy name?

ENGAGE MEGABRAIN !

Weekly exploration?

yes!

that's good -- consistent with the other uses of explore on our site.

and we're starying further away from spotify's 'weekly discoveries' as a bonus

yes!

Could also be something like "Hits of the week" or something, but I suppose that's not the same meaning

they aren't hits, so no.

"Weekly finds", but that's a bit weaker IMO

"jams" for stuff you will likely like. "explore" for things that are (possibly) new. "discoveries" for review type playlists.

that feels sane to me.

Yeah, pretty consistent and pretty clear

I mean, "jams" isn't particularly clear by itself, but I think it won't be tricky to get used to it

I like Weekly Explore, but that also feels close to spotify.

and jams is already a common term, so I agree it will be ok.

Weekly Exploration?

Best so far IMO

feels right

motion carried then?

I guess we also have the option of not using 'weekly' in the title, which frees us up a bit. "You might like…", "New to you", things like that

New to you Jams?

Let's aim for Weekly Exploration, I'll keep my brain online and if anything comes up that's definitely better I'll chime in

ok. lets sleep on it. if nothing else pops out, I"ll change it tomorrow.

👍

Thanks for the huddle

np

mayhem: phew, emailed ~40 people with the press release

Also submitted to hacker news, if someone has suggestions for improvement (text, title, etc), go for it, we can follow up again in a few days with another one: https://news.ycombinator.com/item?id=36150062

I also lean towards dropping ‘weekly’ and going for Explore (but is that what Spotify uses?)

Actually, weekly exploration is pretty cool. I wonder if we should render ‘weekly’ in a different font or something. Then our other playlists could have ‘annual’ in them too (just brainstorming)

lucifer: monkey and anyone else who has a hacker news account: plz upvote: https://news.ycombinator.com/item?id=36150062

e

maybe good time to get one and help out?

Sure

thx

Hi jasje!

Kudos to you for systematically working on the PR!

Just for clarity though, you seem to have added Search as a separate navigation item. Where are we adding search in the UI?

lolololol

akshaaatt: replacing about section

wow. wise paid us a $130 interest last month. useful. time to move more money there.

That sounds like it'd be wise

I agree that no punishment at all seems like more than enough, yes!

NZ will formally enter war with Estonia tomorrow morning

lol

mayhem: https://usercontent.irccloud-cdn.com/file/Bo9zF...

Hope your guys are coming over, because we have no air force planes and like two tiny boats, so otherwise it's going to be a really low-key war

reosarevok: It is going to be very low key indeed! I think we have some planes? But no way do they go that far

aerozol: Jean-Robert is a long time MB fan.

Cool, you want to let me know what to reply? Or shall I write something along the lines of “Thank you for thinking of us - we have also taken notice, and are thinking of next steps, including potentially putting forth a proposal”

(Eventually I will write stuff without checking but let’s take it slow)

"Thank you for mentioning us Jean-Robert! We plan to have a formal response to this initiative soon, given that we've already solved a lot of the problems mentioned."

how is that?

“We are interested to see how this will look without streaming services involved in the agreement, and if there will be further costs to artists in terms of creating new tech, frameworks, and implementation”

I think we can go a bit longer on LI, but that sounds good to me too

aerozol: your version is not edgy enough for us. :)

"Thank you for mentioning us Jean-Robert! We plan to follow this initiative closely and are considering a formal response to this initiative soon, given that we've already solved a lot of the metadata problems mentioned. Most solutions are ready to use today. Gratis."

Wait, gratis? I thought we'd want support :p

"Thank you for mentioning us Jean-Robert! We plan to follow this initiative closely and are considering a formal response to this initiative soon, given that we've already solved a lot of the metadata problems mentioned. Most solutions are ready to use today, many of them gratis."

better?

Maybe? :)

I’m risk averse until I’m really comfortable with how we talk! I have caused… trouble… in the past, going straight for edgy

aerozol: more edgy then? you're not about to get in trouble with me for being a bit more edgy.

reosarevok: gimme something better.

More edgy? "Most solutions are ready to use today, many of them developed by open source people who actually care about artists getting paid, unlike others."

slightly less edgy?

the more edgy was pointed at aerozol , not you reosarevok .