@codesections @eel @rnickson

This new QStyle will be used in the next release of Ripcord (it's not in the current release yet)

@cancel @eel @rnickson

> I just made a significant new portion/feature of it open source a few hours ago :)

Two responses: first *thanks very much*!

It's awesome that you're freeing this library under the GPL. I'll definitely pay for #ripcord without hesitation when you're ready to ask for money!

2nd: my concern with ripcord not being #foss has more to do with not loving the idea of communicating using code that I/we can't audit. This library—while super nice!—doesn't address that issue.

@codesections @eel @rnickson

Yeah, I'm not sure what to do about that. I have to make money from Ripcord at some point to keep developing it full-time, and I have no idea how to do that by asking for donations only.

If you have some established track record with security auditing then email me cancel@cancel.fm (my PGP key is on keybase) and I will grant access to the source code. I'm not worried about the code leaking, just non-paid forks existing that people use without paying me.

@cancel @eel @rnickson

> I have to make money from Ripcord at some point to keep developing it full-time, and I have no idea how to do that by asking for donations only.

That is an entirely reasonable position. I'd *like* to believe that you could still make money developing it full time through donations/voluntary payments (see, e.g., Mastodon) but I can't fault you for not wanting to take that chance.

@codesections @eel @rnickson

The main difference is that Ripcord isn't a service or something that large communities would likely band together to raise funds for (though that's just a guess.)

If there was a guaranteed way for me to be funded by a larger entity then I would be willing to do it. But I feel like one of the reasons there isn't any good chat software now is that there's no demand for it from the players with all the money (large cloud operations w/ service-driven revenue.)

@codesections @eel @rnickson

Instead the client is more like an afterthought, and all of the focus is on the cloud part of the chat service.

@cancel @eel @rnickson

Yeah, couldn't agree more with all of that!

@cancel

> If you have some established track record with security auditing then email me cancel@cancel.fm (my PGP key is on keybase) and I will grant access to the source code.

I don't have a security background, but I hope someone else can help. I'll boost this toot to see if we can find one of the great #infosec and #security folks in the fediverse.

The fact you've build a native discord/slack replacement is incredibly awesome, and I really hope someone can help with an audit of ripcord!