20 |
21 |
22 |
30 |
--------------------------------------------------------------------------------
/composables/useAsset.ts:
--------------------------------------------------------------------------------
1 | export function useAsset(path: string): string {
2 | const assets = import.meta.glob('~/assets/**/*.{svg,png,jpg,jpeg,webp}', {
3 | eager: true,
4 | import: 'default',
5 | })
6 | // @ts-expect-error: wrong type info
7 | return assets[`/assets/${path}`]
8 | }
9 |
--------------------------------------------------------------------------------
/content/help.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Getting Help
3 | description: Learn where to get help and support in the extensive, diverse IPFS ecosystem.
4 | ---
5 |
6 | * **IPFS documentation**: We have a [dedicated docs site](https://docs.ipfs.tech) that's the best first place to look.
7 | * **Technical support**: For specific questions, including technical support, please use the [official IPFS discussion forums](https://discuss.ipfs.tech).
8 | * **General questions and discussions**: Use the [official IPFS discussion forums](https://discuss.ipfs.tech) or [chat on Matrix](https://docs.ipfs.tech/community/#chat).
9 | * **IPFS-related community announcements**: If you'd like to announce something to the IPFS community at large, use the [official IPFS discussion forums](https://discuss.ipfs.tech); we monitor the forums for things to include in the weekly IPFS newsletter! You can also inform people via [Matrix](https://docs.ipfs.tech/community/#chat) and the [other venues](#other-venues) listed below.
10 | * **Bugs and feature proposals**: IPFS-codebase-related bugs and feature proposals can be reported directly in their repositories (most are in the [IPFS](https://github.com/ipfs) and [IPFS Shipyard](https://github.com/ipfs-shipyard) GitHub orgs), for example [Kubo](https://github.com/ipfs/kubo) or [js-ipfs](https://github.com/ipfs/js-ipfs). If you're not sure where the best place to report a bug or request a feature is, ask in the [forums](https://discuss.ipfs.tech) and someone will point you in the right direction.
11 | * **Support for libp2p**: Questions specific to libp2p should use the [libp2p forums](https://discuss.libp2p.io) for faster results.
12 | * **Reporting security issues**: To report [security issues](https://github.com/ipfs/community/blob/master/CONTRIBUTING.md#security-issues), please email security@ipfs.io.
13 | * **Reporting abuse**: To report [abuse](https://github.com/ipfs/community/blob/master/code-of-conduct.md), please email abuse@ipfs.tech.
14 | * **Something else not listed here?** Ask in the [official IPFS discussion forums](https://discuss.ipfs.tech).
15 |
16 |
17 | ### IPFS discussion forums
18 |
19 | We aim to direct the majority of discussions and support questions toward the [official IPFS discussion forums](https://discuss.ipfs.tech). IPFS developers keep an eye on posts in the forums and are happy to jump in to help. This makes it easier to search and learn from previous discussions, and it helps us keep code repositories focused — thereby increasing the ratio of actionable, clearly defined, and scoped issues that anyone can contribute to.
20 |
21 | ### GitHub repositories
22 |
23 | We keep all our codebases and supporting/additional repositories in GitHub. For this, we maintain several GitHub organizations:
24 |
25 | * [IPFS](https://github.com/ipfs) contains the core codebases and related libraries. We aim to keep this organization tidy, with all projects in it being actively maintained by the IPFS core teams.
26 | * [IPFS Shipyard](https://github.com/ipfs-shipyard) contains many side projects, tooling, and endeavors that are not part of the core codebase and therefore may have different levels of maturity and activity. We encourage the community to step up and drive Shipyard projects forward!
27 | * [IPFS Archive](https://github.com/ipfs-inactive) contains archived repositories that are obsolete and no longer under active development (usually because they have been replaced by something else).
28 |
29 | We aim to keep the issue trackers in most repositories for specific, scoped discussions and implementation approaches. Reducing the noise in the repositories via high-quality, on-point issues helps our teams perform more efficiently and serve the developer community faster.
30 |
31 | ### Matrix and Discord
32 |
33 | Our official chat rooms in [Matrix](https://app.element.io/#/room/#lobby:ipfs.io) and [Discord](https://discord.gg/Z4H6tdECb9) are bridged, so you can join whichever you prefer. They can be used to ask questions and discuss with the community — however, while IPFS core developers are usually in these rooms, it can be hard to keep up with the running conversation and questions can be missed or disappear due to a lack of indexing. Therefore, we prefer the [forums](https://discuss.ipfs.tech) for support questions, though you can still try the chats!
34 |
35 | ### Other venues
36 |
37 | Core IPFS developers do not monitor the following venues, but many of our community members do and are happy to help and discuss:
38 |
39 | * [Stack Overflow](https://stackoverflow.com/questions/tagged/ipfs)
40 | * [Reddit](https://www.reddit.com/r/ipfs/)
41 |
--------------------------------------------------------------------------------
/content/legal.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Legal
3 | description: Report copyright infringement on the IPFS Gateway Service.
4 | ---
5 |
6 | Protocol Labs Inc. and the core IPFS team have adopted this copyright infringement policy in accordance with the [Digital Millennium Copyright Act](http://http://lcweb.loc.gov/copyright/legislation/dmca.pdf).
7 |
8 | If you are a copyright owner, or agent of the owner, and you believe that content available on the IPFS Gateway Service hosted at `ipfs.io` or `dweb.link` infringes one or more of your copyrights please notify us by sending a DMCA Notice of the infringement containing the information below. After we receive a valid and complete notice, we will investigate and block or otherwise make the material unavailable through the IPFS Gateway Service. Learn more about our process below.
9 |
10 | **Please note - this policy is only applicable to the IPFS Gateway Service operated by the IPFS team (including `ipfs.io` & `dweb.link`). See [the public gateway checker](https://ipfs.github.io/public-gateway-checker/) for owners of other gateways to contact directly.**
11 |
12 | The email address (preferred) and physical address (less preferred) of our Designated Agent to receive notification of claimed infringement is listed at the end of this policy. Please read it carefully and make sure you are aware of the legal implications of the DMCA. You can be held liable for damages, including costs and attorney fees, if you materially misrepresent that material or activity infringes on your copyright. We may highlight such abuses, too. Consult an attorney before filing a DMCA Notice if you are unsure whether copyrights have been infringed, or if you are unsure whether your materials have been removed in error.
13 |
14 | ### How do you file a DMCA Notice?
15 | Your DMCA Notice must include all of the following information:
16 |
17 | 1. A physical or electronic signature of the copyright owner, or a person authorized to act on behalf of the copyright owner;
18 | 2. Identification (URL) of the copyrighted work or material being infringed upon;
19 | 3. Description of the work or material that you claim to be infringing and would like to be removed, including information regarding its location (URL) with enough detail so that we can and verify it;
20 | 4. Your full legal name, mailing address, telephone number, and email address where we can contact you;
21 | 5. A statement that you have a good faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law; and
22 | 6. A statement that the information in your DMCA Notice is accurate, and under penalty of perjury, that you are the copyright owner or are authorized to act on behalf of the copyright owner.
23 |
24 | ### Where do you email/send the DMCA Notice?
25 | The quickest way is to email it to abuse@ipfs.tech. If you prefer, you can instead send it to:
26 |
27 | Protocol Labs Inc.
28 | Attn: IPFS Designated DMCA Agent
29 | 427 N. Tatnall St. #51207
30 | Wilmington, Delaware 19801
31 |
32 | Our Designated Agent’s telephone number is **+1 (302) 409-0239**.
33 |
34 | ### What happens after sending the DMCA Notice?
35 | If the DMCA Notice complies with the above requirements, we will remove or disable access to the cited content that is allegedly infringing. We will make a good faith attempt to notify the alleged infringer of the takedown, with a copy of your DMCA Notice, using the contact information provided to us.
36 |
37 | ### What happens if you receive a DMCA Notification from us?
38 | If you believe your content was removed in error, you can file a counter notification with the information below (“DMCA Counter Notification”).
39 |
40 | ### How do you file a DMCA Counter Notification?
41 | Your DMCA Counter Notification must include all of the following information:
42 |
43 | 1. Your physical or electronic signature;
44 | 2. Identification (URL) of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled (the description from the DMCA Notice is acceptable);
45 | 3. A statement under penalty of perjury that you have a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled;
46 | 4. Your full legal name, mailing address, telephone number, and email address where we can contact you; and
47 | 5. A statement that you consent to the jurisdiction of Federal District Court for the judicial district in which your address is located, or if your address is outside of the United States, for any judicial district in which Protocol Labs may be found, and that you will accept service of process from the person who provided the DMCA Notice or an agent of such person.
48 |
49 | ### What happens after sending the DMCA Counter Notification?
50 | If we receive valid DMCA Counter Notification that meets the above criteria, we will forward a copy to the person who filed the original DMCA Notice. If we do not receive notice within 10 business days that the person who submitted the DMCA Notice is seeking a court order to prevent the infringement of the content at issue, we will replace or re-enable access to the content that was removed.
51 |
--------------------------------------------------------------------------------
/content/media.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: IPFS Press Kit
3 | description: Resources for the media, including explainers, logos, and more.
4 | ---
5 |
6 | We've created this IPFS press kit to help news and media outlets quickly find material to help understand and explain what IPFS is, who powers the IPFS project, and how it will shape the future of the internet.
7 | If you're a member of the media and would like to request more information or interviews, please [email](mailto:press@protocol.ai).
8 |
9 | ### About IPFS
10 |
11 | _Feel free to reprint the following descriptions in their entirety without explicit approval._
12 |
13 | #### Long description
14 |
15 | IPFS (the InterPlanetary File System) is a peer-to-peer hypermedia protocol for content addressing. An alternative to the HTTP protocol, IPFS builds on the principles of peer-to-peer networking and content-based addressing to create a decentralized, distributed, and trustless data storage and delivery network. With IPFS, users ask for a file and the system finds and delivers the closest copy without the need to trust a centralized delivery source. In addition to more efficient content distribution, IPFS offers improved security, content integrity, and resistance to third-party tampering. _(621 characters/95 words)_
16 |
17 | #### Short description
18 |
19 | IPFS (the InterPlanetary File System) is a peer-to-peer network and protocol designed to make the web faster, safer, and more open. IPFS upgrades the web to work peer to peer, addressing data by _what_ it is instead of _where_ it’s located on the network, or who is hosting it. _(282 characters/52 words)_
20 |
21 | #### IPFS and Filecoin
22 |
23 | Filecoin is an independent, complementary protocol that builds on the content addressing of IPFS to add longer term data persistence using cryptoeconomic incentives.
24 | For details on understanding the relationship between IPFS and Filecoin, please see [this guide in Filecoin documentation (2023)](https://web.archive.org/web/20230223052220/https://docs.filecoin.io/developers/introduction/filecoin-and-ipfs/).
25 |
26 | #### Does IPFS have a blockchain?
27 |
28 | No, [IPFS does not have a blockchain](https://doesipfshaveablockchain.com/).
29 |
30 | ### The IPFS ecosystem
31 |
32 | IPFS is made up of a large number of individuals and teams contributing to the project at a variety of levels, for a variety of individual, non-profit, and corporate projects.
33 |
34 | #### Core team
35 |
36 | The IPFS project is made up of a series of working groups, populated by many full-time and part-time contributors to core project needs.
37 |
38 | [Interplanetary Shipyard](https://ipshipyard.com/) are the core maintainers of many of the popular IPFS and libp2p implementations.
39 |
40 | #### Open-source community
41 |
42 | As an open-source project, IPFS is home to a vibrant, diverse community of thousands of contributors and participants from all over the globe! Learn more about who they are and where to find them [in the Community section of the IPFS docs](https://docs.ipfs.tech/community/).
43 |
44 | #### Projects using IPFS
45 |
46 | A vast variety of commercial and non-profit projects alike are incorporating IPFS as critical to their goals and success. Many are amenable to talking to the media. Find out more about existing success stories at the following resources:
47 |
48 | - [Case studies](https://docs.ipfs.tech/concepts/#examples-and-case-studies) for IPFS success stories in a variety of industries.
49 | - Video presentations and demos from IPFS builders and collaborators in our [YouTube channel](https://www.youtube.com/c/IPFSbot/videos).
50 | - Interactive [IPFS ecosystem directory](https://ecosystem.ipfs.tech) of companies and organizations worldwide building apps, services, and developer tools on IPFS.
51 |
52 | ### Logos
53 | To request official IPFS logos and other graphic elements, please [email](mailto:press@protocol.ai).
54 |
55 | ### Featured news
56 | All IPFS-related news can be found on our [Blog & News](http://blog.ipfs.tech) page. Items can be filtered by topic for easy access:
57 |
58 | - [Blog posts](http://blog.ipfs.tech/?category=Blog%20post)
59 | - [Video content](http://blog.ipfs.tech/?category=Video)
60 | - [News coverage](http://blog.ipfs.tech/?category=News%20coverage)
61 | - [Events](http://blog.ipfs.tech/?category=Event)
62 |
63 | Additionally, you can get up-to-the minute updates on our [Twitter](https://twitter.com/ipfs) and [YouTube](https://www.youtube.com/c/IPFSbot) channels.
64 |
--------------------------------------------------------------------------------
/content/team.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: The IPFS Team
3 | description: Learn how the global IPFS community asynchronously collaborates to decentralize the web.
4 | ---
5 |
6 | IPFS is the collective work of thousands of contributors from multiple geographies and backgrounds, working [collaboratively and asynchronously](https://github.com/ipfs/team-mgmt#how-we-work-together) to decentralize the web.
7 |
8 | ## Open-source community
9 |
10 | As an [open-source project](https://github.com/ipfs/ipfs), anyone can [contribute to IPFS](https://docs.ipfs.tech/community/contribute/ways-to-contribute/) and help make an impact on the future of the web – regardless of areas of interest or specialty. IPFS open-source contributors bring a broad range of valuable skills to the project, making tangible differences in a wide variety of areas:
11 |
12 | - [Protocol design](https://docs.ipfs.tech/community/contribute/ways-to-contribute/#protocol-design) and [implementation](https://docs.ipfs.io/community/contribute/ways-to-contribute/#code)
13 | - [Documentation](https://docs.ipfs.tech/community/contribute/ways-to-contribute/#documentation)
14 | - [Community outreach](https://docs.ipfs.tech/community/contribute/ways-to-contribute/#community) and [support](https://docs.ipfs.io/community/contribute/ways-to-contribute/#support)
15 | - [Functional testing](https://docs.ipfs.tech/community/contribute/ways-to-contribute/#testing) and user testing
16 | - [Visual and user experience design](https://docs.ipfs.tech/community/contribute/ways-to-contribute/#design)
17 | - [Building apps and services](https://docs.ipfs.tech/community/contribute/ways-to-contribute/#applications) that use IPFS
18 |
19 | There's never been a more exciting time to be part of the global IPFS community, so if you'd like to make a difference and help shape the future of the internet, there's a place for you to jump in! The IPFS community is an engaged, inquisitive, and helpful collective with a [Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md) intended to create an environment that is friendly, safe, and accepting, and free from intimidation or harassment.
20 |
21 | If you'd like to start by dipping your toes in the water, [IPFS meetups](https://www.meetup.com/pro/ipfs/) are a great place to begin. Local community meetups happen worldwide, and there's also a well-attended monthly virtual meetup showcasing the latest community projects, current IPFS news and events, and more.
22 |
23 | ## IPFS core team
24 |
25 | While IPFS is primarily an open-source, community-driven project, community priorities are shepherded by a core team that helps to ensure that strategic roadmapping and overall velocity continue to meet the project's high-level goals of decentralizing the web.
26 |
27 | Many, but not all, of the IPFS core team are also part of [Protocol Labs](https://protocol.ai), an open-source R&D lab whose mission is to drive breakthroughs in computing to push humanity forward.
28 |
29 | The IPFS core team is organized flexibly and responsively to nimbly adjust to shifting priorities over time. While team organization may iterate on an as-needed basis to best serve current project priorities, team structure always reflects a high-level commitment to _improving the IPFS developer experience and toolset_ as part of making IPFS and its sibling web3 protocols [Filecoin](https://filecoin.io), [libp2p](https://libp2p.io/), [IPLD](https://ipld.io), and [Multiformats](https://multiformats.io/) a seamless, ubiquitous part of the future web. Current areas of high-level organization include:
30 |
31 | - **Web3 Developer Tools:** Ensuring that developers on the decentralized web have a robust, performant, easy-to-use stack — including IPFS — available to them in order to accelerate the impact of the future internet.
32 | - **Ecosystem:** Seeding the long-term growth of the decentralized web by fostering relationships with a wide variety of developers and other stakeholders who are using IPFS and related protocols and tools in the web3 stack.
33 | - **Stewards:** Ensuring the existing IPFS codebase and related tools are well maintained and iteratively improved upon in response to community needs and future goals.
34 |
35 | The IPFS core team strictly adheres to a policy of _public discussion and communication by default_ in order to maximize opportunities for community involvement and feedback. This means a commitment to communicating and discussing strategic direction and other high-level decisionmaking in public-facing, async-friendly channels such as [GitHub](https://github.com/ipfs) and the [official IPFS forums](https://discuss.ipfs.tech). For example, calls to participate in roadmapping and similar strategic activities will be announced on the [IPFS Blog & News](https://blog.ipfs.tech/), and proposals and discussions regarding future strategic work can be found in the [IPFS Roadmap repo](https://github.com/ipfs/roadmap/issues).
36 |
37 | ## Jobs working with IPFS
38 |
39 | The simplest way to search for jobs building on or working with IPFS is to [subscribe to the IPFS newsletter](https://ipfs.fyi/newsletter) — each week's edition includes new job postings from a wide variety of companies and organizations looking for talented individuals interested in building the decentralized web.
40 |
41 | Additionally, open positions to work on the IPFS core team can be found [here](https://protocol.ai/join/).
42 |
--------------------------------------------------------------------------------
/eslint.config.js:
--------------------------------------------------------------------------------
1 | // eslint.config.js
2 | import antfu from '@antfu/eslint-config'
3 | import unocss from '@unocss/eslint-config/flat'
4 |
5 | export default antfu({}, unocss)
6 |
--------------------------------------------------------------------------------
/layouts/default.vue:
--------------------------------------------------------------------------------
1 |
45 |
46 |
47 |
10 |
11 |
12 | Community: Get in Orbit
13 |
14 |
15 | Join our open source ecosystem of ~2,000 active contributors, plus many more developers and users.
16 |
17 |
18 |
19 |
20 | Connect
21 |
22 |
23 | From the annual IPFS Camp and
24 | IPFS Thing
25 | conferences to
26 | working groups and online forums, our community creates out-of-this-world ideas right here on Earth. Join us!
27 |
28 |
29 |
30 |
31 | Join the conversation
32 |
33 |
66 | Check out the
67 | IPFS Forums
68 | to discuss open problems, share ideas, and get help from the
69 | community.
70 |
71 |
72 |
73 |
74 |
75 | Join a community event
76 |
77 |
78 |
79 | Meet other members of the community virtually or in-person by
80 | subscribing
81 | to our
82 | event calendar
83 | .
84 |
85 |
86 |
87 |
88 | Keep up with what's new
89 |
90 |
91 | Get the latest on news about what's happening in the IPFS ecosystem by
92 | subscribing to our
93 | newsletter
94 | and
95 |
96 | YouTube channel
97 | .
98 |
99 |
100 |
101 |
102 |
114 |
115 |
116 |
117 |
118 |
119 | Events And Working Groups
120 |
121 |
122 | Help us untangle the thorniest problems facing the distributed web (and meet some bleeding edge thinkers) by joining one of our global working groups.
123 |
124 | Subscribe to upcoming events
125 |
126 |
127 |
128 |
144 |
145 | The Next Frontiers
146 |
147 |
148 | We're shooting for the stars, and we can't do it without your help. Here are some
149 | of the unknowns we've yet to discover:
150 |
151 |
152 |
153 |
154 |
155 | How can we introduce privacy and encryption functionality to IPFS?
156 |
157 |
158 | How do we enable connectivity between every platform IPFS runs on, from satellites to lower powered IoT devices?
159 |
160 |
161 | What data structures and recommendations can we create to help other developers?
162 |
163 |
164 | How can we invent a more efficient peer-to-peer data transfer protocol?
165 |
166 |
167 |
168 |
169 |
170 | Interested in solving these challenges together? Join a
171 | community event
172 | , a
173 | working group
174 | , or
175 | forum
176 | discussion.
177 |
178 |
179 |