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

Consider optionally attributing replies to sources in Source Interface #5572

Open
eloquence opened this issue Oct 9, 2020 · 0 comments
Open
Labels
needs/discussion queued up for discussion at future team meeting. Use judiciously. source interface (SI)

Comments

@eloquence
Copy link
Member

eloquence commented Oct 9, 2020

Reply attribution (which journalist sent a given reply) will be visible to journalists in the SecureDrop Client when freedomofpress/securedrop-client#1142 lands. We should consider to also make it visible to sources in the Source Interface. This almost certainly would need to be optional (possibly per-reply) as journalists may sometimes need to respond to problematic submissions where attribution is not desirable.

User research evidence

No clear evidence from journalists or sources yet that this is desirable, though we know that some sources may have a preference for reaching a specific journalist (cf. #1355 and #1550), and therefore may also want to know that they're speaking with that journalist.

User story

As a source, I want to know who I'm talking to, so I'm not disclosing information to someone I don't want to disclose it to.

Previous mockups

From 2017 by @ninavizz, for discussion purposes only:

screen shot 2017-04-21 at 11 36 04 am

Refactored from #1592 filed by @psivesely

@eloquence eloquence added source interface (SI) needs/discussion queued up for discussion at future team meeting. Use judiciously. labels Oct 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs/discussion queued up for discussion at future team meeting. Use judiciously. source interface (SI)
Projects
None yet
Development

No branches or pull requests

1 participant