To really rake things to the next step, we need public key addressing. Ubiquitous adoption of IPv6 would suffice, but public key addressing would be better. Either way, using a domain as a permanent identifier is a fragile and brittle.
Another big problem with AP is that the spec is extensible in ill defined ways while being designed with current social UX in mind, thus counterintuitively making it needlessly restrictive. So there are interoperation problems with different server software that implement the spec differently (look at federating servers like peertube, Lemmy and mastodon, while possible, it is clanky), meanwhile it has to be modified to support ForgeFed (which is what gitea will be using to federate forges).
Perhaps your argument is around DNS spoofing or something but domain names feel pretty non-controversial for most usecases, especially for the fediverse, which is about federation. There's an expectation of multiple multi-user services being the norm!
It is a brittle point of failure in activitypub.
I think I understand better what you’re saying though