The unknown request will be buried in spam - a problem we have already, but worse.

And I do not want an infinite thread conversation. I want to be able to split off - and perhaps archive and export - different conversations by topic.

I recently had to some legal things, which included forwarding copies of a certain conversation to a lawyer. This turns out to be unreasonably difficult because email clients quote previous conversations. You want a clean thread of comment and reply about a specific topic. You don't get that.

You do get it on chat services, but there's no option there to create sub-conversations.

If I was redesigning email I would think long and hard about different use cases and workflows and start with an RFC. Protocols are far downstream of that.

> You do get it on chat services, but there's no option there to create sub-conversations.

It's called threads - even Matrix has these