holmesworcester

Hi @eragon4rya and @JavaDerg -- Thanks for your time and attention. Even if it's just a quick look, we appreciate it. To answer your questions, an audit is planned, yes!...

Here is some exciting new work I just became aware of this morning that addresses the challenges of PCS (and sometimes FS) in the p2p case, including when history is...

Thanks! We'll fix this in our fork and create an issue in the upstream repo. Update: actually this isn't part of a library we're including, this is our own homegrown...

I've created a separate issue for the non-constant-time verification token, which was fixed in 6.0.1: https://github.com/TryQuiet/quiet/issues/2945 We also published a CVE for it: https://github.com/TryQuiet/quiet/security/advisories/GHSA-gpw8-w78h-xj67 And mentioned it here: https://x.com/Try_Quiet/status/1948386138562904203 Thank...

"Same name" isn't clear enough, I don't think. I was wrong about updating this everywhere and thanks for checking! I think we can keep using the "duplicate" label *and* use...

@jgaylor can you post a link here to whatever warning we're showing the user whose name is a duplicate?

Yeah. Though in this case we would want to prompt the users (especially the new user) to change their name.

Left one last note about where to display the warning, but all of this looks good to me.

@ivan2214 @DubemObi either of you is welcome to work on it! @ivan2214 since you asked first, would you like to pick it up? @DubemObi would you like to pick another...

Thank you! I just approved tests to run. It might be necessary to fix e2e or snapshot tests, but possibly not!