Yea, what should happen is that you should preview before anything get's posted. The Geary contract should show the compose window, the Twitter contract should show the Tweet window, etc.
There's nothing we can really do on the Contractor side that really prevents anyone from executing those binaries. On Wed, Jul 18, 2012 at 12:32 PM, Allen Lowe <[email protected]> wrote: > well, considering that the contract just uses an existing command line > interface, they could already do that anyway just as easily. > > > Allen Lowe > > > On Wed, Jul 18, 2012 at 12:09 PM, Sergey "Shnatsel" Davidoff > <[email protected]> wrote: > > In addition to the aforementioned doc with requested changes, voldyman > > drafted a doc that describes how the whole thing is expected to work. > Here > > it is: > > > https://docs.google.com/document/d/1SxrUvlZpbNzjrelfxMljAzwJxR3hvWRbSqQehsK4wl8/edit# > > > > He also makes a valid point about preventing contract misuse, e.g. a > > malicious app could try to post things to your Twitter without you even > > knowing. > > > > -- > > Sergey "Shnatsel" Davidoff > > OS architect @ elementary > > > > -- > > Mailing list: https://launchpad.net/~elementary-dev-community > > Post to : [email protected] > > Unsubscribe : https://launchpad.net/~elementary-dev-community > > More help : https://help.launchpad.net/ListHelp > > > -- Best Regards, Daniel Foré elementaryos.org
-- Mailing list: https://launchpad.net/~elementary-dev-community Post to : [email protected] Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
