Page 1 of 1

Why not to add REST secure sharing? Making it more secure than Signal

Posted: Sun Sep 06, 2026 5:08 am
by ale
The code generated by the tool is loaded directly by WP. But we could not trust the admin, the site, or the server, so why doesn't the standalone BPQ (w3myPQ standalone HTML file) send the ciphered file to a specified host where w3myPQ is installed (and that will share the file). In this scenario, the BPQ (w3myPQ) JS code would not be generated by the server.
We will verify author permissions using the profile's ML-DSA-87 public key.

Coming soon...

Re: Why not to add REST secure sharing? Making it more secure than Signal

Posted: Sat Sep 12, 2026 4:24 pm
by axew3
Move Over Signal: Next w3myPQ and BPQ Are Challenging the Privacy Crown:
https://www.axew3.com/w3/2026/09/move-o ... acy-crown/

Re: Why not to add REST secure sharing? Making it more secure than Signal

Posted: Tue Sep 15, 2026 10:13 pm
by axew3
I am quite proud 😊 to announce that the w3myPQ 3.1.4 plugin and BPQ (aka BennyPQ) standalone file 3.2.0 are coming soon to let you see something that you may never have seen.

🔮 Experience the Present and the Future of Security
The most read about post-quantum migration in whitepapers. And about secrets communications.
With w3myPQ 3.1.4 and BPQ, you can actually run it, verify it, and visualize it directly.

It will be completely decentralized: a user sharing a payload via email tied to their key can use that same email to share the exact same payload across different WordPress sites, as long as those sites have the matching ML-DSA public key loaded (and use w3myPQ!)

Stay tuned lovely and cool people. It will be decentralized and cool!