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

Hijacked Twitter Handles #1068

Open
edsu opened this issue Nov 5, 2017 · 1 comment
Open

Hijacked Twitter Handles #1068

edsu opened this issue Nov 5, 2017 · 1 comment

Comments

@edsu
Copy link

edsu commented Nov 5, 2017

If an agency registers a Twitter account and then decides to change their handle the registry should notice and update the listed handle. If this checking isn't performed then other parties can come in and register the released handle and pose as the agency.

For an analysis of this actually happening please see this writeup concerning the accounts that Twitter suspended because of suspected Russian interference in the election.

In an ideal world the registrant would update the registry themselves. But this isn't really practical. It should be possible for the registry to automatically verify by keeping track of the Twitter user id (which is persistent) and using Twitter's API to periodically check the handles.

@edsu edsu changed the title Hijacked Twitter Accounts Hijacked Twitter Handles Nov 5, 2017
@ryanwoldatwork
Copy link
Collaborator

Hi @edsu - a feature to re-request internal verification if an account is changed, is planned for.

And, using the API's are a good idea, but invoke other concerns regarding application boundaries. So I can't commit to this yet, but noted!

@ryanwoldatwork ryanwoldatwork transferred this issue from GSA/us-digital-registry Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants