-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continue development #4
Comments
+1 |
2 similar comments
+1 |
+1 |
I've picked up (started over, mostly) development at dylex/slack-libpurple. So far, direct messages are working, and hope to have channels working in the next week. Happy to get testers/feedback. |
2 months later, any update? Are channels working? |
Ah, sorry, forgot about this issue. Yes, dylex/slack-libpurple is largely functional (or at least I haven't heard otherwise -- bug reports welcome there). Channels, groups, and IMs are working (though joining new channels/groups isn't complete yet, and multi-party ims haven't been tested). It's a complete rewrite, and only supports libpurple2. Simple text messages only so far (no icons, file transfers), and limited access to advanced slack features like editing and reactions. Only API token-based logins currenly. I use it regularly on multiple slacks, and am still working on it. Suggestions welcome. |
+1 |
Fixes necrosis#4 but causes memory leaks in other cases! At least consistent with other protocols, so this is really a libpurple leak.
Hi! What about continue developing?
The project is alive?
The text was updated successfully, but these errors were encountered: