3 Commits

Author	SHA1	Message	Date
agessaman	e348fd8d53	Enhance profanity filtering to include hate symbol detection and censorship ... - Updated the profanity filter to check for hate symbols (e.g., swastika Unicode) in addition to word-based profanity, ensuring comprehensive message filtering. - Modified the `censor` function to replace hate symbols with `***`, maintaining functionality even when the `better-profanity` package is unavailable. - Updated documentation in `discord-bridge.md` and `telegram-bridge.md` to reflect the new hate symbol handling features. - Added tests to verify detection and censorship of hate symbols, ensuring robustness of the profanity filter.	2026-03-01 21:56:13 -08:00
agessaman	3c56cbb69d	Add profanity filter options for Discord and Telegram bridges ... - Introduced `filter_profanity` configuration option in `config.ini.example` to handle profanity in bridged messages: options include `drop` (default), `censor`, or `off`. - Updated `requirements.txt` to include `better-profanity` for profanity filtering functionality. - Enhanced `DiscordBridgeService` and `TelegramBridgeService` to implement the profanity filter logic, allowing messages with profanity to be dropped or censored before bridging. - Updated documentation in `discord-bridge.md` and `telegram-bridge.md` to reflect the new profanity handling feature.	2026-03-01 21:47:53 -08:00
agessaman	dcb90188c0	feat(telegram-bridge): add one-way MeshCore → Telegram channel bridge ... - Add TelegramBridgeService: CHANNEL_MSG_RECV → sendMessage, per-chat queues, rate limiting, retries; aiohttp with requests fallback; HTML formatting, truncation, no DMs - Config [TelegramBridge]: api_token (or TELEGRAM_BOT_TOKEN), bridge.<channel>=chat_id - Normalize channel matching (strip #, case-insensitive) so bridge.HashTagChannel matches #HashTagChannel - Add config.ini / config.ini.example sections and docs/telegram-bridge.md (setup, private chat ID, troubleshooting)	2026-03-01 10:23:38 -08:00