Live data from Hacker News

Shrugs.app – A native Slack client for macOS

shrugs.app

111–120 of 236 posts

Re: Shrugs.app – A native Slack client for macOS

#111

See also: Ripcord[1], which has both Slack and Discord support. [1]: https://cancel.fm/ripcord/

I actually downloaded Ripcord, immediately saw that they will "never" support video calls or embed videos, and then immediately uninstalled it.

Why do a lot of these alternate clients purposefully leave out vital features?

Re: Shrugs.app – A native Slack client for macOS

#112
post #64
post #46

Earlier quoted context omitted.

That's interesting. I find managing Teams' multiple windows cumbersome and confusing, but find Slack very natural and efficient. Do you end up sending messages in the wrong chat often? Or missing messages or both? What do the main frustrations of a single window setup look like?

I lose stuff all the time when I switch between conversations and channels.

try the back button to jump back to where you were before

Re: Shrugs.app – A native Slack client for macOS

#113
post #24

Earlier quoted context omitted.

What does that have to do with Slack? If your computer has trouble playing high frame rate video it'll be the same on every application.

Except that I can play a 4k 60fps 100Mbps bitrate HEVC video in vlc with 1/6th of the cpu usage slack needs to display a damned gif

I wonder if it would help if Slack converted gifs to MP4s in the background before displaying them, or if the perf problem is in the compositing.

Re: Shrugs.app – A native Slack client for macOS

#114
post #13

The first thing I looked for was a comparison with the official Slack client in terms of performance, since that's the only reason why I'd consider using this. Numbers for CPU load, memory use, time to perform certain actions, crashes. Doesn't seem to be anything available on the site regarding this, which is a shame.

An even better reason would potentially be security. Exploits in electron are pretty common, which may be a result of its ubiquity making it a big target. But also it's just a complicated platform to secure.

How is installing rando native apps any more secure?

Re: Shrugs.app – A native Slack client for macOS

#115

Ripcord survived C&D letters because it didn't charge. I feel bad for OP for putting all this work in, because it's really cool - but you're going to get sued.

I'm of the opinion that using unofficial clients for any online service should be a legal right (unless those unofficial clients cause harm to the respective service, but existing laws/regulations around that would already cover such cases). That doesn't mean the service has to specifically support the unofficial client, but they just can't intentionally block it (or forbid its use).

I am pretty certain that I can prove any client as harmful. I have been on the receiving end of apps misbehaving plenty of times, no matter which platform (JS, iOS, Android). And these were official apps with dedicated development teams.

Endless loops which flood you with API calls are a common issue, managing state is hard. Rate-limiting does not completely solve this.

Re: Shrugs.app – A native Slack client for macOS

#116

Earlier quoted context omitted.

It's funny to see how basically all the official mainstream IM clients like AIM, MSN, ICQ, etc. used to be 1-window-per-conversation, but then in some odd wave of "modernity" (for lack of a better term) that was all dispensed with, and then now, multiple windows is somehow heralded as a new feature again. To me, it's just common sense that each conversation should be in its own window, instead of stuffing them all in…

Clients like Adium (on Mac OS) and Pidgin (elsewhere, but honestly nothing is as nice as Adium), had a great solution for this. A window with tabs, but you can just drag tabs out and have more than one window. Plus you could style messages client-side. Nice and easy, better than anything popular today.

Adium was everything an IM client should be. I wish it would return to relevance, but with the dominance of closed messaging protocols that seems unlikely at best.

Re: Shrugs.app – A native Slack client for macOS

#118
post #115

Earlier quoted context omitted.

I'm of the opinion that using unofficial clients for any online service should be a legal right (unless those unofficial clients cause harm to the respective service, but existing laws/regulations around that would already cover such cases). That doesn't mean the service has to specifically support the unofficial client, but they just can't intentionally block it (or forbid its use).

I am pretty certain that I can prove any client as harmful. I have been on the receiving end of apps misbehaving plenty of times, no matter which platform (JS, iOS, Android). And these were official apps with dedicated development teams. Endless loops which flood you with API calls are a common issue, managing state is hard. Rate-limiting does not completely solve this.

Plus you can land in a situation where a user might associate bad experiences with an unofficial client with the actual service and thus leave with a bad impression overall.

Re: Shrugs.app – A native Slack client for macOS

#119

Earlier quoted context omitted.

This is just wrong lol. Cancel has never received C&D orders for Ripcord, and it does charge $20 for the Slack features. Please don't spread misinformation you're not even informed correctly on, dude. If they were going to order a C&D order to Cancel, then they would've done it around the project's start (around 6ish years ago). Actually research this stuff before posting posts like these, plz.

From this user's top post on HN: > Over the years I've found writing on HackerNews, Reddit and other online sites has given me an outlet to get creative and engage with folks in a way that will shift discourse towards something I'm more interested in. I regularly lie and pretend I know about topics and areas I have zero experience in. I began noticing I received more upvotes and engagement

How do you see top posts?
Post reply on HN