It doubled the complexity of storing and working with events. Also made indexing and finding all events for a pubkey a little more difficult.

I agree its a really cool idea. But for a client to support NIP-26 it would have to support the possibility of two pubkeys for every event it sees
It sounds easy on the surface but it double the complexity if everything downstream of events (which is the whole client) 

 Ok, that makes sense. I wonder if it’s worth the trouble. To me it seems it’s worth it, but I cannot say how much of a trouble it is 🐶🐾🫂 

 Personality I would go with NIP-46 over NIP-26 

 They serve different purposes AFAIK, and more centralized. Unless my understanding is completely off 🐶🐾🫡