# Pin Tweet to IPFS requirements

- You can create repo on your own github, we can transfer ownership later
- Extension should follow [Manifest v3 spec](https://developer.chrome.com/docs/extensions/mv3/intro/)
- We will get some design resources together after a PoC is created

#### User Story:
- As an end-user, I would like to be able to save a tweet and play it back forever.

#### A bit more about intended demographic:
This extension is meant to allow end users who may or may not know or care about IPFS to pin a tweet and be able to recall it at a later date.
The intent is to introduce the concepts of webrecorder.net and IPFS without overloading the user with knowledge and complexity of running their own local node.
This is why for the first version we are only focusing on using a gateway (web3.storage) and existing tools provided by webrecorder.

#### If you run into a blocker:
- document it and ping Dave Justice ([e-mail]), I will try to get you unblocked

#### If you have input or suggestions:
- I (Dave, [e-mail]) would love to hear them!

#### Imagined user flow:
1. click pin-tweet-to-ipfs
2. url is copied, new tab is opened to express.archiveweb.page/#{copiedURL}
3. Once warc(https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/) is generated, the extension uploads it to web3.storage
4. user is presented with dialog/popdown with sharable links to the replayable warc.

#### Unanswered ux questions:
- we will need a way for user to input their web3.storage api key, for now, lets just use a hardcoded one until we get the basic flow working.
- Once the user has inputed their api key, they should be able to access a page on web3.storage of all of their saved tweets.