IPFS最新动态-29

  • 0_1550132873759_408b2bfb-5fbd-46eb-880e-a94ed5668fd8-image.png


    星际文件系统IPFS)是一种新的超媒体分发协议,通过内容和身份进行寻址。IPFS支持创建完全分布式应用程序,它的目的是使网络更快、更安全、更开放。

    由于这是一个相当大的范围,我们会跟进整个生态系统的开发,并在每周进行发布。


    最新资讯

    --


    认识布莱恩·霍夫曼

    --
    IPFS每周电话会议的下一位嘉宾,是布莱恩·霍夫曼(Brian Hoffman)。Brian在2014年从多伦多哈克顿奖的DarkMarket中获得了开源代码,然后开始了OpenBazaar,并从著名的风险投资公司Union Square Ventures和Andreessen Horowitz募集了100万美元,创建了OB1。

    将日历标记为"星期一下午5点"UTC,可以参与下周的会议。

    会议链接:
    https://github.com/ipfs/team-mgmt/issues/866


    相关文章

    --
    以下是最近一周发表,与IPFS有关的文章

    • 《IPFS和分布式文件存储》,发表于2019年2月11日

    • 《IPFS网关问题》,2019年2月7日 发表于Pinata

    • 《为什么选择libp2p?》,2019年2月6日 发表于Parity Technologies

    • 《纺织品更新 2019年1月》,发表于2019年2月6日

    • 《什么是以太坊的Infura?可扩展访问以太坊和IPFS》,发表于2019年2月6日

    • 《开发更新》,2019年2月,发表于Peergos

    • 《什么是IPFS:概述和用例》,发表于2018年12月20日


    社区中的提问🤔

    --
    以下是人们在IPFS生态系统中讨论的一些问题。


    IPFS工具与项目

    --
    Awesome IPFS 是一个用于社区维护和更新的项目、工具清单,任何与IPFS相关的东西都能够在其中找到。如果想要查找相关信息,可以访问GitHub上的Awesome IPFS,然后将要查到的内容添加到搜索列表中。

    • Prattle Network 是一个社交网络,它将内容完全存储在用户设备上,无法进行审查。
      网络地址https://prattle.tk/discover

    • 如果你仍想使用oasis.direct,可以通过DAppNode进行操作!已将它部署到http://oasis.dappnode.eth(使用以太坊+ IPFS),它将永远存在!欢迎来到一个去中心化的世界,没有人可以关闭一个伟大的服务了。😀


    社区活动

    --
    IPFS在discuss.ipfs.io上有一个论坛,注册之后可以看到IPFS在上面发布的公告,同时能够了解到社区即将举行的交流活动。

    --
    ☺️感谢阅读!


    识别二维码进入IPFS社群

    0_1550133344197_f58bb400-4f41-482c-a5f6-7b70a7a55331-image.png

Log in to reply
 

Email:filapp@protonmail.com

Twitter:

https://twitter.com/RalapXStartUp

Telegram:

https://t.me/bigdog403

全球Filecoin中文爱好者网站

  • X

    It has come to my attention that storage clients wish to obtain the CommD and CommR associated with the sector into which the piece referenced in their storage deal has been sealed. The client can already use the query-deal command to obtain the CID of the commitSector message corresponding to that sector - but message wait doesn't show individual commitSector arguments - it just shows some string encoding of the concatenated arguments' bytes.
    I propose to augment the ProofInfo struct with CommR and CommD such that the storage client can query for their deal and, when available, see the replica and data commitments in the query-storage-deal command. Alternatively, the query-storage-deal code could get deal state from the miner and use the CommitmentMessage CID to look up CommR and CommD (on chain) - but this seems like more work than is really necessary.

    阅读更多
  • X

    Hmmmm. These are just my thoughts off the cuff:

    For straight-ahead performance that's not specifically concerned with the issue of loading the data (from wherever), then work on smaller (1GiB) sectors is okay. When considering optimization for space so that large sectors can be replicated, 128GB for >1GiB sectors is obviously problematic from a normal replication perspective. However, if we consider the attacker who wants to replicate fast at any cost, then maybe it's okay.
    Based on this, we could probably focus on smaller sectors as a reasonable representation of the problem. This has the unfortunate consequence that the work is less applicable to the related problem of speeding replication even when memory must be conserved to some extent.
    I guess as a single datum to help calibrate our understanding of how R2 scales, it would be worth knowing exactly how much RAM is required for both 1GiB and (I guess) 2GiB. If the latter really fails with 128GB RAM, how much does it require not to? If the work you're already doing makes it easy to get this information, it might help us reason through this. I don't think you should spend much time or go out of your way to perform this investigation though, otherwise.
    Others may feel differently about any of this.

    阅读更多
  • X

    @xiedapao
    If there does exist such a thing, I cannot find it.

    zenground0 [7 hours ago]
    I don't believe there is

    zenground0 [7 hours ago]
    tho maybe phritz has some "refactor the vm" issues that are relevant

    laser [7 hours ago]
    I assert to you that we must create an InitActor in order for CreateStorageMiner conform to the specification.

    Why [7 hours ago]
    I’ll take things I don’t disagree with for $400 Alex

    zenground0 [7 hours ago]
    Agreement all around. However this is one of those changes that is pretty orthogonal to getting the storage protocol to work and something we can already do. We need to track it but I see it as a secondary priority to (for example) getting faults or arbitrating deals working.

    anorth [3 hours ago]
    Thanks @zenground0, I concur. Init actor is in our high-level backlog, but I'm not surprised there's no issue yet. Is it reasonable to draw our boundary there for now?

    阅读更多
  • X

    Does there already exist a story which addresses the need to create an InitActor?

    阅读更多

Looks like your connection to Filecoin.cn中国爱好者社区 was lost, please wait while we try to reconnect.