ruaok: hi! working on upgrading stripe checkout, the workflow seems to have changed. now it is to redirect the user to stripe's website, where they complete the payment/donation and then they are sent to a success/error page accordingly. the payment/donation details in case of success itself will be sent in a webhook separately to the server.
does that sound fine?
ruaok
Yes, sounds as expected.
Will that allow us to setup recurring donations too?
lucifer
yes, there's an option to allow subscriptions.
ruaok
I'm considering disallowing PayPal, since they are such an incredible pain to deal with.
Please enable the recurring donations then.
lucifer
makes sense. will do.
tandy[m]
<bitmap> "oh ok, so recent edits being..." <- like the bandcamp buying feed
<ruaok> "I'm considering disallowing..." <- have you considered / do we take crypto?
MrClon joined the channel
ruaok
tandy[m]: we did, but it was not really used (bitcoin) and just an accounting hassle, so I turned it off.
tandy[m]
ah thats a shame
i know for other orgs crypto is a nice asset, because one year you might have 100 dollars and the next 10000 lmao
I found it in some code I was reading last night. It looks like it might be a solution for that crazy `(global ?? window).$ = jquery;` that we added in AB
lucifer: do we have any places in LB which read a csrf token from react and use it in a request?
lucifer
alastairp: no, don't think so.
alastairp
just trying to work out the best way to do it. I think putting the token in global props makes sense. we have `csrf_token()` in templates or `form.csrf_token` in forms, but we'd need the value in python to be able to inject into the props
there's a POST in the dataset editor. the fix I added here put a `data-csrftoken=` attribute into our div, but I've replaced this setup with a LB-style page-props: https://github.com/metabrainz/acousticbrainz-se...
lucifer
ah ok. yeah, generate_csrf should work.
alastairp
yep, it works fine 👍
ruaok
I love it when I see picard in the list of apps that need to be updated in Linux.
[15:29] <tandy[m]> <akshat> "lucifer: one of the members on..." <- i think we should make an attempt to make the site work in javascript free browsers
[15:31] <tandy[m]> it would be a shame for the ui revamp to affect users of the site
totally agree
[15:41] <tandy[m]> a lot of other people in our community do too, since its a FOSS project <---
[15:44] <akshat> But yeah, I think the internet is becoming responsible with every day and for any critical information, we do need permissions, such as the user's location <-- honestly I can't think of *any* reason mb should *need* my location. I've given the languages i speak, but willingly. if you don't want to you sohuldn't have to
akshat
Hahaha totally CatQuest I was just thinking of examples from the top of my head
CatQuest
oh yea. also everything bitmap said. sure editing requires js, but just viewing shouldnt :)
i've got a comment on https://musicbrainz-web.web.app/ . the "explore musicbrainz" part takes up al ot of space with huge images that doesnt really do anything
some images is fine but this kinda make our site look like some douchbag "web 2.0 service" thing
same with the "supporters" secton. logoes don' need ot be that huge
I also think the "our software" sectino could be ffurther up. (but agian smaller)
no need for a pagewide rinbow box with black button links. instead we could have a list with those as well as github, source, both our database and picard (link to picard website)
what about a header with a 2-3px rainbow line under it?
I like many of your ideas though!
oh I see the coloured rainbow thing is magenta fading into orange!. heh. that's kinda neat! i liek it!
"supporters" should be lower down.
and the FAQ could be a smaller sideways thing that you click and thne it expands instead of taking up many scrolls
lots of good ideas here. more compacted, more actual info, i thikn this is really good!