keybase / keybase/client

No Block Option from Message's "Gear" Menu

Open
#21,407 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Keybase GUI Version: 5.0.0-20191114182642+f73f97dac6

I recently received my first ever spam/malicious message within the Keybase ecosystem from an unknown person running under the identity of a "debbyswisher". In receiving this message, the message preview offered in the GUI made it clear that this message and individual should not be trusted and best practice would be to not open the message in any form and to block the person in question to prevent/stem future harassment.

However, mousing over the message in the GUI and selecting the revealed "gear" menu only provides options for suppressing the notifications and hiding (but not deleting) the message entirely. This menu should ideally provide user safety actions to delete unwanted messages (not simply hiding them) and optionally blocking the sender as well. As the current implementation stands, users would have to hide the conversation and then separately look them up under "People" and block them from that screen.

While Blocking a user prevents them from adding you to teams and creating new conversations, it does not prevent them from following you and continuing to view your information, a potential privacy concern if users are blocked for concerns of stalking or harassment -- which is a bit ironic given Keybase's security and privacy mindedness.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the message preview's gear menu in the Keybase GUI and trace the existing hide and notification-suppression actions. Define how delete and block should behave from that menu, including the stated privacy concern, then verify that both actions are available and that the existing conversation and People workflows remain consistent.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.