Well not everyone uses #nostr. Just as an example nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 runs a bridge that lets nostr users interact with ActivityPub users.
If you’re only using your own relay, and not reading or writing to any other relays, then you probably don’t benefit from that. (Unless of course you get those bridges to read & write from your relay).
The question is that how those who are running relays benefit off of it? Latest consensus I’ve heard “they don’t and there will be relays operated by big nostr-clients” and then there is a question why if a nostr-client has to operate a relay (since it doesn’t make sense to operate a relay for non-client-affiliated entity) then why would client devs benefit off of interoperability, letting their customers go away to their competitors anytime? Given the fact that current social network “client+relay” developers i.e. Facebook/Twitter are not doing this?
I think there is a difference between users, and relay operators here. The biggest benefits to interoperability are for users.
I think the other assumption with your comment seems to be that of a single relay model. #nostr isn’t a single relay (or server) model. It can be if the user decides to go down that path. But it doesn’t have to be.
Client devs tho benefit off of interoperability because it brings more content into #nostr. Which leads to a better user experience.
