Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2012-09

Writing application that sends things into facebook

11 messages · 6 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

ik

Hello,

I have this hobby project:
https://github.com/ik5/display-quotes

And I wish to add it the ability to send random quote to facebook as well. I never wrote an application for facebook, and I can only find information about web based application that works both ways.

Does anyone here know of a good and up to date tutorial on how to do it, or an open source application that I can learn from ?

Thanks,
Ido

Reply by email

leledumbo
to ik

Start from here: http://developers.facebook.com/docs/reference/api/ The authentication uses OAuth 2.0 which I'm not aware any implementation of. BigChimp and ludob created an OAuth 1.0a implementation in fpctwit, maybe you could take that as a base (though I'm not sure about the effort since I have no idea about the differences between 1.0a and 2.0).

Reply by email

Ludo Brands
to leledumbo
Show quoted text 7 lines
Start from here: http://developers.facebook.com/docs/reference/api/ The authentication uses OAuth 2.0 which I'm not aware any implementation of. BigChimp and ludob created an OAuth 1.0a implementation in fpctwit, maybe you could take that as a base (though I'm not sure about the effort since I have no idea about the differences between 1.0a and 2.0).

I have also written an Oauth2 implementation for the Google API (implemented most of the Google Calendar api). Oauth2 is designed to be easier than Oauth1 and supported by many more companies that all wanted their own thing in the standard. The result is a standard that is lacking portability and every Oauth2 implementation is different and needs coding from almost scratch. Very little in Oauth1 can be re-used in Oauth2. If interested I can sent you the Oauth2 implementation for Google using Synapse for the HTTP layer.

Ludo

Reply by email

Marcos Douglas
to Ludo Brands
Ludo Brands wrote 19 lines
> Start from here: http://developers.facebook.com/docs/reference/api/ > The authentication uses OAuth 2.0 which I'm not aware any > implementation of. BigChimp and ludob created an OAuth 1.0a > implementation in fpctwit, maybe you could take that as a > base (though I'm not sure about the effort since I have no > idea about the differences between 1.0a and 2.0). > I have also written an Oauth2 implementation for the Google API (implemented most of the Google Calendar api). Oauth2 is designed to be easier than Oauth1 and supported by many more companies that all wanted their own thing in the standard. The result is a standard that is lacking portability and every Oauth2 implementation is different and needs coding from almost scratch. Very little in Oauth1 can be re-used in Oauth2. If interested I can sent you the Oauth2 implementation for Google using Synapse for the HTTP layer.

Would be better to create a git repo to this project.

Marcos Douglas

Reply by email

ik
to Ludo Brands: I have also written an Oauth2 implementation for the Google API (implemented most of the…
Ludo Brands wrote 15 lines
> Start from here: http://developers.facebook.com/docs/reference/api/ > The authentication uses OAuth 2.0 which I'm not aware any > implementation of. BigChimp and ludob created an OAuth 1.0a > implementation in fpctwit, maybe you could take that as a > base (though I'm not sure about the effort since I have no > idea about the differences between 1.0a and 2.0). > I have also written an Oauth2 implementation for the Google API (implemented most of the Google Calendar api). Oauth2 is designed to be easier than Oauth1 and supported by many more companies that all wanted their own thing in the standard. The result is a standard that is lacking portability and every Oauth2 implementation is different and needs coding from almost scratch. Very little in Oauth1 can be re-used in Oauth2. If interested I can sent you the Oauth2 implementation for Google using Synapse for the HTTP layer.

Where can I find your OAuth2 unit ?

Show quoted text 9 lines
Ludo -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Reinier Olislagers
to Ludo Brands: I have also written an Oauth2 implementation for the Google API (implemented most of the…
Ludo Brands wrote 15 lines
> Start from here: http://developers.facebook.com/docs/reference/api/ > The authentication uses OAuth 2.0 which I'm not aware any > implementation of. BigChimp and ludob created an OAuth 1.0a > implementation in fpctwit, maybe you could take that as a > base (though I'm not sure about the effort since I have no > idea about the differences between 1.0a and 2.0). > I have also written an Oauth2 implementation for the Google API (implemented most of the Google Calendar api). Oauth2 is designed to be easier than Oauth1 and supported by many more companies that all wanted their own thing in the standard. The result is a standard that is lacking portability and every Oauth2 implementation is different and needs coding from almost scratch. Very little in Oauth1 can be re-used in Oauth2. If interested I can sent you the Oauth2 implementation for Google using Synapse for the HTTP layer.

Ludo,

If you want to and your license allows it to, we can add your OAuth2 code to my existing fpctwit repository (if possible perhaps rename it to fpcoauth).... with some big caveats in the readme about oauth2 being not one standard but many etc...

Regards,
Reinier aka BigChimp

Reply by email

ik
to Reinier Olislagers
Reinier Olislagers wrote 22 lines
On 3-9-2012 16:53, Ludo Brands wrote: >> Start from here: http://developers.facebook.com/docs/reference/api/ >> The authentication uses OAuth 2.0 which I'm not aware any >> implementation of. BigChimp and ludob created an OAuth 1.0a >> implementation in fpctwit, maybe you could take that as a >> base (though I'm not sure about the effort since I have no >> idea about the differences between 1.0a and 2.0). >> > I have also written an Oauth2 implementation for the Google API (implemented > most of the Google Calendar api). Oauth2 is designed to be easier than > Oauth1 and supported by many more companies that all wanted their own thing > in the standard. The result is a standard that is lacking portability and > every Oauth2 implementation is different and needs coding from almost > scratch. Very little in Oauth1 can be re-used in Oauth2. If interested I can > sent you the Oauth2 implementation for Google using Synapse for the HTTP > layer. Ludo, If you want to and your license allows it to, we can add your OAuth2 code to my existing fpctwit repository (if possible perhaps rename it to fpcoauth).... with some big caveats in the readme about oauth2 being not one standard but many etc...

At the moment my application is "public domain", I might change it to MIT/BSD license

Show quoted text 10 lines
Regards, Reinier aka BigChimp -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Ludo Brands
to Reinier Olislagers: If you want to and your license allows it to, we can add your OAuth2 code to my existing…
Show quoted text 10 lines
Ludo, If you want to and your license allows it to, we can add your OAuth2 code to my existing fpctwit repository (if possible perhaps rename it to fpcoauth).... with some big caveats in the readme about oauth2 being not one standard but many etc... Regards, Reinier aka BigChimp

Thanks, I have already created a google code repo for it. I'm cleaning up the demo app and adding some instructions to the code. Probably today I'll upload the code and publish the link.
It really is Oauth2 according to Google and the re-usability for other Oauth2 protocols is limited to picking up some ideas and very little code. The bulk of the code is calendar api related and class hierarchy from/to json streaming using rtti (which can be re-used in other apps). It also includes a tool to assist in the creation of class definitions starting from the Google specs (json resource representation). So very little in common with fpctwit/plurk.

Thanks, Ludo

Reply by email

Reinier Olislagers
to Ludo Brands
Ludo Brands wrote
> If you want to and your license allows it to, we can add your > OAuth2 code to my existing fpctwit repository

<snip>

So very little in common with fpctwit/plurk.

I understand, but the average programmer may not know about the fact that OAuth2 and 1 are so wildly different... and as you had commit rights to fpctwit already...

No matter, I'll just add a reference to your page on mine... perhaps with that new-fangled thing they call a hyperlink ;)

Reply by email

Unknown author
to Ludo Brands: Thanks, I have already created a google code repo for it. I'm cleaning up the demo app…
Ludo Brands wrote 21 lines
> Ludo, > > If you want to and your license allows it to, we can add your > OAuth2 code to my existing fpctwit repository (if possible > perhaps rename it to fpcoauth).... with some big caveats in > the readme about oauth2 being not one standard but many etc... > > Regards, > Reinier aka BigChimp > Thanks, I have already created a google code repo for it. I'm cleaning up the demo app and adding some instructions to the code. Probably today I'll upload the code and publish the link. It really is Oauth2 according to Google and the re-usability for other Oauth2 protocols is limited to picking up some ideas and very little code. The bulk of the code is calendar api related and class hierarchy from/to json streaming using rtti (which can be re-used in other apps). It also includes a tool to assist in the creation of class definitions starting from the Google specs (json resource representation). So very little in common with fpctwit/plurk.

I have been looking for this for ages, this is almost a dream come true. Now I can throw away my own code. :-)

Where did you find the google specs in machine-usable form ? Did you try other than calendar APIs with your tool to assist in creation of class definitions ? I am particularly interested in user provisioning.

Michael.

Reply by email

Ludo Brands
to Unknown author
I have been looking for this for ages, this is almost a dream come true. Now I can throw away my own code. :-)

Don't throw your code away yet;)

Where did you find the google specs in machine-usable form ?

Example:
https://developers.google.com/google-apps/calendar/v3/reference/acl/list The tool takes the Resource Representation and transforms it in class definitions and some other helper routines that can be cut and pasted in the code.

Did you try other than calendar APIs with your tool to assist in creation of class definitions ? I am particularly interested in user provisioning.

No. AFAIK user provisioning is still atom/rss based and not Oauth2.

Ludo

Reply by email