localslackirc VS wee-slack

> Really? Just a git command, a button press on GitHub? So why don't they just do it? Why don't they apply the patches when people send the code in then?

Because the patch was bad.

> Something like a month later the guy just rewrote the patch without even engaging with me.

Do you think he'd have done that if the patch was good? Was his version completely identical to yours?

> Yeah, that made me feel like shit

At least it didn't introduce a new bug to every user… I'm sure collective feelings of the userbase were less harmed in this case.

> Sorry but maintainers don't have the moral superiority to demand free labor

But you have the moral superiority to demand free labour from maintainers, to review, improve, test your patch?

Look at this pull request for example: https://github.com/ltworf/localslackirc/pull/387

How could a thing like that be merged?

When asked to split it, he just proceeded to open tens of pull requests that were all based on the previous one, in a chain. And every commit contains thousands of lines of unrelated changes with what the description is.

Then he got upset.

plugging my IRC gateway https://github.com/ltworf/localslackirc

I find that using slack from IRC, and having the option to deprive some people/channels to notify me is very helpful to reduce the amount of distractions.

I could never understand why people insist on using requests rather than the stdlib (which works just fine).

When async became a thing, I remember hitting some bug in aiohttp so I wrote myself a tiny (just doing the bit I needed) HTTP async client, which I figured was easier than wrestling aiohttp into compliance.

These days aiohttp is quite nice for async, and for sync I just use the stdlib.

My async client, if it can be of interest https://github.com/ltworf/localslackirc/blob/master/slackcli...

I normally use [localslackirc](https://github.com/ltworf/localslackirc) to use slack.

I can grep through the logs if I need to find something. That's really really fast compared to their search on the website.

I also get other advantages such as not automatically being forced to see all the reaction GIFs and being able to silence notifications from certain users that abuse them.

https://github.com/ltworf/localslackirc/ if you are interested.

I replaced the Slack client with wee-slack [https://github.com/wee-slack/wee-slack]. It brings a much more "zen" experience to using Slack and better compliments my keyboard-centric desktop/workflow (e.g. clear all unread channel notifications? keybind! Jump between all the high priority/@mentioned notifications? keybind!) It also helps if you're expected to be available via Slack, since it can keep you showing "green" while you've actually been ignoring it.

Fwiw, last time I looked, wee-slack was a decent improvement for slack text chat. These days maybe a matrix bridge?

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.

It has been unable to log in for the last year: https://github.com/wee-slack/wee-slack/issues/844

When the IRC gateway stopped working, I found https://github.com/wee-slack/wee-slack worked pretty well. But I switched employers months ago and no longer have to use Slack, which is even better! (So, I don't know how well it works today.)

The weechat plugin unfortunately cannot coexist with wee-slack (https://github.com/wee-slack/wee-slack/issues/812, https://github.com/poljar/weechat-matrix/issues/248), so if one wants to participate in the Haskell Foundation Slack, or any other Slack (e.g. for work), then Matrix is off limits. Yeah, it's just a bug that will eventually get fixed, but it does make things unnecessarily complicated. :-/

Not really Vim but there is a plugin for WeeChat: https://github.com/wee-slack/wee-slack

NB. On integrating slack & other webby things. Terminal applications might be a big help here (the Windows terminal now has excellent compatibility if you’re using Windows). For instance, there’s a slack plugin for weechat (a terminal IRC / chat client) which by all accounts works pretty well. Or there’s this client that runs directly in a terminal.

Wee-Slack is a WeeChat plugin that is based on python WebSockets and delivers most of the basic functionality of the Slack client. To use this, you need to receive a Slack API token. One way is - after installing - to run on WeeChat: /slack register This command prints a link you should open in your browser to authorize WeeChat with Slack. Once you’ve accomplished this, you should run: