bellingcat/auto-archiver
1
0
Fork 0
mirror of https://github.com/bellingcat/auto-archiver.git synced 2026-06-07 19:08:30 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'dev' into v1-dm-changes

Browse Source
This commit is contained in:
Miguel Sozinho Ramalho
2025-06-17 13:05:34 +01:00
committed by GitHub
parent b3adc5603a 1b6d85884b
commit 6f949738a3
2 changed files with 11 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/source/installation/authentication.md
View File

@@ -9,8 +9,8 @@ There are two main use cases for authentication:
```{note}
The Authentication framework currently only works with the following modules:
* Generic Extractor
* Screenshot Enricher
* [Generic Extractor](../modules/autogen/extractor/generic_extractor.md) - the main module for extracting content from websites
* [Antibot Extractor/Enricher](../modules/autogen/extractor/antibot_extractor_enricher.md)
To authenticate for WACZ archiving, see the instructions on the [](../modules/autogen/enricher/wacz_extractor_enricher.md) page.
```
@@ -34,7 +34,8 @@ You can save your authentication information directly inside your orchestration
```{note}
The Username & Password, and API settings only work with the Generic Extractor. Other modules (like the screenshot enricher) can only use the `cookies` options. Furthermore, many sites can still detect bots and block username/password logins. Twitter/X and YouTube are two prominent ones that block username/password logins.
Currently, the Username & Password, and API settings only work with the Generic and Antibot Extractors. Furthermore, many sites can still detect bots and block username/password logins. Twitter/X and YouTube are two prominent ones that block username/password logins.
One of the 'Cookies' options is recommended for the most robust archiving, but it still isn't guaranteed to work.
```