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

161–170 of 236 posts

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

#161

Post by tumult »

gbalduzzi wrote: post #145
tumult wrote: post #125

Earlier quoted context omitted.

Author of Ripcord. You don’t know what you’re talking about and shouldn’t broadcast your assumptions as fact.

You keep commenting one-line sentences without any argument supporting your sentence. You may even be right, but am I supposed to blindly trust you, a random commenter from the internet?

I mean, you don't have to. I appreciate the skepticism. I am the actual author of Ripcord. I've had an account here for many years. You will not find someone with better firsthand knowledge about Ripcord surviving or not surviving legal challenges.

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

#162

Post by wildmanx »

anaisbetts wrote: post #149

.

> If you take more than a few minutes to think out how it works (I know, not popular for the typical HN poster)

Such a condescending remark. This kind of thing is not good PR for your company, product or workplace. Would I want to work with colleagues who publicly disparage a whole community like that? If you communicate like that publicly, how can I expect your internal work atmosphere to be?

I know you're probably an engineer at Slack and not in the PR department, but you may want to re-think your communication strategy. I know that my employer would have been unhappy with me for such a comment, and rightfully so.

Judging by other comments in this thread, folks have apparently thought out how it could work for "more than a few minutes", so not just the style but even the content of your message are clearly off. You are getting community feedback here and competent people are giving suggestions -- for free. Embrace that.

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

#163

Post by crollywood »

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

Oof, while I highly value multiple windows - not sure I am ready to give up on some of the things you listed (especially edit & calls)

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

#165

Post by planede »

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

Can they actually sue, or can they just terminate the service for this one account?

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

#167

Post by wildmanx »

aeyes wrote: post #115
amatecha wrote: post #40

Earlier quoted context omitted.

I'm of the opinion that using unofficial clients for any online service should be a legal right (unless those unofficial clients cause harm to the respective service, but existing laws/regulations around that would already cover such cases). That doesn't mean the service has to specifically support the unofficial client, but they just can't intentionally block it (or forbid its use).

I am pretty certain that I can prove any client as harmful. I have been on the receiving end of apps misbehaving plenty of times, no matter which platform (JS, iOS, Android). And these were official apps with dedicated development teams. Endless loops which flood you with API calls are a common issue, managing state is hard. Rate-limiting does not completely solve this.

Doesn't your API have a problem if it can be misused that way? In other words, shouldn't your backend by default distrust the client using its API, no matter whether it's the official one or anything else? Even the official client can have bugs that bring down your backend.

That's what the "zero trust" philosophy is about.

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

#168

Post by maccard »

dubswithus wrote: post #34
maccard wrote: post #6

Earlier quoted context omitted.

For a very long time (ive not checked recently) slack used more memory that my IDE on a multimillion line c++ project. I used to have to shut down slack to compile on a machine with 128GB ram.

How many gigs was it using?

I've changed jobs since so I don't have access to the tickets but I remember it being close to 20GB.

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

#169

Post by chii »

tumult wrote: post #128
tptacek wrote: 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.

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 in control and TOS etc.

Post reply on HN