While going through recent facebook API and platform product changes at :
https://developers.facebook.com/blog/post/2018/04/04/facebook-api-platform-product-changes/
I see that there are few APIs like posts/ , comments/ etc. which are going to be deprecated. It is not mentioned anywhere when are they going to be removed completely and their alternative.
Does anyone have an idea about timeline and alternatives ??
In general, you can see the timeframe for deprecations in the changelog: https://developers.facebook.com/docs/graph-api/changelog/breaking-changes
The endpoints you mentioned (event/posts, event/comments) are removed already, as you can read just a few lines before they got mentioned: "Below are some immediate changes to these APIs."
There are no alternatives, or they would have mentioned it. Access to event feeds is just not possible anymore.
Related
Is it possible to like comments on posts through the Facebook API and if so, how? I haven't found anything in the documentation, only similar SO questions but they are almost ten years old and might be outdated by now.
No, that is not possible. Earlier, it was only used/abused for autoliking and like selling platforms, so they removed the possibility.
yea, the title pretty much sums it up. Is it allowed for an app to access ressources on api-v2.soundcloud.com?
Is there any documentation for it?
Relevant since I'm currently working on a soundcloud app and I just recognized that most of the calls on the websites itself are done with api-v2. The responses from the server would be extremly helpful to build some kind of infinite streaming which is the feature I like most about soundcloud.com.
I cant speak for SoundCloud, but gryzzly (a former SoundCloud engineer) stated in a previous answer:
Letting you know, that using undocumented APIs is not going in line with the our developers’ Terms of Use.
I don't quite know if my question fits here, but I don't know who else to ask...
I recently upgraded my socialengine plugin, which should allow me login to my site via Facebook. The reason I had to upgrade it because it didn't work anymore since Facebook changed the API (API-KEY --> APP-ID). I think this was around 2010!?
Now I bought the latest version of the plugin, just to find out that it still requires an API-KEY. Their support told me that it's not supported anymore because the version of my CMS is not supported anymore (nice to find that out after paying for it). However they offered me to make the plugin work for me, if I am willing to pay, with a hint that due to the massive changes in the API it will need a lot of work.
To come to my question: Have there really been such massive changes? Has a task like logging into a site via Facebook become that different? I am coming from a programming background, may i be able to fix this myself?
The Facebook API is constantly evolving with breaking changes all the time. 2010 is a long time ago for the FB API, so it sounds likely it'll be a lot of work updating the plugin (if the required API features are even still available!)
The answer was "no" back in March 2010:
Browser EventListenerList Implementation
I'm wondering if there has been any progress since then.
If the answer's still "no" ... any indication of when any browser might support it?
For those looking for a practical solution, see: How to find event listeners on a DOM node when debugging or from the JavaScript code?
EventListenerList was in some old draft of DOM 3 Events and was long removed from the spec. As far as I know, at least Gecko still doesn't have anything like this for regular web pages, although it now has an API for privileged code (extensions) to enumerate listeners (see https://bugzilla.mozilla.org/show_bug.cgi?id=570678#c0).
I looked through the W3C mailing lists, and there were a few discussions on this topic, but apparently no use-cases were found to justify the feature. This is the most recent message I could find:
[...] what is the motivation for adding this functionality at all? Previously, the working group resolved to remove the related but less powerful
hasEventListenerNS method for lack of a use case, and because there
are potential security issues.
(2001) http://lists.w3.org/Archives/Public/w3c-wai-ua/2001OctDec/thread.html#msg89 has some discussion from way back when the EventListenerList was considered.
(2006) http://lists.w3.org/Archives/Public/www-archive/2006Mar/0032.html asks a question to the author of quirksmode who seems to be responsible for the DOM3 EventListenerList myth about the use cases of such a feature; the archives do not list a reply.
(2008) another discussion: http://lists.w3.org/Archives/Public/public-webapi/2008Apr/thread.html#msg66
Note: Commenting on my post is not a good way to provide feedback for the browser vendors and standards organizations. I'm not affiliated with either group, and I doubt they will see or act on the comments here..
Do they just scrape or are there APIs?
I think they just scrape, because I haven't seen or heard of any APIs. Check also https://stackoverflow.com/questions/2689711/itunes-app-store-api
I was looking for the same things and found http://code.google.com/p/android-market-api/ (this is not the official api, as it seems they arent' any). It would be nice if there was an official API in the same way itunes has made theirs available