How will this be monetized? I can't imagine it being free in perpetuity if it catches on.
What about security? Passing Facebook user access tokens over http opens them up to being sniffed on the wire, which would allow anyone to impersonate a user of your app. Maybe ssl is supported, but all of the api documentation examples use http.
Regarding security, good point. SSL is supported; however, we are still in the process of obtaining a secure certificate signed by a CA. Most browsers would not let the demo run SSL over AJAX so we have it temporarily disabled, but once we get a certificate, we will re-enable the SSL support for the API. At that point, one simply has to use https instead of http for API calls.
Comments
How will this be monetized? I can't imagine it being free in perpetuity if it catches on.
What about security? Passing Facebook user access tokens over http opens them up to being sniffed on the wire, which would allow anyone to impersonate a user of your app. Maybe ssl is supported, but all of the api documentation examples use http.
Regarding security, good point. SSL is supported; however, we are still in the process of obtaining a secure certificate signed by a CA. Most browsers would not let the demo run SSL over AJAX so we have it temporarily disabled, but once we get a certificate, we will re-enable the SSL support for the API. At that point, one simply has to use https instead of http for API calls.
We hope to monetize this through selling our invite widget.
We're also in the process of determining our pricing scheme, which is why that is not detailed on the site yet.