Activity stream(s) yo:
var activity.post = function(title, callback) {
var streamFolder = 'testFolder';
var streamTitle = 'testTitle';
var streamParams = {'url' : 'http://teststream.com'};
if (opensocial.newStream) {
var user_stream = opensocial.newStream(
streamFolder, streamTitle, streamParams);
var activity_params = {'url' : 'http://foobar.com'};
var user_activity = opensocial.newActivity(
user_stream, title, activity_params);
opensocial.requestCreateActivity(
user_activity,
opensocial.CreateActivityPriority.HIGH,
callback);
} else {
console.log('Activity stream: ' + title);
if (callback) { callback(); }
}
};
(Dan)
(Dan)
On Nov 2, 2007, at 5:49 PM, Mat wrote:
>
> Bump,
>
> Exactly the two concerns I had, I can't see app's spreading without
> some
> form of invite/messaging/notification system. Something is needed
> to allow
> users to contact other users within the social graph who do not
> currently
> have the app installed, and I'm not just talking about biting
> zombies..
>
> For example we run sponsor-me on fb, and our users create campaigns
> and
> invites friends to support them, our users actively want to invite
> others,
> it isn't something we impose. Almost weekly I get a message from an
> angry
> user, who doesn't understand why they can only invite 20 users, (fb
> imposes
> this limit). OpenSocial needs some equivalent, surely every social
> network
> has some messaging feature, and some tie in's could surely be made
> there.
>
> Just my 2c,
> Mat
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On Behalf Of EGreg
> Sent: 03 November 2007 00:38
> To: OpenSocial Developers
> Subject: [opensocial] Re: Question To Google
>
>
> Well, for me, and I imagine many developers, the priorities are
> simple:
>
> 1) allow us to start early or at the same time as other developers, to
> have a fair chance to spread
> 2) Implement notifications or some kind of similar mechanism to reach
> users outside of the app, so it can grow virally
>
> That's all. The rest we can do ourselves, if you implement the
> profile/
> friends part of the api :)
>
> On Nov 2, 5:55 pm, Paul Lindner <[EMAIL PROTECTED]> wrote:
>> On Fri, Nov 02, 2007 at 06:04:35PM -0000, EGreg wrote:
>>
>>> 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...
>>
>> --
>> Paul Lindner
>> hi5 Architect
>
>
>
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
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 at
http://groups.google.com/group/opensocial-api?hl=en
-~----------~----~----~----~------~----~------~--~---
