What does HackerNews think of wee-slack?
A WeeChat script for Slack.com. Supports threads and reactions, synchronizes read markers, provides typing notification, etc..
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.
I figured the likelihood of an admin enabling it at my request was zero so I didn’t bother asking.
- 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.
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.
Link to wee-slack: https://github.com/wee-slack/wee-slack
I find the wee-slack plugin for the WeeChat IRC client to be pretty good (https://github.com/wee-slack/wee-slack)
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 support 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'.
Looks like it just wraps the website in this case.
Yes there are clients that use the API. Slack offers a http rest-like api as well as a websockets realtime api. For example, wee-slack[1] (weechat plugin for slack) and slack-term[2] (curses client in golang).
I don't use slack outside of work, but I always have the idea of using weechat more - for irc and/or other protocols.
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.
https://github.com/wee-slack/wee-slack
It works great!
I'm so used to using wee-slack that I try to use commands like "s/" when I use the web browser interface (which doesn't work).
I also used to use bitlbee, but once AIM died I dropped it.
Slack dropped their irc gateway a while ago. I recommend wee-slack[1] which is a weechat[2] python plugin that uses the Slack API instead of the old IRC gateway, which also means it is a lot more feature rich than the IRC gateway was.
1 - https://github.com/wee-slack/wee-slack 2 - https://weechat.org/
* 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.
OTOH, like someone else said, please contribute to improving riot/matrix instead.
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.
https://github.com/erkin/ponysay
My latest find is to use a combination of weechat and wee-slack for most of my slack usage (it's note quite there when it comes to editing, or in-line reactions). But works well for the chat part:
https://github.com/wee-slack/wee-slack
As a former BitchX and sometime irssi user, weechat feel cozy. And it doesn't eat all your ram just for chat.
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:).
So screen-reader usability is still a thing. The fact it's not using a proper standard open protocol is a problem.
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...
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.
I'm looking at an average CPU usage of 2% and memory usage of ~30MB for three IRC networks and three different Slack teams.
https://github.com/wee-slack/wee-slack
I use it extensively for everyday Slack, where I don't care much about inline media and inline formatting. And for a text client, weechat + this plugin handle it pretty gracefully.