Comments for sambroblog.

Comment on Facebook Open Graph HTML5 Validation Problems by FridayDigital Sherpa | Digital Sherpa

FridayDigital Sherpa | Digital Sherpa — Fri, 09 Sep 2011 02:59:38 +0000

[...] http://sambro.is-super-awesome.com/2011/05/18/facebook-open-graph-html5-validation-problems [...]

Comment on Creating a proper Buffer in a Node C++ Addon by sambro

sambro — Fri, 02 Sep 2011 02:18:23 +0000

Hi Rals,

You should probably actually read my blog post, as I go into exactly why you don’t want to do that (hint: what you’re doing is creating a SlowBuffer).

This blog post *is* fairly old though, and Node.js moves pretty rapidly, perhaps in the more recent Node versions your snippet has the correct behaviour of creating a FastBuffer now. I’m not sure, but I shall definitely keep it in mind!

Comment on Creating a proper Buffer in a Node C++ Addon by rals

rals — Fri, 02 Sep 2011 01:21:49 +0000

This is a bit long winded, when 2 lines is quicker.
I have used this and it worked for me. I dont see why it has to be 10 lines+ in size.
ie.

char *mydata = “Random raw data”;
Local return_buffer = Buffer::New( mydata, strlen(mydata) );
return scope.Close( return_buffer->handle_ );

Comment on Facebook Open Graph HTML5 Validation Problems by Evan Carroll

Evan Carroll — Thu, 16 Jun 2011 14:55:02 +0000

This trick no longer works as meta-name’s must be registered as Meta Extensions: http://wiki.whatwg.org/wiki/MetaExtensions . FB Has not made a proposal that has gotten accepted yet. The choice is between pissing off W3C or not using FB’s Open Graph.

Comment on Creating a proper Buffer in a Node C++ Addon by sambro

sambro — Tue, 17 May 2011 23:49:41 +0000

Hey!

Yeah I’ve been under the pump at work for a few weeks! Thanks for the encouragement I’ve actually been kicking myself for not posting more “a-ha!”‘s from when I was developing node-gitteh…

Comment on Creating a proper Buffer in a Node C++ Addon by Tim Branyen

Tim Branyen — Tue, 17 May 2011 15:33:04 +0000

Hey Sam!

Haven’t seen you around in ages, but you need to keep posting gems like this. IMO this post should be pushed into the nodejs `creating native extensions` documentation. +1

Comment on Facebook Access Tokens from Canvas Apps by Niklas B

Niklas B — Tue, 17 May 2011 09:44:42 +0000

Awesome, I was looking for this very solution. Code works wonderful. Thank you!

Comment on Facebook Access Tokens from Canvas Apps by Dan

Dan — Wed, 04 May 2011 04:02:59 +0000

Mate,

you are an absolute genius! I am gonna worship you! LOL
This is exactly what I needed. I have been looking for this for about three days now! The part were you “self-manufacture” the session… brilliant!

I don’t know what I would have done without this. Thank you so much for sharing this!
You are the man!! (Not kidding) I hope someone pays you shit loads of money for the work you do. You certainly deserve it! haha.

I am gonna drink on you!

Thanks again!

Comment on Gotcha: Removing iframe border in IE. by Alex

Alex — Mon, 28 Feb 2011 12:08:47 +0000

I’ve ran into that one before. jQuery even abstracts that away. https://github.com/jquery/jquery/blob/master/src/attributes.js#L22

Comment on Facebook Access Tokens from Canvas Apps by JC

JC — Wed, 02 Feb 2011 12:25:10 +0000

The problem right now with using OAuth 2.0 (so we get signed_request), or enabling the ‘session’ key is that we then ONLY get those variables through in POST. The rest (fb_sig_*) variables are lost, for me at least. Right now, that means there’s no way to check in a fan page tab if the viewing user is a fan without first getting the user to authorise. With legacy canvas authentication, we had fb_sig_is_fan, currently there’s no direct alternative with signed_request. The documentation suggests checking the user’s likes via Graph. That’s fine if the user has authorised so we have their user ID, but we don’t on fan page tabs, unless we’re doing an Ajax call.