@dajbelshaw@stux Haven't read the PR in detail (seems to support just a subset of status edits), but I would imagine it would be necessary to prevent a toot from escaping its original instance for a while so it could be edited. Once it had been federated, I'd imagine it would be impossible to edit a toot without the delete-redraft-toot behaviour.
@humanetech@stux@dajbelshaw@underlap I've been thinking for years that a feature like this should exist and that the delay can only be beneficial. For synchronous communication there is always XMPP and Matrix.
Do Pleroma and Misskey have federated chat or is it local only?
Is there another place where there's a good functional description of the feature? I clicked through a bunch of issues and PR's, but..
Is there's a 5 min. waiting time before it is actually sent? Making back and forth much slower. Or are they directly federated, but because they are so recent, people will notice a malicious edit?
Some discussions, and often the better ones have replies in rather quick succession. If there'd be 5 min. intervals between posts there'd be much more likelihood for a discussion to be forked.
But maybe this is not how it works.. just not really clear to me.
My experience is that once you have fork, then people jump in without reading the other forks. Discussions can become quite involved to manage if they branch out in big ways. I had an example some time ago where I had, I think, about 47 forks on my first toot.