Same. And even if you were to fuck up, have people never heard of the reflog
…?
Every job I’ve worked at it’s been the expectation to regularly rebase your feature branch on main, to squash your commits (and then force push, obv), and for most projects to do rebase-merges of PRs rather than creating merge commits. Even the, uh, less gifted developers never had an issue with this.
I think people just hear the meme about git being hard somewhere and then use that as an excuse to never learn.
It’s not about prohibiting e2ee; it’s about enforcing client-side scanning.
Yes, that also breaks e2ee, but they can still go “nooo! E2ee is still perfectly fine and legal! You know, as long as we get to read anything anyways”
And realistically, this will probably end up being implemented on an OS-level as well. So even using a self-hosted matrix server would not be immune.
Not to mention that both you and your conversation partner needs to take steps to evade this; one party is not sufficient.