【IPFS更新追踪】js-ipfs v0.31.0版本发布

【IPFS更新追踪】js-ipfs v0.31.0版本发布

 更新时间:2018年7月29日

 资讯来源:IPFS官方推特

更新出处:GitHub

消息发布:Alan·Shaw

更新概述:消息发布人Alan·Shaw在Twitter中公布js-ipfs v0.31.0版本已更新,并感叹更新速度如此之快,正好可以赶上2018年分布式网络峰会中展示。


以下为IPFS原力区追踪代码译文及本次更新内容原文,供各位爱好者参考

译文

🗺 什么还有待发布

  •  IPNS本地 (下一个版本)
  •  CID基本选项 (下一个版本)
  •  部分ipfs.resolve实施 (下一个版本)
  •  支持生叶
  •  连通性魔术
  •  “已打包,无更多” – 更新到最新的libp2p

🔦 强调

🧚连接魔术

最近对节点的基础结构更改IPFS作为网关运行意味着它们不能用作引导程序节点。这是坏消息,js-ipfs因为它还没有DHT来发现内容。因此无法连接到具有大量内容的节点意味着js-ipfs在网络上查找内容的机会变得更糟。

不过好消息!已经配置了全新的专用节点,这些节点连接到网关节点,可以用来js-ipfs引导自身以及获取此预加载您添加到IPFS的内容!这是正确的,当您向IPFS添加内容时,会提示预加载节点自动对其进行抢占,以便可以立即与网络上的其他IPFS节点共享。

🌿 原始数叶

原始数叶对你来说更健康,因为它们在烹饪过程中不会丢失维生素。说真的。如果你想从IPFS中传输原始数据(如视频)而没有解压缩protobufs的开销,那么它们就很棒。当您需要将数据放在仅处理原始数据(如URL)的数据存储中时,它们也很有用。

我们现在有这些!只需--raw-leaves=true在向IPFS添加内容时传递,您创建的DAG的叶子将仅包含原始数据。

🏗 API更改

  • preload已向IPFS构造函数提供的选项中添加了新的配置属性。使用以下API添加到IPFS的内容将自动预加载到一组IPFS节点上。要更多地了解如何配置此功能,请检查IPFS构造函数文档。
    • dag.put
    • block.put
    • object.new
    • object.put
    • object.patch.*
    • files.add*
    • files.write
    • files.mv
    • files.cp
  • --raw-leaves选项已启用files.add

✅ 发布清单

  • 坚固和质量
    •  ipfs-pubsub-room(#54)
    •  peerpad-core(#22)
    •  ipfs-log(#144)
    •  orbit-db(#423)
    •  单元
    •  互操作
    •  sharness
    •  确保所有测试都通过,包括:
    •  使用新版本运行以下项目的测试:
  • 文档
    •  确保README.md是最新的
    •  确保运行所有示例
  • 通讯
    •  推特
    •  IRC
    •  书签交易
    •  创建发布问题
    •  公告(预发布和发布后)
    •  博客文章

🙌🏽想要贡献?

您是否愿意为IPFS项目做出贡献而不知道如何做?好吧,有几个地方你可以开始:

  • 检查help wanted我们的聊天板块中Ready列的标签问题- https://waffle.io/ipfs/js-ipfs?label=help%20wanted
  • 加入IPFS All Hands,自我介绍并告诉我们您想要贡献的地方 – https://github.com/ipfs/pm/#all-hands-call
  • 用IPFS攻击并告诉我们你做了什么!All Hands电话也是演示的完美场所,加入并向我们展示您的建设
  • 加入http://discuss.ipfs.io/的讨论,帮助用户找到答案。
  • 加入⚡️ⒿⓈ核心开发团队每周同步🙌🏽并成为Sprint行动的一部分!

⁉️ 你有问题吗?

有关IPFS的问题,工作原理以及使用它可以做些什么的最好的地方是discuss.ipfs.io。我们也可以在Freenode的#ipfs频道上找到。

原文

🗺 What’s left for release

  •  IPNS locally (next release)
  •  CID base option (next release)
  •  Partial ipfs.resolve implementation (next release)
  •  Support for raw leaves
  •  Connectivity Magic
  •  “Already piped, no more” – Update to latest libp2p

🔦 Highlights

🧚 Connectivity Magic

Recent infrastructure changes to the nodes IPFS runs as gateways meant that they couldn’t be used as bootstrapper nodes. This was bad news bears for js-ipfs since it doesn’t yet have a DHT to discover content. So not being able to connect to the nodes that have a lot of the content meant the chances of js-ipfs finding content on the network took a turn for the worse.

Good news though! Brand new dedicated nodes have been provisioned that are connected to the gateway nodes and can be used by js-ipfs to bootstrap itself as well as, get this, preload content you add to IPFS! That’s right, when you add stuff to your IPFS, the preload nodes are prompted to slerp it up automatically so that it can be shared instantly with other IPFS nodes on the network.

🌿 Raw Leaves

Raw leaves are much healthier for you because they don’t lose their vitamins during the cooking process. Seriously though. They’re great if you want to stream raw data (like video) out of your IPFS without the overhead of unpacking protobufs. They’re also useful when you need to put your data in a data store that only deals with raw data, like a URL.

We have these now! Just pass --raw-leaves=true when adding content to IPFS and leaves of the DAG(s) you create will contain just the raw data.

🏗 API Changes

  • A new configuration property preload has been added to the options provided to the IPFS constructor. Content added to IPFS using the following APIs will be automatically preloaded on a set of IPFS nodes. To lean more about how to configure this feature, check the IPFS constructor docs.
    • dag.put
    • block.put
    • object.new
    • object.put
    • object.patch.*
    • files.add*
    • files.write
    • files.mv
    • files.cp
  • The --raw-leaves option has been enabled for files.add

✅ Release Checklist

  • Robustness and quality
    •  ipfs-pubsub-room (#54)
    •  peerpad-core (#22)
    •  ipfs-log (#144)
    •  orbit-db (#423)
    •  unit
    •  interop
    •  sharness
    •  Ensure that all tests are passing, this includes:
    •  Run tests of the following projects with the new release:
  • Documentation
    •  Ensure that README.md is up to date
    •  Ensure that all the examples run
  • Communication
    •  Twitter
    •  IRC
    •  Reddit
    •  Create the release issue
    •  Announcements (both pre-release and post-release)
    •  Blog post

🙌🏽 Want to contribute?

Would you like to contribute to the IPFS project and don’t know how? Well, there are a few places you can get started:

  • Check the issues with the help wanted label at the Ready column in our waffle board – https://waffle.io/ipfs/js-ipfs?label=help%20wanted
  • Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute – https://github.com/ipfs/pm/#all-hands-call
  • Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
  • Join the discussion at http://discuss.ipfs.io/ and help users finding their answers.
  • Join the ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 and be part of the Sprint action!

⁉️ Do you have questions?

The best place to ask your questions about IPFS, how it works and what you can do with it is at discuss.ipfs.io. We are also available at the #ipfs channel on Freenode.

ipfs原创,作者:IPFSforce,转载请注明出处:http://ipfser.org/2018/07/30/js-ipfs-v0-31-0/

0

扫一扫,分享到微信

猜你喜欢

文章评论

电子邮件地址不会被公开。 必填项已用*标注

获取验证码
后发表评论

微信公众号

知识星球