# Webrecorder / IPFS-Enabled extensions Sync

## 8/30

### Agenda

* What needs to be done to get warc files generated in mv3?
* How are uploads to web3.storage working?
* What does sharing look like? warc viewer. Do we want to build a front end for this?
* What is the status of warc viewer being supported on gateways?

### Action Items

* Dave
* Ilya
* Mauve
* Contra
* Look into credentials proxy server

### Notes on webrecorder

- if we can fetch from anywhere, we may be able to grab authenticated content
- public content can be "witnessed"
- private is harder to verify that it has not been modified, will need to show a disclaimer that its unverified

### Notes on web3.storage

- 100mb upload limits, we use SDK streaming api for durin.
- We need a prototype to see if we can fetch in serviceworker with credentials in manifest v3, https://github.com/RangerMauve/auto-js-ipfs/tree/initial
- users will need to bring their own web3.storage credentials or we could have our own server manage tokens and proxy to web3.storage
- create a new user on extension install, and use that token

## Links

- https://replayweb.page/
- https://github.com/webrecorder/archiveweb.page/blob/main/src/ext/ipfs.js#L99
- https://github.com/webrecorder/archiveweb.page
- https://github.com/RangerMauve/auto-js-ipfs/blob/initial/index.js
- https://tweet-signed-witness.glitch.me/
- https://github.com/ipfs/ipfs-companion/issues/666
- https://express.archiveweb.page
- https://github.com/webrecorder/archiveweb.page/blob/main/src/embed.html

- We can punt on private tweets for mvp, if we cannot fetch in page with credentials to generate the in-page archive. This would need a disclaimer to say that it cannot be verified.

Next steps:
- user stories
- Send drew