Miles WardandClaude Fable 5.1
ad3720edbf
Platform-neutral successor to Discord Authenticator, forked from its v0.1.2
state with fresh history. Same vault, same UI, same live-message mechanism —
now behind one `Sink` that speaks three platforms.
Why each platform needs what it needs (this drove the whole settings model):
- Discord: an incoming-webhook URL. Webhooks can edit their own messages.
- Slack: a bot token (xoxb-, scope chat:write) + channel ID. Slack incoming
webhooks can post but never edit, and editing IS the live mechanism, so
chat.postMessage / chat.update via a bot is the only path.
- Telegram: a bot token + chat id. No webhook concept exists. The app detects
the chat id itself from the bot's pending updates ("send /start, then
Detect"), since users rarely know it.
- core: Provider enum; settings hold all three configs so switching back and
forth never re-asks for tokens; per-platform shape validation that names the
common mistakes (xoxp- user token, #name instead of channel ID); a
destination key that clears message ids on platform/channel change but not
on token rotation
- delivery: shared DeliveryError + pacing Governor; Discord client refactored
onto them; new Slack client (classifies Slack's ok:false-on-HTTP-200
errors) and Telegram client ("message is not modified" is success; chat
detection via getUpdates); provider-agnostic message builders — code in a
copyable span everywhere, rollover time as live as each platform allows
- http-api: setup accepts an optional provider; settings PUT/GET carry the
full model; /api/slack/whoami, /api/telegram/whoami, /api/telegram/chats
- webui: three-way optional picker on setup and in Settings → Delivery with
guided per-platform fields; "Check token" (Slack) and "Detect chat"
(Telegram); inline white mark via currentColor
- brand: white mark on the dark plate; blue stays with the Discord sibling
- docs/TEAMS.md: exploration for v0.2 — Teams connectors were disabled May
2026 and Workflows webhooks can't edit, so live tiles need a Bot Framework
bot; options for the inbound endpoint on a homelab and a recommended scope
Verified against mock Discord, Slack and Telegram servers speaking each
platform's real protocol shape: edits target the same message rather than
re-posting, deleted tiles are recovered, dead credentials are surfaced with a
next step, renames refresh without a rollover, and switching platform reposts
on the new one and leaves the old one alone. 138 tests.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
26 lines
919 B
Rust
26 lines
919 B
Rust
//! Dump sample tiles for eyeballing: `cargo run -p openmfa-render --example preview`.
|
|
fn main() {
|
|
let out = std::env::args().nth(1).unwrap_or_else(|| ".".into());
|
|
for (issuer, label, code, period) in [
|
|
("Cloudflare", "[email protected]", "482913", 30),
|
|
("Plex", "[email protected]", "071204", 30),
|
|
("Ubisoft", "casperadmin", "93810245", 30),
|
|
] {
|
|
let t = openmfa_render::Tile {
|
|
issuer,
|
|
label,
|
|
code,
|
|
period,
|
|
};
|
|
let png = openmfa_render::tile_png(&t).unwrap();
|
|
let webp = openmfa_render::tile_webp(&t).unwrap();
|
|
std::fs::write(format!("{out}/tile-{issuer}.png"), &png).unwrap();
|
|
std::fs::write(format!("{out}/tile-{issuer}.webp"), &webp).unwrap();
|
|
println!(
|
|
"{issuer:12} png {:>6} B webp {:>6} B",
|
|
png.len(),
|
|
webp.len()
|
|
);
|
|
}
|
|
}
|