As you know, Facebook stop search public post functionality on their Graph API with the arrival of 2.0 version (which was release the October 1st, 2014).
BUT (^^), i absolutely need this functionality because a part of my work requires recurrently search on public post.
It's so boring and alienating that i decide to try to develop a web scraping program for scrap information on public post.
The hardest part of this is to manage the infinite scroll page, so i try to find how to go to the next page.
With many tests i finally find that the element that determines the next page is a variable name "cursor" and not the variable "page_number" as one might think (we can change the page_number variable but nothing happen).
But the problem is that the variable seems encryt (below an example of what does it look like), so i'm stuck here...
A genius or a hero can give me a solution ? Or the problem can't be resolve ?
Thank you in advance.
Example : cursor":"AbpBsSIW2IKe5HycoZe-7AEPeP007M_RW_RYmHnUINzLGEBePZi8sy0snwURnd7FGcrRcH5AzrE7Ne3k0xjVR3v-D9GI1HYeLGwGNRlYTg74MMs24jpHDH72wMN5M_gD41clWHMRAq1IBZwyS-iB6AVq_mPoxc5jGnTayhaQqblAqgwuKHpXf7YcGc0te49Z_9fYcYmn61pE4d4KQAKFgqzsVW8tWn4sX7UeMhFs2U9iQe4gnBiMt93fEK7AobOueJVR7FjSmm8AJ_Jth3xPOsjQlbLDSOWKYgLRAx-pCwSS9suI9g56sio5XloQwjkXJUGPSoV7cU6VYnet4z6wiejOqY5pQBdHwN2DmijI8MvIVrOUHLJvLeGdo6zC-sLHDiMZfURkTmgDQ7YgrTZ76Wz17csw636nmr2HfsRvmOWgaf7F7UZdwar8YfDg3Kh2Il2VkhlgTweEsO5v1Zn4YRj5iGO0xzYzMBKB7gImqTD9a_FhvFZLpFhVlvfnNuX81S2CBVZQGbRIBnhg5g2h2f3YNlY7CsMlmu62F_cR36fI1oHzIHCVp0t1DvkDlcNn71JZzVJiMPf2KqVYJQRvwm6Fx_MhQ04ZEdOaSWPEWpHeyi5O6dX9TOu0yGgu_x94pZy0PMz4--x3nTKax6Y01NCfwjXjCegN_Zv5fjMOOz_TRgH4K8vMmWFttimxfoW8C97CHUjqkPIodz8Dwvv5j6AIb6A-CTaRDtyldcQOHf9_thFfRRtpkJkXeEDWgoIt5ZtI3AJZ5_6Ph-F1gmv1FvyB9Oix5heNc1LFZrtAMA3gy7pC1cHFXvwgG2redy5JsQ68Zg_thNHVM0sErzd9ReBDzzWmE2jWQgaXDjoMuArobPsRczI2JoVs7Z9yPA0A1Wp87TppjJE8hdsB2KygEwsJR_EiEhJ003xEO2GiWCN7ceybyKXHnZDwE9V5GZNg6kSQFCeCfOV-i4cASj9YFkbX2F7rXxt3BU6ACDm9Sl8xV3NYrQYb82v1UBfK0bdGXu4LdxNSgc7DZ8n5JeS8QOCAMXqJ359StxjYxuME_LRc3w"
Related
I am working on a new version of our website, based on a commercial framework (Aspdotnetstorefront) with a responsive template.
We have a few pages where we want to include a Facebook "like button". I tried to use the same code we have in our current site in the new responsive version but it's ruining the design (its width disregards the limit of the device screen size and so the contents of the whole page is cut).
The code we have is the one auto generated by the Facebook developers page (it creates a class called 'fb-root').
I checked the Facebook developers page and the solution they offer is still the old one I have, or in other words, completely useless.
I would like to know if there is any available version that WORKS.
Thank you!
PS: This "facebook like button" RIGHT BELOW is exactly what I need as it seems to work very responsively.
how can i extract name list && phone numbers of the users liking certain page ?
I have tried using software called facepager but i couldn't extract names .
note:I'm not the owner of the page
You'd most likely have to write code yourself to do something like this. However,
Almost no-one publicly shares their phone number.
Facebook try to prevent this kind of data collection.
Even when facebook list's "likers" of a page, it'll wait till you scroll down to load more. You'd have to play with your browsers debug tools and look into where it get's that data from
https://www.facebook.com/search/<group id here>/likers
In the end you'll probably not get much better than just searching for the page and clicking each person's profile because the site is designed to not let what you're trying to do happen...
I am writing an application that needs to retrieve all posts on any given facebook page. For the McDonald's page, I would use this url:
https://graph.facebook.com/McDonalds/posts?access_token=xxx&limit=5000
The problem is that first, I do not receive any posts older than 2011-11-01 and the number of posts shown is much less than 5000. This means that the limit parameter isn't working properly. I looked this up and found that it was a known bug.
Then I tried to follow the next and previous paging information provided in the end and even using that I can't get past 2011-01-24. After following the next link 2 times, an empty page comes up. The McDonalds page is much older and contains more posts. So the question is, how on earth am I supposed to retrieve older posts. Is there any workaround at all?
There is a limit on the limit. Try using since & until to extend the date params
https://graph.facebook.com/McDonalds/posts?access_token=xxx&limit=5000&since=2+years+ago&until=now
&limit=5000&since=2+years+ago&until=now
&limit=5000&since=3+years+ago&until=now
Looks like an issue was closed related to the question I'm about to ask, so I wonder if I'm going to be skating on thin ice, but here goes. I feel like even though this is kind of localized by nature, it could be a useful example for other developers dealing with the Like button.
I seem to be having issues regarding the Facebook like button. The infuriating part is that I'm pretty confident I have everything setup properly, and even though the linter says "hey, this all looks kosher!" the like button fails to get the correct content and uses cached info from a different page.
Here's the case: referlocal.com. We serve daily deals, and list them right off the homepage. There can be one of many deals listed on that homepage, so obviously Facebook is seeing just one when it goes to take a peek at the root directory. Now, on the homepage, whatever deal your viewing has a FB Like XFBML tag with href and ref attributes set. Every page that displays a deal also has OG tags pointing directly to the offer view page. Deals can also be viewed on user pages. So, on these three paths:
/
/{username}
/offers/{city}/{title-url-alias}
a like button is included as well as OG tags that point to /offers/{city}/{title-url-alias}. For about 3 weeks, the button worked like a champ. But recently, it's been performing strangely. For any deal, regardless of the 3 locations, it always uses the information cached from the previous days "/" deal. Regardless of the OG tags or origination.
Here's the wildly confusing part. The Facebook Linter is supposed to recache the information on the page, right? Well, it sort of does. It picks up on all of the appropriate information set in the OG tags, but when you click the Like button at the bottom of the page, no dice, still uses the deal FB saw on the homepage from the day before.
I know this is probably killing my argument for localization, but check this out:
http://developers.facebook.com/tools/lint/?url=http%3A%2F%2Freferlocal.com%2Foffers%2Fdallas%2Fget-20-of-authentic-italian-american-cuisine-for-only-10-at-leggios-italian-ristorante-dallas
Regardless of the fact that the linter finds all the appropriate information, the like button at the bottom still is liking a deal FB cached from the previous day.
Any ideas?
I had this problem too. The linter caches things in a very weird manner - seems like the best thing to do is either to add a query string and change it every time, or just rename the file every time you're checking.
That's my first question in here, I've been looking through old questions, but nothing matched with my problem. Here it is.
I'm creating some site with one main functionality. We want this site to display content of other sites, but in a specific way. User chooses let's say two pages from five and want to see their content. He clicks button 'Display' and goes to next page where he finds let's say view from web cam, and here comes problem.
I want to cache image that is hidden behind the url from which image was downloaded, so after refresh image won't be downloaded again, but browser will get it from cache.
I've been looking through documentation of Django, but nothing seemed to be useful.
I know that I should:
1) create table which stores cache
2) add to settings.py some CACHE_BACKEND = ...
3) use #cache_page(300) before declaration of function which returns content which should be cached,
but... it doesn't seem to work.
I will be greateful if someone tells how to solve that problem, maybe with some sort of code showing the mechanism.
Cheers,
Chris.
I think that right way to do this will be to store image somewhere on your server and delete it later with cron or something similar.
Django cache framework wasn't created for the purpose you are trying to use it.