wee-slack VS tg

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:

Telegram CLI

Hmm I had some experience with Telegram bots. So if the case is that you just need the notification about new message to the stdout of the command line, I would suggest Telethon library. It acts as usual client, therefore it's not a bot and you don't have to register it at BotFather. Yet you'll have to create an application for https://my.telegram.org/apps and get credentials from there. Also check out unofficial CLI tool: https://github.com/vysheng/tg/

Check this out then https://github.com/vysheng/tg

Fair enough, that seems to be the best course of action. From the Telegram website they list this unofficial CLI app, guaranteed this one won't take any GPU resources.

Ok this sure beats the living daylight out of my script with sed and other useless stuff. It did print out the output I needed in the subshell. I got a FAIL: 38: can not parse arg #1 from Telegram-Cli but this seems to be a known bug, besides the scope of my bash script. Thank you.

I tried a couple of those projects (to even somehow script them to make it automatic/daily) but no use. There is https://github.com/vysheng/tg which I was able to use to connect to telegram but trying to use https://github.com/tvdstaaij/telegram-history-dump/ failed with exception (mostly because of Ruby).

In this case, we are lucky. We have a well-supported CLI application, telegram-cli. To try this, after installing, run: