src/_blog: Add rust-libpp2p in 2022 post #26

mxinden · 2022-12-30T18:18:24Z

End of the year blog post on rust-libp2p, recapping on the many things in 2022. Also useful reflection exercise for the team.

src/_blog/rust-libp2p-2022.md

Co-authored-by: João Oliveira <hello@jxs.pt>

mxinden · 2023-01-04T10:25:51Z

@p-shahi could you give this post a review?

Steve mentioned that you were working on a general libp2p-in-2022 post. Sorry that I missed that. Any suggestions on how to proceed? I am fine with two separate posts.

mxinden · 2023-01-04T10:40:27Z

Tried the one-line-per-sentence markdown formatting here to ease reviews and git diffs. Unfortunately this is not properly rendered by our blog, i.e. the blog interprets a single \n as a newline within a paragraph.

Will keep it as is for now. Will reformat before we merge.

(//CC @thomaseizinger for the idea in general and //CC @elenaf9 given that this is exactly the behavior you predicted in our 1on1.)

marten-seemann · 2023-01-04T10:47:39Z

Does it make sense to have a separate rust-libp2p post here? This would kind of demand a “go-libp2p in 2022” post to be written up as well, and I’m not sure that would be a good use of our time. My preference would be to have a single “libp2p in 2022” post that covers all implementations.

Going forward, I think we’ll be better served by writing blog posts about single topics / features, shortly after we ship those, instead of long summary articles.

mxinden · 2023-01-04T19:14:06Z

Does it make sense to have a separate rust-libp2p post here? This would kind of demand a “go-libp2p in 2022” post to be written up as well, and I’m not sure that would be a good use of our time.

I don't think this is an all (js, go, rust, nim, ...) or nothing.

My preference would be to have a single “libp2p in 2022” post that covers all implementations.

Not opposed to a general libp2p post. In case someone volunteers to write such post, I am happy to integrate this one into the general one.

Going forward, I think we’ll be better served by writing blog posts about single topics / features, shortly after we ship those, instead of long summary articles.

My mindset thus far was: As long as the signal-to-noise ratio (/quality) is high, the more blog posts, i.e. the more we share about our work, the better.

p-shahi · 2023-01-04T19:54:01Z

Steve mentioned that you were working on a general libp2p-in-2022 post. Sorry that I missed that. Any suggestions on how to proceed? I am fine with two separate posts.

Yes I'm working on that.
I think it's fine to have two separate posts as this article is more detailed and I was presenting highlights

Going forward, I think we’ll be better served by writing blog posts about single topics / features, shortly after we ship those, instead of long summary articles.

My mindset thus far was: As long as the signal-to-noise ratio (/quality) is high, the more blog posts, i.e. the more we share about our work, the better.

These posts are retrospectives of what happened in the last year and so I think they're equally valuable as standalone posts for shipped features

p-shahi

A super quick review! Some suggestions are optional (like the new headers with emojis).
Might be a good idea to have @DannyS03 review this as well 🙏

p-shahi · 2023-01-04T20:06:52Z

src/_blog/rust-libp2p-2022.md

+date: 2022-12-30
+permalink: "/2022-12-30-rust-libp2p-in-2022"
+translationKey: ''
+header_image:


I put in a request for a header image: https://www.notion.so/crcle/rust-libp2p-in-2022-blog-header-7a6b7896e0fd4189b4891f3c9a2e713a

src/_blog/rust-libp2p-2022.md

p-shahi · 2023-01-04T20:24:17Z

src/_blog/rust-libp2p-2022.md

+
+The rust-libp2p project has made significant strides in 2022, with numerous technical advancements and improvements to the project itself.
+Let's take a closer look at some of the technical highlights and on the meta level developments of the project itself.
+Note that while I (Max Inden) am writing this blog post, this is the work of many across various organizations.


Suggested change

Note that while I (Max Inden) am writing this blog post, this is the work of many across various organizations.

This is the work of many across various organizations including [Protocol Labs](https://protocol.ai/), [Parity Technologies](https://www.parity.io/), [Sigma Prime](https://sigmaprime.io/), [Iroh](https://iroh.computer/), and [Little Bear Labs](https://littlebearlabs.io/).

Among the three PL steward libp2p projects, I think rust-libp2p is the one that gets most activity/contribution from organizations across the ecosystem. What do you think of highlighting that here?

Added a mention of the organizations and further below is the contributor count. Sounds good?

src/_blog/rust-libp2p-2022.md

Co-authored-by: Prithvi Shahi <50885601+p-shahi@users.noreply.github.com>

mxinden

Appreciate all the help @p-shahi. I addressed all comments.

src/_blog/rust-libp2p-2022.md

mxinden · 2023-01-05T14:35:13Z

src/_blog/rust-libp2p-2022.md

+Over the year we worked on two new transports, namely [WebRTC](https://github.com/libp2p/rust-libp2p/pull/2622) and [QUIC](https://github.com/libp2p/rust-libp2p/issues/2883), which we both released towards the end of the year as alphas.
+
+WebRTC allows browsers to connect to rust-libp2p based servers without those servers having signed TLS certificates.
+QUIC is the better TCP+Noise+Yamux in every dimension, e.g. faster connection establishment, better multiplexing, higher hole punching success rates.


Thanks for rephrasing.

Regarding results on Notion, I think we should treat them as preliminary for now and thus not mention them here.

src/_blog/rust-libp2p-2022.md

p-shahi

Good stuff!
Two things that occurred to me:

I think it's worth mentioning the rust-libp2p Open Maintainers Calls and how many you hosted in the last year.
Adding a generic "Resources/Help Contribute" section at the bottom like https://blog.libp2p.io/2022-12-19-libp2p-webtransport/#resources-and-how-you-can-help-contribute

src/_blog/rust-libp2p-2022.md

elenaf9

Really nice to reflect again on everything the team did in 2022. Thank you for writing this up @mxinden!

src/_blog/rust-libp2p-2022.md

Co-authored-by: Prithvi Shahi <50885601+p-shahi@users.noreply.github.com> Co-authored-by: Elena Frank <elena.frank@protonmail.com>

thomaseizinger

Awesome post @mxinden , thanks for writing this up!

It is great to see all these improvements enumerated.

Also feeling a bit proud to have initiated and pushed for a few things that ended up being mentioned here ☺️

Something I think we can still improve on is cycle time (and as an effect of that, velocity). Reduced CI times and more automation are helping with that already but things like our crate structure, release process and changelog management are still hurting that. I am looking forward to seeing those improved so we can ship more things :)

thomaseizinger · 2023-01-09T05:03:58Z

Tried the one-line-per-sentence markdown formatting here to ease reviews and git diffs. Unfortunately this is not properly rendered by our blog, i.e. the blog interprets a single \n as a newline within a paragraph.

That is a shame. Markdown should not care about single newlines but only start a new paragraph on double newlines ...

mxinden · 2023-01-10T21:19:27Z

Thanks everyone for the help here.

@p-shahi this is ready to go live. Do you mind merging whenever you see fit?

p-shahi · 2023-01-10T21:20:21Z

@mxinden will do, I'm waiting for the blog header from the design team.

BigLep

Great recap. Fun to see it laid out in a consolidation place. Thanks for taking this on.

thomaseizinger · 2023-01-13T03:45:20Z

Tried the one-line-per-sentence markdown formatting here to ease reviews and git diffs. Unfortunately this is not properly rendered by our blog, i.e. the blog interprets a single \n as a newline within a paragraph.

Will keep it as is for now. Will reformat before we merge.

(//CC @thomaseizinger for the idea in general and //CC @elenaf9 given that this is exactly the behavior you predicted in our 1on1.)

The source for this behaviour seems to be this configuration option:

blog/src/.vuepress/config.js

Lines 75 to 77 in 4b7f7d7

    
           md.set({ 
        
             breaks: true, 
        
           })

I submitted a PR to remove this setting: #40

mxinden added 3 commits December 30, 2022 19:17

src/_blog: Add rust-libpp2p in 2022 post

3b5855b

Restructure post

de78517

Fix minor issues

5bac6e2

jxs reviewed Jan 2, 2023

View reviewed changes

src/_blog/rust-libp2p-2022.md Outdated Show resolved Hide resolved

mxinden and others added 2 commits January 2, 2023 15:40

Update src/_blog/rust-libp2p-2022.md

0155945

Co-authored-by: João Oliveira <hello@jxs.pt>

Rephrasing some after chatting with a certain chat

85cf6ce

mxinden marked this pull request as ready for review January 3, 2023 08:32

p-shahi reviewed Jan 4, 2023

View reviewed changes

mxinden and others added 5 commits January 5, 2023 15:17

Apply suggestions from code review

7ff7ce9

Co-authored-by: Prithvi Shahi <50885601+p-shahi@users.noreply.github.com>

Adopt subheading suggestions

672c8a0

Co-authored-by: Prithvi Shahi <50885601+p-shahi@users.noreply.github.com>

Mention of companies

e2b67df

Rephrase QUIC

0c05d91

Mention Thomas and me

0d1d2d0

mxinden commented Jan 5, 2023

View reviewed changes

p-shahi approved these changes Jan 5, 2023

View reviewed changes

src/_blog/rust-libp2p-2022.md Show resolved Hide resolved

p-shahi reviewed Jan 5, 2023

View reviewed changes

src/_blog/rust-libp2p-2022.md Outdated Show resolved Hide resolved

src/_blog/rust-libp2p-2022.md Outdated Show resolved Hide resolved

elenaf9 reviewed Jan 5, 2023

View reviewed changes

mxinden and others added 5 commits January 6, 2023 15:12

Apply suggestions from code review

465c2d0

Co-authored-by: Prithvi Shahi <50885601+p-shahi@users.noreply.github.com> Co-authored-by: Elena Frank <elena.frank@protonmail.com>

Mention removal of listener streams

1f92e80

Remove dead link around Rust language

06f8c7b

Update contributor number and link to GitHub

7bef7cd

Move coding guideline to housekeeping

80a1e83

thomaseizinger approved these changes Jan 9, 2023

View reviewed changes

Format to one line per paragraph

6cb3e00

BigLep approved these changes Jan 11, 2023

View reviewed changes

add blog header and update date

f8cc9c1

p-shahi merged commit 4b7f7d7 into libp2p:main Jan 12, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

src/_blog: Add rust-libpp2p in 2022 post #26

src/_blog: Add rust-libpp2p in 2022 post #26

mxinden commented Dec 30, 2022 •

edited

mxinden commented Jan 4, 2023

mxinden commented Jan 4, 2023

marten-seemann commented Jan 4, 2023 •

edited

mxinden commented Jan 4, 2023

p-shahi commented Jan 4, 2023

p-shahi left a comment •

edited

p-shahi Jan 4, 2023

p-shahi Jan 4, 2023

mxinden Jan 6, 2023

mxinden left a comment

mxinden Jan 5, 2023

p-shahi left a comment

elenaf9 left a comment

thomaseizinger left a comment

thomaseizinger commented Jan 9, 2023

mxinden commented Jan 10, 2023

p-shahi commented Jan 10, 2023

BigLep left a comment

thomaseizinger commented Jan 13, 2023

	Note that while I (Max Inden) am writing this blog post, this is the work of many across various organizations.
	This is the work of many across various organizations including [Protocol Labs](https://protocol.ai/), [Parity Technologies](https://www.parity.io/), [Sigma Prime](https://sigmaprime.io/), [Iroh](https://iroh.computer/), and [Little Bear Labs](https://littlebearlabs.io/).

src/_blog: Add rust-libpp2p in 2022 post #26

src/_blog: Add rust-libpp2p in 2022 post #26

Conversation

mxinden commented Dec 30, 2022 • edited

mxinden commented Jan 4, 2023

mxinden commented Jan 4, 2023

marten-seemann commented Jan 4, 2023 • edited

mxinden commented Jan 4, 2023

p-shahi commented Jan 4, 2023

p-shahi left a comment • edited

Choose a reason for hiding this comment

p-shahi Jan 4, 2023

Choose a reason for hiding this comment

p-shahi Jan 4, 2023

Choose a reason for hiding this comment

mxinden Jan 6, 2023

Choose a reason for hiding this comment

mxinden left a comment

Choose a reason for hiding this comment

mxinden Jan 5, 2023

Choose a reason for hiding this comment

p-shahi left a comment

Choose a reason for hiding this comment

elenaf9 left a comment

Choose a reason for hiding this comment

thomaseizinger left a comment

Choose a reason for hiding this comment

thomaseizinger commented Jan 9, 2023

mxinden commented Jan 10, 2023

p-shahi commented Jan 10, 2023

BigLep left a comment

Choose a reason for hiding this comment

thomaseizinger commented Jan 13, 2023

mxinden commented Dec 30, 2022 •

edited

marten-seemann commented Jan 4, 2023 •

edited

p-shahi left a comment •

edited