HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dylex
slack-libpurple
C2019–2025
dylex / slack-libpurple

slack-libpurple

Slack module for libpurple

6Distinct people
7Mentions
0Explicit recommenders
289GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Slack module for libpurple

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2019-01-13 00:22:23 UTC to 2025-01-31 10:48:11 UTC.

01232019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC303
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

7 sources
Eion Robb has done an incredible amount of work in this space. His GitHub page[1] has tons of plugins, and I particularly appreciate the work he has done on the Matrix plugin to make it available to Windows users. Lest you think this is less than cool because you don't use Pidgin, bitlbee[2] is a great tool to get slack (and others!) into your IRC client. I haven't run it myself, but I know that it heavily relies on purple[3] for its magic. I can tell it gets a lot of use, perusing the issues on the slack purple plugin[4] for example. 1: https://github.com/EionRobb?tab=repositories 2: https://www.bitlbee.org/main.php/news.r.html 3: https://wiki.bitlbee.org/ 4: https://github.com/dylex/slack-libpurple/issues?q=is%3Aissue...
In Purple-Teams: MS Teams Plugin for Pidgin (2022)
> 4. A few good, Open Source native ports already exist, and people are just unaware of them. Native GUI clients: - Ripcord: https://cancel.fm/ripcord/ - Wey: https://github.com/yue/wey ("written in Node.js with native UI powered by the Yue library") - Volt: https://volt-app.com IRC bridges (allow using Slack from native IRC clients): - wee-slack: https://github.com/wee-slack/wee-slack - irc-slack: https://github.com/insomniacslk/irc-slack - bitlbee: http://bitlbee.org (using libpurple) libpurple plugin (allows using Slack from Pidgin, Adium, bitlbee): - https://github.com/dylex/slack-libpurple - Adium (native macOS app) plugin based on it: https://github.com/victori/slack4adium CLI clients: - https://github.com/erroneousboat/slack-term - https://github.com/haskellcamargo/sclack - the emacs one you mentioned Most of these clients don't su
Read the rest
pport 100% of Slack's features, aren't as pretty, and are generally not as 'polished' as the official client. But they're also mostly written by individuals in their spare time, as opposed to a team of full-time employees. So no, I don't think that native clients are 'actually a lot harder to build and maintain'.
In When a rewrite isn’t: rebuilding Slack on the desktop

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.