keybase / keybase/keybase-issues
Suggestion - send encrypted Twitter DM
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
It is possible to send a Direct Message via [Twitter Web Intents](https://dev.twitter.com/web/intents)
For example, to send a DM to me, you need to send the intent `D edent your message`
https://twitter.com/intent/tweet?text=D%20edent%20testing
You can use this to send "unlimited" length DMs - even though the compose window shows them as being too long.
For example -
The message still comes through -
I've written a [detailed guide about sending and receiving Keybase generated cipher-texts on my blog](https://shkspr.mobi/blog/2015/09/pgp-encrypt-twitter-dms-with-keybase/).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked Twitter Web Intents documentation and the linked guide about Keybase-generated ciphertexts. Identify the client or website entry point for social-message integrations, then establish the required scope and acceptance criteria for sending encrypted Twitter DMs before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100