There is every reason. The federated model is by definition sticky. And that stickyness is based on the fact the URLs gain reputation over time. It's an archtectural design rather than a bug to be fixed. For example nostr is portable by design so that moving from one app to another "just works", and that's because of the architecture. Not trying to argue that one way is better than other, but rather, saying there are architectural trade-offs that are by design. There are hybrid architectures that can merge the two of course, this is a more difficult problem. So far the best we have is bridges, and that's OK!
nostr:npub1melv683fw6n2mvhl5h6dhqd8mqfv3wmxnz4qph83ua4dk4006ezsrt5c24 The video is a bit aspirational in that respect, but people are working on it. No reason it can't be made to work.
Discussion
nostr:npub1melv683fw6n2mvhl5h6dhqd8mqfv3wmxnz4qph83ua4dk4006ezsrt5c24
I understand the architectural differences :-)
I also believe that using the same account with multiple servers, and changing identifiers and "home base" for when interacting with the fediverse are very solvable problems. With the caveat that it hasn't really been broadly implemented.