Facebook image archiving about auto-archiver HOT 3 CLOSED

Hi Dave, thanks for opening this discussion.

From #26 we should not use archive.ph since it has captchas and will stop working rather quickly.

My fear is that automation with selenium will lead to the same result as facebook is quite aggressive on that, nonetheless that's the only option still on the table (unless some potentially hacky library is around). If you want to give it a go you can try using the webdriver and using the clicks to get to the content but this would need some experiments to see how quickly facebook detects the automated behaviour and blocks the page. Tbh, this has been the reason we have not tried automating facebook posts :/

from auto-archiver.

I've made a fb archiver on my fork of this codebase: https://github.com/djhmateer/auto-archiver/blob/main/auto_archive_fb.py

Have been running in production well (with caveats!).. it's pretty specialised and has to run on its own server.

Maybe close this as an issue, as it is working well enough for me.

from auto-archiver.

Closing this issue for now since the caveats with facebook archiving usually require passive accounts and proxies. the wacz_archiver_enricher can be used in combination with facebook login credentials to achieve this result.

from auto-archiver.