Findings and sharing
Findings are where you keep what you learn: a security observation with a title, severity, the affected endpoint and method, evidence and a fix. They need an account and live under Findings in the sidebar.
Create a finding
Section titled “Create a finding”- From chat: save as Finding on an answer.
- From Code Lab: promote a snippet to a finding. See Code Lab.
- By hand, in Findings.
Findings are private by default: only you can see them.
Share and publish
Section titled “Share and publish”- Share creates a read-only link to one finding. Anyone with the link can read it; nobody can change it.
- Publish puts a finding on the community feed, where every signed-in user can read it. You can make it private again at any time; it disappears from everyone’s feed immediately and stays in your own list.
- On the feed, published findings show their author’s public nickname — “User 7” until you choose one in Settings — never your email address.
- Reading someone’s published finding, you can reuse it: that starts a new chat in your own workspace, seeded with the finding.
Reports
Section titled “Reports”Add to Report marks the findings that belong in a report. See Findings and reports for writing findings that stand up.
Oyster is made by Red Orca, alongside Dolphin and Shark. One account for all three.
