Live data from Hacker News

Ask HN: Is there any interest in a native Qt/C++ Discord client?

news.ycombinator.com

31–40 of 43 posts

Re: Ask HN: Is there any interest in a native Qt/C++ Discord client?

#31
Discord bans 3rd party clients, but that doesn't mean there's no audience.

The reason why Discord is so strict is because the platform was super insecure back in 2015 and third party clients could ban people/destroy servers/etc.

That isn't true anymore yet the ban is still in place.

Re: Ask HN: Is there any interest in a native Qt/C++ Discord client?

#33

You are literally just lying? There is approximately nothing in this repo: https://github.com/txtsd/kind Too many posts on HN now are just nasty liars like this OP looking to bullshit others.

I haven't pushed the code yet. I was waiting until the quality is sufficient per my standards. It should be pushed within 2 hours from now.

EDIT: Code is live.

Re: Ask HN: Is there any interest in a native Qt/C++ Discord client?

#34

There are already a bunch of these. gtkcord (disset) comes to mind for an open-source native client: https://github.com/diamondburned/dissent They seem to be most popular with the open source crowd. I think you could gain traction with the "normal" users by also including many of the gaming features that other native clients lack (game streaming, voice/video chat, soundboards, the lot). Also maybe consider actually s…

Thank you for your input.

Everything you listed will be worked on after initial release. It's in the works.

Nitro features will be for Nitro users only, except things that non Nitro users can see anyway.

Re: Ask HN: Is there any interest in a native Qt/C++ Discord client?

#37

That all sounds good and all but I feel like this would be a major engineering effort for a centralised system that seems particularly vulnerable to regulation right now. A good example of that is Discord "servers" with NSWF channels now require you to submit your ID to Discord for verification to join the channel. As almost all servers have main channels marked NSFW (they need to because servers can be closed if NSF…

I share your concerns. kind is not the ideal solution. All my communities are on discord though, so it is the practical solution until a replacement for discord completely does away with the need to use it in the first place.

Re: Ask HN: Is there any interest in a native Qt/C++ Discord client?

#38
post #29
post #5

Earlier quoted context omitted.

While I can't argue against the risk, all these third party clients continue to be allowed to exist. Ripcord and discordo were my favorites amongst the alternatives. kind is the missing Qt FOSS alternative.

Aside from the risk, I don't understand why you would put your time into it. They can change their stance any minute and your work is just down the drain. I guess you could do it for learning and experience? idk... > kind is the missing Qt FOSS alternative. Nah. What's missing is an alternative to discord itself, with enough pull behind it.

I can't argue with that. kind is the practical solution, not the ideal one.

Re: Ask HN: Is there any interest in a native Qt/C++ Discord client?

#39
post #38
post #29

Earlier quoted context omitted.

Aside from the risk, I don't understand why you would put your time into it. They can change their stance any minute and your work is just down the drain. I guess you could do it for learning and experience? idk... > kind is the missing Qt FOSS alternative. Nah. What's missing is an alternative to discord itself, with enough pull behind it.

I can't argue with that. kind is the practical solution, not the ideal one.

Instead of making it work with Discord, built it around xmpp with as many of the same niceties that discord offers and get yourself a working alternative on an open, powerful protocol, fully FOSS.

People want to get away from closed, centralised applications. The sentiment is the strongest it's ever been. But they don't have compelling and working enough alternatives to do so.

Post reply on HN