It might be helpful to have secondary prizes for jailbreaks for only some of the models - i.e., maybe the 4S won't be jailbroken but all the others are; this still deserves some commendation.
Personally I've found the reasons to jailbreak have decreased more and more over time. A perfect example for me is Control Center replacing what I used SBSettings for.
I tried to find an iOS bitcoin wallet. Turns out, Apple pulled them all from the store because they have mobile payment ambitions - and one doesn't let predators into ones own garden. The walled garden is beautiful, but innovation is relentlessly weeded out by its tenders. I much prefer iOS, but I was seriously creeped out by their anti-competitive practices. I can't run the software I wish to, so I'm going to buy an Android phone, even though I'd much prefer an Apple product that actually lets me run competitive software.
That's true, but it really only takes one missing feature or annoyance to make Jailbreaking a consideration.
Case in point: When I plug my iPhone 5 into my car's USB port, the Music app's display changes to an "Accessory Connected" splash screen. I can only control my music through my car's awful dashboard interface. Jailbreaking allows me to disable that splash screen.
Other things like 5 column springboard/dock, FakeClockUp (reduce or speed up slow animations), and BiteSMS (Messages app replacement that can be used on the lock screen), are just minor interface and functionality tweaks that, together, make my jailbroken iOS6 a far superior UX than iOS7.
That car compatibility stuff is definitely something that needs to dealt with. The fact that it entirely takes over your phone is entirely unacceptable.
I agree, but I'd still like to do it. Control center and officially-sanctioned WiFi tethering took care of most of my jailbreak-related needs. However, there are still some features I miss, like the add-on I used that looked up incoming calls from unknown numbers.
Serious question: Why bother? Why is there such an interest in using a very closed system in a way the vendor does not support if there are (more) open alternatives?
Is it because you are forced to use an iPhone by external factors, like your employer? Are there critical features missing from Android and all the others? Is it just your personal preference?
I really don't mean to offend anyone, it's just that I perceive the closed ecosystem of the iPhone as an intentional "feature" and as I personally don't like it, I would never put my money into such a closed system just to try to jailbreak it afterwards.
Its nice to use. I like how it integrates with my Mac stuff better than Android does, and iTunes Match is a killer feature. But I'd love to load FOSS onto it, so a jailbreak would be super handy.
"because we can" is obviously a very legitimate reason for something like a jailbreak :) But I am not sure if it answers my question completely, because we are talking about a site which a collects money because it seems like we can't at the moment. There's nothing wrong with that, but it shows that an iPhone jailbreak seems to be a high-priority task for many here and that's something which "because we can" does not fully explain (EDIT:) because nobody collects money for a better integration of android into the mac world so far, right?
Your argument about Mac integration seems valid, I did not think about it as I am no mac user :)
I find it less compelling to jailbreak. When I switch from one provider to another it usually takes the form of contract and right now a provider like AT&T or T-Mobile gives good deal on phones. I am actually less and less on phone spec. My Atrix used to be a top phone on spec but after using it for 6, 7 months I notice it being slower and slower. And then you can't upgrade to latest Android because officially Motoral doesn't support it and I don't want to deal with custom upgrade (I have done too many and many just fail my phone). I used to get expensive unlocked phones myself but now I can get a good deal from contract bundle and they offer quite a good range of selections.
After two years I am still using this old Atrix. I might switch to Nexus one day if I had the budget for it. iPhone isn't my cake so I'd passed on. But I have to praise a closed system like iOS - update is great. No fragmentation.
"because we can" seems like a pretty good answer. Also, a thing that's interesting to me about campaigns like this one is there are so many iphone users. Even if a small fraction of them actually want to jailbreak their phones - for carrier reasons, to install some goofy skin, whatever - there's a lot of value in getting it done. How much value? I'm not sure - but I don't think $50,000 or even $100,000 would be surprising...
Android tablet software is the same as the phone software. The software should be written to automatically handle different screen sizes, orientations and aspect ratios as needed in a single bundle.
I'm with you on this one. I value my ability to develop applications for my Android device free from worry about a future update taking that ability away from me. My applications never need to be on an app store, and I can share them with whomever I like, in any manner I like.
Why would I buy into an ecosystem that then forces me to hope someone far smarter than I is able to break the security of that system for me? Jailbreaks are worrisome because they introduce a potential loss of security on mine, and all users phones.
That's just not even remotely true. What Apple does (to my annoyance) is allow the carriers to control whether or not the phone allows tethering. But they do allow it if the carrier does, and plenty of carriers allow it (usually after making you pay extra). I've been tethering with my iPhone on AT&T, officially, for years now.
You're right, sorry for not being more clear. What I intended to say was that Apple won't allow you to tether without approval on any networks. At least it defaults to allowing on all networks by T-Mobile.
Apple even respects T-Mobile's wishes on the matter.
I put a SIM connected to one of T-Mobile's $30/5GB prepaid accounts in my iPhone 5. When I try to turn the tethering function on, I get a prompt telling me to go to a T-Mobile website to get on a plan that supports tethering.
The nice thing about android is that you don't have to care what Google and your your Provider do in many cases, because the "jailbreak" is official: You can install CyanogenMod or even Replicant.
AFAIK, it doesn't. 4.4 contains a setting that allows a provider to specify a different APN for tethering use, which I can imagine is a legitimate feature. You can also turn it off (on IPv4 at least)
The same Nexus 4 + Android KitKat 4.4 + AT&T SIM Card does not detect unauthorized tethering.
Surprisingly this "feature" only appears when using T-Mobile SIM Card.
It is not the case with Android Jelly Bean 4.3
iPhones, ostensibly, integrate much better with iTunes. I still have hundreds of Protected AAC files I bought on iTunes pre-2009 that will not play on Android phones. The only way to get around that is to burn/rip the AAC files or pay Apple to upgrade them to the other format.
It's funny that this is your reason to use an iPhone because a quite similar experience of mine was a main reason for my decision to stay away as much as possible from closed systems :)
If I could do it all over again, I wouldn't build my listening workflow around iTunes. Ten years of play counts, dozens of smart lists, and hundreds of Protected AAC files later, I'm pretty locked-in.
Just fyi: I believe [make sure this is right before you do it!] you should be able to subscribe to iTunes Match ($25/year), delete the songs from your computer, then redownload them in the DRM-free format. Not free, but probably cheaper to do that than to upgrade a bunch of songs one-by-one to the DRM-free format. Then you could drop the iTunes Match subscription.
Not a bad idea. I wonder if all of my previous purchases are still available in the store, though. Some distributers pulled out of the iTunes store when they dropped DRM.
I find it to be the most stable and usable of the platforms I've seriously tried (iOS, Android, Blackberry). That said, there are a few power user features I like that aren't allowed by default:
* F.lux
* FakeClockUp (to decrease animation times)
* Adblock
* Themes (because after 6 years of using them, smartphones look a bit boring)
I could get these on Android, but generally find that I must then sacrifice on form factor (I don't like very large phones), stability, build quality (this is getting better on Android though), and ease of use (Facetime with family, iMessage, etc.).
In the end it's not a single killer feature, but tight integration with my life. I might be able to do this all on Android, but it would take more time and probably more maintenance.
1) Vender lockdown & habits - I've been using an since the second iPod Touch (as a PDA). I'm not ready/eager to change "my workflow".
2) Accessibility - iOS (and the mac os) has had some the best (or at least easiest to setup) accessibility support. I'd be happy to be wrong about this but Androids documentation is either really lacking on these features or the features aren't there.
You're absolutely right. The accessibility features are lightyears better on iOS. This means that far more people with visual impairments are using iOS and thus more apps are being developed for the blind on iOS than other platforms. It's a pretty virtuous cycle :)
I had to switch from an iPhone to a Galaxy S4 for a trip recently. Though there were some upsides, I lost count of how many points of inferiority and annoyance I noted while using it. I'm more than a little biased, but if I can have both what I perceive as a far better phone and openness, I don't want to settle for one or the other.
Then again, I haven't used a jailbreak for anything significant in a long time, so for me, the openness is more in theory.
TouchWiz is terrible. It's bloated, riddled with security holes, and doesn't follow the android UI guidelines. Users with TouchWiz are missing out on the the majority of design improvements android has had in the last 3 years.
Try out an AOSP based build (maybe the ROM from the google play edition?) on your phone. It's like night and day.
Swype sucks if you use a lot of acronyms. Most of my work emails involve such. The iOS keyboard is really good at hunt/peck typing which is what's needed for such terse communications.
Swype causes keyboard popup delay of several hundred milliseconds on my N5. I stopped using it after 3 days.
Also what's with the default throb on key press in Android? Why would anyone find that useful?
Obviously you're right on a practical level: if you want to have a phone you can hack there are far better alternatives. That said, I think part of the principle here is that all devices should be hackable, and doing so can be fun for those involved and maybe improve life for some stuck using these things. I won't be writing them a check, but I don't think it's a pointless cause either.
There are a number of reasons I prefer iOS to the alternatives (mostly the quality of the third-party app ecosystem).
There are a number of reasons I like the flexibility afforded by a more open system than an out-of-the-box iPhone (from my pre-iOS 7 jailbroken days, mostly F.lux and being able to set non-Apple apps as default handlers for links/maps/etc).
For me, the former list is more compelling than the latter, so I'll happily keep using a non-jailbroken iPhone rather than switch to Android/Windows Phone/etc.
While there’s still about zero percent chance of it happening in the near term, I have to think that long-term, Apple will port Gatekeeper to iOS. It’s a near-ideal balance of security on OS X: Non-technical users can stay in the walled garden of the Mac App Store, semi-technical users can allow signed binaries, and power users can run whatever they want.
I work in the mobile healthcare space, and right now, we’re starting to move away from iOS as a platform for future projects because of the restrictions and hassle of the App Store. We’re not making 99-cent games and artisan to-do lists, so the fact that iPhone users are far more likely to spend money on apps doesn’t matter to us – we need a platform that lets us communicate with medical devices and display information for healthcare professionals without a mercurial third party deciding what we can and can’t do.
I also make mobile medical software. When we evaluated potential tablets three years ago, all the available android tablets were pretty terrible. Especially since we wanted to prevent long-term lock-in by writing most of our application as Javascript / HTML5. iPad was very far ahead in Javascript & HTML rendering performance.
Android seems to have caught up quite a bit, but now we have momentum behind iOS. We could switch without too much difficulty, but we're in no rush to start supporting a second platform.
because the consideration was "oh, everybody has and is familiar with iOS devices, we'll waste less time training them and they won't make as much mistake poking around."
This is exactly my problem. I have an iPad 2. I know that if I move off iOS5 I have to move to iOS7, which really wasn't designed with the iPad 2 in mind.
I'm now stuck between a rock and a hard place. Stay where I am and many apps (like Spotify which I pay for) no longer work, or upgrade to iOS7 and know that the iPad 2 just isn't powerful to run it in the same way in runs iOS5 (for which it was designed for).
I'm desperately waiting for a jailbreak so I can install iOS6, which I see as a half way house.
The reality is that Apple are deliberately degrading older devices, in order to make them obsolete. Of course I understand they are just building software that is designed to run on the most current and powerful of their devices, but the deliberate prevention of installs of older iOS versions when a user specifically wants it is frustrating.
In hindsight I shouldn't have bought an iPad, but there wasn't a viable alternative at the time.
I'd tend to disagree with your assessment of iOS' performance on the iPad 2. I have an iPad Air and an iPad 2 and quite frankly the iPad 2 crashes less and runs more consistently on iOS 7, as opposed to my Air. It feels as though iOS 7 wasn't ready for the Air, but it has been improving with each update.
> Non-technical users can stay in the walled garden of the Mac App Store, semi-technical users can allow signed binaries, and power users can run whatever they want.
As the signed binary and app store only is the default, it's unlikely that non-technical users will actually change it.
GateKeeper will not arrive on iOS, rather the converse will happen. Apple will lock down OSX. You will need a developer license to install 'non-approved' software. The success of iOS has demonstrated to them that people like velvet handcuffs. If you have any interest in open platforms you should not be giving Apple your money, and should be doing what you can to explain the dangers to others.
See, that’s what FOSS zealots keep telling me, but I don’t buy it. The day Apple jails the Mac is the day they turn OS X into OS Xcode, because that’s the only professional software people will use on it anymore.
Adobe, Autodesk, Microsoft, and other enterprise companies will never agree to a 30% Apple cut for their Mac software, and Apple will never allow their kludgily-accreted codebases onto the App Store. Apple’s executive team may have the balls to cut all these companies out of the platform, but they’re not stupid.
I bother for two main reasons. Firstly, I vastly prefer the hardware of iOS devices over the competitors. Secondly, the software openness isn't that big of a deal—I still prefer stock (non-jailbroken) iOS to stock Android (I confess that I haven't extensively tried Windows RT or any other alternatives).
Jailbroken iOS is just icing on the cake. When there's a major iOS upgrade that causes me to lose my jailbreak, I lose a few niceties (the biggest of which is the ability to "try," as in pirate, applications), but it's not a big deal.
I like the iOS ecosystem, as well the OS X ecosystem. I like Mac products. I have a Macbook Pro. I do all sorts of hacks on it, because OS X is not locked down. I don't see why I can't do the same on iOS. I don't want to use Android or others.
I think we've transitioned into a world where no one can assume that a given device/OS combination will be jailbroken in just a few months. The state of the art of security for physical devices will be good enough, such that only used equipment and older versions will be jailbroken.
Y'know, I finally got an iPhone (a 4S), moving from Android and Meego (gosh I miss my N9...), and I thought I'd probably jailbreak to get the "freedom" I was missing. Instead, I installed iOS 7, and it does nearly everything I want it to do.
It's not perfect, I'd like to be able to load FOSS onto it without going through the app store (I don't trust TOR browsers in a marketplace like that), and a few UI niggles, but for the most part I now just use my phone for phone tasks, Siri to dump stuff into Reminders for processing later, and playing Poker on the go. I was as surprised as anyone; I've been hacking smartphones since the Sony Ericsson M600i!
Just pitched in $10. I'll agree with previous comments that the reason for jailbreaking has decreased in recent years, but I'll be damned if I don't want root access on my phone. There's a level of control I've come to appreciate and desire as I code and deploy software, and I'd like that to extend to the one device I use the most in my life. The reason for me, at least, is "freedom," even if idealized and largely inconsequential. It's the spirit of the matter.
I'm not anti JB or anything, and used to JB my devices all the time but for the most part iOS has changed a lot since the early days and like others I find I don't need to JB to use it how I want now.
I do wish you could JB the last ATV version that has been out over a year for XBMC goodness. ATV2 is still one of the best XBMC devices out there but only support 720p.
> Jailbreaking is also critical to ensuring that the disabled are able to use their mobile devices as easily as possible.
This reason, while good and noble, feels really wonky. From what i understand, iOS's accessibility has much miles better then Android's accessibility options. If their main motives is to give a better mobile experience to people with special needs, maybe focusing on implementing these improvements system wide changes would be time better spend.
You work hard to make these changes then iOS 7.x.y comes out and the user updates by mistake and loses all the changes a jailbreak gives. It is this constant fighting with the system that has made staying with iOS less appealing these days.
Worrying about updates is a fact of everyday life for people dependent on accessibility features, on the OS as well as the APP level. Updates to apps often include changes to UI, which completely change the way blind users interact with the App via VoiceOver. This means that with every update there is a risk of the app no longer being accessible or having to relearn the entire interface.
It's true that Apple's accessibility features are miles better than Android's, but they aren't perfect. Jailbreaking allows people to add the functionality they need that isn't currently supported.
A great example of this is f.lux which is an amazingly useful app for people with low-vision, but is not supported on non-jailbroken devices.
Everything I've ever heard, including in this thread, says that iOS and its apps are still way ahead of Android and its apps in accessibility. I'm not very personally familiar with the accessibility on either so I can't say, but I'd be surprised if this has changed as radically as you say.
you should do some research then. for a blind person, IOS7 is unusable. while recent samsungs are almost fine... though i hate pretty much everything samsung did with android, the accessibility stuff was ok.
There are tons of blind and vision-impaired users using iOS 7 and a quick web search shows articles praising the improvements for those users. No doubt there are vision-impaired users who don't like it, too, but it's silly to make a blanket statement that it's unusable.
Why can't people be patient? Jailbreaks exist for iOS 7. Be patient, and it will be released sometime soon. iH8sn0w gave an ETA of before 2014. They're carefully picking when to release. Don't rush things.
Nobody here or on that site have any use for rooting (jailbreak is such a silly term). They just want to be cool.
Cory doctoraw, ifixit ceo... It's just a publicity stunt.
And everyone in this thread? They keep dumping their money happily on the latest device. Even though ios7 does zero more than a rooted ios6 (the only new feature that is not aesthetic is the control bar, which is better on ios6 with unofficial code anyway)
When I had an iPhone 4 I had a use for rooting: to run an ssh server so I could easily transfer files from/to my iphone without dealing with itunes or other special software.
However, it turned out that the real solution was just to switch to an Android phone that not only allows me to use my phone as a drive when plugged in, but also doesn't have the software restrictions that made running a daemon impossible in the first place.
I haven't really kept up with ios so this might not be a problem now, though.
Man, this takes me back to watching the Jailbreak community like a hawk back in like 2008 or something when I had an iPod touch and I was waiting for iOS 3 to be jailbroken. Man, those were some really fun times.
I can remember scanning the forums for hours, knowing that there would be a jailbreak soon, but not knowing when. I remember when the first untethered jailbreak got released, in all it's sketchy, poorly explained glory, and carefully going through the lengthy procedure to make it work.
Why does it matter if it's "open" or not? Stop trying to break other people's stuff already. We all want things our own way, so why not respect other people's ways as well.
The problem I have with this website is that it attempts to change the dynamics from one of "people who do things that are fun to make devices more open" to one of "people who do things to win cash prizes". Meanwhile, it changes the dynamics in the minds of the people contributing: normally, people contribute after the fact to the teams that built something that they found of value; under the model of this website, people contribute ahead of time, and then hope that the thing that is released works for their specific device, and if it doesn't they are kind of out of luck.
I've seen the effects of bounties in the Android ecosystem, and they are quite negative. I tried to explain this to the person behind this project (Elizabeth Stark), but she really didn't seem to care: in essence, she's currently working on a project that is a crowd funding platform for software, and she wants to use the iOS community as a test case; she didn't want to spend any time thinking about the ramifications of her decisions going into the project, and she didn't send me a response about the issues I saw with her project until this morning (coincident with the release of her website).
Hi Saurik, I'd love to hear your response to the substantive aspects of my email as opposed to an ad hominem attack. I didn't send it until this morning because I was sick and traveling for the holidays.
Look, claiming I made an ad hominem attack means that I said "X is bad because X was made by person Y and Y is bad". I did not do that: I stated first a concrete (yet highly summarized reason) why I felt that X was bad (specifically regarding incentive changing). I then also explained the reason behind the project (which is a property of X, not of Y), which I have multiple sources close to the project (including you) backing up (so it isn't like I'm lying or something: this isn't like someone claiming a study is flawed because the author is biased <- instead, I'm more like someone showing a study is flawed because the author actually stated they did the study for biased reasons). If you are going to throw around logical fallacies as weapons, as least know what they mean :(. (I will now provide more responses, but separately, as I felt the need to get this out more quickly as it was such a slap and people might not pay enough attention to realize it was wrong ;P.)
(Also, on the last point about when you sent the e-mail, which is the closest you can get in my comments to "ad hominem" and to me was a defense against why I wasn't more prepared for this: you were more than willing to get involved in a "synchronous conversation" with me at the time, which would have taken even longer and been even more difficult ;P.)
[Some context for others: when I first was responding to the idea of this bounty program, it was to someone else who had previously been considering working with Elizabeth; I was contacted in a kind of after-the-fact/"FYI" style. This was when the only real information was "bounty for iOS 7 jailbreak", without most of the extra restrictions that are now in place on the program, such as "open source". At the time, it for example seemed clear that evad3rs--the group that has been making the jailbreaks for the last two years--was going to get the bounty anyway. I already had started to bring up the incentive structure issues, and managed to get this other person to drop his involvement with the project. My original e-mail to Elizabeth thereby only talked about these issues, which is why this comment has to delve so deeply into the "final" point.]
So, your e-mail seems to make four points. The first point, taking up two paragraphs, is related to your career and your project. In these paragraphs, you did not address any of the specific example reasons I could come up with for why you were involved, and if anything simply raised a few more. These paragraphs, however, are largely ignorable.
The third point (setting off the second for a minute) was the argument made to attempt to address an incentive change on the side of the people building jailbreaks. This argument hinges on a specific example of a previous bounty, claiming that it did not cause the ramifications I am predicting.
> While I am sensitive to your concerns around community incentives, it’s unlikely that our approach will threaten them. For example, when Adafruit created a prize for open Kinect drivers, instead of devolving into a community of mercenaries, it enabled an ecosystem of Kinect hackers to flourish.[1]
The problem with this argument is that it is looking at entirely the wrong level: you are claiming that by having the driver for Kinect get constructed, people were able to start hacking on Kinect, causing an ecosystem on the other side of the driver to flourish. We already have that ecosystem on the other side of the jailbreak.
Instead, we are looking at the actual construction of the jailbreaks here; the correct analogy is to instead look at the market for construction of drivers for closed video game controllers. What you need to demonstrate is that a "success" for that crowd funding doesn't lead the people who were working on that driver to end up with different incentives, or cause other people watching to expect the same (again, in a "success" situation: I know people who work with Kinect, and I'd never heard the driver was crowd funded, so any community effects would be quite narrow due to the limited reach; likely as it was so little money).
FWIW, that people's incentives change in these situations is well documented: this isn't just my assertion, this is something you can read about in books like "Punished by Rewards". Given that a new jailbreak is needed at least once a year (and in a perfect world, would happen no less than twice a year), this is critical: you are playing an iterative game, and have to think about the ramifications on incentives not immediately, but a few steps ahead.
In reality, the community is already anticipating the release of an iOS 7 jailbreak (evad3rs has already publicly stated that they have all the pieces they need and are just working on implementing and finalizing). We (the community of people who use these jailbreaks: I do not build them myself) thereby are not in a position where this bounty is going to change anything: it is just going to change how funds are directed (5%, for example, will be given directly to your new company,...
"Finally" (in the aforementioned second point), your e-mail makes the argument for the jailbreak tool being open source. You feel like this "could open the doors to greater community contribution, encouraging larger groups of people to work together to solve the problems more quickly". The argument makes sense: if jailbreaking were secretive and closed (which is a bullet you dodged, btw: on Android, where bounties are common, jailbreak tools are not only often closed source but techniques are hoarded and under-described so as to win more bounties <- you actually need this open source clause to not fall into the obvious trap) people are not in a position to learn how all of the systems of Apple's device work in a way that would let them later build their own tools.
Would it surprise you to find out that most of the code in a jailbreak is already open source, and that the only parts that are not tend to be the GUI and the specific exploit technique for that one specific version of iOS?
- All of the libraries that are use to connect to the device in its normal mode are licensed under LGPL (they are part of a suite called libimobiledevice, which was primarily developed by members of the iPhone Dev Team, and now maintained by nikias from evad3rs).
- The libraries used to talk to the device in recovery and DFU mode are open source and licensed under GPL (developed by posixninja, who has been maintaining them recently under the openjailbreak project).
- The libraries used to decrypt and modify image files (kernels, devices trees, disks, and bootloaders) has been open source for years (developed and maintained by planetbeing from evad3rs). The same developer (planetbeing) has released a number of utility libraries like this, including ones to download portions of IPSW files from Apple's servers without having to download the whole file (this is why jailbreaks never need to distribute copyrighted content). All of this code is under GPL.
It is thereby not just useless but insulting that in your e-mail you make the point that "the jailbreaking teams
are not an island—they rely heavily on FOSS software in their work": the people who build these tools (which again, does not include myself) quite often release code for large or critical parts of their work, and almost exclusively do so under "free software" licenses.
In fact, many previous jailbreak tools have been or have become open source, and currently the tool to jailbreak the iPhone 4 on iOS 7 (opensn0w) is itself open source (under GPL). Now, one thing that is really interesting here: this project (which has now existed for years) actually tried to crowd fund itself (which, to be 100% clear, doesn't cause the same kinds of issues as a third-party bounty program) and failed. Out of its $3,000 it got $30.
This, of course, flies in the face of your comment that the goal is to set a precedent of jailbreaks being open source: and in case you think I'm playing up one example, the iOS 4 jailbreaks from comex were open source as well; the source code for both JailbreakMe 2.0 and JailbreakMe 3.0 were released (I believe fairly soon after the jailbreak, but clearly as this was all years ago "soon" is relative: there are tons of open source examples).
The team behind the tool greenpois0n (which includes the aforementioned posixninja) also open sourced much of their work as "syringe". The opensn0w tool in fact uses a lot of this code, as have been a number of third-party tools based on this older limera1n exploit (which, interestingly enough, was itself released to the community by geohot giving everyone a few lines of source cod...
You're missing the point here—we're grateful that people in the jailbreak community release things as FOSS, but the majority of jailbreaks as you yourself mention are not FOSS themselves, which is part of what motivated Chris, who proposed the prize, and myself.
It seems to me that that opensn0w campaign may have been fake (there are a lot of those on IndieGoGo).
And to be clear, in talking to friends in the security space, the auditing the code aspect was a huge concern, so I'm glad we can at least agree on something. :)
We're also planning on helping to fund many open hardware projects, and I'll actually be speaking at the SF Hardware Startup meetup tonight to solicit ideas from the community.
> You're missing the point here—we're grateful that people in the jailbreak community release things as FOSS, but the majority of jailbreaks as you yourself mention are not FOSS themselves, which is part of what motivated Chris, who proposed the prize, and myself.
In other places you've stated the reason he wanted this prize was to get software on his iPhone so he could help with some accessibility issues. This is an incentive that aligns with long-term open hardware, not short term open software. You can't have it both ways. If you are really dropping all of the incentive arguments I'm making and want to concentrate on open source, that's fine: but let's get our stories straight.
> It seems to me that that opensn0w campaign may have been fake (there are a lot of those on IndieGoGo).
I just contacted the developer of opensn0w: no, that was not fake, it just didn't take off. I personally can assert to you that opensn0w (which many people are using right now) is not itself a fake (and I'm one of the people who generally are asked to determine this ;P).
> And to be clear, in talking to friends in the security space, the auditing the code aspect was a huge concern, so I'm glad we can at least agree on something. :)
I talked about auditing changes, not auditing code, and I even explicitly stated that the code was not in any way a concern to someone who really knows what they are doing, so no: we don't really agree on this :/. I have on many occasions, in articles and talks, made the argument that open source is overrated, and that what really matters is open hardware: that in addition to the gap between source code and machine code decreasing over time due to better analysis tools and frameworks, that as long as hardware is capable of being closed off it doesn't matter how much of the code is open <- the iOS jailbreak community is at the front line of this particular battle.
> We're also planning on helping to fund many open hardware projects, and I'll actually be speaking at the SF Hardware Startup meetup tonight to solicit ideas from the community.
FWIW, having third-parties construct open hardware doesn't really help the cause of forcing large companies who make closed hardware to provide means of opening it; that said, I do appreciate that you have future goals, but it may have been more useful to start with them.
You're absolutely right that changing motivations from intrinsic to an extrinsic can have negative affects. I'm pretty sure there is a study that people paid a dollar to complete a crossword or some other word puzzle did worse than people who were asked to do it for no pay.
However, I think there are cases where extrinsic motivation can be beneficial. This campaign provides a good example.
Those with the programming skills necessary to jailbreak the iPhone may not be as intrinsically motivated to do so as the OS matures, and so they stop dedicated time. But these engineers are by no means the only people who might benefit from jailbreaking.
The disabled community is one such group. They, in general, may not have the skills necessary to write the software necessary to jailbreak their devices, but could benefit greatly if such software existed. Offering a bounty is a way for them to cross that skill gap.
These campaigns aren't meant for the benefit of software developers. They are for the benefit of those who have great ideas, but lack the skills to fulfill them.
Extrinsic motivation may not be the ideal condition, but that does not mean it is something that should be avoided.
To the extent to which I believe these are interesting arguments to have, I think that this should be discussed only after the intrinsic motivation has failed; as it stands, it is my understanding that a jailbreak is coming from evad3rs in the near future: planetbeing has already stated that they have what they need, and they are just working on integration and support for all devices (which is a lot of busywork). As for getting paid, they actually do get a good number of after-the-fact donations, but that is a drastically different kind of expectation from the users giving the donations, as well as a drastically different kind of mentality that goes behind the developer (as even if all you cared about was money, you aren't shopping for large sums ahead-of-time).
To our knowledge, no one was working on an open source jailbreak, and given that the site I'm building is designed to incentivize things like free and open source software, this was a huge component. I've also been told there are a good number of people that have jailbreaks, and it's possible that they might be motivated to release it as FOSS if enough funds are raised.
And it's not like anything is keeping evad3rs from getting donations if they release a closed source jailbreak, or even if they or anyone else releases a FOSS one and claims the prize (in fact with other related campaigns, lots of donations came in after the fact).
> To our knowledge, no one was working on an open source jailbreak...
(responded to elsewhere, maybe with more emphasis on openjailbreak.org)
> ...and given that the site I'm building is designed to incentivize things like free and open source software, this was a huge component. I've also been told there are a good number of people that have jailbreaks, and it's possible that they might be motivated to release it as FOSS if enough funds are raised.
I believe my response to this notion (when it was brought up by the other person who contacted me about your bounty a few weeks ago) was that you would be better off then attempting to do this for a later version of iOS, as the kinds of numbers that had been thrown around as "the magic number" to make that happen was hundreds of thousands of dollars... it will take a lot of time and a lot of really hungry users that don't see jailbreaks (open or closed) on the horizon, to generate that kind of money. Releasing this now kind of calls that goal into question: that goal incentivizes waiting.
I'd also add that creating a cash incentive enables you to encourage an open sourced jailbreak, which is doubly important in this case since given all the opportunities for a jailbreak to introduce malicious code
111 comments
[ 3.0 ms ] story [ 203 ms ] threadAnd yet Pingit is still in the app store. https://itunes.apple.com/gb/app/barclays-pingit/id496552142
Case in point: When I plug my iPhone 5 into my car's USB port, the Music app's display changes to an "Accessory Connected" splash screen. I can only control my music through my car's awful dashboard interface. Jailbreaking allows me to disable that splash screen.
Other things like 5 column springboard/dock, FakeClockUp (reduce or speed up slow animations), and BiteSMS (Messages app replacement that can be used on the lock screen), are just minor interface and functionality tweaks that, together, make my jailbroken iOS6 a far superior UX than iOS7.
Is it because you are forced to use an iPhone by external factors, like your employer? Are there critical features missing from Android and all the others? Is it just your personal preference?
I really don't mean to offend anyone, it's just that I perceive the closed ecosystem of the iPhone as an intentional "feature" and as I personally don't like it, I would never put my money into such a closed system just to try to jailbreak it afterwards.
Oh, and the main reason? 'cause we can :)
Your argument about Mac integration seems valid, I did not think about it as I am no mac user :)
2. insert other end into ipad
3. get a dialog "trust this computer"
4. click "trust"
5. goto 3.
#*@! you apple.
After two years I am still using this old Atrix. I might switch to Nexus one day if I had the budget for it. iPhone isn't my cake so I'd passed on. But I have to praise a closed system like iOS - update is great. No fragmentation.
Why would I buy into an ecosystem that then forces me to hope someone far smarter than I is able to break the security of that system for me? Jailbreaks are worrisome because they introduce a potential loss of security on mine, and all users phones.
/sarc
I put a SIM connected to one of T-Mobile's $30/5GB prepaid accounts in my iPhone 5. When I try to turn the tethering function on, I get a prompt telling me to go to a T-Mobile website to get on a plan that supports tethering.
The carrier control of tethering made sense back before the iPhone had market dominance. Now it's stupid and user-hostile.
I could get these on Android, but generally find that I must then sacrifice on form factor (I don't like very large phones), stability, build quality (this is getting better on Android though), and ease of use (Facetime with family, iMessage, etc.).
In the end it's not a single killer feature, but tight integration with my life. I might be able to do this all on Android, but it would take more time and probably more maintenance.
1) Vender lockdown & habits - I've been using an since the second iPod Touch (as a PDA). I'm not ready/eager to change "my workflow".
2) Accessibility - iOS (and the mac os) has had some the best (or at least easiest to setup) accessibility support. I'd be happy to be wrong about this but Androids documentation is either really lacking on these features or the features aren't there.
Then again, I haven't used a jailbreak for anything significant in a long time, so for me, the openness is more in theory.
I blame TouchWiz primarily, as my fiancees N4 and my N5 are both an absolute dream to use.
So perhaps one of the things in Apple's favor here is the unified UI across all devices.
Try out an AOSP based build (maybe the ROM from the google play edition?) on your phone. It's like night and day.
The bluetooth connection seems a bit better, and the screen is bigger, but usability wise, iOS7 is better.
I don't want most of the customizability (i.e., separate home screens/themes) and the keyboard is simply harder to use than iOS.
The whole OS feels laggy (still) even with almost-comparable hardware to the latest-get iPhone.
The only reason I want jailbreak is for something like F.lux/Twilight on iOS.
... it is 2013... get with the program and use Swype. It is impossible to go back.
Swype causes keyboard popup delay of several hundred milliseconds on my N5. I stopped using it after 3 days.
Also what's with the default throb on key press in Android? Why would anyone find that useful?
There are a number of reasons I like the flexibility afforded by a more open system than an out-of-the-box iPhone (from my pre-iOS 7 jailbroken days, mostly F.lux and being able to set non-Apple apps as default handlers for links/maps/etc).
For me, the former list is more compelling than the latter, so I'll happily keep using a non-jailbroken iPhone rather than switch to Android/Windows Phone/etc.
I work in the mobile healthcare space, and right now, we’re starting to move away from iOS as a platform for future projects because of the restrictions and hassle of the App Store. We’re not making 99-cent games and artisan to-do lists, so the fact that iPhone users are far more likely to spend money on apps doesn’t matter to us – we need a platform that lets us communicate with medical devices and display information for healthcare professionals without a mercurial third party deciding what we can and can’t do.
Android seems to have caught up quite a bit, but now we have momentum behind iOS. We could switch without too much difficulty, but we're in no rush to start supporting a second platform.
Apple's solution for running business apps and distributing them outside the app store is actually not that bad.
I'm now stuck between a rock and a hard place. Stay where I am and many apps (like Spotify which I pay for) no longer work, or upgrade to iOS7 and know that the iPad 2 just isn't powerful to run it in the same way in runs iOS5 (for which it was designed for).
I'm desperately waiting for a jailbreak so I can install iOS6, which I see as a half way house.
The reality is that Apple are deliberately degrading older devices, in order to make them obsolete. Of course I understand they are just building software that is designed to run on the most current and powerful of their devices, but the deliberate prevention of installs of older iOS versions when a user specifically wants it is frustrating.
In hindsight I shouldn't have bought an iPad, but there wasn't a viable alternative at the time.
As the signed binary and app store only is the default, it's unlikely that non-technical users will actually change it.
Isn't that Apple?
Adobe, Autodesk, Microsoft, and other enterprise companies will never agree to a 30% Apple cut for their Mac software, and Apple will never allow their kludgily-accreted codebases onto the App Store. Apple’s executive team may have the balls to cut all these companies out of the platform, but they’re not stupid.
Yes, this one for me. Audio latency and all the music making apps that iOS has.
Yes, this one applies for me. Low-latency audio and all the music making apps that iOS has.
Jailbroken iOS is just icing on the cake. When there's a major iOS upgrade that causes me to lose my jailbreak, I lose a few niceties (the biggest of which is the ability to "try," as in pirate, applications), but it's not a big deal.
It's not perfect, I'd like to be able to load FOSS onto it without going through the app store (I don't trust TOR browsers in a marketplace like that), and a few UI niggles, but for the most part I now just use my phone for phone tasks, Siri to dump stuff into Reminders for processing later, and playing Poker on the go. I was as surprised as anyone; I've been hacking smartphones since the Sony Ericsson M600i!
I do wish you could JB the last ATV version that has been out over a year for XBMC goodness. ATV2 is still one of the best XBMC devices out there but only support 720p.
This reason, while good and noble, feels really wonky. From what i understand, iOS's accessibility has much miles better then Android's accessibility options. If their main motives is to give a better mobile experience to people with special needs, maybe focusing on implementing these improvements system wide changes would be time better spend.
You work hard to make these changes then iOS 7.x.y comes out and the user updates by mistake and loses all the changes a jailbreak gives. It is this constant fighting with the system that has made staying with iOS less appealing these days.
It's true that Apple's accessibility features are miles better than Android's, but they aren't perfect. Jailbreaking allows people to add the functionality they need that isn't currently supported.
A great example of this is f.lux which is an amazingly useful app for people with low-vision, but is not supported on non-jailbroken devices.
Absolutely no way I'd use a phone with regular lighting now.
But anyone with visual disability will still have to scavenge for a phone with actual buttons. And good luck with that...
You're right, all the people working on it are amazing and deserve more accolades and less heckling.
Cory doctoraw, ifixit ceo... It's just a publicity stunt.
And everyone in this thread? They keep dumping their money happily on the latest device. Even though ios7 does zero more than a rooted ios6 (the only new feature that is not aesthetic is the control bar, which is better on ios6 with unofficial code anyway)
However, it turned out that the real solution was just to switch to an Android phone that not only allows me to use my phone as a drive when plugged in, but also doesn't have the software restrictions that made running a daemon impossible in the first place.
I haven't really kept up with ios so this might not be a problem now, though.
I can remember scanning the forums for hours, knowing that there would be a jailbreak soon, but not knowing when. I remember when the first untethered jailbreak got released, in all it's sketchy, poorly explained glory, and carefully going through the lengthy procedure to make it work.
Aaaahhhhh memories...
I've seen the effects of bounties in the Android ecosystem, and they are quite negative. I tried to explain this to the person behind this project (Elizabeth Stark), but she really didn't seem to care: in essence, she's currently working on a project that is a crowd funding platform for software, and she wants to use the iOS community as a test case; she didn't want to spend any time thinking about the ramifications of her decisions going into the project, and she didn't send me a response about the issues I saw with her project until this morning (coincident with the release of her website).
(Also, on the last point about when you sent the e-mail, which is the closest you can get in my comments to "ad hominem" and to me was a defense against why I wasn't more prepared for this: you were more than willing to get involved in a "synchronous conversation" with me at the time, which would have taken even longer and been even more difficult ;P.)
So, your e-mail seems to make four points. The first point, taking up two paragraphs, is related to your career and your project. In these paragraphs, you did not address any of the specific example reasons I could come up with for why you were involved, and if anything simply raised a few more. These paragraphs, however, are largely ignorable.
The third point (setting off the second for a minute) was the argument made to attempt to address an incentive change on the side of the people building jailbreaks. This argument hinges on a specific example of a previous bounty, claiming that it did not cause the ramifications I am predicting.
> While I am sensitive to your concerns around community incentives, it’s unlikely that our approach will threaten them. For example, when Adafruit created a prize for open Kinect drivers, instead of devolving into a community of mercenaries, it enabled an ecosystem of Kinect hackers to flourish.[1]
[1]: https://www.adafruit.com/blog/2010/11/04/the-open-kinect-pro...
The problem with this argument is that it is looking at entirely the wrong level: you are claiming that by having the driver for Kinect get constructed, people were able to start hacking on Kinect, causing an ecosystem on the other side of the driver to flourish. We already have that ecosystem on the other side of the jailbreak.
Instead, we are looking at the actual construction of the jailbreaks here; the correct analogy is to instead look at the market for construction of drivers for closed video game controllers. What you need to demonstrate is that a "success" for that crowd funding doesn't lead the people who were working on that driver to end up with different incentives, or cause other people watching to expect the same (again, in a "success" situation: I know people who work with Kinect, and I'd never heard the driver was crowd funded, so any community effects would be quite narrow due to the limited reach; likely as it was so little money).
FWIW, that people's incentives change in these situations is well documented: this isn't just my assertion, this is something you can read about in books like "Punished by Rewards". Given that a new jailbreak is needed at least once a year (and in a perfect world, would happen no less than twice a year), this is critical: you are playing an iterative game, and have to think about the ramifications on incentives not immediately, but a few steps ahead.
In reality, the community is already anticipating the release of an iOS 7 jailbreak (evad3rs has already publicly stated that they have all the pieces they need and are just working on implementing and finalizing). We (the community of people who use these jailbreaks: I do not build them myself) thereby are not in a position where this bounty is going to change anything: it is just going to change how funds are directed (5%, for example, will be given directly to your new company,...
"Finally" (in the aforementioned second point), your e-mail makes the argument for the jailbreak tool being open source. You feel like this "could open the doors to greater community contribution, encouraging larger groups of people to work together to solve the problems more quickly". The argument makes sense: if jailbreaking were secretive and closed (which is a bullet you dodged, btw: on Android, where bounties are common, jailbreak tools are not only often closed source but techniques are hoarded and under-described so as to win more bounties <- you actually need this open source clause to not fall into the obvious trap) people are not in a position to learn how all of the systems of Apple's device work in a way that would let them later build their own tools.
Would it surprise you to find out that most of the code in a jailbreak is already open source, and that the only parts that are not tend to be the GUI and the specific exploit technique for that one specific version of iOS?
- All of the libraries that are use to connect to the device in its normal mode are licensed under LGPL (they are part of a suite called libimobiledevice, which was primarily developed by members of the iPhone Dev Team, and now maintained by nikias from evad3rs).
- The libraries used to talk to the device in recovery and DFU mode are open source and licensed under GPL (developed by posixninja, who has been maintaining them recently under the openjailbreak project).
- The libraries used to decrypt and modify image files (kernels, devices trees, disks, and bootloaders) has been open source for years (developed and maintained by planetbeing from evad3rs). The same developer (planetbeing) has released a number of utility libraries like this, including ones to download portions of IPSW files from Apple's servers without having to download the whole file (this is why jailbreaks never need to distribute copyrighted content). All of this code is under GPL.
It is thereby not just useless but insulting that in your e-mail you make the point that "the jailbreaking teams are not an island—they rely heavily on FOSS software in their work": the people who build these tools (which again, does not include myself) quite often release code for large or critical parts of their work, and almost exclusively do so under "free software" licenses.
In fact, many previous jailbreak tools have been or have become open source, and currently the tool to jailbreak the iPhone 4 on iOS 7 (opensn0w) is itself open source (under GPL). Now, one thing that is really interesting here: this project (which has now existed for years) actually tried to crowd fund itself (which, to be 100% clear, doesn't cause the same kinds of issues as a third-party bounty program) and failed. Out of its $3,000 it got $30.
http://www.indiegogo.com/opensn0w
This, of course, flies in the face of your comment that the goal is to set a precedent of jailbreaks being open source: and in case you think I'm playing up one example, the iOS 4 jailbreaks from comex were open source as well; the source code for both JailbreakMe 2.0 and JailbreakMe 3.0 were released (I believe fairly soon after the jailbreak, but clearly as this was all years ago "soon" is relative: there are tons of open source examples).
http://www.idownloadblog.com/2011/07/19/jailbreakme-now-open...
The team behind the tool greenpois0n (which includes the aforementioned posixninja) also open sourced much of their work as "syringe". The opensn0w tool in fact uses a lot of this code, as have been a number of third-party tools based on this older limera1n exploit (which, interestingly enough, was itself released to the community by geohot giving everyone a few lines of source cod...
It seems to me that that opensn0w campaign may have been fake (there are a lot of those on IndieGoGo).
And to be clear, in talking to friends in the security space, the auditing the code aspect was a huge concern, so I'm glad we can at least agree on something. :)
We're also planning on helping to fund many open hardware projects, and I'll actually be speaking at the SF Hardware Startup meetup tonight to solicit ideas from the community.
In other places you've stated the reason he wanted this prize was to get software on his iPhone so he could help with some accessibility issues. This is an incentive that aligns with long-term open hardware, not short term open software. You can't have it both ways. If you are really dropping all of the incentive arguments I'm making and want to concentrate on open source, that's fine: but let's get our stories straight.
> It seems to me that that opensn0w campaign may have been fake (there are a lot of those on IndieGoGo).
I just contacted the developer of opensn0w: no, that was not fake, it just didn't take off. I personally can assert to you that opensn0w (which many people are using right now) is not itself a fake (and I'm one of the people who generally are asked to determine this ;P).
> And to be clear, in talking to friends in the security space, the auditing the code aspect was a huge concern, so I'm glad we can at least agree on something. :)
I talked about auditing changes, not auditing code, and I even explicitly stated that the code was not in any way a concern to someone who really knows what they are doing, so no: we don't really agree on this :/. I have on many occasions, in articles and talks, made the argument that open source is overrated, and that what really matters is open hardware: that in addition to the gap between source code and machine code decreasing over time due to better analysis tools and frameworks, that as long as hardware is capable of being closed off it doesn't matter how much of the code is open <- the iOS jailbreak community is at the front line of this particular battle.
> We're also planning on helping to fund many open hardware projects, and I'll actually be speaking at the SF Hardware Startup meetup tonight to solicit ideas from the community.
FWIW, having third-parties construct open hardware doesn't really help the cause of forcing large companies who make closed hardware to provide means of opening it; that said, I do appreciate that you have future goals, but it may have been more useful to start with them.
However, I think there are cases where extrinsic motivation can be beneficial. This campaign provides a good example.
Those with the programming skills necessary to jailbreak the iPhone may not be as intrinsically motivated to do so as the OS matures, and so they stop dedicated time. But these engineers are by no means the only people who might benefit from jailbreaking.
The disabled community is one such group. They, in general, may not have the skills necessary to write the software necessary to jailbreak their devices, but could benefit greatly if such software existed. Offering a bounty is a way for them to cross that skill gap.
These campaigns aren't meant for the benefit of software developers. They are for the benefit of those who have great ideas, but lack the skills to fulfill them.
Extrinsic motivation may not be the ideal condition, but that does not mean it is something that should be avoided.
And it's not like anything is keeping evad3rs from getting donations if they release a closed source jailbreak, or even if they or anyone else releases a FOSS one and claims the prize (in fact with other related campaigns, lots of donations came in after the fact).
(responded to elsewhere, maybe with more emphasis on openjailbreak.org)
> ...and given that the site I'm building is designed to incentivize things like free and open source software, this was a huge component. I've also been told there are a good number of people that have jailbreaks, and it's possible that they might be motivated to release it as FOSS if enough funds are raised.
I believe my response to this notion (when it was brought up by the other person who contacted me about your bounty a few weeks ago) was that you would be better off then attempting to do this for a later version of iOS, as the kinds of numbers that had been thrown around as "the magic number" to make that happen was hundreds of thousands of dollars... it will take a lot of time and a lot of really hungry users that don't see jailbreaks (open or closed) on the horizon, to generate that kind of money. Releasing this now kind of calls that goal into question: that goal incentivizes waiting.