mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-17 04:11:35 +00:00
from a live blocked-sites pass (no PII): - posture shift: blind opt-out is the DEFAULT, not a fallback -- submit on every site with an accessible removal channel even without first confirming a listing (own identifiers to the broker's own official channel = still least-disclosure). guided flows double as the authoritative search. - blocked-form rule: when a form is automation-hostile (hard captcha / cloudflare / datadome / slide-to-verify), default to the broker's CITED rights-email rather than recording blocked. - captcha policy clarified: never defeat behavioral/token/slider challenges; ok to read a static distorted-text or plain-arithmetic captcha on the subject's own opt-out; stop if the whole submission is rejected after a correct answer (fingerprinting the automation, not grading it). - intelius/peopleconnect: delete-wipes-suppression is field-confirmed -- a deletion-complete email means the suppression is gone and the subject re-lists cluster-wide; re-run suppression and verify the Control step reads "suppressed". guided-mode session persists; DOB is an <input type=date>. - new records: addresses.json (intelius front-end, cluster-covered) and socialcatfish.json (cited rights-email lane + automation-hostile form). - new references/site-playbooks.md: per-site game-plan matrix (8 blocked-tail sites), the meta-search no-op skip-list (idcrawl/lullar/yasni/webmii/namesdir/itools/skipease), and the infopay / peopleconnect backend clusters. OSINT-list triage taxonomy added to methods.md. - state-machine.md: fixed doc drift + documented submitted->not_found illegal (resolves as awaiting_processing), blocked->submitted via action_selected, operator_manual_check, --evidence & pitfall. tests: standalone 99, PR 97 (+1 cluster-coverage regression); ruff + windows-footguns clean.
52 lines
1.8 KiB
JSON
52 lines
1.8 KiB
JSON
{
|
|
"id": "addresses",
|
|
"name": "Addresses.com",
|
|
"category": "people_search",
|
|
"priority": "standard",
|
|
"jurisdictions": [
|
|
"US"
|
|
],
|
|
"covered_by": "intelius",
|
|
"search": {
|
|
"method": "url_pattern",
|
|
"url": "https://www.addresses.com/",
|
|
"fetch": "web_extract",
|
|
"match_signal": "result",
|
|
"by": [
|
|
"name"
|
|
],
|
|
"url_patterns": {
|
|
"name": "https://www.addresses.com/people/{First}+{Last}"
|
|
},
|
|
"url_format_quirks": [
|
|
"Name people page: /people/{First}+{Last} (a literal '+' joins first and last). Surfaced a real subject listing during the OSINT cross-check.",
|
|
"It is a PeopleConnect/Intelius FRONT-END: every 'report' link resolves to tracking.intelius.com. The data is the Intelius cluster's."
|
|
]
|
|
},
|
|
"optout": {
|
|
"tier": "T1",
|
|
"method": "web_form",
|
|
"url": "https://suppression.peopleconnect.us/login",
|
|
"requires": {
|
|
"profile_url": false,
|
|
"email_verification": true,
|
|
"captcha": false,
|
|
"gov_id": false,
|
|
"account": false,
|
|
"phone_callback": false,
|
|
"payment": false
|
|
},
|
|
"inputs": [
|
|
"contact_email"
|
|
],
|
|
"notes": "COVERED BY THE INTELIUS/PEOPLECONNECT CLUSTER -- do NOT file a separate opt-out. addresses.com is a front-end (report links -> tracking.intelius.com), and 'addresses' is listed in intelius.owns, so one PeopleConnect suppression (see intelius.json) removes it too. Recorded here only so the scan cross-check has the URL pattern and knows it maps to the parent. After the intelius suppression confirms, re-scan this URL to verify it dropped.",
|
|
"quirks": [
|
|
"Front-end only; holds no independent removal channel. The PeopleConnect Suppression Center is the lever."
|
|
],
|
|
"est_processing_days": 7,
|
|
"reappearance_risk": "medium"
|
|
},
|
|
"last_verified": "2026-07-03",
|
|
"source": "field_verified",
|
|
"confidence": "documented"
|
|
}
|