# ipfs enabled extensions We want to define a "spec" for what IPFS Enabled extensions will look like. An IPFS Enabled extension is an extension that demonstrates the power of IPFS through a single feature, focused web extension. The goal is to showcase the possiblities while getting ipfs into the everyday uses of end users. #### Requirements * Should be focused to single-feature/Focused feature set * Should be compatible with Manifest V3 ## Architecture / Implementation * ~~js-ipfs?~~ * light client prototype? * store data locally vs service? both? ## Ideas ### pin website to ipfs Simply pin a website to ipfs with a single click from your browser toolbar - uses web recorder ### pin tweet to ipfs pin a tweet with a single click from your toolbar - uses web recorder - datestamped? (edit button) - https://express.archiveweb.page/#https://twitter.com/IPFS/status/1520178112671059969 users: * dis/misinfo communities * political communities * any content platforms that embed tweets twitter-specific features: * archive-to-embed ### pin image/content to ipfs - right click to pin users: * pinterest ppl * nfts * researchers * designers (moodboards) * developers (image compression) features * collections (w/ metadata - eg tagged, etc) * https://squoosh.app ### ipfs toolbox devtools enabled addon https://hackmd.io/sJZib5iiShGxmQ2x-OD8SQ - cid explorer (cid.ipfs.io) - regex matches for cid - is-ipfs (right click link or cid to see if matches is-ipfs) - quick links to ipfs related resources - inspect dnslink - inspect x-ipfs-path - peer count - explore ipfs network - view node config - dag explorer - generate cid for content (without adding/publishing) - list providers of a cid - local node connectivity debugging - am i dialable (or another peer id) - ENS/ANS/SNS/etc testing - gateway testing, gateway list checking - performance testing of content - ipld explorer - vs code extension ### journal opens up a full page text editor that can be published and shared on ipfs - full page textarea/content editable - "undo" (unpin from local node) - could integrate with fleek.co notes: - see Agregore's local-first blog approach - good testcase for ipfs template - writable gateways https://github.com/ipfs/in-web-browsers/issues/189 - can use web3.storage in meantime ### pin gist to ipfs pin gists and snippets to ipfs - vscode extension to pull these into editor - git-ipfs-rehost ### pin playback pin videos from youtube and other video sharing sites - webrecorder ### pin them all - download them all (but for ipfs) ### reader mode pin news stories for later (and defeat paywalls) to share aka "local-first Pocket" - webrecorder - github meehow/2read - https://archive.ph/ ### watch pinned watch a pinned item, pin updates and add to activity log for cid (stored in ipfs or local storage) - option for notification on update - can choose to keep versions or not - can choose to republish or not notes: * can build things like Twitter extension on top of this ### generate qr code generate qr code to direct to ipfs hosted content - qr code design prior art: https://share.ipfs.io/ ### diffuse music player from ipfs - awesome-ipfs - https://github.com/icidasset/diffuse - supports webdav :P https://diffuse.sh/about/ ### ipfs drive - file manager - awesome-ipfs - https://github.com/fazo96/ipfs-drive ### doom on ipfs - https://medium.com/play-to-earn/classic-doom-running-on-decentralized-skynet-39d469ff0618 ### record audio directly to ipfs - mini editor (think audacity) in page before publish - webaudio api ### record video directly to ipfs - mini editor before publish (like iphone built in editor)