51–60 of 236 posts
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 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.
See also: Ripcord[1], which has both Slack and Discord support. [1]: https://cancel.fm/ripcord/
Ripcord is great and I use it for Discord and Slack, but it is far from feature complete. Important to note that Ripcord is developed by one person. Some major things that are lacking: * No search (Slack/Discord) * No huddles in Slack * Thread support in Discord For these reasons, I typically navigate to Discord/Slack in the browser when I need access to those features. Not ideal, but the snappiness of Ripcord over t…
See also: Ripcord[1], which has both Slack and Discord support. [1]: https://cancel.fm/ripcord/
Ripcord is great and I use it for Discord and Slack, but it is far from feature complete. Important to note that Ripcord is developed by one person. Some major things that are lacking: * No search (Slack/Discord) * No huddles in Slack * Thread support in Discord For these reasons, I typically navigate to Discord/Slack in the browser when I need access to those features. Not ideal, but the snappiness of Ripcord over t…
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?
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.
Sued for what, exactly?
> [...] Further, you will not: [...] (C) access our APIs or documentation in order to replicate or compete with the Services;
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.
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
They can certainly attempt to block 3rd party clients, though. Or threaten to / actually sue, even if they’re unlikely to be successful.
Earlier quoted context omitted.
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.