The requests for the ability to edit a toot are as numerous as the explanations given as to why that is technically complex in a federated network of independently operated servers. I’d like to propose an optional “Toot Confirmation Prompt” that would act as an off-ramp opportunity for a user to notice a change they would like to make before actually sending the toot.
An example process flow for a user with the confirmation prompt toggled on:
User types toot as normal and clicks/taps the Toot button.
The user is shown a client-side-only rendering of the toot as it will be displayed in their home feed upon confirming, along with a “Commit” (but will better verbiage) button, an “Edit” button, and a “Cancel (Delete Toot)” button, each triggering the obvious action.
I think this could eliminate many user issues around the lack of edit functionality without requiring a massive engineering effort that is ultimately doomed to fail in actual practice until such point that the underlying protocols have a well-adopted strategy that makes this type of trick obsolete.