Thanks! Decrypting a message is super easy, you just use the "Decrypt" button. A Hive account is not required from the sender of an encrypted message, but the addressee must have an account,

Thanks for the feedback! Regarding your suggestion: To be frank not sure I get what you mean. In order to send a message using Hive-Mail the sender needs 1) the recipient account name, and 2) the message

Thanks! Please help spread the word.

Thanks!

Thanks for the suggestion. This is actually very interesting. Hive-Mail's quantum-resistant messages could be sent via Reticulum, if one didn't want them stored onchain on Hive. Still Hive would be useful,

Yes, that's a correct enumeration of risks. In sum, there's no privacy risk, IF the only compromised key is the Posting one. A caveat though: you said "they could send encrypted messages as you"

Hey, I'd suggest you try to use the new protocol, these doubts you're having would most likely dissipate. It's CLI-only, but it's already fully functional. That said, I understand your concern that Posting

Thanks! Make sure to test it. Yes, encrypted messages are conveyed in custom_json ops, requiring only Posting Authority signing. Yes, I'm aware PeakD offers this Sting messaging. However, I don't think

The creation of a "Hive-Mail vault" requires both the Private Posting Key and the Private Memo Key. The Active Key isn't used anywhere, for security reasons. Specifically, the Posting Key is

Messages published onchain using Hive-Mail are quantum resistant, but this does not change anything in the way how Hive currently works. Hive like most blockchains is not expected to resist Shor's Algorithm

Thanks!! Make sure to test it

Thanks! Do let me know what you think after testing it

Hey, just a heads-up, I changed the link to this toolbox and its GitHub repository, here the new addresses:

Thanks! As I mentioned, this week I'm adding and improving things in the "Non-Owner Operations Toolbox", I expect to finish these tasks next week, then if all goes according to plan I'll publish

Many thanks for the kind words! And thanks for the suggestion, I'll add a download button or maybe succinct instructions as to how to download the page, when the next version comes out

Sure, here it is: I will include the github link in my next posts. Though it's quite dry as you'll see it, it's just the unified HTML code. Gandalf, do let me know if you have suggestions for improvement

Sir, you raise important concerns, which I will try to discuss in depth in a future post. At any rate, I envisage that the "scientific front-end" we want on Hive won't auto-conceal (i.e. censor)

Welcome onboard @gwajnberg!

For the record: as per suggestions received, I just added the tag #INTRODUCEYOURSELF to this post. The post itself was not altered in any way.

Thanks!❤️