Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Shrugs.app – A native Slack client for macOS

shrugs.app

Post reply on HN
Print view View original

171–180 of 236 posts

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

#171

Post by pxc »

aeyes wrote: post #112
st3fan wrote: post #64

Earlier quoted context omitted.

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

I just navigate Slack entirely by search and redirect all conversations to public channel as as much as possible, and I find that pretty natural. CTRL+K to navigate between convos and channels, CTRL+F to find things based on content (if I don't want to think about whether something was in a DM or a channel, and just go back to the same one).

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

#172

Post by tumult »

chii wrote: post #169
tumult wrote: post #128

Earlier quoted context omitted.

Author of Ripcord. You’re wrong, and creating and using software compatible with services is fair.

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.

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

#173

Post by pxc »

ChrisMarshallNY wrote: post #84
pxc wrote: 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?

> Do you end up sending messages in the wrong chat often? Yup. It’s probably my most frequent mistake (and can be embarrassing). I make the same mistake with messages. What I have done to mitigate the issue, is give each workspace a different color theme. At least, it helps me to avoid crosstalk between organizations. I’m not a “native slacker,” so I’m probably not a particularly good candidate for a focus group.

> What I have done to mitigate the issue, is give each workspace a different color theme. At least, it helps me to avoid crosstalk between organizations.

Ok yeah the different workspaces in one window is more of a pain than just different channels and chats in one window for me, at least the way it's done in Slack. I haven't felt that way on IRC, for whatever reason.

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

#174

Post by santiagobasulto »

samanator wrote: post #170
anaisbetts wrote: post #149

.

The comment has been edited as if to be deleted. Does anyone have the original?

The commenter said they worked at Slack in the Desktop app team. He quoted the app page where it says that Shrugs.app supports multiple windows because it's a native app and said that nothing prevented Electron (or the official Slack app) to have multiple windows. It was just that they decided not to do it because of UX reasons.

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

#175

Post by wakeupcall »

dubswithus wrote: post #2

I remember people on HN complaining about responsiveness. Never found it to be a problem personally.

After trying microsoft teams, slack feels like a thing from the future.

But try using weechat+weeslack (+ url_hint, so that you can download urls and see images with a single shortcut) as one example of how I consider a chap app should feel.

I remember pidgin being in a similar ballpark, but I haven't used it in years.

It's a shame most other modern chat clients (ripcord, and most matrix clients) do not come even remotely close.

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

#176

Post by that_guy_iain »

> We do not offer refunds. Please make sure that you can login into your Slacks and that the app works for you by using the free test version.

From my experience when someone says they don't offer refunds it's generally a sign that lots of people ask for their money back. I've not once dealt with a company that had a no refunds policy that was a good company to deal with.

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

#177

Post by [deleted] »

kstrauser wrote: post #103
selcuka wrote: post #57

Earlier quoted context omitted.

Violating the API Terms of Service [1]? > [...] Further, you will not: [...] (C) access our APIs or documentation in order to replicate or compete with the Services; [1] https://slack.com/intl/en-au/terms-of-service/api

Sincere question: is an alternate app competing with Slack’s services? We pay for each user who uses Slack, whether it’s by phone, desktop, or web. The client is 100% free; the right to connect to their service is what costs money. Slack makes exactly the same whether I use their app or an alternative. I’m definitely not a lawyer, but it’s not clear to me that this would violate the ToS.

[deleted]

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

#178

Post by zild3d »

vzaliva wrote: 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

missing search is a non starter. "Searchable Log of All Conversation and Knowledge" rings true in my experience

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

#179

Post by that_guy_iain »

selcuka wrote: post #57
userbinator wrote: post #36

Earlier quoted context omitted.

Sued for what, exactly?

Violating the API Terms of Service [1]? > [...] Further, you will not: [...] (C) access our APIs or documentation in order to replicate or compete with the Services; [1] https://slack.com/intl/en-au/terms-of-service/api

I would be confused as to how an add-on service such as a premium Slack client would compete with Slack. It seems it would be complementing it and the use of the client would not compete but fundamentally cooperate with Slack as a service.

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

#180

Post by flakyfilibuster »

ARandomerDude wrote: post #110

No way I would use this for internal company stuff. Is it safe? Probably. But it's not worth the risk to me personally unless the IT/management people agree to it first. At the company I work for (and I suspect many others) Slack is a treasure trove.

my first thought - I was surprised, that I had to scroll down this far to find this post...
Post reply on HN