Skip to content

Issues: ipfs/specs

IPFS Specifications Licensing
#137 opened Sep 28, 2016 by RichardLitt
Open 14
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
9 Open 7 Closed
9 Open 7 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Add specification for Web Pathing kind/missing-specs A gap in specs for things already used in the real world P1 High: Likely tackled by core team if no one steps up
#432 opened Aug 14, 2023 by lidel
@lidel
gateway: add CORS to specs dif/expert Extensive knowledge (implications, ramifications) required effort/days Estimated to take multiple days, but less than a week kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up
#423 opened Jun 26, 2023 by lidel
Add DNSLink specs for resolving /ipns/{fqdn} content paths dif/medium Prior experience is likely helpful kind/missing-specs A gap in specs for things already used in the real world P1 High: Likely tackled by core team if no one steps up
#389 opened Mar 26, 2023 by lidel
Create IPIP: UnixFS and Gateway support for explicit MIME/Content-Type need/triage Needs initial labeling and prioritization P1 High: Likely tackled by core team if no one steps up
#364 opened Jan 12, 2023 by lidel
7 tasks
1
Create Routing Specs dif/expert Extensive knowledge (implications, ramifications) required P1 High: Likely tackled by core team if no one steps up
#347 opened Nov 21, 2022 by lidel
6 tasks
Broken link in readme dif/easy Someone with a little familiarity can pick up effort/hours Estimated to take one or several hours P1 High: Likely tackled by core team if no one steps up topic/docs Improvements or additions to documentation
#339 opened Nov 9, 2022 by mrodriguez3313
1
IPIP numbering need/community-input Needs input from the wider community P1 High: Likely tackled by core team if no one steps up
#303 opened Aug 2, 2022 by thibmeu
2
Naming blocks in the datastore P1 High: Likely tackled by core team if no one steps up
#242 opened Mar 12, 2020 by Stebalien
16
IPFS Specifications Licensing dif/expert Extensive knowledge (implications, ramifications) required kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up
#137 opened Sep 28, 2016 by RichardLitt
14
ProTip! What’s not been updated in a month: updated:<2024-09-01.