← Back to team overview

elementary-dev-community team mailing list archive

Re: Luna Check Up


Another example of this is the print contract which provides you with the print settings dialog. It's up to the developer of the contract to provide a proper

On Wed, 18 Jul 2012 14:25:02 -0700, Daniel Foré wrote:
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 <lallenlowe@xxxxxxxxx> 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
<sergey@xxxxxxxxxxxxxxxx> wrote:
> In addition to the aforementioned doc with requested changes, voldyman > drafted a doc that describes how the whole thing is expected to work.
> it is:

> 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

Pim Vullers