dhive issueshttps://gitlab.syncad.com/hive/dhive/-/issues2020-07-13T09:30:20Zhttps://gitlab.syncad.com/hive/dhive/-/issues/10Setup CI to auto build bundle and documentation files after each merge2020-07-13T09:30:20Zgood-karmaSetup CI to auto build bundle and documentation files after each mergeGoal is to automate builds and documentations on merge requests and don't include compiled/minified dhive files in repo. Let CI do publishing to npmjs...
Documentation is hosted on github pages (https://openhive-network.github.io/dhive/...Goal is to automate builds and documentations on merge requests and don't include compiled/minified dhive files in repo. Let CI do publishing to npmjs...
Documentation is hosted on github pages (https://openhive-network.github.io/dhive/), as we mirror this repo there, it was easy to setup. We need gitlab pages enabled by admin here before we can utilize gitlab pages.
Please share or discuss good way/approach before implementinghttps://gitlab.syncad.com/hive/dhive/-/issues/3Add memo encoding helper2020-06-21T07:08:02Zgood-karmaAdd memo encoding helperfunction/helper to encrypt memo, consider using public-key encryption as oppose to aes.
There are some pros and cons, @netuoso suggested public key encryption.
pros: it doesn't require private key of sender and only public key of receiv...function/helper to encrypt memo, consider using public-key encryption as oppose to aes.
There are some pros and cons, @netuoso suggested public key encryption.
pros: it doesn't require private key of sender and only public key of receiver should be sufficient
cons: only receiver will be able to decrypt the message with their private key, sender won't be able to decrypt in future I believe.
AES implementation hivejs uses allows sender to decrypt as well, but it requires private key of sender to encrypt.