You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
We need to detect whether the publicName is encrypted and set the encrypt state of the service accordingly.
We should also allow the creation of both public and private publicNames, to allow people to create private blogs. I'm not sure how valuable a private blog would be, but it's built in to the network protocol, so we should support it regardless.
The text was updated successfully, but these errors were encountered:
The web hosting manager encrypts all of its publicNames by default (https://github.com/maidsafe/safe_examples/blob/2f06aa65025a417a70cf6e93185dbe5ffcb44b9e/web_hosting_manager/app/safenet_comm/api.js#L84) and we create unencrypted services by default. Trying to create a public service within an encrypted service name throws a network error.
We need to detect whether the publicName is encrypted and set the encrypt state of the service accordingly.
We should also allow the creation of both public and private publicNames, to allow people to create private blogs. I'm not sure how valuable a private blog would be, but it's built in to the network protocol, so we should support it regardless.
The text was updated successfully, but these errors were encountered: