[OpenSocial] if banning someone does not work

2009-02-19 Thread Gary

People can use their OpenId to identify themselves on a site.

What happens if some problem comes up with a user and there needs to
be follow up?

For example, in the past if someone was abusive, you ban them.
If they get on with another id and repeat over and over, you
eventually contact the isp.

Can I follow up with the OpenId providers and hope to get anywhere?

Am I looking at this the wrong way?

Gary






--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"OpenSocial Application Development" group.
To post to this group, send email to opensocial-api@googlegroups.com
To unsubscribe from this group, send email to 
opensocial-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/opensocial-api?hl=en
-~--~~~~--~~--~--~---



[OpenSocial] Re: why so difficult?

2009-02-13 Thread Gary

Howdy

More FC examples!!! WooHoo!

I wanted to do something with OpenSocial and OpenId etc. for a while
but was not sure where to jump into that ocean. FC was a great way to
get my feet wet. I set up a simple page and put some of the examples
on and then put a few example gadgets on iGoogle then my FC site. It's
starting to make sense.

I did stumble around at first. I did not get that I had to login to FC
and set up a site THEN log in again when I came back to manage my FC.
It seems simple now, but I was confused at first.

I just worked with someone that hit some bumps getting started. He did
not want to d/l the two files (he has learned that d/lding files can
be uhhh bad) and then we had to smooth some more bumps to get his
first app running, I used my site as an example and he was up and
social pretty quick.

He wants to hook a javascript database to his apps. I did not get any
details and am not sure how he can save the state of the d/b easily
with FC.

I installed shindig and my helloworld example from my FC test just
worked. I will be interested in any FC examples.

It's a lot to get all at once for me. I'll get there. Examples help a
lot :-)

Thanks

Gary
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"OpenSocial Application Development" group.
To post to this group, send email to opensocial-api@googlegroups.com
To unsubscribe from this group, send email to 
opensocial-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/opensocial-api?hl=en
-~--~~~~--~~--~--~---



[OpenSocial] Re: why so difficult?

2009-02-12 Thread Gary

Great post,

Are the 4 options in a faq?
Is Friend Connect an example of option 3?

and I wasv also feeling somewhat deflated. We have some small social
groups, mostly mailing lists with some stuff on web pages and getting
them more social sounds like a good idea. I tried Friend Connect and
it went well to build a few hello world kinds of examples.

I was about to install shindig (php version for that first test) but
now think I need to also look more at OpenID and OAuth.

Lots to look into.

Gary


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"OpenSocial Application Development" group.
To post to this group, send email to opensocial-api@googlegroups.com
To unsubscribe from this group, send email to 
opensocial-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/opensocial-api?hl=en
-~--~~~~--~~--~--~---



[OpenSocial] Re: Failed to parse JSON

2008-05-13 Thread Gary Helmling

The "failed to parse JSON" error simply indicates a null return value
from gadgets.json.parse() in makeRequest().

So the best I can offer in that case is to check the firebug console
to see the proxy request being made and open the proxy request
directly to check the response text.  The response should be a JSON
object in the format:

{
body: "your JSON response escaped as a string",
rc: 200,
errors: []
}

See if your JSON is being escaped correctly in the body property.

Or have you already done this and are only getting the errors property
populated?  In that case you'll need to provide more details on what
OpenSocial container you're using and probably follow up in the
container specific discussion group.

--gh

On Tue, May 13, 2008 at 4:55 AM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
>  Hi, Sorry, I modified the output a little and skipped the comma.
>  It should be as you typed. Can you help any further?
>
>  On May 12, 8:35 pm, "Gary Helmling" <[EMAIL PROTECTED]> wrote:
>
> > On Mon, May 12, 2008 at 3:09 PM, [EMAIL PROTECTED]<[EMAIL PROTECTED]> wrote:
>  >
>  > >  Sample Output:
>  > >  {"d":[{"__type":"LetsTalk.Running","ID":"0efb9b64-a1a4-40cf-
>  > >  a26e-2109a475e47f","SenderID":"123123
>  > >  ","ReceiverID":"123123""Message":"this is a
>  >
>  >^
>  >
>  > >  test","Modified":false,"DateSent":"\/Date(1210637247460)\/"}]}
>  >
>  > If this is the actualJSONoutput from your web service, it looks like
>
> > you're missing a comma between the value for "ReceiverID" and
>  > following "Message" key.  So your output should be more like
>  > (reformatted for line wrapping):
>  >
>  >  
> {"d":[{"__type":"LetsTalk.Running","ID":"0efb9b64-a1a4-40cf-a26e-2109a475e47f",
>  > "SenderID":"123123","ReceiverID":"123123", "Message" : "this is a 
> test",
>  > "Modified":false, "DateSent":"\/Date(1210637247460)\/"}]}
>  >
>  > Hope this helps.
>  >
>  > --gh
>
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"OpenSocial Application Development" group.
To post to this group, send email to opensocial-api@googlegroups.com
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
-~--~~~~--~~--~--~---



[OpenSocial] Re: Failed to parse JSON

2008-05-12 Thread Gary Helmling

On Mon, May 12, 2008 at 3:09 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
>
>  Sample Output:
>  {"d":[{"__type":"LetsTalk.Running","ID":"0efb9b64-a1a4-40cf-
>  a26e-2109a475e47f","SenderID":"123123
>  ","ReceiverID":"123123""Message":"this is a
   ^
>  test","Modified":false,"DateSent":"\/Date(1210637247460)\/"}]}
>

If this is the actual JSON output from your web service, it looks like
you're missing a comma between the value for "ReceiverID" and
following "Message" key.  So your output should be more like
(reformatted for line wrapping):

 {"d":[{"__type":"LetsTalk.Running","ID":"0efb9b64-a1a4-40cf-a26e-2109a475e47f",
"SenderID":"123123","ReceiverID":"123123", "Message" : "this is a test",
"Modified":false, "DateSent":"\/Date(1210637247460)\/"}]}

Hope this helps.

--gh

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"OpenSocial Application Development" group.
To post to this group, send email to opensocial-api@googlegroups.com
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
-~--~~~~--~~--~--~---