What does HackerNews think of wee-slack?

Good distraction-free usable Slack already exists as the wee-slack plugin for WeeChat:

https://github.com/wee-slack/wee-slack

https://www.futurile.net/2020/11/30/weechat-for-slack/

My company forced us all onto Slack and I'd hate being forced to use the official interface. My productivity would fall due to the woeful implementation of threads hiding information, and the pathetic control and filtering of notifications.

It may not be helpful in your particular case depending on how your Slack is administered and similar, but my setup is like so:

- https://github.com/wee-slack/wee-slack with WeeChat (weechat.org) for IM only (i.e. configured so that it only notifies when an IM (one-on-one or group) is received); and

- https://github.com/tomhrr/paws for retrieving messages from Slack as email, and sending responses to those emails to Slack.

https://github.com/nicm/fdm is used for all filtering of email, including Slack messages. This allows for rules like e.g. marking everything from Slack as read, unless it's from channel X and matches your username, or it was sent after 6pm, or similar.

With this setup, IMs still come through as IMs, but everything else goes to email and is treated like email. Retrieving email and Slack messages happens based on local configuration, so it can e.g. be set up to fetch once per hour, and then all of those messages can be dealt with in one go. As the filters are refined, the number of useless messages that have to be reviewed decreases. With this configuration, at least in my experience, Slack is much less of a nuisance.

There is a pretty well updated cli for Slack built on top of WeeChat (hailing from IRC heritage) https://github.com/wee-slack/wee-slack

> - My company uses Slack's enterprise auth, and all the CLI slack clients I could find haven't been updated in years and no longer work.

https://github.com/wee-slack/wee-slack is decent.

> - The web is using more javascript than in the past.

cli browsers are probably the only truly unrealistic thing. An idea that I've been kicking around for a while is to build a simple CLI "browser" that uses PhantomJS or similar under the hood to request, load, and render the page into an image, convert the image to sixel (https://en.wikipedia.org/wiki/Sixel) and display it that way (or use any of the various terminal emulator-specific features (KiTTY has https://sw.kovidgoyal.net/kitty/graphics-protocol/ for example)). Probably pretty clunky, but it's doable if you're in the mood to write something purely for fun.

> - Mutt doesn't handle multiple email accounts natively for work/personal. The solutions are hacks at best. Email servers are starting to use more complete auth mechanisms that don't work well with mutt.

I don't think they're hacks. You can define exactly how you want it to work. That's a feature, not a bug. Sure, it takes a little bit of work to set up but you can use https://github.com/cweagans/dotfiles/tree/master/.config/mut... as a starting point if you'd like.

There's also https://github.com/wee-slack/wee-slack which is a plug-in for the weechat irc client.

I don't, but I use weechat (wee-slack) for 99% of my desktop slack. Less obtrusive than the stand alone and web clients. And way less resource hungry.

I don't use slack outside of work, but I always have the idea of using weechat more - for irc and/or other protocols.

https://github.com/wee-slack/wee-slack

Looks like a good project, I may give it a try on Windows.

On Linux, I use weechat to connect to a local bitlbee for Discord and Hangouts. When I was using Slack I used wee-slack [0] with success, but it looks like bitlbee has a plugin for Slack, too [1]. This lacks a few of the features of Ripcord (e.g. voip, graphical emoji, emoji completion), but it works.

[0] - https://github.com/wee-slack/wee-slack

[1] - https://wiki.bitlbee.org/

ctrl-f "wee-slack"... not found.

https://github.com/wee-slack/wee-slack

It works great!

I can also recommend you to look at: https://github.com/wee-slack/wee-slack

* Email - neomutt + notmuch.

* Chat - Weechat + WeeSlack (https://github.com/wee-slack/wee-slack)

* Pair Programming - tmate.io + neovim

* Google Play Music - tuijam(https://github.com/cfangmeier/tuijam)

I really like bat (https://github.com/sharkdp/bat) as a cat replacement, and I've been enjoying using entr (http://entrproject.org/) for running tests automatically when code changes.

There are already 3rd party Slack clients ( https://github.com/wee-slack/wee-slack https://github.com/bkanber/Slackadaisical https://github.com/evanyeung/terminal-slack ). Using the same approach as them would let you have more control.

OTOH, like someone else said, please contribute to improving riot/matrix instead.

How does this compare to wee-slack (slack gateway/plugging for the wee-slack irc client)?

https://github.com/wee-slack/wee-slack

Neat idea for a minimal slack experience.

However if all you want is a low bandwidth text only slack alternative to use with slow and glitchy cellular I’ve got an excellent alternative:

wee-slack + mosh

https://github.com/wee-slack/wee-slack

wee-slack gives you a minimal terminal based slack client within weechat and mosh handles ssh connections over low bandwidth, high latency connections.

Using this set up I’ve been able to reply to messages at times a ping to 8.8.8.8 resulted in >90% package loss.

I quickly abandoned the slack "App", but even dedicating a chromium tab to Slack ended up being absurdly heavy. So I've finally migrated to weechat+weechat slack plugin. For a moment I thought I was too late, as slack is killing the xmpp and irc bridges - but the dedicated slack plugin for weechat uses the slack api.

As an added bonus, there are no more animated emojis in my peripheral vision that can be mistaken for an update / alert.

I'm on Linux, but I presume wc works fine on Mac. A bit of a shame that the qt-based client seems abandoned - but it's open source and python so maybe it'll pick up some steam for those that want something a bit less console only, but still not Web app crappy.

https://github.com/wee-slack/wee-slack

https://github.com/weechat/weechat

https://github.com/weechat/qweechat

I imagine that both for the console client and the qt one it should be possible to map some of the more common emojis to Unicode (eg :heart:).

FWIW, you can still use your favorite IRC client (e.g. WeeChat + Glowing Bear) with Slack by using wee-slack (https://github.com/wee-slack/wee-slack)

WeeChat Slack API plugin (works without IRC-gateway)

https://github.com/wee-slack/wee-slack

Background

I'm not associated but I thought I had to share this. Since about a year back I've migrated to wee-slack for slack usage in my WeeChat IRC-client, it's also possible to use WeeChat as a bouncer through WeeChat relay (if not mistaken there's irssi-proxy:esque proxy-plugin too).

I've been a die hard irssi-fan and still use it for much of my IRC interaction and been using weechat as a irssi-like slack client. As a bonus we can use many of the features that didn't work through the irc-gateway.

You can also see a preview of my setup on my twitter

https://twitter.com/ahultner/status/923588418126348289

If you're interested of my personal setup you can find it in my dotfiles

https://github.com/Hultner/dotfiles/tree/master/cetrezMBP/.w...

WeeChat with the wee-slack plugin is pretty good (https://github.com/wee-slack/wee-slack). That doesn't help folks that don't use WeeChat though.

I have been investigating Riot/Matrix lately. One of the things that really bothers me about the Slack desktop client is its lack of multiple windows. Participating in more than one conversation at a time is a flurry of clicks/keystrokes to keep up. Unfortunately the Riot client doesn't appear to have multiple windows either and the status of the Slack gateway is somewhat unclear.

For weechat users, there's always the wee-slack plugin [0] which runs on the Slack API, rather than the IRC gateway.

[0] https://github.com/wee-slack/wee-slack

Alternatively, this plugin: https://github.com/wee-slack/wee-slack for WeeChat is surprisingly full-featured.

At work I use wee-slack ( https://github.com/wee-slack/wee-slack ) a plugin for weechat that uses the slack API (not the IRC gateway.) Images / code snippets / etc. were rendered as an HTTP link. It works pretty well, CPU and memory usage are low, unlike the web interface.

Haven't seen it posted here yet but wee-slack [0] works wonders if you're not afraid of using weechat.

I'm looking at an average CPU usage of 2% and memory usage of ~30MB for three IRC networks and three different Slack teams.

[0] https://github.com/wee-slack/wee-slack