Skip to content
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.

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

Add IPFS on the Web update blog post #699

Open
wants to merge 30 commits into
base: main
Choose a base branch
from
Open

Add IPFS on the Web update blog post #699

wants to merge 30 commits into from

Conversation

2color
Copy link
Member

@2color 2color commented Oct 29, 2024

Copy link
Member

@SgtPooki SgtPooki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is great.. left some comments

src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
2color and others added 2 commits October 29, 2024 19:27
Co-authored-by: Russell Dempsey <[email protected]>
Co-authored-by: Russell Dempsey <[email protected]>
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
@2color 2color marked this pull request as ready for review October 31, 2024 13:19
@achingbrain
Copy link
Member

This is awesome. Do you think people will read it all or is it too long?

@2color
Copy link
Member Author

2color commented Nov 4, 2024

This is awesome. Do you think people will read it all or is it too long?

I've tried to make it more easily digestible and linkable with images, permalinks, and headers. It's also intended to be consumed piecemeal.

We can later publish separate posts focusing in on specific topics, etc.

src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

src/_blog/shipyard-2024.md Outdated Show resolved Hide resolved

**Resilient, decentralized, and verified** IPFS retrieval on the web is finally a reality.

This breadth and reach of this work is only possible because of the open-source nature of the IPFS and libp2p projects. But it also underscores the importance of funding the Interplanetary Shipyard team so that we can continue to shepherd these efforts across the ecosystem.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😍 🫶

* [Reliable, decentralized, and verified retrieval of CIDs](https://ipshipyard.com/initiative-roadmap/reliable-decentralized-and-trustless-browser-fetching-of-ipfs-content) (content identifiers) in browsers. The idea is to allow web browsers to fetch CIDs in a verifiable and trustless manner without being vulnerable to centralized chokepoints. You can participate and follow along with this work in the [IPFS dApps Working Group](https://lu.ma/ipfs-dapps).
* [IPFS for pioneers](https://ipshipyard.com/initiative-roadmap/ipfs-for-pioneers-enable-building-interoperable-ipfs-systems-using-http-protocols). We aim to enable the building of interoperable IPFS systems using extremely minimal HTTP-based protocols so that building IPFS-compatible tooling in something like Python (that doesn’t have much IPFS or libp2p tooling today) is super easy and appealing.
* [Self-service tooling for debugging IPFS request handling](https://ipshipyard.com/initiative-roadmap/self-service-tooling-for-debugging-ipfs-request-handling). The idea here is that a user can hit a Boxo-based HTTP gateway and if they experience an error, get a link to download an IPFS request trace. They can then use easy tooling locally or centrally hosted to pinpoint the issue.
* [Reliable, decentralized, and verified retrieval of CIDs](https://ipshipyard.com/initiatives/reliable-decentralized-and-trustless-browser-fetching-of-ipfs-content) (content identifiers) in browsers. The idea is to allow web browsers to fetch CIDs in a verifiable and trustless manner without being vulnerable to centralized chokepoints. You can participate and follow along with this work in the [IPFS dApps Working Group](https://lu.ma/ipfs-dapps).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the dapps working group is up anymore? Helia WG is the only ipfs event: https://lu.ma/ipfs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants