User:Mstone/Rainflow
Carrying on the tradition of naming software via puns, I'll lay down some thoughts on how to answer the question:
- When should our software automatically do risky thing X?
Background
People have been concerned with this question (and with variants and related questions) for some time:
- <trac>5657</trac>, on spoofing-resistant update algorithms for de-isolated activities
- questions on activity signing and update thread
- activity semantics conversation
- runtime build customization thread and <trac>6432</trac>
- user-created activities and updates thread
- horizontal distribution thread
- homunq's ideas on bundles and updates
the devil is truly in the details.
Consequently, here's an attempt at details.
