3 ms·
- Developer was hacked and is unaware of it. - Developer accidentally clicked "revoke my cert" (no idea if that's a real button, but that's not the point). -
by ballenf 6y ago
- Developer was hacked and is unaware of it.
- Developer accidentally clicked "revoke my cert" (no idea if that's a real button, but that's not the point).
- A national security agency sent one of those scary letters preventing Apple from speaking but requiring the action.
- Developer had a mental breakdown and has lost grip on reality.
- Developer realized app was infected with malware and ...
Truth is stranger than fiction, so it's actually really hard to think of all the possible strange explanations. Which is why it seems imminently reasonable to take a wait and see approach at least for a reasonable period of time.
- gruez 6y ago> - Developer was hacked and is unaware of it. If that's the case why wasn't that communicated to him? >- Developer accidentally clicked "revoke my cert" (no idea if that's a real button, but that's not the point). >- Developer had a mental breakdown and has lost grip on reality. While these are possible, they seem very unlikely. Compare the numerous cases of Big Tech silently revoking people's account with no notice or appeal, to the number of times that someone made a public announcement, and then went "nvm it was me lol".
- ilikehurdles 6y agoBig Tech is not a monolithic entity and citing cases across different entities may not be an appropriate way to compare these issues. Asking for patience while both sides have a chance to explain the situation is reasonable. Also, whenever you suggest something is "very unlikely," keep in mind that this likelihood is one instance in the context of 20 million developers. Are you suggesting it's like a 1 out of 100 chance, or a 1 out of 20 million chance?
- LorenPechtel 6y agoYou first case is the first thing that came to mind--his certificate was found to have signed malware. They would revoke without notice in such a situation.