shipyard hello world blog post #677
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @bethanymarz |
aschmahmann
force-pushed
the
blog/shipyard-hello-world
branch
from
27c4969 to
bff9a6c
Compare
aschmahmann
commented
Mar 29, 2024
mishmosh
previously requested changes
Apr 3, 2024
There was a problem hiding this comment.
- I think your roadmap is one of the strongest parts of this post. Consider moving it out of the FAQ and into the body. Also, this post says you're eager for input on the roadmap. How can readers of this blog post give that input? Forum thread/Github place/chat?
- Shouldn't mention "maybe token" without thorough legal review, which is probably not worth doing while it's still in the idea phase.
- The "we" in this post is still tricky. The IPFS Project vs. Shipyard vs. Foundation. Made a few suggestions inline to clarify.
src/_blog/shipyard-hello-world.md
Outdated
|
|
||
| We have an extensive [initiative roadmap](https://ipshipyard.com/initiative-roadmap) and are eager to get more input from the developer community. To shout out just a few ideas we’re working on: | ||
|
|
||
| * [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. |
There was a problem hiding this comment.
Would be great to mention DApps WG, latest PRs/ongoing work, and how people can learn more/get involved.
There was a problem hiding this comment.
Added a bit more info on the dApps WG and reaching us on the forums or by email (unfortunately libp2p.io doesn't have a section with the forums, chat, etc. to link to so just went with the linking to the libp2p forums and the IPFS community section in the docs)
mishmosh
reviewed
Apr 3, 2024
aschmahmann
commented
Apr 3, 2024
Co-authored-by: Mosh <1306020+mishmosh@users.noreply.github.com>
aschmahmann
commented
Apr 3, 2024
aschmahmann
commented
Apr 3, 2024
aschmahmann
commented
Apr 3, 2024
aschmahmann
commented
Apr 3, 2024
aschmahmann
commented
Apr 3, 2024
aschmahmann
commented
Apr 3, 2024
lidel
reviewed
Apr 5, 2024
bethanymarz
reviewed
Apr 8, 2024
* chore: improve implementations table adds useful links and annotations, allowing reader to explore details of each area --------- Co-authored-by: Adin Schmahmann <adin.schmahmann@gmail.com>
aschmahmann
commented
Apr 8, 2024
| <tr> | ||
| <td rowspan="2" style="border-width: thin; border-color: #888; padding: .5rem;"> | ||
| <p><a href="https://github.com/ipfs/boxo/#readme">Boxo</a> <small>(GO SDK)</small></p> | ||
| <p><a href="https://github.com/ipfs/kubo/#readme">Kubo</a> <small>(Server, Desktop, Brave)</small></p> |
There was a problem hiding this comment.
@lidel do you think we should link Brave here in case people aren't familiar? e.g.
Suggested change
| <p><a href="https://github.com/ipfs/kubo/#readme">Kubo</a> <small>(Server, Desktop, Brave)</small></p> | |
| <p><a href="https://github.com/ipfs/kubo/#readme">Kubo</a> <small>(Server, Desktop, <a href="https://brave.com/">Brave</a>)</small></p> | |
There was a problem hiding this comment.
Don’t think we need to link to Brave
aschmahmann
commented
Apr 8, 2024
src/_blog/shipyard-hello-world.md
Outdated
| description: 'Check out the new IPFS community calendar where you can participate and contribute to one of the many working groups advancing IPFS.' | ||
| author: Adin Schmahmann | ||
|
|
||
| date: 2024-03-29 |
There was a problem hiding this comment.
Suggested change
| date: 2024-03-29 | |
| date: 2024-04-08 | |
aschmahmann
commented
Apr 8, 2024
aschmahmann
commented
Apr 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.