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.
Shrugs.app – A native Slack client for macOS
71–80 of 236 posts
Re: Shrugs.app – A native Slack client for macOS
#72I just want a slack CLI client
Re: Shrugs.app – A native Slack client for macOS
#73The 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.
Re: Shrugs.app – A native Slack client for macOS
#74The 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.
Re: Shrugs.app – A native Slack client for macOS
#75Re: Shrugs.app – A native Slack client for macOS
#76Earlier 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?
Re: Shrugs.app – A native Slack client for macOS
#77Earlier 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?
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
#78It 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.
Re: Shrugs.app – A native Slack client for macOS
#79I just want a slack CLI client
it exists! https://github.com/wee-slack/wee-slack
Re: Shrugs.app – A native Slack client for macOS
#80See also: Ripcord[1], which has both Slack and Discord support. [1]: https://cancel.fm/ripcord/