Live data from Hacker News

Shrugs.app – A native Slack client for macOS

shrugs.app

71–80 of 236 posts

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

#71
post #68

Earlier quoted context omitted.

The point is it's not fair that Terms of Service can impose that restriction. Just like it wasn't fair when you were only allowed to use phones that you rented from your phone company.

Why isn't it fair? They run the service. What gives other people the right to tell them how to run it? If you don't like their terms, there are about 100 alternative projects you can use. There are pretty clear, practical reasons you might want to control the client of a commercial network service.

What part of your argument wasn't true of the phone company too?

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

#73
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.

If I was worried about security then I think I'd probably move to using the web client (or a web wrapper) instead of switching to a third party native application.

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

#74
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.

That's a common refrain I hear that Electron apps aren't secure. It was more true in the past and less-so now. I've been maintaining a secure Electron template for 2 years that's got traction in the community, if you are interested - https://github.com/reZach/secure-electron-template.

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

#76
post #68

Earlier quoted context omitted.

Why isn't it fair? They run the service. What gives other people the right to tell them how to run it? If you don't like their terms, there are about 100 alternative projects you can use. There are pretty clear, practical reasons you might want to control the client of a commercial network service.

What part of your argument wasn't true of the phone company too?

The phone company is the sole-source provider and you couldn't opt for another platform. The more relevant analogy is soda fountains in a restaurant - the provider chose Coke, but I want Pepsi. (My OSS founder wanted Slack, I want discord.)

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

#77
post #68

Earlier quoted context omitted.

Why isn't it fair? They run the service. What gives other people the right to tell them how to run it? If you don't like their terms, there are about 100 alternative projects you can use. There are pretty clear, practical reasons you might want to control the client of a commercial network service.

What part of your argument wasn't true of the phone company too?

Phone companies are different in that they were monopolies with special legal status. Slack, on the other hand, is just one of many private companies offering roughly equivalent services.

You can still argue your case, of course, but phone companies are a bad analogy here.

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

#78
post #43
post #4

It 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

Yeah, but multiple windows! OMG! I find managing multiple conversations with Slack so incredibly challenging. Having multiple windows open for active conversations is sooo good.

I'd love to have multiple windows. At some point in the last few months Slack broke the command-up/command-down shortcuts that would take you to the next conversation with an unread message -- if you restart it'll work for a short while and then break again. Having multiple windows would resolve this and other annoyances.
Post reply on HN