keybase / keybase/keybase-issues

Admin report confidentiality

Open
#3,749 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

While I approve of the move to reduce spam and fake accounts, I fear the "Report to Admin" feature is Infringing on the key beliefs that make key base such a great alternative to current solutions. privacy. this is something that I seek, and although I do not Immediate need for this; I trust my colleagues, I simply fear what this could mean for some people. When discussing crucial assets to My business, privacy is a must, and unless I can be guaranteed it, I must find a new home. A potential solution is a "confidential mode" and if both participants agree, logs in that period can not be reported.

That being said, I congratulate you on the success and am excited about what the future holds for key base.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified. First clarify the requirements for a mutually agreed confidential mode, including how agreement works and what cannot be reported; done would require an accepted design and corresponding implementation scope.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.