Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Working on FaceBook API 2.x #5260

Closed
ghostnegotiator opened this issue Sep 30, 2014 · 3 comments
Closed

Working on FaceBook API 2.x #5260

ghostnegotiator opened this issue Sep 30, 2014 · 3 comments
Labels
services

Comments

@ghostnegotiator
Copy link

Hello there,

Today I noticed that FaceBook is closing down API 1.x on 25th December and all API's will have to be updated prior 25th December. Is D* already running API 2.x or still under the old API or is it already running API 2.X???

Proof:
http://i.imgur.com/jx0Iup7.png

Regards,
Anime Machina
@jhass jhass added the services label Sep 30, 2014
@Flaburgan Flaburgan mentioned this issue Jan 18, 2015
Closed
@jaywink
Copy link
Contributor

jaywink commented Feb 21, 2015

The dates are wrong as discussed on various forums:

With the launch of v2.0 of the API, we have two versions in service at the same time:

Version 1.0, which is what we call the API as it existed the day before v2.0 was launched. We'll support v1.0 for one year and it will expire on April 30th, 2015.
Version 2.0, which is what this upgrade guide covers. Version 2.0 is supported for at least two years. At the earliest, it will expire on April 30th, 2016.

https://developers.facebook.com/docs/apps/upgrading#v1tov2

The problem I have is I can't figure out from anywhere why our current integration would even work, since we've never required afaict publish_actions - and this is not changing in v2.. Maybe time for a podmin poll..

But AFAICT our code should be all good with api v2. I don't see anything in the v2 API that would break our current implementation.

@ghostnegotiator
Copy link
Author

I did had error messages showing up about post actions, it definitely needs more info in future. Although I personally dropped FaceBook and Twitter support on my pod cause some one violated their terms.

@Flaburgan Flaburgan mentioned this issue May 4, 2015
Closed
@jhass jhass mentioned this issue May 4, 2015
Closed
@denschub denschub mentioned this issue May 12, 2015
Closed
jaywink added a commit to jaywink/diaspora that referenced this issue May 23, 2015
@jaywink
Introduce 'authorized' configuration option for services
d9bb27b 
Since the Facebook API has changed and additional permissions are required for all users on a pod to cross-post, an additional 'authorized' flag is needed to be set for the Facebook service.
This flag allows either all users, one user or no users to use the cross-posting service.

Clarifies the situation for diaspora#5923, diaspora#5260 and diaspora#5085.
@jaywink jaywink mentioned this issue May 23, 2015
Closed
jaywink added a commit to jaywink/diaspora that referenced this issue May 24, 2015
@jaywink
Introduce 'authorized' configuration option for services
cef1a48 
Since the Facebook API has changed and additional permissions are required for all users on a pod to cross-post, an additional 'authorized' flag is needed to be set for the Facebook service.
This flag allows either all users, one user or no users to use the cross-posting service.

Clarifies the situation for diaspora#5923, diaspora#5260 and diaspora#5085.
jaywink added a commit to jaywink/diaspora that referenced this issue May 24, 2015
@jaywink
Introduce 'authorized' configuration option for services
67eb382 
Since the Facebook API has changed and additional permissions are required for all users on a pod to cross-post, an additional 'authorized' flag is needed to be set for the Facebook service.
This flag allows either all users, one user or no users to use the cross-posting service.

Clarifies the situation for diaspora#5923, diaspora#5260 and diaspora#5085.
jaywink added a commit to jaywink/diaspora that referenced this issue May 24, 2015
@jaywink
Introduce 'authorized' configuration option for services
ef6591f 
Since the Facebook API has changed and additional permissions are required for all users on a pod to cross-post, an additional 'authorized' flag is needed to be set for the Facebook service.
This flag allows either all users, one user or no users to use the cross-posting service.

Clarifies the situation for diaspora#5923, diaspora#5260 and diaspora#5085.
jaywink added a commit to jaywink/diaspora that referenced this issue May 24, 2015
@jaywink
Introduce 'authorized' configuration option for services
778e321 
Since the Facebook API has changed and additional permissions are required for all users on a pod to cross-post, an additional 'authorized' flag is needed to be set for the Facebook service.
This flag allows either all users, one user or no users to use the cross-posting service.

Clarifies the situation for diaspora#5923, diaspora#5260 and diaspora#5085.
jaywink added a commit that referenced this issue May 25, 2015
@jaywink @denschub
Introduce 'authorized' configuration option for services
7c0e50c 
Since the Facebook API has changed and additional permissions are required for all users on a pod to cross-post, an additional 'authorized' flag is needed to be set for the Facebook service.
This flag allows either all users, one user or no users to use the cross-posting service.

Clarifies the situation for #5923, #5260 and #5085.

closes #5985
@denschub
Copy link
Member

Closing this. Additional configuration available with 7c0e50c, additional information regarding this change and issues in #5085. Feel free to reopen if you feel the urge of doing so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
services
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jhass @denschub @jaywink @ghostnegotiator