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

81–90 of 236 posts

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

#81

Post by wpietri »

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

I would also expect the authors are going to have a hard time keeping up with Slack. One of Slack's goals in picking their architecture was to allow for experimentation, iteration, and expansion. Reverse-engineering an API inevitably means being behind. And given the number of engineers Slack has, it could well mean being further and further behind over time.

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

#82

Post by heretogetout »

kevingadd wrote: post #51
Mandatum wrote: post #23

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.

IMO lawsuits are less of a concern than your end users getting banned, especially since slack is typically used for work. If your existing customers are loudly angry about you in public it's gonna make it hard to get new ones

If I got banned, I don't know what I'd do first -- open a bottle of champagne or dance a little jig?

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

#83

Post by blairbeckwith »

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.

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

#84

Post by ChrisMarshallNY »

pxc wrote: post #46
st3fan wrote: 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?

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

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

#85

Post by userbinator »

madrox wrote: post #63
Mandatum wrote: post #23

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.

To be fair, I'd love to see a case like this brought to court. I'm not sure there's great precedent here. I think a case could be made that Slack was not harmed through this work.

The closest precedent might be something like https://en.wikipedia.org/wiki/Lexmark_International,_Inc._v..... or whatever laws make the aftermarket parts industry legal.

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

#86

Post by tadfisher »

tptacek wrote: post #68
josephcsible wrote: post #60

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.

There are reasons, but it's also not smart. Organizations that pay for Slack pay for the service, not the shitty client.

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

#88

Post by harikb »

Shadonototra wrote: post #45
Mandatum wrote: post #23

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.

hopefully people at Slack are smart and they hire the dude but since they spit buggy electron shit for decade already, i think you are right, they'll do everything possible to shut this down and keep with their inefficient and bloated electron way

Slack is no longer a small private company. They are owned by Salesforce

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

#90

Post by userbinator »

st3fan wrote: post #43
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

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.

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 into one window that only shows one at a time.

There's another comment here about how Teams' multiple windows is confusing, but I think that's more to do with it being Teams than anything else; as I mentioned above, all IM clients were originally multiple-window and people certainly didn't have trouble using them.

Post reply on HN