Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Answer why CyberD is better for Web3 then Google #328

Closed
npopeka opened this issue Jun 14, 2019 · 2 comments
Closed

Answer why CyberD is better for Web3 then Google #328

npopeka opened this issue Jun 14, 2019 · 2 comments
Assignees

Comments

@npopeka
Copy link
Contributor

npopeka commented Jun 14, 2019

In general you can find out IPFS hash only if you uploaded content or have access to IPFS node and able to use 'ipfs refs local' command. So only content creator can index IPFS hash as a CiD.
Google wont be able to search in IPFS ever, because he wont be able to get CiD's from IPFS.

@npopeka npopeka changed the title Answer why CyberD is better for Web3 Answer why CyberD is better for Web3 then Google Jun 14, 2019
@mastercyb
Copy link
Member

Loading search result directly from IPFS :-) Yeees!

@mastercyb
Copy link
Member

I have added the following arguments in the whitepaper:

During implementation of proposed architecture we realize at least 3 key benefits a Google probab;y would not be able to deliver with conventiaon approach:

  • search result can be easily delivered from p2p network right into search results: eg. .cyber can play video.
  • payment buttons can be embedded right into search snippets, so web3 agent can interact with search results, eg. agents can buy an items right in .cyber. Also so e-commerce can flourish because of transparent conversion attribution.
  • search snippets must not be static but can be interactive, eg. .cyber eventually can answer location based answers.
    I am sure this answer the question completely

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants