ENGLISH | 简体中文
This project aims to transport messages between different IM platforms.
Imagine a world...
...where it is as simple to message or call anyone as it is to send them an email.
...where you can communicate without being forced to install the same app.
This project assumes that different message sources are distributed on networked computers, so different IM-related components need to communicate and coordinate their actions through messaging.
This project is therefore built on top of NATS, an open source, lightweight, high-performance distributed messaging middleware. Different chat platforms communicate through NATS.
- High Performance: Uses coroutines (aka green threads), and on the JVM we aggressively use platform-related JNI libraries.
- Asynchronous: Does not block the main thread on Minecraft related platforms and implements structured concurrency as much as possible. Almost no blocking IO is used.
- Low Overhead: Try to use GC-free Rust to write related components and JVM to use off-heap memory with the help of JNI.
- Automation: The project uses GH-Action for continuous integration and focuses on a highly reproducible build process. New changes to the application code are regularly built, tested and released to GH-Release.
See User Guide
- Text message
- Image message
- Video message
- File message
- Voice message
- Reply to quote
- Mention(@)
- Merged forward message
- Group chat
- Private chat
- Log pull
- TG Channel Post
- TG channel discussion forum
- QQ-MiraiConsole via mirai
- QQ-OneBot12 via walle-core Delayed
- Telegram via teloxide
- Discord via serenity
- Minecraft-Bukkit 1.12-1.19
- Minecraft-Fabric 1.16-1.18
- Minecraft-Forge 1.18
- Minecraft-Bungeecord/Velocity WorkInProgress
- Matrix-Oicq-Bridge via Matrix WorkInProgress
@Itsusinn/逸新(Maintainer)
Any PR would be welcomed.