Slashdot Mirror


Apple Accepts, Then Rejects BitTorrent iPhone App

An anonymous reader writes "Apple recently approved an iPhone app called IS Drive, which lets users check and manage downloads from ImageShack.us, while also offering users the option to use the company's BitTorrent service to download files to their ImageShack account. Once Apple got wind of what the app was capable of, however, it was promptly removed from iTunes."

7 of 163 comments (clear)

  1. Re:Bandwidth by biryokumaru · · Score: 2, Insightful

    The ImageShack servers do the torrenting. You just tell them what to download so you can download it straight from them later.

    --
    When you're afraid to download music illegally in your own home, then the terrorists have won!
  2. How many types are secretly banned? by burris · · Score: 2, Insightful

    From Apple via the TFA:

    We have chosen to not publish this type of application to the App Store.

    In addition to the published list of restrictions there is a second, secret, list of types of application that Apple has chosen not to publish. There is no way to know if your type of application is on that list without submitting a fully working application.

  3. Re:Seems strange they approved it at all by gstoddart · · Score: 5, Insightful

    Apple keeps an iron grip over apps. It's weird that they would approve something like Bittorrent at all!

    From TFA ...

    Kepner theorized that the app was able to sneak in past Apple’s censors because he avoided using the word “torrent.” Well played, Sir Kepner. Well played.

    So, the way he described it, they didn't quite realize what it was actually doing. The reasoning from Apple was:

    this category of applications is often used for the purpose of infringing third party rights. We have chosen to not publish this type of application to the App Store.

    I can see why they don't want to get embroiled in any of the legal stuff associated with Torrents. While they do have non-infringing uses, I can see a company like Apple just deciding they don't want to risk the legal actions which could result.

    The *AAs aren't above suing absolutely everyone who had anything to do with distributing anything which can be/is used to do filesharing. Apple doesn't want to jeopardize their iTunes contracts by appearing to support that.

    --
    Lost at C:>. Found at C.
  4. Total breakdown of their vetting process. by wvmarle · · Score: 2, Insightful

    Once Apple got wind of what the app was capable of...

    Isn't the whole purpose of vetting apps to figure out what they are doing (and that no "bad" behaviour is included - no malware)? It seems that if this app gets through the vetting process, from the of it doing only what it's advertised to do, that there's something terribly wrong with Apple's vetting process.

    1. Re:Total breakdown of their vetting process. by Have+Blue · · Score: 2, Insightful

      From the description in the article, especially the phrase "sneak in", it sounds like he deliberately obfuscated the functionality of the app. It's happened a few times before- an app is submitted with a questionable feature disabled, then once it's in the wild a switch is thrown on a server and suddenly it's capable of more than was ever shown to Apple. The vetting process being susceptible to targeted attempts to circumvent it does not mean that a "total breakdown" occurred.

  5. Re:Seems strange they approved it at all by characterZer0 · · Score: 2, Insightful

    I can see why they don't want to get embroiled in any of the legal stuff associated with the Internet. While it does have non-infringing uses, I can see a company like Apple just deciding they don't want to risk the legal actions which could result.

    --
    Go green: turn off your refrigerator.
  6. Obious Reason by whisper_jeff · · Score: 5, Insightful
    To everyone planning on blasting Apple for rejecting the app, please check the submission guidelines they recently published. The reason this app was rejected is spelled out in clear detail there - the developer has nobody to blame but themself for the app's rejection. They knew they were submitting an app that wouldn't be approved because they hid certain functionality, which is precisely the reason the app was going to be rejected.

    2.4 Apps that include undocumented or hidden features inconsistent with the description of the app will be rejected.

    When you do something against the rules and get caught, don't be surprised that there are consequences. Don't want to play by those rules, then don't. That simple.