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 -~----------~----~----~----~------~----~------~--~---
