v1.62.0 — per-echo boost toggle

FeedEcho v1.62.0 — per-echo boost toggle

Boost is no longer all-or-nothing per Mastodon account. Each Mastodon echo on the Echoes page now has its own Boost: On/Off toggle, so you can boost only specific echoes without turning on the account-wide setting.

How it works

• Account setting off: the per-echo toggle decides. New and existing echoes default to off; flip on only the echoes you want boosted. Applies from the moment you switch it on — already-published posts are not boosted retroactively.
• Account setting on: every echo to that account is boosted. The per-echo control shows as a locked Boost: Account badge instead of a toggle, and the API refuses per-echo enables — the two settings can't both be newly turned on for the same destination.
• Turning the account setting back off restores whatever per-echo flags you had set; nothing is wiped.
• Editing an echo's destination clears its boost flag, so a stale flag can never attach to a different destination. Edits that don't change the destination (template, content warning, etc.) leave it alone.
• Import/export deliberately does not carry the flag — restoring a config export leaves per-echo boost off (same precedent as one-shot state).

The scheduler-level gate is unchanged: only public and unlisted echoes are ever boosted, and a boost request remains fire-and-forget (a booster outage never delays or fails the post itself).

Who sees this

The per-echo toggle (and the account-level toggle) only appear when a FeedBooster is configured (FEEDECHO_BOOSTER_URL + FEEDECHO_BOOSTER_TOKEN). On the hosted service that's @feedbooster@feedecho.net. Self-hosters running their own FeedBooster get the same toggles; without a booster configured nothing is shown and nothing changes.

Upgrading

No action required. No new environment variables, no config or startup gates; the new column is added by the startup migration and defaults to off. Boost behavior for accounts that already had the account-level toggle on is unchanged.