Skip to content
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

Open
prowsu opened this issue Jun 2, 2017 · 7 comments
Open

Continue development #4

prowsu opened this issue Jun 2, 2017 · 7 comments

Comments

@prowsu
Copy link

prowsu commented Jun 2, 2017

Hi! What about continue developing?
The project is alive?

@covert8
Copy link

covert8 commented Jun 17, 2017

+1

2 similar comments
@gatlinnewhouse
Copy link

+1

@andreineustroev
Copy link

+1

@dylex
Copy link

dylex commented Jul 12, 2017

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.

@tofof
Copy link

tofof commented Sep 7, 2017

2 months later, any update? Are channels working?

@dylex
Copy link

dylex commented Sep 7, 2017

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.

@revmischa
Copy link

+1

grimmy pushed a commit to grimmy/slack-libpurple that referenced this issue Oct 12, 2019
Fixes necrosis#4 but causes memory leaks in other cases!  At least consistent
with other protocols, so this is really a libpurple leak.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants