Hacker News Reader

Comment by mostlysimilar | Hacker News Reader

I love the interface, but how does it connect with Discord and how long until they try to shut it down?

I'm not very familiar with Discord, but I thought the same about Slack. Slack has been aggressive in the past sending C&D letters to those who threaten their walled garden. I'm not saying it'll definitely happen in this case and I wish all the best to the developers and users of Ripcord. I sympathize with their want for non-electron desktop clients. But I wouldn't be surprised at all if they received a terse and disapproving letter from Slack's legal team.

> Slack has been aggressive in the past sending C&D letters

Could you elaborate? Slack provides client tokens and they don't seem to forbid that in the way Discord does (in fact they explicitly provide client tokens via OAuth).

To be fair, the ones I specifically remember were various browser extensions and plug-ins that would modify the browser version of Slack's official client.

However, I could have sworn there were a few full-fledged clients that Slack didn't like. I feel like one of them was a terminal-based client.

It's pretty rough really, within Discord's native or webapp you have to pop open the devtools/network-tab and grab an auth token from a request header, heh

Works really well though. I've been lazy about addressing a mic-not-working issue on the linux client, and had been resorting to using the webapp when I wanna voice

This ends up working fine for me though re: voice

Low footprint is nice too

Reply on news.ycombinator.com