smtp/mike-2

An early fork by smtp focused on making database upgrades safer to replay.

Very early days: one tracked thread and a single push so far, both on 14 August 2026.

smtp's fork is an early infrastructure-focused variant, aimed at making selected database upgrade steps safe to run again without failing.

There is no stated rebrand, audience niche, or deployment offering yet. smtp is the only identity signal available. One caution for evaluators: the same update removes a substantial set of recent upgrade steps without explaining why, so GitHub is the right place to inspect the details before adopting it.

What's in it

Repeatable upgrades Hardens selected older database upgrades so they can be replayed more safely.
Upgrade-history change Removes a substantial set of recent upgrade steps, with no stated rationale.

Direction

infrastructure

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

📝 smtp fixes database replays but strips key safeguards 1 commit 23h ago securityinfrastructure draft

One useful installation fix is bundled with removals that could break fresh deployments and weaken data protections.

Threads of work (detailed view)

1 thread have been distilled into posts.

smtp fixes database replays but strips key safeguards

One useful installation fix is bundled with removals that could break fresh deployments and weaken data protections.

securityinfrastructure

1 commit · latest 23h ago