Duplicated maps cost nothing unless we’re dealing with millions but a 1core->64core instance would never have such use case so it’s no inefficiency there. Simply an inconvenience for those that spent long hours coding with these private apis.
Fortunately for me it was a matter of adding producers to appData and keeping track that way, but for global search I had mapped the room and user handle. Ex.
So if I loop through a room or its users I can still through appData get their producers, if there’s active consumers which pipes/networks they belong to, how much they’ve been consumed.
I’ll admit, using the private API I didn’t think was a risk but I get it fully, there’s better ways to setup and IBC just trying to apply the dankest standards. No foul here and hope others can adjust. IBC you do amazing work, this is one slip up for me but answered quickly and is no problem.