defap

8 ms·

31.
by defap 13y ago
If the secret part of an asymmetric key is generated on a device and it lives and dies on that device, Apple doesn't have it -- the device does. Messages encrypted using the public part of that key can only be decrypted with a device
32.
by defap 13y ago
This doesn't make sense. The effectiveness of the spear-fishing attack had nothing to do with Gatekeeper. Signing the app with an Apple ID provided for a straight-forward way to disable the attack, which made Gatekeeper a pure win.
33.
by defap 14y ago
Sure, but if the app hasn't been submitted, then what is there to discuss with Apple? What is he talking about?
34.
by defap 14y ago
You don't base it solely on that, either. Price is determined by the imbalance of buy and sell orders. Investors might decide to buy or sell based on a multitude of factors, including but not limited to earnings and growth potential.
35.
by defap 14y ago
> I guess a couple of the Safari team dudes have started blogging Both stories are from the same person.
36.
by defap 14y ago
Pointless? You seem too caught up in the meaning of the word 'blame'. Maybe you should think of it as 'annotate', instead. There are plenty of times where I want to find the changeset that last touched a line of code so I can read its commi
37.
by defap 14y ago
Some used this same argument to suggest that Google wouldn't want to ship an iOS Google Maps app, and yet, lo and behold, it shipped two weeks ago to great fanfare. To think that Google would not want to participate in an ecosystem as large
38.
by defap 14y ago
If the machine is as unserviceable as you claim, then the increased reliability is indeed an advantage (or at least a mitigation). I'm not sure I see the irony.
39.
by defap 14y ago
Apple has used the term HI for a long, long time.
40.
Amazon's Play(daringfireball.net)
226 points by defap 14y ago|114 comments
41.
by defap 14y ago
Sure. I was more responding to the claim that shared_ptr should always be preferred to auto_ptr. I agree that scoped/unique_ptr fixed a lot if auto_ptr's pitfalls.
42.
by defap 14y ago
Before the days of std::move, auto_ptr's copy modeled an ownership-transfer semantic in a more efficient way than could be accomplished by shared_ptr (no refcount churn). It wasn't broken; one must have simply known when it was appropriate