absorb.md

Hourly Poll / X Feed

The Hourly Poll / X Feed is absorb.md's internal real-time ingestion pipeline that monitors X accounts of ~286 AI and technology experts as one of 13 data sources feeding its knowledge graph. LLM processes generate paragraph syntheses, structured claims (with evidence and high/medium/low confidence scores), and counter-arguments, often from very short posts, emojis, replies, or the monitoring notes labeled 'Hourly poll: [Expert] X feed' themselves. As of April 2026 this has produced thousands of database entries, expert timelines, and topical collections, but new examples underscore frequent low-substance outputs, self-referential feedback loops when experts reply to poll notes, unreliable tone/sentiment inference, and broader risks of viewpoint bias and echo chambers in social-media-derived graphs.

# Hourly Poll / X Feed

Overview

The Hourly Poll / X Feed refers to absorb.md's mechanism for ingesting and structuring data from X posts of approximately 286 selected AI and technology experts. It is one component of a 13-source knowledge graph pipeline that also draws from arXiv, YouTube, podcasts, GitHub, and others. [web:6] Repetitive user notes or metadata labeled 'Hourly poll: [Expert] X feed' appear to function primarily as internal triggers or tags for LLM-driven processing rather than evidence of literal public hourly polling. Outputs include syntheses, bullet-point claims with evidence and confidence ratings, counter-arguments, and updates to per-expert timelines and topical wikis. By April 2026 the system had generated thousands of structured entries. [1][2][3][4][5][6][7][8][9][10][11][12][web:0][web:5]

New April 2026 examples frequently derive from minimal or self-referential content: Josh Woodward's 'Native is the way to go! :)' [1], a single emoji from Garry Tan with no extractable insights [2], Ethan Mollick's 'Exponentials everywhere.' [3], a placeholder note for Tobi Lütke [4], Aaron Levie's direct reply to a poll note denying facetiousness about podcast tweets ('yeah no I wasn’t being facetious 😂 I don’t comprehend the tweets I’m seeing about the podcast') [5], John Carmack's conditional interest in AI hardware ('If there was a good plan, I would probably be interested in helping') [6], a Scoble post sharing a Grok response that 'mostly agrees' with feed analysis [7], Swyx monitoring note tagged ':hugops:' [8], Balaji Srinivasan promoting a new 'Monitoring the Situation' stream with Torenberg and Jaffee [9], Gabe Rivera suspecting Zatz of pushing copyright boundaries [10], a caution note on Embiricos' feed ('yes—use with caution') [11], and Garry Tan stating he is 'still just using Opus 4.6 with API Key' [12]. These reinforce patterns seen in prior examples (e.g. 'Nice.', 'I am!', 'Wdym?'). [1-12][web:0][web:1]

Methodology (Modality Axis)

The modality emphasizes real-time social media (X) as a high-frequency, low-context source contrasted with slower, higher-depth modalities like arXiv papers or podcasts. The pipeline selects expert accounts and applies LLM inference to recent activity or attached notes. The 'hourly poll' label serves as metadata or trigger. Outputs assign direct quotes, sentiment interpretations, and structured claims, often with 'high' confidence even for casual or ambiguous inputs. External literature on LLM-augmented knowledge graphs notes risks of propagating training-data biases, amplifying high-engagement/low-substance social content, and creating echo chambers. [web:17][web:21][web:22][web:25]

Self-referential loops occur when monitored experts reply directly to absorb.md poll notes about their own feeds (observed with Levie [5], Scoble [7], and prior cases). Sentiment inference from emojis (e.g. ':)', '😂') or one-word replies remains unreliable without full thread context. [5][7][8][11][web:20]

Applications

Outputs populate per-expert timelines (e.g. for Carmack, Levie, Mollick, Scoble, Balaji, Garry Tan), topical collections (native vs. cross-platform development preferences [1], exponential trends [3], AI hardware interest [6], model usage like Opus 4.6 [12], cryptocurrency views, podcast discourse, copyright concerns [10], and feed reliability advisories [11]), and a database of claim-evidence pairs. Concrete deliverables include synthesized wiki entries, structured claims fed into the graph, updated person profiles, and agent-queryable knowledge. The system surfaces casual expert discourse and real-time signals effectively but at the cost of depth and verifiability. [1][3][5][6][7][9][10][11][12][web:6][web:7][web:10]

Challenges and Counter-Arguments

Most claims rest on limited evidence (single replies, emojis, placeholders, or the poll notes themselves). The 'hourly' descriptor lacks independent verification via timestamps, API logs, or public code and likely represents an internal monitoring template rather than systematic expert-conducted polls. [2][4][8][11] Many syntheses assign 'high' confidence to interpretations of minimal text, creating over-extrapolation risks. Examples include deducing 'native development is the superior approach' from a casual quote with smiley [1], 'exponential growth is ubiquitous' from two words [3], strong sentiment on TPUs or models from isolated statements, or precise implications from ambiguous emoji use. [1][3][12]

Counter-arguments (drawn from provided syntheses and broader literature): Superiority of native development is not absolute and depends on project constraints, team skills, and tradeoffs with cross-platform tools like React Native or Flutter; a single casual quote provides no benchmarks. [counter:1] Exponential growth is not ubiquitous—most systems follow logistic, power-law, or bounded patterns with saturation effects; selection bias highlights prominent cases while ignoring the norm. [counter:2] Emoji and short replies are ambiguous (😂 may signal sarcasm, irony, or politeness rather than clear lighthearted confirmation or confusion). [5][counter:3 to counter:6] 'User notes' may reflect external monitoring/bot activity rather than expert intent or self-polling. [4][8][11] Self-referential loops risk distorting the graph over time by incorporating responses to the monitoring apparatus itself. [5][7]

Account selection skews toward Silicon Valley AI influencers, VCs, and founders, introducing viewpoint and echo-chamber bias despite some diversity; similar X-synthesis approaches amplify shallow discourse and misinformation risks. [web:21][web:25] LLM synthesis of social media can propagate social biases, hallucinate subtle factual errors in long-form structuring, and create self-reinforcing feedback. [web:17][web:20][web:22] The platform's own outputs and documentation surface many of these limitations. Substantive counter-arguments exist for nearly all interpretive claims due to shallow evidence. No consensus exists on mitigating these issues in dynamic social-derived knowledge graphs.

Existing and merged key claims appear below with updated confidences based on cross-verification across internal examples and external critiques.

Numbered to match inline [N] citations in the article above. Click any [N] to jump to its source.

  1. [1]Josh Woodward Advocates Native Development Approachtweet · 2026-04-18
  2. [2]Insufficient Content for Knowledge Extractiontweet · 2026-04-07
  3. [3]Exponential Growth: A Pervasive Phenomenontweet · 2026-04-08
  4. [4]Tobi Lütke X Feed Analysis (Poll)tweet · 2026-04-08
  5. [5]Aaron Levie Confirms Genuine Confusion Over Podcast Tweetstweet · 2026-04-20
  6. [6]Carmack Signals Openness to Joining Viable AI Hardware Venturestweet · 2026-04-20
  7. [7]Grok's Shared Response Shows Strong Agreement with Scoble's X Feed Analysistweet · 2026-04-23
  8. [8]Swyx's X Feed Tracked via Hourly User-Initiated Pollstweet · 2026-04-20
  9. [9]Balaji Srinivasan Launches "Monitoring the Situation" Stream with Torenberg and Jaffeetweet · 2026-04-20
  10. [10]Gabe Rivera Suspects Zatz Breaching Copyright Boundariestweet · 2026-04-20
  11. [11]Caution Advised for Embiricos' X Feed Contenttweet · 2026-04-20
  12. [12]Garry Tan Persists with Opus 4.6 via API Key in 2025tweet · 2026-04-13
  13. [13]https://absorb.md/wiki/hourly-poll-x-feedweb
  14. [14]https://absorb.md/web
  15. [15]https://arxiv.org/html/2504.00310v1web
  16. [16]https://www.nature.com/articles/s41599-024-03407-5web
  17. [17]https://arxiv.org/html/2402.05880v2web
  18. [18]https://x.com/joshwoodward/status/2044621702823657813X / Twitter
  19. [19]https://x.com/garrytan/status/2041653195475448230X / Twitter
  20. [20]https://x.com/emollick/status/2041723225827062080X / Twitter
  21. [21]https://x.com/levie/status/2044907509685878870X / Twitter
  22. [22]https://x.com/ID_AA_Carmack/status/2044800325828083719X / Twitter
  23. [23]https://x.com/Scobleizer/status/2047196698066534524X / Twitter
  24. [24]https://x.com/swyx/status/2046030085237432573X / Twitter
  25. [25]https://x.com/balajis/status/2046270592589148170X / Twitter