otty / dotfiles

All tools/Maigret

Maigret

maigret

Collect a dossier on a person by username from thousands of sites.

Detected by maigret | macOS, Linux, Windows |github.com

Sync it maigret.toml

Sync rules

What travels, what stays, what never leaves

Maigret in your home directory Every rule on this page, by file

…

"max_connections": 100,

"recursive_search": true,

"info_extracting": true,

"cookie_jar_file": "/home/octocat/investigations/cookies.txt",machine-local

"ignore_ids_list": [],

"reports_path": "reports",

"proxy_url": null,

…

Each machine keeps its own copy of these.

openai_api_key

Lifted into your secret store; the rest of the file syncs.

· data.json Exclude

· activation.json Never synced

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/maigret.tomlThe file this page is generated from

id = "maigret"

name = "Maigret"

homepage = "https://github.com/soxoj/maigret"

description = "Collect a dossier on a person by username from thousands of sites."

# The project's own logo, from its repository.

icon = "https://raw.githubusercontent.com/soxoj/maigret/main/static/maigret.png"

detect = ["maigret"]

# maigret/settings.py, SETTINGS_FILES_PATHS: the bundled

# resources/settings.json, then '/etc/maigret/settings.json', then

# path.expanduser('~/.maigret/settings.json'), then a settings.json in the

# working directory. Only the third is per-user. The documented behaviour

# matches: https://maigret.readthedocs.io/en/latest/settings.html.

paths = ["~/.maigret/settings.json"]

# maigret/db_updater.py: MAIGRET_HOME = path.expanduser("~/.maigret") and

# CACHED_DB_PATH = path.join(MAIGRET_HOME, "data.json") — the 3,000-site

# database Maigret re-downloads whenever a newer one is published. Derived

# data, not configuration.

exclude = ["~/.maigret/data.json"]

# maigret/activation.py: ACTIVATION_CACHE_PATH = path.join(MAIGRET_HOME,

# "activation.json"), written through os.open(..., 0o600). It caches the

# session tokens Maigret obtains from sites that require activation.

secret = ["~/.maigret/activation.json"]

# Read once at startup by a process that then runs one search.

side_effect = false

# maigret/resources/settings.json ships "openai_api_key": "" alongside

# openai_model and openai_api_base_url, filled in by users who run the --ai

# analysis mode. The rest of the file — timeouts, report formats, site lists —

# is ordinary configuration, so only the key itself is lifted out.

[[secret_paths]]

file = "~/.maigret/settings.json"

match = { key_path = ["openai_api_key"] }

# cookie_jar_file names a cookies file by absolute path on the machine that

# exported it. The proxy URLs next to it are not listed: tor_proxy_url and

# i2p_proxy_url default to loopback addresses that are the same everywhere,

# and proxy_url is a preference a user generally does want to carry. The jar

# path is the user's own doing and worth keeping to rebuild this machine, so it

# is stored for this device instead of being thrown away.

[[machine_lines]]

file = "~/.maigret/settings.json"

match = { key_path = ["cookie_jar_file"] }

scope = "backup"

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/maigret. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these keeps the credential file out. None of them splits cookie_jar_file for you — that part is Otty’s own sync, or a template you write by hand.