Explainer · suggestion
What is HTTP/2, and why is everyone looking it up this week?
Hook: HTTP/2 is getting attention. Explain what changed and who should care, in plain words.
Based on: Wikipedia views up 1.5× against its 4-week median.
Developer Tools & Programming · first detected 21 Aug 2026 · scored 15 Nov 2026 ·
Attention data: Wikipedia pageviews via the Wikimedia Analytics API · News data: GDELT Project · Research data: arXiv (thank you to arXiv for use of its open access interoperability) · Community data: Hacker News (Y Combinator) official API · Headlines: niche publications via their public feeds (headline, date and link only) · Developer activity: GitHub API · Community data: Hacker News Search by Algolia · Q&A data: Stack Overflow (Stack Exchange Network), CC BY-SA · Social data: Bluesky (AT Protocol) post counts · Research data: OpenAlex (CC0)
Attention is above its usual level, and the topic is moderately covered: a good time to make something about it.
Trend
63/100Above usual
Attention is above its usual level.
Opportunity
26/100Good
Worth a look: steady or growing, with room left.
Confidence
91%High
Several sources and a long history back this score.
Trend, 30 days
| Component | Value | Weight | Points |
|---|---|---|---|
| Attention growth | 64% | 0.41 | +26.4 |
| Coverage growth | 0% | 0.00 | +0.0 |
| Cross-source breadth | 50% | 0.12 | +5.9 |
| Acceleration | 82% | 0.18 | +14.4 |
| Audience size | 68% | 0.29 | +20.1 |
| Saturation (subtracted) | 40% | 0.10 | −4.0 |
| Trend score (0–100) | 62.9 |
Opportunity = trend 62.9 × (1 − ½ × saturation 40%) × stage weight 0.8 × (½ + ½ × niche relevance 0.8) = 26.0
Saturation parts: volume 68%, time elevated 18%, mainstream 0%. Spike ratio = mean of the last 3 days ÷ median of days 4–31. Growth parts are centred: 50% means at the usual level. A source counts as spiking at ≥ 1.5× and robust z ≥ 2.
| Source | Spike | Robust z | Week over week | Spiking |
|---|---|---|---|---|
| rss | 0.00× | 0.0 | 0% | no |
| arxiv | 0.00× | 0.0 | 0% | no |
| gdelt | 0.00× | 0.0 | 0% | no |
| wikipedia | 1.49× | 1.1 | 55% | no |
| hacker news | 0.00× | 0.0 | 0% | no |
Full method: methodology. Rising means rising now; it is not a prediction that a topic will go viral.
Wikipedia views
262/day
last 3 days on average · usual 177 · latest day 160
2026-10-17 → 2026-11-15 · fetched 16 Nov, 13:08 UTC
Bluesky posts
2/day
latest day
2026-10-18 → 2026-11-15 · fetched 16 Nov, 13:27 UTC · not used in today's score
GitHub stars
0/day
latest day
2026-10-21 → 2026-11-15 · fetched 16 Nov, 13:17 UTC · not used in today's score
Hacker News stories
0/day
latest day
2026-10-17 → 2026-11-15 · fetched 16 Nov, 13:20 UTC · not used in today's score
Hacker News stories (live feed)
0/day
latest day
2026-10-19 → 2026-11-15 · fetched 15 Nov, 12:31 UTC
New arXiv papers
0/day
latest day
2026-10-19 → 2026-11-15 · fetched 16 Nov, 13:13 UTC
New research works
0/day
latest day
2026-10-19 → 2026-11-15 · fetched 15 Nov, 12:29 UTC · not used in today's score
News coverage
0/day
latest day
2026-10-19 → 2026-11-15 · fetched 16 Nov, 13:30 UTC
Niche headlines
0/day
latest day
2026-10-18 → 2026-11-15 · fetched 15 Nov, 12:31 UTC
Stack Overflow questions
0/day
latest day
2026-10-21 → 2026-11-15 · fetched 16 Nov, 13:31 UTC · not used in today's score
Attention data: Wikipedia pageviews via the Wikimedia Analytics API · News data: GDELT Project · Research data: arXiv (thank you to arXiv for use of its open access interoperability) · Community data: Hacker News (Y Combinator) official API · Headlines: niche publications via their public feeds (headline, date and link only) · Developer activity: GitHub API · Community data: Hacker News Search by Algolia · Q&A data: Stack Overflow (Stack Exchange Network), CC BY-SA · Social data: Bluesky (AT Protocol) post counts · Research data: OpenAlex (CC0) · Data as of 16 Nov, 13:31 UTC
Observed (measured data)
Interpretation (our reading, not a fact)
No source shows a sharp jump: the score comes from attention that is high or building gradually, not from a sudden spike.
Latest headline: “erizeta/qinetic: Expressive web framework for Go with routing, middleware, and native HTTP/1.1, HTTP/2, and…” (GitHub, 2 Nov). It gives context; the numbers show attention, not its cause.
Written from the measured data and headlines on this page (scored 15 Nov 2026).
Each headline opens the original article on the publisher's site. We show headlines and links only and never republish article text.
Check what people are posting about “HTTP/2” right now on Reddit and YouTube. Opens their sites; we don't collect their data.
Suggestions written from the signals on this page, not advice and not a forecast.
Explainer · suggestion
Hook: HTTP/2 is getting attention. Explain what changed and who should care, in plain words.
Based on: Wikipedia views up 1.5× against its 4-week median.
Comparison · suggestion
Hook: Both are protocols people compare; HTTP/2 is the one gaining attention. Test them on the same task.
Based on: Vulkan is the strongest other protocol of its kind on this radar today. Wikipedia views up 1.5× against its 4-week median.
Tutorial · suggestion
Hook: What the spec looks like in practice: one client, one server, one working call.
Based on: Wikipedia views up 1.5× against its 4-week median.
Angle 1 · short video
Hook: GitHub just published “erizeta/qinetic: Expressive web framework for Go with routing, middleware, and native HTTP/1.1, HTTP/2, and…”. Here's where I agree, and where I don't.
Copy the chart above as a PNG, share the link (it comes with a trend card), or embed a live widget that updates with every data refresh.
Wikipedia views up 1.5× against its 4-week median
Passes the rising rules: Wikipedia views at 11× its 4-week median, 2× or more on each of the last 3 days
Wikipedia views up 4.4× against its 4-week median
Wikipedia views up 7.6× against its 4-week median
Wikipedia views up 2.5× against its 4-week median
Wikipedia views up 1.9× against its 4-week median