Facebook Developers

I've always liked the way the multiFeedStory form allowed users to post to friends' profiles without forcing the app to have knowledge of the users' friends.  Is there a way to do such a thing in the stream.Publish model?  From what I can see, it looks like Stream.Publish requires the caller to know target ids.

see wiki, actor should work for caption.
there is a bug there but your example should work with actor as far as I understand

ck so you give us 2 month to switch to your new publish system - what's the rush - with over 650,000 applications out there you think that's a fair time? - bad decision making in my opinion, but then again it's your platform, you can do what you want.

andybrock wrote:

starg wrote:

"shrinking the size of images to be rendered at a maximum of 90 pixels high or 90 pixels wide"

If the image size is 130 x 100, do we need to shrinking the size by ourself or faceook would do it automatically?

I need a clear answer, please,

thank you.

I can't find a clear answer in the documentation, however if you look at the example code they provide the code that produces a feed with a picture of a cat... the image on the web site that i passes through is much bigger than 90 x 90 but it is displayed at 90 x 90 on the feed.  So it certainly seems that facebook are shrinking it for you.

Andy

If facebook is shrinking it for you it will be of a much lower quality than when you do it your self beforehand in photoshop.
just my 2 cents

three simple uestion

1) why you choose that we can't use FBML?
2) how about fb:intl???? you recently sponsorized your exciting about facebook connect translation...and now???
3) why now I have to request adding permission also to publish one line story while I hadn't before? Since this will be the only way to publish to the Stream don't you think this should be integrated in first application's authorization????

Last edited by donachy (2009-11-02 14:27:57)

Why the new php library doesnt have the stream function?!!
Come on Facebook, we need updated php library to start using the new functions!

FendyBt2 wrote:

FLindblom wrote:

If streamPublish is to replace templates then we need attachment description (and possibly caption) to accept some basic html like <br> <b> and <i> the way template bundles do now.

Second that...

then please vote for this bug: http://bugs.developers.facebook.com/sho … gi?id=7357

I don't see any reason for the stream to support any kind of formatting.  Facebook have stated that it is partly to aid in having the updates render on multiple devices and in different formats.  This means that the HTML tags you want may not be available on that platform.

I'm happy they're going.  stream stories are designed to be short and simple.

Keep up the great work FB API Team.

Did you guys notice that if we're using the new stream publish to publish our feed story, the via app link doesn't work anymore...

Feed story example: 30 minutes ago via Some App Name · Comment · Like · See Wall-to-Wall

Usually when the user click the "Some App Name" link, it will be forwarded to the app canvas page...
But now, it's forwarded to the live feed URL...

Example: http://www.facebook.com/widgets/live_fe … d=01234567

And it didn't go to the app canvas page as it should but it was redirected to the Facebook home page...
That's odd... :-/

donachy wrote:

FendyBt2 wrote:

Did you guys notice that if we're using the new stream publish to publish our feed story, the via app link doesn't work anymore...

Yes...I've noticed yesterday!!! grrrrr

Looks like i 'll soon have to add "Google our application for more info" at the end of stream stories. Facebook, stop this 'plaintext'
nonsense, the web was called hypertext for a reason.

Hi Matt - what about support for stream publish in the Actionscript library? It's not there yet AFAIK.

Thanks, Dave

So I get the new stream publish protocol and have published from a test app using it, but I'm unclear as to exactly what I'm going to need to change in all my FBML applications. Does our code in the publisher interfaces need to be changed? Does the attachment logic need to change?

More specifically, for a an FBML-based application that uses ALL the Facebook integration points, what will need to be changed?

1. Main FBML canvas page -- Does the feedstory forms and multifeedstory forms go away? So we have to change to using a stream publish function instead?

2. User's Publisher and Publisher on their Friend's walls -- Does the publisher interface go away? I assume probably not since I can't really think of a way to interact with the publisher differently than we do today. The publisher itself handle's all the logic to actual post to the user and/or user's friend's wall.

3. Attachments (mail) -- The whole methodology for adding attachments just changed recently. It took me quite a while to get it figured out (and I don't like what it produces as a result as much, but that's another story). Right now it acts more like the publisher interface than it used to. Will this need to be changed as well?

Also, I do agree with the comments here about needing to be able to at least include links and some FBML like fb:pronoun. Or at least some simple functions (both PHP and Javascript) to accomplish the same thing. I hope we don't all have to write our own complex functions to try to look up what sex a user is and factor in whether more than one person are being referenced.

I did also want to comment in general that the new stream publish method at least doesn't require feed templates. The way those were implemented was pretty cumbersome. I totally get why they did it that way, so that feed stories could be aggregated, but now with the live stream they didn't make as much sense. Of course now they are going full-circle and trying to thin out the news on the home page by choosing for us which stories are interesting enough to publish to the main home page.

On a side note, OpenSocial, the competing social media app API's used by MySpace, Google Orkut, LinkedIn, and pretty much everyone else besides Facebook are right now introducing "templates" to news feeds. Although with theirs you don't have to register anything with the container (social-networking site), but you just define them and use them in your own app. Its really just a way to separate the text of your posts from the code. The syntax is similar to FB templates. It almost reminds me of a glorified sprintf() function, but you do use actual "variables" like {source}, {target}, etc. Anyway, we need to be able to easily format these stream posts somehow.

Thanks for listening and I'd appreciate some direction on what all I need to change with my apps.