Live data from Hacker News

Shrugs.app – A native Slack client for macOS

shrugs.app

41–50 of 236 posts

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

#42
post #24

Earlier quoted context omitted.

it's an obscenity that somebody pasting one high frame rate GIF into a slack channel can cause a quad-core, tenth generation core i7 laptop CPU to peg itself at 85% usage and begin wasting battery, heating up, spinning fans, etc. if somebody told me twenty years ago how powerful this CPU was, relative to what I was using at the time for a desktop PC, and that a chat application could pretty much max out the CPU and u…

What does that have to do with Slack? If your computer has trouble playing high frame rate video it'll be the same on every application.

It's not just high framerate stuff, it's pervasive.

Folks used to post walls of dancing bananas in phpBB and my Pentium III could handle that without breaking a sweat.

The exact same wall of dancing bananas makes any modern CPU jump to ridiculous two-digit usage relative to the task at hand.

I was also chatting over IRC from a Palm Pilot which had something on the order of 1MB of RAM, connected over RS232 to a GPRS phone, and the current experience of chat performance is basically on par with that, which boggles the mind given that I now have ten thousand times the RAM, an internet connection that can't be saturated in practice, and latency largely bound by the speed of light.

Slack's requirements are completely ludicrous in regard of what it's set to achieve.

> it'll be the same on every application.

Except, it's not. Counterexamples of chat apps with reasonable to stellar performance abound over the last two decades.

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

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

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

#44

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.

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

[deleted]

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

#45

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

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

#46
post #43
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.

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?

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

#48
post #35

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.

it sucks that you could be sued if you are using a "public" api like this to write a client. I would like to think that as long as you do not brand yourself as slack or violate any trademarks, you should be able to write an app like this. Things like email clients would fall into this category.

It's not public as in an utility. It has its own Terms of Service.

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

#49
post #17

It’s an interesting start, but it’s missing some pretty vital features the official Slack client has. I get how development works and I understand needing funding to support development, but I’ll be holding off on this until there is at least a much closer feature parity. I suppose I’m getting too old to beta test daily driver software.

It’d be cool if there was a kind of “feature escrow”. You might pay $20 today, but $5 of that is held and paid to the developer once a specific feature you want is implemented.

There’s probably too much overhead to be useful, but it’d be an interesting way of prioritizing features.

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

#50
post #43
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.

+1 It's painful to keep multiple active discussions in threads (or anywhere else for that matter).
Post reply on HN