dropthejase publishes an honest scorecard for the AWS rebuild
Most forks quietly drift from upstream. This one writes down exactly where it has drifted, and where it falls short.
dropthejase is in the middle of rebuilding Louis on Amazon's cloud, and rather than burying the work in commit messages, the team has shipped a set of plain-English tracker documents alongside the code. One enumerates every feature in the original Mike and marks whether this fork preserved it, replaced it with an AWS-native equivalent, or deliberately skipped it. Another lays out the new system design end-to-end, with diagrams of how login, file upload, and chat now flow through Amazon's services.
Most striking is a "Known Gaps" section that openly lists what the fork does worse than upstream today - things like drag-and-drop attachments and certain sharing behaviours. There is also a short demo video linked from the README. For a fork in active migration, this level of self-auditing is unusual and unusually useful.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?