GSoC/2017/StatusReports/DavideRiva
Brooklyn
Chat Bridge (now called Brooklyn) is intended to be a protocol-independent chat-bridge to allow messages forward to and from various chat systems.
It has to support Telegram, RocketChat and IRC but it has to be modular (for future expansions).
Current solutions do not offer an adequate integration because, besides generic text, not much is implemented. A big missing feature is the ability to exchange complex formats, such as images or file attachments.
Work report
Blog posts
- First month report: my feelings about gsoc
- Brooklyn 0.1 is out there: full Telegram and IRC support
- Stop writing code like we're in the '90s: a practical approach (PART I)
- Brooklyn 0.2 released, ready for production
Code
Contributions to external repos
- Informations about token expiration
- Connection message missing in Realtime-API documentation
- Java-WebSocket 1.3.3 doesn't exist on maven
- Alias not changing when messages are sent without receiving other messages between
- DDP slingshot/uploadRequest returns "The directive rocketchat-uploads does not seem to exist"
- Improvement on messages readability
Binaries
Who uses it and where?
Last update: 14 august 2018
- Wikitolearn: #general, #wikitolearn-tech and #general-ita channels on IRC, Telegram and Rocket.Chat.
- UnixMiB: #unixmib on IRC and Telegram.
Citations
- Phoronix - KDE Brooklyn Chat Bridge Sees Its First Release
- Phoronix - KDE Brooklyn Chat Bridge Declared Production-Ready
- Reddit - KDE Brooklyn Chat Bridge 0.2 released, ready for production
- Conheça o KDE Brooklyn Chat, um IM versátil para múltiplos protocolos
- Chatanwendung »Brooklyn« vorgestellt
- Chat-Anwendung Brooklyn für den Einsatz freigegeben