|
@@ -135,4 +135,20 @@ mcporter --config "$CONFIG" call news.detect_emerging_topics limit=10
|
|
|
```bash
|
|
```bash
|
|
|
mcporter --config "$CONFIG" call news.get_news_sentiment entity=Bitcoin timeframe=24h
|
|
mcporter --config "$CONFIG" call news.get_news_sentiment entity=Bitcoin timeframe=24h
|
|
|
mcporter --config "$CONFIG" call news.get_news_sentiment entity=Ethereum timeframe=72h
|
|
mcporter --config "$CONFIG" call news.get_news_sentiment entity=Ethereum timeframe=72h
|
|
|
|
|
+
|
|
|
|
|
+## Blacklist enforcement (optional back-clean)
|
|
|
|
|
+
|
|
|
|
|
+If you change `ENTITY_BLACKLIST`, existing clusters in `news.sqlite` may still
|
|
|
|
|
+contain entities/keywords that would now be filtered at extraction time.
|
|
|
|
|
+
|
|
|
|
|
+For one-off cleanup, run:
|
|
|
|
|
+
|
|
|
|
|
+```bash
|
|
|
|
|
+./.venv/bin/python scripts/enforce_news_blacklist.py --dry-run --limit 200
|
|
|
|
|
+./.venv/bin/python scripts/enforce_news_blacklist.py --limit 1000
|
|
|
|
|
+```
|
|
|
|
|
+
|
|
|
|
|
+This enforces `ENTITY_BLACKLIST` inside stored clusters by removing matching
|
|
|
|
|
+entries from `payload.entities` and `payload.keywords` and (if needed) setting
|
|
|
|
|
+`payload.topic = "other"`.
|
|
|
```
|
|
```
|