Allowlist & Scheduled Sharing
Allowlist
Section titled “Allowlist”The Allowlist controls which domains are eligible for scheduled auto-sharing. Only pages on allowlisted domains will be extracted on a timer.
Manual sharing (popup, shortcut, context menu) works on any domain regardless of the Allowlist.
Adding Domains
Section titled “Adding Domains”- Go to Settings → Allowlist
- Type a domain pattern and press Enter
- Toggle domains on/off individually
Domain Patterns
Section titled “Domain Patterns”| Pattern | Matches |
|---|---|
github.com | Exact domain |
*.github.com | All subdomains (gist.github.com, docs.github.com, etc.) |
news.ycombinator.com | Exact subdomain |
Presets
Section titled “Presets”Click a preset button to add a curated group of domains:
| Preset | Domains |
|---|---|
| Dev | github.com, stackoverflow.com, developer.mozilla.org, etc. |
| News | reuters.com, bbc.com, cnn.com, nytimes.com, etc. |
| Social | reddit.com, twitter.com, mastodon.social, etc. |
| Streaming | twitch.tv, youtube.com |
Per-Domain Template
Section titled “Per-Domain Template”Each allowlisted domain can optionally bind to a specific template. When the scheduler extracts that domain, it uses the bound template instead of the default.
Scheduled Sharing
Section titled “Scheduled Sharing”When enabled, Context Bro periodically extracts pages from allowlisted domains and sends them to your default endpoint.
Configuration
Section titled “Configuration”Go to Settings → Schedule:
| Setting | Options |
|---|---|
| Enable | Toggle auto-sharing on/off |
| Interval | 5min, 10min, 15min, 30min, 1hr, 2hr |
| Mode | Focused tab only / All allowed tabs |
How It Works
Section titled “How It Works”- The Chrome Alarms API fires at your configured interval
- Context Bro queries your open tabs
- Tabs matching allowlisted domains are selected
- For each selected tab:
- Content is extracted
- A SHA-256 hash is computed
- If the content hasn’t changed since last share → skip (dedup)
- Otherwise → compile template → POST to default endpoint
Deduplication
Section titled “Deduplication”Content hashes are stored locally in chrome.storage.local. This prevents sending the same unchanged page repeatedly. Hashes are cleared when you clear extension data or uninstall.