ipfs/ipfs-companion

Change IPFS Path format

Open

#1,222 opened on 2023年6月20日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,992 stars) (364 forks)batch import
P3effort/hoursexp/beginnergood first issuekind/discussionneed/maintainer-input

説明

Is your feature request related to a problem? Please describe. Currently sharing an IPFS url in the browser isn't as straightforward as a http url. I need to copy the the "IPFS Path" first, (/ipfs/bafy...), and then manually replace the prefix /ipfs/ with ipfs:// in order to have a link that can be pasted in another browser using IPFS Companion.

Also, having a "shareable Link" suggest that the other links (e.g IPFS path) are not shareable. Maybe it would be good to rename Shareable Link to something else (e.g HTTP Link, Web2 Link, ...) to emphasize that other links are also shareable.

Describe the solution you'd like

  • Change the IPFS Path format from /ipfs/bafy... (interpreted as a file), to ipfs://bafy... that can be resolved by a browser.
  • The same with IPNS Path
  • Rename Shareable Link to HTTP Link, Web2 Link or something else.

Describe alternatives you've considered I don't know much about browsers, but an alternative (even better?) solution could be to have the ipfs://bafy... directly in the url bar, that was it is easier to copy paste and share.

Having the following urls (respectively CID and IPNS name) in the url bar isn't very insightful for the end user (especially the .ipfs.localhost:8080 part). Sure, under the hood it is served by a local http server, but the end user should not have to care about it.

http://bafybeic6dlhlnsmzkvzdx3htx4jr6xqgu6ecbrm5dhqmkgvhsi3sbqpxci.ipfs.localhost:8080/2023-how-to-host-dynamic-content-on-ipfs/#use-case-edge-computed-applications http://blog.ipfs.tech.ipns.localhost:8080/2023-how-to-host-dynamic-content-on-ipfs/#use-case-edge-computed-applications

But again, maybe it is something that cannot be changed in browsers, it is just a "nice to have" if it is possible.

コントリビューターガイド

技術スタック
javascripthtmlcss
領域
frontend
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
basic browser extension developmentunderstanding of IPFS paths
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
70
調査方針
The issue requests changing IPFS Path format from '/ipfs/...' to 'ipfs://...' and renaming 'Shareable Link' to 'HTTP Link' or similar. Start by identifying where IPFS paths are displayed in the extension's popup or settings pages. Modify the path formatting logic to prepend 'ipfs://' instead of '/ipfs/'. Update the localization strings for the link labels. Test the changes in a local build of the extension. Consider checking if the browser's URL bar can directly show ipfs:// URIs, but note that may require additional permissions or changes to how the extension integrates with the browser. The existing issue comments may contain further context.
Change IPFS Path format · ipfs/ipfs-companion#1222 | Good First Issue