Nick Young

Sure, https://github.com/kevinzg/facebook-scraper/commit/bd7690306d219d15ddc0fdb397ae488de031a923 should do it

Sure, https://github.com/kevinzg/facebook-scraper/commit/e4e1390c4186a0d23270a9d5908f5c7705514203 should do it. Removing source is pretty easy, `top_post.pop("source")` or `del top_post["source"]` can do it

When you use a scraper, you're impersonating a web-based normal user. The usage limits are keyed for what's reasonable for a human to do. It's not reasonable for a human...

Perhaps they're using the official API. See https://developers.facebook.com/docs/groups-api/guides#getting-group-posts and https://developers.facebook.com/docs/graph-api/overview/access-levels

Yes, you can use the `start_url` parameter. See https://github.com/kevinzg/facebook-scraper/issues/310#issuecomment-852652846

Hi, `for post in get_posts("zuck", options={"comments": 13000, "progress": True}, cookies="cookies.txt" ):` is the correct syntax. Yes, this limit was in place to reduce the risk of temporary bans. I've increased...

>I mean b this if can I retrieve the comments of particular posts in real-time?? No, but if you check regularly enough, you can get them near real-time >options={"comments": "generator"}...

You're not wrong, this is a limitation of m.facebook.com. Perhaps you could check the total comment count, and only extract comments if it's increased significantly.

Try pass cookies as per the readme

Most users don't connect to Facebook from heroku, so Facebook is probably extra suspicious of their IP range. Don't use heroku for scraping