3 ms·
There's no question that this will be pulled soon. The question is: will Apple also disable the app remotely for all those who purchased it, something that is p
by lukifer 15y ago
There's no question that this will be pulled soon. The question is: will Apple also disable the app remotely for all those who purchased it, something that is possible, but (I believe) unprecedented.
- arn 15y agofwiw, Tether (the company) claims Apple was aware of what the app did: http://twitter.com/#!/Tethercom/status/141415159376781312 http://twitter.com/#!/Tethercom/status/141415159376781312
- deleted 15y ago[deleted]
- masklinn 15y ago> The question is: will Apple also disable the app remotely for all those who purchased it, something that is possible, but (I believe) unprecedented. They did not do it for the previous iteration of the concept (Netshare, those who kept it can still use it, although I'm not sure it still works on recent iOS versions). It's very unlikely they'd do it this time either, remote kill is for actively dangerous/harmful applications and they'd get a complete shitstorm using their killswitch for this.
- ugh 15y agoThat seems unlikely. I think there already was a tethering app which Apple pulled from the Store but didn’t pull from devices. I do think that Apple is serious when they say that their ability to remotely pull apps is reserved for malware. The much more elegant solution for Apple is to make this app silently stop working with the next OS update.
- timerickson 15y agoThis is correct. The app was NetShare, and it still resides on my phone.
- ugh 15y agoDoes that app still work with the current version of the OS?
- Cowboy_X 15y agoYes. I had sporadic trouble with it under ios 4, but it resumed working properly in ios 5. Never liked uncommon ports, though.
- ugh 15y agoThat’s very interesting. Wouldn’t it be very easy for Apple to break the app with an OS update? You would almost expect that an app stops working after so many OS updates (not because someone purposefully made it stop working but rather coincidentally).
- xorglorb 15y agoChances are NetShare reused existing code from an open source SOCKS proxy implementation, which would probably just use standard UNIX APIs. Combine that with the simplicity of the GUI, and it's very possible that none of the APIs it is using have changed since release.