As with all client side applications, you cannot possibly reliably protect
yourself against piracy. However, if you choose to try it, your best option
is probably to require some sort of serial in the code (as a pref) - and
hope no-one will care enough to edit your code to remove this "feature" -
while obfuscating the code might give you a better shot at that, it will
also decrease the likelihood of people actually subscribing, as they are
unable to read and assess the code behind it.

-- cers / Christian Sonne

On Thu, May 21, 2009 at 9:46 AM, Aurimas <[email protected]> wrote:

>
> I mean those features are implemented entirely in client-side code
> (JavaScript + jQuery + XPCOM).
>
> On May 21, 10:32 am, Aurimas <[email protected]> wrote:
> > No, the problem is that special features are just jQuery plugins and
> > do not require a server-side component.
> >
> > On May 21, 10:19 am, Aza <[email protected]> wrote:
> >
> > > If the special features require a server-side component, then you are
> set.
> >
> > > -- aza | ɐzɐ --
> >
> > > On Wed, May 20, 2009 at 11:48 PM, Aurimas <[email protected]>
> wrote:
> >
> > > > I have created a very specific and powerful ubiquity extension that
> > > > has taken half a year to develop. I would like to monetize it on a
> > > > freemium model, i.e. making it free to use, while charging for
> > > > advanced or special features. But I can't think of a way how to
> > > > protect these special features and enable them only for logged in
> > > > users, who have paid for them. Maybe someone might have a clue how to
> > > > accomplish this within ubiquity commands?
> >
> >
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"ubiquity-firefox" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/ubiquity-firefox?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to