Shrugs.app – A native Slack client for macOS
1–10 of 236 posts
Re: Shrugs.app – A native Slack client for macOS
#2I remember people on HN complaining about responsiveness. Never found it to be a problem personally.
Re: Shrugs.app – A native Slack client for macOS
#3How long until this gets banned?
Re: Shrugs.app – A native Slack client for macOS
#4It looks nice, but if you plan to try it as you default Slack client be aware it is lacking many features:
- Edit posted messages (big one, TBA) - Authentication w/ XOXC tokens - Loading older messages - Typing indicators - Starring & Pinning things - Search - Sharing messages - Screensharing and Calls (aka Screenhero) - Joining and creating channels
Re: Shrugs.app – A native Slack client for macOS
#5See also: Ripcord[1], which has both Slack and Discord support.
Re: Shrugs.app – A native Slack client for macOS
#6I remember people on HN complaining about responsiveness. Never found it to be a problem personally.
For a very long time (ive not checked recently) slack used more memory that my IDE on a multimillion line c++ project. I used to have to shut down slack to compile on a machine with 128GB ram.
Re: Shrugs.app – A native Slack client for macOS
#7How long until this gets banned?
It's been around for quite some time now, so... ;P
Re: Shrugs.app – A native Slack client for macOS
#8See also: Ripcord[1], which has both Slack and Discord support. [1]: https://cancel.fm/ripcord/
+1 for ripcord. So much better than using a bloated web browser
Re: Shrugs.app – A native Slack client for macOS
#9I remember people on HN complaining about responsiveness. Never found it to be a problem personally.
For a very long time (ive not checked recently) slack used more memory that my IDE on a multimillion line c++ project. I used to have to shut down slack to compile on a machine with 128GB ram.
I think it improved quite a lot. I’ve just checked and it’s using 58mb on my Windows 11 workstation.
Re: Shrugs.app – A native Slack client for macOS
#10I remember people on HN complaining about responsiveness. Never found it to be a problem personally.
Well, it's a problem for me, though definitely less than it was, so I'm personally very happy that this exists. "voting with our wallets" might make Slack put it on the prio board.
Right now I'm using wee_slack.py which integrates weechat with slack; though with the obvious trade-offs.