Hi, op here, I'm actually working on a hosted solution right now making use of a set of physical Macs and fast user switching. Hoping to have something to show for it in the next several weeks!
I think this is one of those projects we all think about doing, then realize an Apple ID is way too critical to a Mac / iPhone user's security (remote wipe anyone?) to let a third party authenticate with it.
It would be really handy as something I could run on my own mac.
Yeah, the service will essentially be a man in the middle on the account, and I believe it will be very important to communicate that with users. I'll think about releasing a standalone "server" app based on the code although I've already built something somewhat similar (although even "clunkier" if you can imagine that) here: https://github.com/CamHenlin/imessageservice
> Yeah, the service will essentially be a man in the middle on the account, and I believe it will be very important to communicate that with users.
No, it will be very important not to do it, because you are knowingly busting security open on Apple IDs with your service and think that educating users is the best way to mitigate that. We all know most of your users won't know any better. The better way to mitigate it is to not accept Apple IDs in the first place.
If you launch that service, I would feel obligated to tip off the iCloud folks that you're knowingly compromising Apple IDs. That isn't because I want to see you fail, but because you are compromising Apple IDs and your users are caught in the middle.
This is an idea you should let go. I know that sucks to hear.
I generally hate posts that are just a +1 to something, but I feel your point is important enough that it needs echoing. I as well will do the same as you if I see a service like this.
