3 ms·
Bit confused on one point -- so SoundCloud revised their ToS to deny downloads, but they kept the download URL in the API response? Amazing that after two diffe
by zaroth 12y ago
Bit confused on one point -- so SoundCloud revised their ToS to deny downloads, but they kept the download URL in the API response? Amazing that after two different illegal take-downs it just kept getting back on top of the listings.
Random Android question: When the app was taken down, I guess you lose app storing listing and IAP. But existing users would still be able to run it, and the developer would still get ad impressions and ad revenue?
I don't quite understand SoundCloud's rationale... Why is it OK for me to do an HTTP GET from one user agent but not another? How is that something they have legal standing to dictate?
Hartig seems perfectly happy to let his obviously well liked software be stomped into oblivion? SoundCloud could perfectly well provide the equivalent functionality, but instead they snuff out an honest developer?
It's not even like he was deep-linking the content (oh no, don't actually use hypertext markup how it designed to be used, shiver), this was just an added intent in the existing 'Share' dialog.
So serious question: 3rd party apps insert themselves into the Share dialog. It's purposefully designed that way. In that dialog, the user gets to choose how to handle the data being shared. Basically, it's in a clipboard and the user is choosing where to paste it. How does SoundCloud get Google to nuke an app for properly using this interface?
(Sorry, that's like a dozen different questions that this post has raised in my mind)
- GuiA 12y agoBecause lawyers don't get what you just explained.
- coldtea 12y agoOr they get it just fine, since top lawyers of the kind hired by SoundCloud are as smart or even smarter than most programmers, and some even have technical training, but they have their reasons. Like, they know that the fact that you can "get around" something doesn't matter as much as there being a slight inconvenience. If, for example, at some point the official SoundCloud app allows direct download, people will use that, and not the "get around" method -- whereas if they allowed third party clients to have that feature it wouldn't be so clear what the users would choose.
- res0nat0r 12y agoThey aren't snuffing out any developers, they just don't want people to download their content directly to their phones per their TOS. I'm sure their rationale is reasonable and probably has to do with some overall terms probably with major content providers or studios.
- hobs 12y agoSo go to the link on your phone's web browser and tap the download button? The only answer is lawyer garbage.
- Freestyler_3 12y agoYes, you only have to go around the mobile version.
- zaroth 12y agoIt sounds like they are claiming their ToS can dictate how you can use the data they are putting in your computer's clipboard. They then used that claim to remove the equivalent of a 'wget' program from the app store. I don't like what SoundCloud has done here. I'm pretty sure it was line noise for Google, but I don't like that they went along with it either. Note these are published files that are generally available for download. The download is an HTTP GET on a public URL, which they publish freely and directly on their own site. It's in no way "ripping" the file from the site or defeating any DRM.
- res0nat0r 12y ago> It sounds like they are claiming their ToS can dictate how you can use the data they are putting in your computer's clipboard. Yup. When you are using their api to power your app you have to abide by their TOS.
- deleted 12y ago[deleted]
- 12y ago
- ch0wn 12y agoHi, author here. > Bit confused on one point -- so SoundCloud revised their ToS to deny downloads, but they kept the download URL in the API response? Amazing that after two different illegal take-downs it just kept getting back on top of the listings. I think they eat their own dogfood here. As far as I can tell, they have no special privileges for their owned and operated clients. If you for example look into the network panel when using the web client, you'll see that they directly access `api.soundcloud.com`. > Random Android question: When the app was taken down, I guess you lose app storing listing and IAP. But existing users would still be able to run it, and the developer would still get ad impressions and ad revenue? Yes indeed. I'm surprised how much of a long tail the app has. Even though it's now been almost two months since I've taken down the app and SoundCloud has also revoked the API key, I'm still getting a sizeable amount of ad impressions in a completely dysfunctional app. :/ > I don't quite understand SoundCloud's rationale... Why is it OK for me to do an HTTP GET from one user agent but not another? How is that something they have legal standing to dictate? It's their platform, they can do whatever they want. As operator of a platform like this, it's natural wanting to control the experience. I think it's remarkable how open SoundCloud remained over the years whereby most other platforms leverage their APIs as a way to find initial adoption and then quickly close them down as soon as they reached a certain point. > Hartig seems perfectly happy to let his obviously well liked software be stomped into oblivion? SoundCloud could perfectly well provide the equivalent functionality, but instead they snuff out an honest developer? I'm certainly not happy about this, quite the contrary. But I see and understand their rationale, learned a lot along the way and SoundCloud has always treated me fair. > How does SoundCloud get Google to nuke an app for properly using this interface? I'm quite interested in the exact process myself. I presume that this all works under the ominous "copyright" umbrella.
- e12e 12y ago>> Bit confused on one point -- so SoundCloud revised their ToS to deny downloads, but they kept the download URL in the API response? Amazing that after two different illegal take-downs it just kept getting back on top of the listings. > I think they eat their own dogfood here. As far as I can tell, they have no special privileges for their owned and operated clients. If you for example look into the network panel when using the web client, you'll see that they directly access `api.soundcloud.com`. But it is strange that they in their TOS for the website state: "You must not copy, rip or capture, or attempt to copy, rip or capture, any audio Content from the Platform or any part of the Platform, other than by means of download in circumstances where the relevant Uploader has elected to permit downloads of the relevant item of Content." In other words, they seem to allow users to download content that is available for download. So if I write my own web browser, I'm free to download downloadable content -- but not if I write an app for Soundcloud... Or perhaps, it's this clause: "(x) You must not rent, sell or lease access to the Platform, or any Content on the Platform, although this shall not prevent you from including links from Your Content to any legitimate online download store from where any item of Your Content may be purchased." It's unclear to me how Soundcloud cannot get Firefox for Android banned under this clause as well... (well that would be insane, but you can ask for the desktop version of the site, and download from there?). Note that this is the user TOS[1], not the API TOS[2] -- but that line is a little more fuzzy than they would like it to be IMNHO. [1] https://soundcloud.com/terms-of-use https://soundcloud.com/terms-of-use [2] https://developers.soundcloud.com/docs/api/terms-of-use https://developers.soundcloud.com/docs/api/terms-of-use [edit: entirely forgot to thank the author for being open about this, and publishing the app for everyone to access. On another note: did you already provide source to some of the users on request? Or did you just recently add cert pinning?]