-
Notifications
You must be signed in to change notification settings - Fork 81
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
docs: Fix blockchain question in FAQ #295
Conversation
Signed-off-by: Facundo Tuesca <[email protected]>
✅ Deploy Preview for docssigstore ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
content/en/about/faq.md
Outdated
@@ -146,7 +146,7 @@ We would love that. The more people monitoring the logs and providing useful ser | |||
|
|||
There's no need for a distributed source of transparency as there can be multiple points of transparency which only adds more sources of security guarantee, not fewer. An entity can post to as many Rekor logs as they want and inform users of where they post. We do encourage folks to use common public instances, but we don't seek to enforce this. We do plan to look to produce a gossip protocol, for those that desire a more decentralised model (if there's demand). | |||
|
|||
### How do I verify downloaded code? | |||
### Why not use a blockchain? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, what do you think about deleting this section entirely? It's a good discussion topic, but it's quite technical for an FAQ and I think the answer here is a bit too concise and maybe even a bit inaccurate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me, we can always re-add it later if necessary
Signed-off-by: Facundo Tuesca <[email protected]>
cc @bobcallaway @ltagliaferri for merge |
Summary
Fixes #294. The current FAQ located here seems to have a question that does not match the answer:
This changes the question to what it was originally (see the linked issue for more details)This now deletes the question, as per the discussion in the review comments