lucifer: seems better, thanks. I think we will need to tweak this over time -- still doesn't feel amazing. but I have to remind myself that the list of tracks is not a finished product, but input to the next step.
lucifer
agreed on both points.
ruaok
lucifer: #1645 is ready for review.
I think I am going to so some mapping cleanup and then finish the work to emit MBIDs with listens.
alastairp
ruaok: once you have some time I have 2 or 3 things that I want to run past you
ruaok
I think after/during lunch might be good for that.
btw the summit is next weekend, we should put up some agenda/session info up.
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, MeB Summit Planning (lucifer)
personally I'd prefer a vm because it'd just be a matter of cloning the sentry repo and running docker-compose up. any other option requires faffing around
ruaok
exactly that. stop faffing, code more.
alastairp
is it worth going up to a CX41 for memory overhead?
hence why I stopped and sent the email
ruaok
if you think it is necessary, then lets do it.
pick the specs you want, not the specs you think we'll approve. :)
I told zas a long time ago that if we needed resources, we should use them. but lets make sure we don't waste any -- that's dumb.
alastairp
the only guidelines I have to go on is what sentry says is required, and I don't know if they include overhead, or are bare minimum requirements
let's go higher. as I said, there are 30 containers in a sentry setup!
ruaok
then go one step above the minimum and then we'll evaluate. we can always upgrade.
alastairp
OK, let's provision a CX41 in Finland
ruaok will let zas do the honors and initial setup.
lucifer: regarding the recommendations we provide, can we make sure that we don't include the already listened songs by the user?
lucifer
akshat: we just removed that step earlier today because it doesn't work as expected. that is the raw set of tracks though. troi could always do that while creating the playlist.
monkey: did you manage to have a look at my PR yet? I want to confirm I have done the submit listens block correctly
i didnt include all of the error catches that are in the APIService, should I include these?
ruaok is being buried in BS faster than he can vanquish it
<tandy[m]> "i didnt include all of the error..." <- i'm half tempted to just copy in the whole proc from the APIService ..
akshat
ruaok: I see that the MusicBrainz twitter handled isn't much active. Can we do something to automate a tweet as soon as a blog is posted on blog.meb, a post at community.meb becomes very popular or a release is made?
Else someone can take the responsibility to manage the account
ruaok
monkey: when I use brainzplayer, its only a matter of time until that page ends up spinning hard and taking up 100% of one core. are you aware of this?
alastairp
akshat: we've been trying harder to tweet and blog more, but sometimes we stop doing it because we have other things to do
of course, to tweet a blog post we need to blog more too :)
akshat
My point being, I want to embed the Twitter id on the mb web revamp. That could be our source of updates for everyone somewhat like how lb does
ruaok
akshat: yes, please tweet more! can you access the syswiki?
akshat
alastairp: I do feel we have enough content! :)
ruaok
syswiki is where we have internal documentation.
akshat
Okayy ruaok
alastairp
akshat: specifically for that, we'll need to be careful - the twitter embed on LB and AB sets a twitter cookie, which is a big no no for us, and we need to do something about it on those sites
ruaok
yeah, twitter embeds are a thing of the past for us. Listing our handle, sure. but embedding recent tweets, lets no do that.
alastairp
so we'd need a way to show a twitter feed without setting 3rd party cookies. If you can find a way to do that, it'd be really helpful!
ruaok
(we need to remove it from the LB home page)
tandy[m]
alastairp: RSS embed could work without the nastiness?
tandy[m]: yes, though that'd probably require us to apply some kind of formatting to make it look nice. If you have any knowledge on how to do that please tell us!
alastairp: we could probably make a react thing to do that so we could use it across metabrainz
alastairp
akshat: tandy[m]: That sounds like a good option, as long as we can confirm that this process sets no twitter.com cookies (I just checked the demo above and I have some cookes set, not sure from which demo)
ah, it's possible those were just my regular "you're logged into twitter" cookies, because now after deleting them I'm logged out
tandy[m]
if this is a long term idea ill make a Meta ticket
akshat
I think this package is a good option
tandy[m]
cos its best to keep dependencies off services like twitter when we already have an rss feed
alastairp
tandy[m]: yes, please create a ticket
tandy[m]
done
alastairp
the react-twitter-widgets app still makes many requests to twitter.com from the user's web browser, so we can't use it. maybe there are other options