Smule.com wrapper

[michei69]

would adding support for the website api's help? Im thinking about the Arrangement publishing part, because the website editor SUCKS when it comes to lyrics timing. Although it would need a different session token, and XSRF tokens... maybe a separate script?

[michei69]

partial (essential) web support now exists, although there are still lots of endpoints which i'll have to add. keeping this issue open, but will unassign myself for now, as this is something ill tackle later on

[michei69]

entire web api seems to be broken atm. Does it use recaptcha or something? Last time i checked there's no captcha there either. Should i opt for sth like puppeteer just in case? although i feel like even if there is recaptcha, it should be bypassable due to how smule implements stuff lol

Currently all important endpoints (e.g. login, create arrangement) return 403 unauthorized. I was suspecting the smulen secret/calculation changed, but that doesnt seem to be the case? Maybe im getting the csrf wrong? No idea atm, and im too tired to check

also dont even get me started on the stupid 418 which didnt even happen back when i was testing it initially. fixed it by passing an empty accept header, since it would send the html either way. i thought that was why it gave 403 afterwards, but removing the forced empty accept doesnt seem to change anything. i wonder if the analytics event http posts are required? ill have to check that later on too