Hence the hard swallowing.

Disabling the root user again with

  dsenableroot -d

does not re-enable the exploit

I wonder how many sperm or egg donors will register on 23andme and receive an interesting email... Or how many children conceived in that way will find half brothers and half sisters. I wonder if you could see traces of "prolific" sperm donors via their related offspring...

http://www.nytimes.com/2011/09/06/health/06donor.html?pagewa... and http://www.foxnews.com/health/2014/01/24/more-children-from-...

I have also had a simple app rejected, then approved once some complexity was added. It was a totally silly app that was pretty much an exercise in what exactly they would accept as the simplest app. (https://itunes.apple.com/us/app/iuplift/id469338399)

Initially, the app was just showing canned upifting phrases. This was rejected. Second submission allowed the user to add their own phrases, using some native controls to show/edit this list of phrases. This was accepted.

What I would suggest is perhaps adding something like a way to manage different collect links in the app. Keep track of which photos you have sent to a collect. They seem to also love you to do things that are not easy to do in a web app. Maybe if you added camera access from within the app (useless I know, but still), maybe image cropping etc before upload? Is there metadata attached to their submissions to the collect link? Perhaps allowing them to edit this metadata in a table view.

I think you need to come up with reasons why you can't just make it a web app and want it to be an app (why do you want that anyway?) and be sure to implement those things.

My reasons for wanting my apps to be apps and not web sites is because phone apps are cool and people want an app not a website - it seems weird to me that apple do not think the same way. I understand they don't want any more fart apps, but most phone apps could be reasonably done as web apps now anyway.

> What I would suggest is perhaps adding something like a way to manage different collect links in the app.

Good idea.

> Keep track of which photos you have sent to a collect.

We are already doing this in the app. But maybe doing it for the multiple "collect"s that we're tracking might help.

This. The tech described is pretty neat... Give you my email creds? Hell no. But _I_ could do all that myself. I think that would be one way that linkedin could save this - release an easy to set up open source version, say one click to a heroku instance or something. Then one could add all sorts of smart stuff into their own emails.

Agreed. Imagine if you could have other providers snap into this? It's a shame that they're hacking their way around Apple's walled garden, but a self hosted proxy server is a nifty way to add functionality to email.

What could they do about it? Not allow you to create a mail account that points to linkedin.com as the server?

Apple could yank the certificate that LinkedIn is using for configuration profiles, which would make installation significantly more difficult for the average user.

Apple, to my knowledge, has never revoked a single cert for config profiles since they're rarely used outside of the mobile dev market.

Any examples of them doing what you have proposed?

There is really no Apple approval to be given or not given here. It is really just creating a new email account. There is no real way that Apple could stop them from doing this if they wanted to. It is up to you if you tell linkedin your email credentials. I would certainly not recommend it, even without their track record.

It's pretty easy to convince yourself that "* with the type" is wrong when you see this:

int* a, b; // a is int* but b is int

Bingo, that's the exact reason to pair the asterisk with the variable name. Especially in C-family languages where you can actually end up with code that compiles and even works, until it breaks. Think pointer arithmetic on something you assume is a pointer to a signed integer...