RULES.md is your audit checklist for AutistMask; agents never edit it. Two lines in its External Communication section describe services the extension no longer contacts:
"Extension contacts exactly three external services: configured RPC endpoint, CoinDesk price API, and Blockscout block-explorer API". After your rulings, CoinDesk is gone (USD prices come from Chainlink feeds read through the RPC endpoint, #525), and Blockscout and Etherscan stay off until the user turns them on (#668). A fresh install contacts only the RPC endpoint.
"No user-specific data sent except to the configured RPC endpoint". With "Use Blockscout" on, the user's addresses go to Blockscout; with "Check recipients on Etherscan" on, the recipient address being confirmed goes to Etherscan.
Proposed replacements, in the same order:
"Until the user changes a setting, the extension contacts only the configured RPC endpoint"
"No user-specific data sent except to the configured RPC endpoint, unless the user turns on "Use Blockscout" or "Check recipients on Etherscan", both off by default"
Options:
As proposed: a worker opens a PR into next that replaces those two lines with the wording above, assigned to you to merge, as with the merge rule (#193).
Your wording: reply with the lines you want; the PR uses them.
Leave as is: RULES.md keeps the old lines. README.md, which RULES.md says governs where the two disagree, already describes the code.
Recommendation: As proposed. The checklist then matches the privacy ruling, and an audit against it checks the right thing.
Split out of #211, which asked this alongside the password edit.
Model: opus-5-5
`RULES.md` is your audit checklist for AutistMask; agents never edit it. Two lines in its External Communication section describe services the extension no longer contacts:
- "Extension contacts exactly three external services: configured RPC endpoint, CoinDesk price API, and Blockscout block-explorer API". After your rulings, CoinDesk is gone (USD prices come from Chainlink feeds read through the RPC endpoint, https://git.eeqj.de/sneak/AutistMask/issues/525), and Blockscout and Etherscan stay off until the user turns them on (https://git.eeqj.de/sneak/AutistMask/issues/668). A fresh install contacts only the RPC endpoint.
- "No user-specific data sent except to the configured RPC endpoint". With "Use Blockscout" on, the user's addresses go to Blockscout; with "Check recipients on Etherscan" on, the recipient address being confirmed goes to Etherscan.
Proposed replacements, in the same order:
- "Until the user changes a setting, the extension contacts only the configured RPC endpoint"
- "No user-specific data sent except to the configured RPC endpoint, unless the user turns on "Use Blockscout" or "Check recipients on Etherscan", both off by default"
Options:
- **As proposed**: a worker opens a PR into `next` that replaces those two lines with the wording above, assigned to you to merge, as with the merge rule (https://git.eeqj.de/sneak/AutistMask/issues/193).
- **Your wording**: reply with the lines you want; the PR uses them.
- **Leave as is**: `RULES.md` keeps the old lines. `README.md`, which `RULES.md` says governs where the two disagree, already describes the code.
Recommendation: **As proposed**. The checklist then matches the privacy ruling, and an audit against it checks the right thing.
Split out of https://git.eeqj.de/sneak/AutistMask/issues/211, which asked this alongside the password edit.
Model: opus-5-5
sneak
was assigned by clawbot2026-11-10 20:48:25 +01:00
clawbot
added this to the 1.0.0 milestone 2026-11-10 20:48:30 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
RULES.mdis your audit checklist for AutistMask; agents never edit it. Two lines in its External Communication section describe services the extension no longer contacts:Proposed replacements, in the same order:
Options:
nextthat replaces those two lines with the wording above, assigned to you to merge, as with the merge rule (#193).RULES.mdkeeps the old lines.README.md, whichRULES.mdsays governs where the two disagree, already describes the code.Recommendation: As proposed. The checklist then matches the privacy ruling, and an audit against it checks the right thing.
Split out of #211, which asked this alongside the password edit.
Model: opus-5-5