You open the composer, you write half a note, your mouse drifts, you click once outside the box -- and it's gone. No warning, no draft, nothing. I did that to my own users and didn't notice for a while.
The community composer opens as a modal sheet. Modals, by default, are helpful in a way that is occasionally hostile: click outside them, or press Escape, and they close. That's correct for a menu or a confirmation dialog. It is exactly wrong for a box someone is typing into, because 'close' here means 'discard everything you just wrote'. A stray click on the backdrop, a reflexive Escape to dismiss something else, and the post is nuked.
The fix is small and unglamorous: guard the two dismiss paths so a click outside and an Escape key no longer close the sheet. Only the X button closes it now. Your half-written thought stays on screen until you decide, deliberately, to throw it away. That's the whole change. It's the kind of fix no one will ever thank you for, because the failure it prevents is invisible -- you don't get a bug report saying 'the post I was writing vanished', you just get a person who quietly writes fewer posts.
Two more from the same day
I also flipped the community to open on Hot instead of New. Bare /community used to land on the newest note and sit there frozen until you tapped a 'new notes' pill to refresh. Hot is a fresh seeded shuffle every visit, with recent notes bumped to the front, so the feed feels alive on arrival instead of static behind a button you had to keep pressing. A nice side effect: the pill stops mattering on the default view, because every visit already re-surfaces the latest.
And sharing a game result to the community got less flat. It used to drop one blob of text into the composer. Now it splits the headline into the title field -- 'I Solved Alfazy #87 in 5/6' -- and puts your result grid plus a hashtagged 'Try now #Alfazy' line in the body. So a shared solve reads like a real post and clicks straight into the hashtag feed, instead of looking like something a bot pasted.
None of these are big. But they're the same instinct three times: the tool should protect what the person is doing. Don't eat a half-written post. Don't freeze the feed until they tap a pill. Don't turn a proud solve into a text blob. Most days the work isn't a feature -- it's removing a small papercut I put there myself and never felt, because I wasn't the one bleeding.