In that case, overloading wouldn’t be a general solution either, even ignoring everything else, because the clashing methods may happen to have similar types.
I’d suggest that actor interfaces defined to be implemented by other actors should take care of properly namespacing method names, e.g., by some “owner” prefix. We might want to think about establishing some conventions for that.