SoundCloud could be forced to close after $44m losses

Re:SoundCloud could be forced to close after $44m losses by jeffbr13 on Thursday February 11, 2016 @10:56AM (#11080845)

At my company we have a bunch of content that's only archived on SoundCloud. The main barrier I've had to backing up original uploads (only available through the web interface) is the terrible reliability of all the AJAX calls. Even with browser automation, it requires a LOT of error-handling just to navigate between resources successfully.

It seems that all these microservices[1] are there for the sake of blogging about using microservices[2] as there haven't been any new significant new features delivered in years, and the whole application now seems to be delivered through AJAX calls.

[1]: https://developers.soundcloud.com/blog/building-products-at-... [2]: http://philcalcado.com/2015/09/08/how_we_ended_up_with_micro...

[ Parent | on HN ]

Re:SoundCloud could be forced to close after $44m losses by toomuchtodo on Thursday February 11, 2016 @10:59AM (#11080862)

Have you tried using youtube-dl? It extracts the relevant data from Soundcloud's JSON API to perform the download:

https://rg3.github.io/youtube-dl/

I know you mentioned originals are only accessible through the web interface, but I was not sure if you were aware of the JSON API.

[ Parent | on HN ]

Re:SoundCloud could be forced to close after $44m losses by zimpenfish on Thursday February 11, 2016 @11:43AM (#11081223)

Oh, I didn't know that. I ended up writing my own SoundcloudSync.py to keep a backup. Not very sophisticated but easy enough to run by hand whenever I upload something new.

[ Parent | on HN ]

Re:SoundCloud could be forced to close after $44m losses by zimpenfish on Thursday February 11, 2016 @11:47AM (#11081245)

I seem to be getting originals through the JSON interface - the MD5s of the downloaded m4as match the MD5 of the m4as I've got in Audioshare.

[ Parent | on HN ]