Live data from Hacker News

Shrugs.app – A native Slack client for macOS

shrugs.app

201–210 of 236 posts

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

#201
post #46
post #43

Earlier quoted context omitted.

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.

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?

On a Mac, Teams doesn't obey many of the user interface guidelines, so multi-window use is unintuitive and difficult.

Of course nothing in Mac Teams is nearly as bad as their incoming call notification - calls pop up under all your existing calendar/email/... notifications, which you have to furiously click away in order to answer the call.

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

#202

Very important line from the FAQ: Q: Is this still developed? Yes, it is used and developed. Just not very actively. Most importantly Shrugs does not yet support “XOXC” tokens, which are often required by company Slack installations. We are interested in adding this feature, but there is no timeline yet.

IMHO, XOXC tokens are a critical feature. If I still need the regular Slack client for work chat, now I have two Slack clients. :-(

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

#203

Earlier quoted context omitted.

I run a very small audio plugin company as a side-hustle/just for the love of it. Refunds through my payment platform cost me money. I offer a very generous trial (3 weeks unrestricted, nag screens after that). I think because of that no-one actually asks for refunds (or perhaps my plugins are good enough that everyone who buys is satisfied). I do offer refunds for accidental double purchases though (usually I'm the…

I understand that refunds cost money. I have a SaaS boilerplate ( https://getparthenon.com ) with a 30-day free trial and then still offer a 6-month refund policy (6-months if you pay for the year, the full currente month if you're paying monthly). Why? Because I believe in my product. I also don't want people to go around regretting buying it, if they try to make something it doesn't go well for them then they can h…

> Also, not many people actually ask for refunds. So mostly, it's just a good policy to have that costs me very little.

Actually this is a very good point and I think I very well may reconsider my position, because since no-one actually ever asks for a refund perhaps it would "look" better if I didn't explicitly insist that there are "no refunds".

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

#204

Earlier quoted context omitted.

Not a single crash on Mac in 5 months I’ve been using it. Perhaps it’s the Linux version? Or your system?

You’ve never seen Slack reload while using it? Often, that’s a “crash” in an Electron app.

I have not seen that. It's crash-free for me, running 24x7.

But all that tells you is that it's crash-free on at least a small % of machines, so not a great way to analyze robustness. Maybe create an HN poll?

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

#205

Very important line from the FAQ: Q: Is this still developed? Yes, it is used and developed. Just not very actively. Most importantly Shrugs does not yet support “XOXC” tokens, which are often required by company Slack installations. We are interested in adding this feature, but there is no timeline yet.

IMHO, XOXC tokens are a critical feature. If I still need the regular Slack client for work chat, now I have two Slack clients. :-(

localslackirc supports them, but it's a gateway to an IRC client, not a full client by itself.

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

#207
post #172
post #169

Earlier quoted context omitted.

i do agree it's fair, but it's also true that the service provider could argue that they are supposed to be in total control of the service, including the front-end. It's by societal consensus that this can be made fair, and to convince people that it is fair, there needs to be a logical, indisputable argument that it's fair. Otherwise, the service providers can always just hide behind the counter-argument of being i…

In the case of Discord, for example, the terms of service doesn't even mention third-party clients. Also, these services are accessible from web browsers, which are made by third parties. There are more reasons, like users being able to run whatever they want on their own computers, but just the ones above are enough.

"You may not copy, modify, create derivative works based upon, distribute, sell, lease, or sublicense any of our software or services"

This seems to make it pretty clear they don't want you to create 3rd-party clients for their service.

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

#208
post #172

Earlier quoted context omitted.

In the case of Discord, for example, the terms of service doesn't even mention third-party clients. Also, these services are accessible from web browsers, which are made by third parties. There are more reasons, like users being able to run whatever they want on their own computers, but just the ones above are enough.

"You may not copy, modify, create derivative works based upon, distribute, sell, lease, or sublicense any of our software or services" This seems to make it pretty clear they don't want you to create 3rd-party clients for their service.

Ripcord isn't a derivative work, both practically and in the legal sense. It's implemented from scratch. Ripcord isn't a resell of their service or a sublicense of their service.

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

#209
post #141
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.

> crashes I've literally never had or heard of Slack crashing, across Windows, Ubuntu and macOS, regardless of memory available (8-32GB) and use. Do people really have Slack regularly crash on them or is that just something that gets attached to Electron (for some reason).

I’ve never seen one on Mac OS Slack

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

#210

Earlier quoted context omitted.

You’ve never seen Slack reload while using it? Often, that’s a “crash” in an Electron app.

I have not seen that. It's crash-free for me, running 24x7. But all that tells you is that it's crash-free on at least a small % of machines, so not a great way to analyze robustness. Maybe create an HN poll?

> I have not seen that.

No offense, but you must have blinders on then. On a fresh install on a new machine it’ll do it in the first day.

> It's crash-free for me, running 24x7.

There was a person who legit got struck by lightning multiple times in their life and lived, so anything is possible. Your claim is comparatively improbable though, but still has the possibility of being true.

Post reply on HN