Maddox
f8f89b794e
Issue #3. Audit confirmed every Emby endpoint we use (/System/Info/Public, /Sessions, /Users/{id}/Items[/Latest|/Resume], /Items/{id}/Images/Primary) is API-compatible with Jellyfin, and the ?api_key= auth scheme works on both. So 'add Jellyfin support' is really 'document it and fix display labels' — no client branching needed. Added a 'type: emby|jellyfin' field inside the emby config block (defaults to emby for backward compat). New _media_label() helper sources the label from config and is threaded through: - !media health server name - !media nowplaying header + empty-state - !media help section header + health command summary - daily digest 'not yet in <server>' line README updated with a Jellyfin example block and notes that the URL should NOT include the /emby suffix when pointing at Jellyfin. |
||
|---|---|---|
| .. | ||
| clients | ||
| __init__.py | ||
| bot.py | ||
| db.py | ||