It would be nice if implementations settled on unified API patterns but that's never going to happy, especially when there's no feature parity and implementations have bigger fish to fry.
We'd really like to break our connectors off into its own library for others to use at some point. That could go a long way in helping developers integrate multiple implementations at once and give users more options. That being said we have a lot of things we're working on, so who knows when we'll get around to it
I started one and asked the same question on the previous Alby AMA #41443 https://github.com/dolu89/una We had some discussions with Bumi from Alby about an unified API. Maybe you should come talk with us?
reply