Closed p-shahi closed 1 year ago
What are folks thoughts on the article length? It runs a bit long given that there's a lot to cover, I think I will try to make it more concise. Raul suggested that we might split this apart into multiple posts, my preference is to keep it as one but trim it a bit. Wdyt?
Do people like the screenshots of GitHub issues and pull requests? They're a bit large right now, but I can scale them down.
The article ends a bit abruptly so I'll work on the conclusion and add a section with links to resources as well
What are folks thoughts on the article length? It runs a bit long given that there's a lot to cover, I think I will try to make it more concise. Raul suggested that we might split this apart into multiple posts, my preference is to keep it as one but trim it a bit. Wdyt?
Do people like the screenshots of GitHub issues and pull requests? They're a bit large right now, but I can scale them down.
The article ends a bit abruptly so I'll work on the conclusion and add a section with links to resources as well
Splitting into multiple posts is a good option. Also, this could very well be a series (or turn into a series), calling it something simple like "Ethereum and libp2p".
One of many ways to split:
Splitting into multiple posts is a good option. Also, this could very well be a series (or turn into a series), calling it something simple like "Ethereum and libp2p".
One of many ways to split:
* The first post could present the story and timeline, something along the lines of "Ethereum and libp2p: Ethereum's Journey Toward libp2p Adoption", ":A Retrospective on the Journey to Integration", etc. * Followed by a second post about the merge "Ethereum and libp2p: Together at Last", ":Ethereum Embraces libp2p", etc. * The optional section that compares libp2p and devp2p could turn into it's own post.
So my main concern about splitting it into multiple articles is that we'll lose traffic. The benefit of one article is that though it may be lengthy it can be shared/referenced more easily (easier to direct folks to one place than many.) If people feel strongly about this then I'm happy to do it
Images automagically compressed by Calibre's image-actions ✨
Compression reduced images by 31.7%, saving 238.09 KB.
Filename | Before | After | Improvement | Visual comparison |
---|---|---|---|---|
src/assets/eth-libp2p-2016.png |
197.35 KB | 135.98 KB | -31.1% | View diff |
src/assets/eth-libp2p-2018-1.png |
106.46 KB | 72.09 KB | -32.3% | View diff |
src/assets/eth-libp2p-2018-2.png |
95.33 KB | 64.83 KB | -32.0% | View diff |
src/assets/eth-libp2p-2018-3.png |
154.74 KB | 103.88 KB | -32.9% | View diff |
src/assets/eth-libp2p-2020-1.png |
115.43 KB | 75.62 KB | -34.5% | View diff |
src/assets/eth-libp2p-beacon-nodes.png |
81.57 KB | 60.37 KB | -26.0% | View diff |
36 images did not require optimisation.
Images automagically compressed by Calibre's image-actions ✨
Compression reduced images by 14.5%, saving 8.43 KB.
Filename | Before | After | Improvement | Visual comparison |
---|---|---|---|---|
src/assets/eth-libp2p-client-diversity.png |
58.16 KB | 49.73 KB | -14.5% | View diff |
42 images did not require optimisation.
Blog post about the libp2p efforts to integrate with Ethereum