I work for IPinfo. We really would appreciate more constructive feedback on how to present data driven stories that is approachable to everyone.
> I stopped reading after the first graphic.
Now, let's see what we had before the first graphic.
1st Paragraph: Explains what BGP is.
2nd Paragraph: Tells a story about the Pakistani ASN accidental BGP hijack. A story which is known in the network engineering community, but not by most people.
3rd Paragraph: Introduces RPKI.
4th Paragraph: Summary states that builds the foundation of the article.
Then the first graphic shows the RPKI validation. That is all.
How would you structure the blog post about RPKI adoption, which is a data-driven technical story? I am not absolutely trying to be demeaning, but would you rather start from what BGP, RPKI, and those things are?
Then we have a series of community post around them:
> I stopped reading after the first graphic.
Now, let's see what we had before the first graphic.
1st Paragraph: Explains what BGP is.
2nd Paragraph: Tells a story about the Pakistani ASN accidental BGP hijack. A story which is known in the network engineering community, but not by most people.
3rd Paragraph: Introduces RPKI.
4th Paragraph: Summary states that builds the foundation of the article.
Then the first graphic shows the RPKI validation. That is all.
How would you structure the blog post about RPKI adoption, which is a data-driven technical story? I am not absolutely trying to be demeaning, but would you rather start from what BGP, RPKI, and those things are?
Then we have a series of community post around them:
- https://shubhamjain.neocities.org/bgp-explainer (HIGHLY RECOMMENDED)
- https://community.ipinfo.io/t/internet-from-scratch-in-10-sl...
- https://community.ipinfo.io/t/how-your-internet-traffic-actu...
- https://community.ipinfo.io/t/understanding-an-asn-page-peer...