New Newsletter! \o/ #52
Closed
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
|
@Kubuxu ping |
|
|
||
| ### [go-ipfs](//github.com/) | ||
|
|
||
| We updated `go-ipfs` to 0.4.3-rc3 on August 8th. As we state in the [changelog](https://github.com/ipfs/go-ipfs/blob/master/CHANGELOG.md), this release candidate fixes a panic that occurs when input from stdin was expected, but none was given. Check out [this issue](https://github.com/ipfs/go-ipfs/pull/3050) for details. If you missed the 0.4.3 roll-out, you can take a look at that changelog [here](). |
There was a problem hiding this comment.
bringing up a minor bugfix as the only mention of whats changed in this release kinda sells it short. Theres a bunch of really cool stuff in the changelog that @lgierth really nicely wrote up
There was a problem hiding this comment.
Thanks @whyrusleeping. Didn't realize that this was not the only fix; will dig back through the changelog.
There was a problem hiding this comment.
@whyrusleeping no, wait, I am confused. That minor fix is the only mentioned in the changlog for rc-3. Am I missing something? https://github.com/ipfs/go-ipfs/blob/master/CHANGELOG.md#043-rc3---2016-08-09
There was a problem hiding this comment.
cc @lgierth can you help me out here, too?
There was a problem hiding this comment.
How much we want to talk about v0.4.3 depends on the scope of the newsletter. The last release v0.4.2 is over three months old, so I'd say probably only the very recent developments of v0.4.3 are relevant (i.e. rc3).
Is the only change between rc2 and rc3 really just ipfs/kubo#3050?
If you missed the 0.4.3 roll-out, you can take a look at that changelog here.
Not sure what "rollout" means here -- we haven't released it yet. It's good to point to the rc1/2/3 binaries on dist.ipfs.io though :)
There was a problem hiding this comment.
Oh the entirety of v0.4.3 is probably worth mentioning a la "check the changelog, or wait for the release blog post"
|
LGTM |
|
|
||
| Orbit, the decentralized chat app run on top of IPFS, has just integrated uPort identities. There's a writeup on what uPort is [on Medium](https://medium.com/@ConsenSys/uport-the-wallet-is-the-new-browser-b133a83fe73) - essentially, it is a web-based wallet and identity management system. This means that users will be able to use their uPort name and profile picture in Orbit, as well as provision a signing key that will sign Orbit messages. We've been working with [ConsenSys](https://consensys.net/) to make this happen. You can track this [here](https://github.com/haadcode/orbit/issues/37). | ||
|
|
||
|  |
|
@lgierth @whyrusleeping Fixed. Thoughts? |
RichardLitt
assigned ghost
, jbenet, dignifiedquire, daviddias and whyrusleeping and unassigned jbenet, dignifiedquire, daviddias and whyrusleeping
|
|
||
| We've updated `go-ipfs` to 0.4.3-rc3 on August 8th. 0.4.2 is still the stable version; however, if you're interested in trying out the release candidates, take a look at the binaries on [dist.ipfs.io](https://dist.ipfs.io/go-ipfs). The 0.4.3-rc comes with a couple of nice enhancements, and improves the performance of storage, bitswap, as well as content and peer routing. It also introduces a handful of new commands and options, and fixes a good bunch of bugs: you can take a look at the full changelog [here](https://github.com/ipfs/go-ipfs/blob/master/CHANGELOG.md). | ||
|
|
||
| Moving to go1.7 is in the works, as it will give us performance improvements, `context` has been added into stdlib, and `net.Diallib` will allow our calls to vastly improve resource consumption and downtime. It also adds support for macOS Sierra. [Track that here](https://github.com/ipfs/go-ipfs/issues/3093). |
There was a problem hiding this comment.
I think it's net.DialContext, not net.Diallib -- https://golang.org/doc/go1.7#net
There was a problem hiding this comment.
also maybe something like "and net.DialContext will allow us to improve resource consumption", without vastly, better be modest conservative with words and let numbers speak for themselves :) (TODO we needa automated benchmarks)
There was a problem hiding this comment.
Oh yeah, i thought i mentioned that already? dont see my comment anywhere though...
|
|
||
| The [js-ipfs-api](https://github.com/ipfs/js-ipfs-api) v7 has now been shipped; a full exposition of this and the thinking behind it can be found [here](https://github.com/ipfs/js-ipfs-api/pull/305). The short story is that it now has 30% more files interfacing, which means more interop with go-ipfs and more you can do with it. For future changes, [follow this issue](https://github.com/ipfs/interface-ipfs-core/issues/55), which will communicate interface changes on js-ipfs and js-ipfs-api. | ||
|
|
||
| Moving to pull-streams: The 🚲🏠 (bike-shedding) was strong in this one, but we've finally made a call on the Control Flow library to use in order to solve the hiccups we have had in the past with Node.js Streams. This discussion took a lot of input from several people familiar with the js-ipfs project and the contenders for the Control Flow Library. You can read the whole thread [here](https://github.com/ipfs/js-ipfs/issues/362). |
There was a problem hiding this comment.
Probably no need to use the term bikeshedding in a Newsletter
|
LGTM pending diasdavid's comments and the TODO at the bottom of the newsletter. Sweet! 💯 |
|
Oops! Have some amendments! See the individual comments. |
|
|
||
|  | ||
|
|
||
| Orbit also now has a [textui](https://github.com/haadcode/orbit-textui). This uses [blessed](https://github.com/chjj/blessed), a curses-like library with a high level terminal interface API for Node.js. This means you can chat to people using Orbit, straight from where you get your work done, in the terminal. Of course, other venues, [like Slack](https://github.com/haadcode/orbit/issues/71), are also in the pipeline. |
There was a problem hiding this comment.
Should change to "Orbit also now has a terminal client
There was a problem hiding this comment.
I would remove "Of course, other venues, like Slack, are also in the pipeline.". The goals linked here is waaaaay into the future and I'm not even sure what will come out of that. I would leave it out.
|
I still need to get commits. I've fixed name-your-contributors (thanks so much for the help, @dignifiedquire ), and have the lists for this week. Thing is - the list is massive for IPFS. This is because any issue @whyrusleeping closed, no matter how old, brings along all of the names of the creators for those issues. So, we have people who haven't commented on IPFS in a while in this list. Should I try and remove them? I think this is OK, as their contributions were still valid until this final action - echo effects. Full list: |
|
@diasdavid Edited! All good? Unassign yourself if so. |
ghost
removed their assignment
|
@RichardLitt i think remove those contributors that didnt do something in that span of time |
|
What are we doing about the gap of newsletters? it should probably be filled? there's a large period of time with important things that is not accounted for. |
|
@richard my basic feedback on this newsletter (and others have mentioned it in conversation) is that the newsletter contains little compared to the number of things that happened in that period of time. This is the recurring thing from before-- so i think either:
|
|
To add: To Do
|
|
Don't add anything about Planet Express, it's too early. |
|
Add: |
|
Closing as won't fix. Too much time has passed, unfortunately. I am going to work on name-your-contributors to fix the bug that was present here, but for now I am stepping away from making the newsletter. |
|
Too bad, because it's really useful :( |
jennwrites
added a commit
that referenced
this pull request
Jul 30, 2019
First draft of IPFS Weekly #52
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.
What I need:
Then I think we should be good to go. This only covers since the IPFS Workshop in July.