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.
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 in…
Shrugs.app – A native Slack client for macOS
101–110 of 236 posts
Re: Shrugs.app – A native Slack client for macOS
#102It 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
#103Earlier 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’m definitely not a lawyer, but it’s not clear to me that this would violate the ToS.
Re: Shrugs.app – A native Slack client for macOS
#104Earlier quoted context omitted.
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.
Except that I can play a 4k 60fps 100Mbps bitrate HEVC video in vlc with 1/6th of the cpu usage slack needs to display a damned gif
Re: Shrugs.app – A native Slack client for macOS
#105Earlier quoted context omitted.
This is just wrong lol. Cancel has never received C&D orders for Ripcord, and it does charge $20 for the Slack features. Please don't spread misinformation you're not even informed correctly on, dude. If they were going to order a C&D order to Cancel, then they would've done it around the project's start (around 6ish years ago). Actually research this stuff before posting posts like these, plz.
From this user's top post on HN: > Over the years I've found writing on HackerNews, Reddit and other online sites has given me an outlet to get creative and engage with folks in a way that will shift discourse towards something I'm more interested in. I regularly lie and pretend I know about topics and areas I have zero experience in. I began noticing I received more upvotes and engagement
someone admitting to that behavior on HN should be banned. that's actively hostile to the discourse here.
Re: Shrugs.app – A native Slack client for macOS
#106Earlier 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.
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 in…
Re: Shrugs.app – A native Slack client for macOS
#107Earlier quoted context omitted.
I feel like it being based on Electron is the least bad thing about it. Native or not, you have to reach the API for everything and that's slow.
Agree to disagree. Selecting a channel in Slack takes like 300ms for me almost every time. There seems to be an inherent UI lag with Slack and Discord. Ripcord, on the other hand, is instantaneous.
To me it sounds like an artifact of architectural choices, eg by polling before rendering to avoid flicker, lack of client side caching, or possibly just bloat. Companies won't stop their poor software practices even if they switched to native.
Re: Shrugs.app – A native Slack client for macOS
#108Earlier quoted context omitted.
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.
I'd like to hear a lawyer (HN has several) corroborate this "Slack must articulate harm" claim, because there is a whole branch of civil law that exists to enforce contracts in the absence of torts; as I understand it, it's called "contract law".
But agree, would love to see some lawyers weigh in.
Re: Shrugs.app – A native Slack client for macOS
#109The 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.
Want to double-down on this. I read "native" and immediately assumed the main selling point was perf - which enticed me to open the link.