13 hours ago
- Building a custom bridge between Slack and Teams involves multiple bridge types based on user management, such as dual licenses, no dual licenses, multiple apps, or multiple guests, each with different costs and user representation challenges.
- Representing 'other side' users (absent users) is a core challenge, requiring solutions for messages, DMs, files, channel membership, and reactions, which vary based on licenses and API updates.
- Asymmetrical features between Slack and Teams, like channel types, threads, file handling, and platform limits, create technical complexities that must be addressed in the bridge's logic.
- A robust architecture is needed to achieve low latency, scalability, API agnosticism, error/retry management, and security, all while adapting to evolving APIs.