Als Antwort auf @max:kamax.io
I don't use it, so can't help with the specific item menu

mextor: 𝓜𝓪𝔁𝓲𝓶𝓲𝓵𝓲𝓲𝓵𝓲𝓪𝓷 I'll take this opportunity to explain a bit more what is going on, which I'll re-use for the wiki page...

Up until two days ago, there was no mechanism in the stable identity spec to remove emails and phone numbers. This was never a problem since synapse had a client API endpoint and just removed it from its database. All well and good. Then NV decided to go for a way to remove it which we disagreed with.

At this, instead of behaving like good imlementation neighbour, they used an arbitrary and unspeced enpoint in live environement as if it was totally legal and already in the spec. That removal because synapse expected the identity server to implement the endpoint. So while it was working fine for matrix.org that had the full custom stack, it broke for everyone else.

People kept on reporting the issue which I always redirected to synapse. Tried to talk with the NV peeps that the spec matter was one thing, but breaking people experience over an unstable endpoint wasn't right. Be a good neighbour. Just show a warning or smth, have a config option, whatever. But don't break implementation that follow the latest stable spec. Tired of having the blame constantly shifted to mxisd, we added the warning

Now, the new stable spec offers two ways to authenticate while removing emails, but Riot and synapse only still implement/offer one of them. Given that mxisd is allowed per spec to decline the use of one but allow the other, we did that in v1.4.5 and removed the warning.

Two issues were spotted in synapse and the spec regarding this, so I hope that maybe finally synapse and Riot will behave in a user friendly manner and not just account for matrix.org and/or vector.im userd and be the neutral custodian of the spec they claim to be, without favoritism for their own people.

mxisd v1.4.5 allows removal of 3PID via regular "send email validation, click link" method. It would be best to not be a bystander if you want it supported in Riot/synapse and go open/+1 issues about it.