A question to the hi5 Architect:

If hi5, as a container, implements the OpenSocial interface that
allows the application to connect to a web-server through the
OpenSocial container (hi5 being the container in this case), then how
does it handle privacy?

All of the data that the app communicates with a server through the
container goes through the container, which means hi5 sees all of that
communication. That can be a problem if my app connects to my server
through this mechanism and I have a privacy policy commitment to my
users that is now broken (because I let private info go to hi5), or if
I just don't feel like sharing all of this info with hi5 unless they
make a policy of how they will not use, or only selectively use, this
data.

With OpenSocial, as far as I can see, the information goes from the
app to the container unencrypted so it is hard to see how this is
solved technologically. Hence the interest in polices.

I asked the same about Orkut, with no reply so far.

(http://groups.google.com/group/opensocial-orkut/browse_thread/thread/
3e94ea0dc7cc2fb5?hl=en#)

Matt

On Feb 17, 5:16 pm, Paul Lindner <[EMAIL PROTECTED]> wrote:
> Hi Greg,
>
> I'm cleaning out my inbox and found your message.  Hopefully you've
> followed the Opensocial developments in the past months and are aware
> that hi5 has had an open access sandbox for quite some time now.
>
>
>
>
>
> On Sat, Nov 03, 2007 at 06:48:49PM -0000, EGreg wrote:
>
> > Paul - how can a developer start developing for hi5 when it opens, so
> > as to produce a quality widget to submit to hi5? With orkut, you sign
> > up but then they say "wait and we'll contact you" when a spot is
> > available. Will hi5 do this as well? If so, who gets to go first?
>
> > Greg
>
> > On Nov 2, 5:55 pm, Paul Lindner <[EMAIL PROTECTED]> wrote:
> > > On Fri, Nov 02, 2007 at 06:04:35PM -0000,EGregwrote:
>
> > > > Hey guys, BIG PROPS for rolling out a new industry standard, AND
> > > > getting so many partners on board. You are going to get a huge number
> > > > of app developers as well.
>
> > > > In that regard, I want to ask you -
> > > > * Even though the standard is called OpenSocial, it is up to the
> > > > social networks (the "containers") to allow developers to submit their
> > > > applications and so forth. So they can restrict app developers or give
> > > > head starts to some and not others, right?
>
> > > Open Social Sites can adopt whatever policy they want.
>
> > > At Hi5 we're going to offer a self-serve developer signup system in
> > > the next two weeks, and a sandbox that works with that.  This data
> > > will form the basis of our Application Gallery.
>
> > > So far we've been creating dev accounts by hand and it obviously
> > > doesn't scale.
>
> > > For developer off the street you can get a certain number of API calls
> > > per minute/hour/day to test things out.  To publish in the application
> > > gallery will require a little more information, either embedded in
> > > your XML or listed with us directly.
>
> > > I'd be interested in hearing what developers out there would rate
> > > their highest priorities so we can hit thost targets...
>
> > You received this message because you are subscribed to the Google Groups 
> > "OpenSocial Developers" 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 
> > athttp://groups.google.com/group/opensocial-api?hl=en
> > -~----------~----~----~----~------~----~------~--~---
>
> --
> Paul Lindner
> hi5 Architect
> [EMAIL PROTECTED]
>
>  application_pgp-signature_part
> 1KDownload- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenSocial Application Development" 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/opensocial-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to