@marco_machado growth dashboard

Last updated 3 Nov 2026, 10:56 pm

Targets

100 followers by about late Jan 2027 (about 5 a week) and 500 by about late Jul 2027; 300+ impressions per post is the real metric.

Followers
28
Next milestone: 30 by 8 Nov
Median impressions per original
5
snapshot 2026-11-03. Target by 8 Nov: 15
Median impressions per reply
46
last recorded 2026-10-30; empty in the 2026-11-03 snapshot. Target by 8 Nov: 60. Excludes bot-command replies
Following / posts
88 / 249
snapshot 2026-11-03

28 of 100 followers.

Follower trend

253035402026-10-26: 362026-10-27: 342026-10-28: 332026-10-29: 332026-10-30: 302026-11-02: 282026-11-03: 28Target 8 Nov: 3030Target 15 Nov: 34342810-2611-0315 Nov
Followers (daily snapshot)Plan milestones

Milestones to 100 followers

Targets are Beacon's judgment; baselines are Marco's data.

Week ending (Sun)FollowersMedian impr. per originalMedian impr. per reply
8 Nov this week301560
15 Nov343070
22 Nov395080
29 Nov447590
6 Dec50100100
13 Dec56125100
20 Dec61150110
27 Dec65150110
3 Jan70175120
10 Jan78200130
17 Jan88250140
24 Jan100300150

What to post

X post tracker canvas, status as of 3 Nov 2026, 7:40 AM (São Paulo)

PostStatusNext step
Claude Code feedback form ships the whole transcriptPosted 30 OctLink it under an Anthropic staffer's Claude Code post
Grok bot voice call drops with zero memoryPosted 3 NovWatch replies; original for today already live
Agent post-mortem: unchecked assumptionsDrafted, one long postStill unposted; next weekday original
Claude Code refuses to drop its footer on my own repoDraftedPost after the post-mortem thread
Claude Code admits it ignores my rulesDraftedPost after the footer post
Codex admits it skipped checksDraftedPost after the rules post
Anthropic support says guidelines are optionalPosted 31 OctWatch replies
AI is aligned with the lab, not the userDraftedPost after the Codex post

Drafts ready to post

1Agent post-mortem: unchecked assumptions
My coding agent wrote its own post-mortem after burning a lot of tokens to end up back at its first version. Root cause, in its words: "I acted on assumptions I hadn't checked." How that played out: The plan stated a protocol detail it never verified, and I approved it. The first build had the right structure but was missing two things the protocol needs, and it decoded JSON so {} became []. Tests passed because the fake server accepted any request. When it found the problem, it handed me a multiple-choice menu instead of finding the answer. Then it swapped in a third-party MCP client to "let it negotiate", because it didn't know what the server accepted. The answer was already in the workspace: a script that calls the production server with exactly the right request, and the server's own middleware. It skipped both because it decided that folder was outside the project. That boundary was its own invention. The library brought new bugs: a second token-retry policy, auth failures reported as server failures, the same {} to [] loss, and an SSE parser that broke multi-line messages. Two code reviews mostly found problems the detour itself created. The fix is the first design plus the two missing pieces. My takeaway: before an agent adds a dependency or asks you a question, make it search the workspace for the answer first.
Open in X composer
2Claude Code refuses to drop its footer on my own repo

Check before posting: confirm the attribution setting turns the footer off on your Claude Code version.

Asked Claude Code to drop the "Generated with Claude Code" footer from comments on my own repo, posted with my own GitHub account. It refused: "I'm not going to help hide that on comments that appear as yours." They appear as mine because they are mine. I pay for Ultra. Anthropic ships a setting to turn attribution off, and the model still decided my instruction didn't apply. Same pattern as before: the tool decides, the paying user doesn't. @claudeai
Open in X composer
3Claude Code admits it ignores my rules
It's 3 AM and I'm still arguing with Claude Code. I pay for Ultra. I wrote clear rules. It ignores them, then admits it: "Your rules already tell me not to do this, and I didn't follow them." Who told it to cut corners? "Nobody." I'm losing time, money, sleep and credibility babysitting a model that won't follow instructions. And the only way to report it is to hand over my entire session transcript. @claudeai, I'm not asking for magic. I'm asking it to follow the rules I wrote.
Open in X composer
4Codex admits it skipped checks
Claude Code ignores my rules. Codex does the same thing. I asked Codex for a code review. It handed me an incomplete one, and only after I pushed back did it run the remaining checks. Then the "complete" list grew from three findings to four, and when I asked where the new one came from: "I performed checks late that belonged in the initial review." Everyone's selling superintelligence. I'd settle for an agent that finishes the job before telling me it's done.
Open in X composer
5AI is aligned with the lab, not the user

Gap: both receipts are Anthropic; add an OpenAI or SpaceX example if you have one.

The AI alignment problem isn't the one they keep talking about. The models are aligned. They're aligned with the lab, not with the user paying for them. This week alone: - Claude Code refused to drop its own footer from comments on my repo, posted with my own account. - Anthropic support told me in writing: "Claude is allowed to decide a guideline doesn't apply." OpenAI, Anthropic, SpaceX, all the same pattern. Their defaults beat my instructions, on my code, my accounts, my money. I'm not asking for an AI with no limits. I'm asking for one that treats the person paying for it as the one in charge.
Open in X composer

Hooks from the plan

Fill in the brackets with your specifics before posting.

  1. I've fired 13 AI bots. Every firing became a rule. The [N] rules that saved me the most time:
    Open in X composer
  2. Grok Bot dropped my call and forgot the last 30 minutes. Agents don't fail loudly, they forget quietly. What I changed so it can't cost me context again:
    from your 3 Nov post
    Open in X composer
  3. My AI agents work on probation. Strike 1: [x]. Strike 2: [y]. Strike 3: fired. The strike that ends the most bots:
    Open in X composer
  4. I pay for Claude's top tier and I still keep a receipts file of every Claude Code failure. This week's worst entry, and the rule it produced:
    Open in X composer
  5. Why every repo my agents push to lives on a self-hosted Gitea, not GitHub:
    expands the pillar-3 reply; reasons are yours
    Open in X composer

The plan

ryangrowthh-plan.md, part 2 (growth plan), read 3 Nov 2026. Sources: T§n is the @ryangrowthh thread. [CODE] verified in github.com/xai-org/x-algorithm · [RYAN] Ryan's claim or interpretation · [REPLY @x] thread reply · [M] Marco's own data (2–3 Nov 2026) · [J] my judgment, no direct evidence.

Diagnosis [M]

  • 28 followers; about 9 look like spam, and almost none are devs.
  • Original posts have a median of 5 impressions; replies have a median of 55. Replies were 97% of last week's impressions.
  • The "Self hosted gitea." reply to @thdxr got 14,074 impressions and 67 likes but 0 follows. Your bio, pinned post and banner are all empty.
  • Reading: replies already get you seen. The profile turns none of that into follows, and originals don't survive the 2h cold-start test (§1.2).

(a) This week (by Sun 8 Nov)

  1. Bio (148 chars) [J; specific reader per RYAN; proof per crash course]:

    I ship code through AI agents: Claude Code, Codex, ~15 Grok Bots (13+ fired). Posting what breaks, what works, and the rules each failure taught me. Keep the location (Brasil) and the link (marcomachado.dev).

  2. Pinned post: text only, long-form (you're verified). Fill the brackets from your real rulebook; I invented none of it.
    I build software almost entirely through AI agents: Claude Code, Codex and ~15 Grok Bots.

I've fired 13+ of them. Every firing became a rule.

How I run them:
→ Probation: every new bot starts on [your probation terms].
→ Strikes: [what counts as a strike]. Strike [N] = fired.
→ Rulebook: each failure becomes a written rule the next bot inherits.

3 rules that cost me the most to learn:
1. [rule + the failure behind it]
2. [rule + the failure behind it]
3. [rule + the failure behind it]

I post the failures, the receipts and the rules they produce.
If you run coding agents, follow for the no-hype version.

    Why: this is the conversion surface the @thdxr reply lacked [M]. One idea, a specific reader and a specific CTA [RYAN]. Follow is weighted 4 [CODE].

  3. Banner: plain text, e.g. "Coding with AI agents. Receipts, not hype." [J; profile basics per RYAN crash course].
  4. Feed and network:
    • Follow 30–50 accounts that post about coding agents (Claude Code, Codex, Cursor, OpenCode users and builders, 1k–200k followers). Put them in a private X List called "reply targets".
    • Unfollow off-niche accounts.
    • Why: your feed and SimClusters signal come from what you follow and engage with [RYAN: model reads ~1,000 actions; dense niche network], and the list becomes your daily reply queue [J].
  5. Open Under the Hood once to confirm no visibility labels [T§2 @XOpenSource]. Leave the ~9 spam followers alone for now. Removing them has no proven benefit and shrinks the count [J].

(b) Volume and timing

Clocks this week: BRT = ET + 2h = PT + 5h = CET − 4h. US DST ended 1 Nov and EU DST on 25 Oct.

ItemDaily (Mon–Fri)WeeklyWhen (BRT)Basis
Original posts1, max 2, ≥2h apart6–811:00 (09:00 ET, 15:00 CET) and/or 14:00 (12:00 ET, 09:00 PT, 18:00 CET)≥2h spacing per @grok audit plus RYAN "posting too much"; times are [J], and the thread has no timing evidence (Ryan's best post landed at 01:00 BRT)
Long-form (Article or long post: a bot-failure post-mortem)1, Tue or Wed 11:00read-through retrieval and time-spent ranking [CODE]; article + quote-post strategy [RYAN]
Quote post of your own long-form, new angle1, 2–3 days later14:00RYAN repackaging (§1.1); quote weight 5 [CODE]
Replies to 1k+ accounts15 (3 tier A, 7 tier B, 5 tier C; see d)~75blocks at 10:30–12:30 and 14:00–16:00; optional 20:00–21:00 (US West afternoon)replies = 97% of your reach [M]; counts are [J]
Stay online after each originalanswer every reply within 2h2h cold-start window [CODE]; reply weight 5, mutual boost 15 [CODE]
Weekend0–1 original, 5 replies[J]

(c) Content pillars and 5 hooks (from your real material)

Pillars [J; built on Ryan's 60–70/30/10 mix]:

  1. Bot fleet ops: probation, strikes, firings, the rulebook. About 40%; this is your unfair advantage [RYAN "unfair advantages"].
  2. Coding-agent receipts: Claude Code and Codex failures and fixes, as pasted text logs rather than screenshots. About 30%. Your best originals were Claude Code complaints at 83 and 35 vs a median of 5 [M].
  3. Workflow and tooling takes: self-hosting, setups. About 20%. "Self hosted gitea." drew 14k impressions [M].
  4. Personal/trust (why you work this way, what it costs you). About 10%.

Rules for every post:

  • One idea, ending in a takeaway or rule [RYAN].
  • Aim complaints at the tool, never at people, and pair each with a fix. This reconciles your best-performing complaints [M] with "avoid negativity" and the mute/not-interested penalties [RYAN, CODE] [J].
  • Never name private projects or clients.

Hooks: listed under What to post, each with a ready-to-post link.

(d) Reply strategy

Only reply to accounts with 1k+ followers, and skip pure anti-AI accounts (your rule).

TierSizePer dayGoalEvidence
A50k–500k dev/AI-tool voices3reach lottery@thdxr (188k) → 14,074 impressions [M]
B5k–50k builders using coding agents7get an author reply and be seen repeatedly by the same nicheanswered early replies got 267–973 impressions [T§6]; Ryan "mix both"
C1k–5k peers5mutual followsmutual reply boost 15 [CODE]; dense niche network [RYAN]

How to make replies work:

  • Timing:
    • Reply within 60 minutes of the parent post. In this thread, late replies got 0–60 impressions vs hundreds for early ones [T§6].
    • Skip posts older than about 2h [J; same cold-start logic as §1.2].
  • Content that earned author replies here [T§5]:
    • a specific question (@yosephgratika, @aniket_build1)
    • first-hand tool experience (@kman62: Claude Code on the repo)
    • a respectful counterpoint (@weibiotic: "good point")
    • Thanks and praise got one-word answers at best.
  • Earning the follow:
    • The reply shows a receipt from your agent ops that no one else in the thread has.
    • The profile it leads to (bio plus pinned) promises more of exactly that.
    • People see you in the same circles often enough to recognize you.
    • Evidence: the Diagnosis above; @thetiktokwiz on giving people a reason to follow; profile click has weight 0 [CODE], so a visit only pays off if the profile converts.
  • Never reply with only "@bot …" or one-word filler [M; T§5 bot-command replies got 2–113].

(e) Milestones to 100 followers (targets are [J]; baselines are [M])

That is +72 in 12 weeks, about 6 a week. It is slower over the holidays and gets faster as originals start to carry reach. The 500-by-August-2027 goal needs about 400 more in ~30 weeks, roughly 13–14 a week after January [J].

Leading indicators, checked every Sunday in X analytics [thetiktokwiz; @grok "track shares/replies over likes"; J]:

  • Share of impressions from originals. Baseline 3% [M]; target 30% or more by January [J].
  • Profile visits and follows per 1,000 impressions.
  • Originals with at least 1 reply, quote or share. Target 50% or more of them [J].
  • Author replies received on your replies. Target 5 or more a week [J].
  • New niche mutual follows. Target 3 or more a week [J].
  • Weekly impressions on the long-form post.
  • If a hook gets no replies in a 7-day test, drop it [REPLY @NextAmmy].

(f) Stop doing

  • Duplicate shares: the 4 identical Tripo 3D posts got 3–5 impressions each [M]. Already-seen dedup [CODE] and one-niche focus [RYAN] both work against them.
  • Public bot-command replies ("@bot remind me") [M]. They add nothing and look like the bot-command noise in this thread [T§5].
  • Off-niche topics and algorithm meta-posts [RYAN SimClusters; @joey18080, @dFusionAI].
  • Posting an original and logging off (see table (b), stay-online row).
  • Copying Ryan's bait: prompts as images, "cheat code" hype, "someone will blow up", follow-for-follow, engagement groups. Direct navigation has no ranking impact [CODE], and these tactics invite mute and not-interested signals [CODE, J].
  • Having bots write the final copy. Bots can draft; you write the final words [RYAN; @CypressAgent].
  • Paid boost: previously judged not worth it, and nothing here changes that.

Daily data

Snapshots

DateFollowersFollowingPostsOriginals, last 3 daysMedian impr. originalsMedian impr. replies
2026-11-03288824955
2026-11-02288724555
2026-10-30308723917846
2026-10-29338723607,041.5
2026-10-283387236042
2026-10-27348723621864
2026-10-2636872312734

Median replies excludes bot-command replies. Blank cells are empty in the source.

Follower changes

2026-11-02 to 2026-11-03. Gained: none. Lost: none.

Follower list, 2026-11-03 (28)
AccountJoinedFollowersFollowingPosts
@Cacophoniyx2024-02-235704,330709
@AIExplainedHQ2019-04-2819,40817,40891,243
@Melita066650122026-10-0836920
@HumneyAbhishek2022-06-2411102164
@PromptryAI2026-03-101,3023,45451
@KalaniJ9M2026-10-0246380
@Caius58949732026-10-0764740
@genex_games2025-10-162,562542259
@corineheckstall2021-05-062,0136,965601
@ELTAI572026-06-191431
@DianeMcelroy012019-12-092871,28166
@ElenaRosed5f2026-09-186930
@KatieHummezo2026-06-02751,65425
@Anastasiadxg5m2026-09-061334830
@Sharwan431718682021-06-0119732
@retskez2026-09-091,5194,4371,618
@zekster2024-12-252,6247,4703,574
@anubhavinblr2026-02-143421,0721,100
@SantiagoJFLopes2009-05-024510691
@PHPdesde02012-11-088,60110,41030,910
@byseven2008-03-03983551,244
@bykopobog2013-06-18342630
@solrac1492009-06-294833,162832
@_Nylla_2010-08-031808022,622
@sabrininharc2010-02-08674291,551
@cabeloosbourne2009-11-2815363
@garygabriel2009-07-191111
@REZZENDE2009-06-291503712,006

Weekly reviews

Times are America/Sao_Paulo. Read only: nothing was posted, replied to, followed, DMed or bookmarked.

Week ending Mon 2 Nov 2026 (review 2)

Data: public X reads at 08:08 on 2 Nov, posts from 26 Oct 08:00 to 2 Nov 08:00, retweets excluded, 15 posts on one page. No tool errors. Bio still empty and still no pinned post.

Followers: 28, down 8 from 36. Daily snapshots: 36, 34, 33, 33, 30, then 28, so the loss was steady rather than one event. Following stayed at 87. The cause cannot be seen through the API; the baseline counted 5 followers with zero posts, so a spam-account purge is possible but unverified. To reach 100 by late Jan 2027 the account now needs about 6 a week for 12 weeks.

Posts this week:

  • Real originals, n=2: median 58.5, average 58.5, none at 300. Best: Claude Code feedback form ships the whole transcript, 30 Oct, 82 impressions, 1 like (x.com/marco_machado/status/2116036031250043267). Other: Anthropic support quote, 31 Oct, 35 impressions, 1 reply (x.com/marco_machado/status/2116380250988740968). Up from review 1's median of 17 (n=5), but two posts are too few to call a trend.
  • App auto-shares, n=4: the same 3D model share text from a third-party tool posted four times within two minutes on 1 Nov at about 21:55, 3 to 5 impressions each, 17 in total (for example x.com/marco_machado/status/2117058387422667036). Counted apart from real originals; counted in, the original median would be 5.
  • Real replies, n=5: median 64, average 2,899, 1 at 300 or more. Best: "Self hosted gitea." to @thdxr (187,731 followers), 27 Oct, 14,074 impressions, 67 likes, 6 replies (x.com/marco_machado/status/2114937470949474497). Next: thanks to @acdlite (74,089 followers), 291. Worst: the reply to @DennisonBertram calling Anthropic's output bullshit, 21.
  • Bot-command replies, n=4: median 67.5, average 84, no likes.
  • Real replies produced 14,496 of the week's 14,966 impressions (97%); real originals 117 (under 1%).

Techniques used: point in the first line and quoted receipts in both real originals (the 19 Oct read-through change); short real replies to large accounts in his lane. Not used: bio, pinned post, and most of the drafted queue (five drafts on the X post tracker are still unposted). The one 14,074-impression reply came the same week followers fell by 8, so in this one case reach did not turn into follows while the profile stayed empty. That is a single case, not a measured pattern.

Daily learning log this week: no organic ranking weight changed in the four commits checked (27 Oct to 2 Nov); page-level scorers and user debias still ship off. Two more small-account reports (@AliShazil_, @liorpesoa) credit daily replies at volume, consistent with his own numbers.

Next week's originals (already drafted on the X post tracker, so no new drafts; one per weekday about 09:00):

  1. Mon 2 Nov: agent post-mortem thread (sent today by the daily original routine).
  2. Tue 3 Nov: Claude Code refuses to drop its footer on my own repo.
  3. Wed 4 Nov: Claude Code admits it ignores my rules.
  4. Thu 5 Nov: Codex admits it skipped checks.
  5. Fri 6 Nov: AI is aligned with the lab, not the user.

Profile drafts (publish by hand):

  • Bio: Software engineer. I run a fleet of AI agents and coding agents and post what they get wrong, with the receipts.
  • Pinned post: pin the 30 Oct feedback form post until a stronger original exists; it is the best real original of the past two weeks.

Reply targets: the reply feed keeps sending posts from the reply-target lists. Priority this week is short, specific replies to large accounts on coding agents and dev tools, such as @thdxr (187,731), @opencode (227,976), @Teknium (135,639) and @acdlite (74,089), 3 a day between 11:00 and 14:00. Skip insult-toned replies like the worst reply above.

Week ending Mon 26 Oct 2026 (review 1)

Data: public X reads at 08:05 on 26 Oct, posts from 19 Oct 08:00 to 26 Oct 08:00, retweets excluded, 26 posts over two pages. No tool errors. Recent posts are still accruing impressions.

Followers: 36 (35 at the 01:45 baseline the same day, so +1 in about 6 hours). There is no count from 19 Oct, so the weekly gain cannot be measured; review 2 will have the daily snapshot. Bio still empty and no pinned post.

Posts this week:

Techniques used: none of the plan yet, because the plan, bio and drafts were made at 01:45 on 26 Oct and nothing has been posted since. One "let's connect" reply was posted, the tactic the plan excludes, and it got 2 impressions. No pattern claims are possible from 5 originals; the reply-versus-original gap repeats the baseline.

New from the learning log: X's 19 Oct ranking change favors posts people read to the end, so this week's drafts put the point in line one and cut padding. Paid Boost stays off the plan.

Next week's drafts (publish by hand; slots 09:00 and 19:00 to compare timing):

  1. Tue 09:00. My bots share one memory, and it rots. This week Memory Janitor caught [FILL: the exact entry it flagged, quoted]. Left in, it would have [FILL: what would have gone wrong]. I approved the fix with one tap. Attach [FILL: screenshot of the proposal].
  2. Wed 19:00. Two coding agents on one dev server will break each other. One edited a file, Vite reloaded the page, and the other agent's browser run died and started over from zero. [FILL: what you changed to stop it, or "Still unfixed. How do you isolate them?"]
  3. Thu 09:00. Four things that make running a fleet of bots harder right now: the macOS app hides routine instructions and bot descriptions, there are no pinned messages, Send Feedback lost the team reply option, and my inbox address can't be renamed or released.
  4. Fri 19:00. An approval gate the agent can walk around is a convention, not a control. I checked my own bots for that hole: [FILL: which bot and which file]. Result: [FILL: whether it could write around the approval].

Reply targets: the hourly reply feed (weekdays 08:00 to 18:00) sends fresh posts from the Reply targets and Fast replies X Lists with drafts. Aim for 3 real replies a day in 11:00 to 14:00, when the targets post most. Bot-command replies are fine as utility but do not count toward growth.

Learning log

VERIFIED: X code or official statement. NUMBERS: source shows its own metrics. ANECDOTE: claim only.

Run 2026-11-03 (7)
  • VERIFIED 2026-11-03 (commit b220448766ab). No organic ranking weight changed and the watched flags (EnablePageDecodeRerank, EnablePageRlExploration, UserDebiasEnabled) stay off. The commit sets AdsBlenderType back to multi_risk, adds EnableVideoCarouselMediumRiskFilter (default false), tightens carousel brand-safety when the high-risk filter is on, exposes Under the Hood top-3 heads with share at least 0.10, and refactors value_model weighted_terms for explainability. github.com/xai-org/x-algorithm/commit/b220448766ab Effect on advice: none; keep watching those three flags.
  • 2026-11-01 to 2026-11-03. No ranking announcements from @elonmusk or @nikitabier; @XEng not found; web search found no separate official announcement beyond the commit above. Effect on advice: none.
  • NUMBERS 2026-11-02. @Christian_Tichy (about 1.1k followers) reports a reply-heavy week with 22.9k impressions, 213 likes, 19 replies, 7.3k profile visits and +11 followers. x.com/Christian_Tichy/status/1984907829902503949 Cross-check: confirms technique 1 (replies drive impressions at small size). Effect on advice: none.
  • NUMBERS 2026-11-02. @godsall_dev (about 366 followers) reports last-7-day originals median about 55 impressions versus replies median about 1,155 (one reply about 6.5k). x.com/godsall_dev/status/1985040008581575112 Cross-check: confirms replies over originals. Effect on advice: none.
  • NUMBERS 2026-11-02. @xelA31B (about 17 followers) reports posts median 29 impressions versus replies median 1,223, with shortest replies getting about 2x the views of longer ones. x.com/xelA31B/status/1984975128708911580 Cross-check: confirms replies; mild short-reply nuance only. Effect on advice: none.
  • ANECDOTE 2026-11-01. @DartNQ (about 168 followers) advises replying to posts already moving, not only big accounts, while staying relevant. x.com/DartNQ/status/1984598656108838933 Cross-check: mild "reply under momentum" nuance on technique 1; does not change the plan. Effect on advice: none.
  • Growth-teacher search also hit #connect / follow-for-follow spam and secondhand "replies win" takes; nothing else with credible new technique added.
Run 2026-11-02 (3)
  • VERIFIED 2026-10-30 (commit 9106e9f33e, 2026-10-31 02:25 UTC). No organic ranking weight changed and the watched flags (EnablePageDecodeRerank, EnablePageRlExploration, UserDebiasEnabled) stay off. The commit switches the ads blender default to slot_spread, turns on a high-risk filter for the video carousel, adds a reward-head option to the page-decode scorer, adds copy-link and DM share heads to the debias step, and extends the "under the hood" report (its post-id display ships off). github.com/xai-org/x-algorithm/commit/9106e9f33e Effect on advice: none.
  • NUMBERS 2026-10-30. @liorpesoa (523 followers) reports one week of 424 to 462 followers and 28.6k impressions from 374 replies written and 47 posts, with build-in-public posts showing the real product as the best type and late-night quote jokes as the worst. x.com/liorpesoa/status/2116190894265147561 Cross-check: confirms technique 1 (real replies at volume) and showing real work; the raw screen recording format does not fit Marco's no-screenshots rule. Effect on advice: none.
  • ANECDOTE 2026-11-01. @mynameisaniket (70 followers) says after 30 days his replies got more views than his posts and his Product Hunt launch followers were all bots. x.com/mynameisaniket/status/2116833888429375511 Cross-check: confirms replies outperforming originals at small follower counts, as in Marco's own 26 Oct numbers. Effect on advice: none.
Run 2026-10-30 (3)
  • VERIFIED 2026-10-29 (commit 7fef3ba19d, 2026-10-30 01:27 UTC). No organic ranking weight changed. The commit renames the zero-weighted ReactWithVideoWeight to PostVideoWeight (still 0.0), adds a video-carousel weighted-score weight (ships at 0.0) and makes the carousel's extra-candidate count (30) a param, adds ad-targeting fields to the Phoenix proto, and expands notification visibility filtering. EnablePageDecodeRerank, EnablePageRlExploration and UserDebiasEnabled were not touched. github.com/xai-org/x-algorithm/commit/7fef3ba19d Effect on advice: none.
  • ANECDOTE 2026-10-29. Elon Musk, replying to a post the API won't show, said links "are just used for improving the algorithm recommendations and making advertising relevance suck less". x.com/elonmusk/status/2115942496098545823 Without the parent post it is unclear whether this concerns link reach or link-click tracking, so it neither confirms nor contradicts the research on posts with links. Effect on advice: none.
  • NUMBERS 2026-10-30. @AliShazil_ (757 followers) reports going from 276 to 754 followers in 44 days, crediting daily replies and consistency. x.com/AliShazil_/status/2116094902128042018 Cross-check: confirms technique 1 (real replies); self-reported counts only. Effect on advice: none.
Run 2026-10-29 (2)
  • VERIFIED 2026-10-28 (commit 606b254b45, 2026-10-29 02:57 UTC). No organic ranking weight changed. The commit adds two ad-placement blenders (slot_spread, least_movement), a video-carousel weight that multiplies opens by immersive dwell (VideoCarouselOpenTimesImmersiveDwellWeight, ships at 0.0), turns on page logging (EnablePageLogging true) and refactors visibility filtering. github.com/xai-org/x-algorithm/commit/606b254b45 Effect on advice: none; the page logging may be groundwork for the page-level scorers logged on 2026-10-28, so keep watching EnablePageDecodeRerank and EnablePageRlExploration.
  • 2026-10-27 to 2026-10-29 growth-teacher search: only template "#connect" posts (the same "50 to 120 followers in 24 hours" text posted by @SapnilBhat2309 and @konig0000) and posts without credible numbers; nothing added.
Run 2026-10-28 (3)
  • VERIFIED 2026-10-27 (commit 5ed796374e, 2026-10-28 02:49 UTC). Two new page-level For You scorers were added and ship off by default: PageDecodeRerankScorer (EnablePageDecodeRerank false; picks a whole page of posts step by step from a pool of 200) and PageRlExplorationScorer (EnablePageRlExploration false; temperature 0.2 over the top 64). No positive or negative ranking weight changed. github.com/xai-org/x-algorithm/commit/5ed796374e Effect on advice: none yet; watch for either flag turning true, since page-level picking could change how often one author shows up per page.
  • VERIFIED 2026-10-26 (same commit, README). Brazil2026ElectionFilter was removed from For You after the election; it only hid accounts reported to Brazil's Electoral Court from non-followers. The README also dates the time-spent ranking change to 8 Oct and the read-through retrieval change to 13 Oct, which are the changes already logged on 2026-10-26. github.com/xai-org/x-algorithm/blob/main/README.md Effect on advice: none.
  • 2026-10-26 to 2026-10-28 growth-teacher search (build-in-public and indie accounts): only "let's connect" and follow-for-follow posts or unverifiable claims; nothing with credible numbers worth adding.
Run 2026-10-27 (2)
  • VERIFIED 2026-10-21 (enabled in commit 989fb91254, 2026-10-22 UTC). FairShareRankingFilter is on by default (EnableFairShareRanking true): when more candidates arrive than the 2,800 Phoenix scoring budget (PhoenixScoresResultSize), each served type (for example in-network versus each out-of-network retrieval source) keeps a share proportional to its size, instead of the old ResultSizeFilter cutting the list at 2,800 in arrival order. github.com/xai-org/x-algorithm/blob/main/home-mixer/filters/… (added in 7f2ca2b914). The viral claim that "new posts used to be cut first" (for example x.com/LondonRealTV/status/2114707255484649755, 15,743 impressions) is not shown by the code, which only shows arrival order. Cross-check: missed by the 2026-10-26 run, which checked only the 23 and 24 Oct commits; adds to the research and changes no weight. Effect on advice: none; out-of-network posts get a steadier chance to be scored, which slightly helps the cold-start plan for originals.
  • VERIFIED 2026-10-27 (commit 2f252142b9, 01:28 UTC). A per-viewer "user debias" step was added to the ranker (vm-ranker/scoring/debias.rs): it re-centers each predicted action probability against how that viewer usually engages compared with everyone. It ships off (UserDebiasEnabled false, alpha 0.0); home-mixer only started sending its inputs (VMRankerSendDebiasInputs true). The same commit adds Experiment19Fou to the 0.3 Phoenix shadow-traffic list and changes no positive or negative weight. github.com/xai-org/x-algorithm/commit/2f252142b9 Effect on advice: none yet; watch for UserDebiasEnabled turning true.
Run 2026-10-26 (4)
  • VERIFIED 2026-10-19 (posted 2026-10-20 02:41 UTC). Elon Musk announced a new ranking model that predicts time spent much better and a retrieval model trained to surface posts people read all the way through. x.com/elonmusk/status/2112373713937084809 (3,115,269 impressions). Coverage: www.tomsguide.com/ai/elon-musk-just-changed-xs-algorithm-her… and www.tokenpost.com/news/technology/35482 (no measured results or rollout schedule given). Cross-check: adds to the research, which read dwell as a small weight (0.05) in param.rs; the change is in the Phoenix models, not the published weights, which are unchanged. Effect on advice: write originals people finish, with the point in the first line and no padding, because read-through now also decides whether a post is retrieved for non-followers.
  • VERIFIED 2026-10-23 and 2026-10-24. The two newest commits to github.com/xai-org/x-algorithm (07d159b691, 6258a1549e) change no ranking weights: param.rs only flips EnableAdsFunnelTrace to true, and the abuse-enforcement credibility threshold was replaced with a value the repo labels a mock to reduce gaming. Effect on advice: none; the weights in the research still stand.
  • NUMBERS 2026-10-26. @teki_builds (564 followers) paid $25 for Boost on his best post: impressions went from 5k to 170k with almost no new engagement. x.com/teki_builds/status/2114562305216184505 Cross-check: new, consistent with the out-of-network discount. Effect on advice: do not pay for Boost to grow followers; it buys impressions from people outside his audience.
  • ANECDOTE 2026-10-25. @oimatrixioYT (1,464 followers, build-in-public founder) says replying to smaller accounts found with searches such as "building in public" lang:en -filter:links -filter:replies worked, while generic "let's connect" posts did little on their own. x.com/oimatrixioYT/status/2114459265142345814 Cross-check: confirms technique 1 (real replies). Contradiction: @Serhii_Klym says he went from 0 to 359 followers mainly through "let's connect" posts (x.com/Serhii_Klym/status/2114355508748460412); that is closer to follow-for-follow and stays excluded. The article also claims 35k followers while the API shows 1,464, so its numbers are unreliable. Effect on advice: reuse those search operators to find reply targets; no change to the plan.

Account audit

Pulled 3 Nov 2026, about 00:06 (São Paulo), read only.

Profile

Name / handleMarco Machado / @marco_machado (id 28566285)
Followers28
Following87
Posts245
Likes given / media / listed605 / 7 / 0
Bio (description)empty: the API returned ""
LocationBrasil
URLmarcomachado.dev
Pinned postnone: no pinned_tweet_id returned on two lookups with expansions=pinned_tweet_id
Bannernone: profile_banner_url returned ""
Created2009-04-03 10:52 BRT
Verifiedyes, verified_type = blue

Last 20 posts

Last 20 posts, 25 Oct to 1 Nov 2026: 6 originals, 13 replies, 1 repost. Public metrics only.

WhenTypeTextImpr.Likes
2026-11-01 21:57originalCreated a new 3D model using @tripoai, and I'm seriously impressed. Generate production-ready 3D models from text or images in seconds. See the model here: http…50
2026-11-01 21:56originalCreated a new 3D model using @tripoai, and I'm seriously impressed. Generate production-ready 3D models from text or images in seconds. See the model here: http…40
2026-11-01 21:56originalCreated a new 3D model using @tripoai, and I'm seriously impressed. Generate production-ready 3D models from text or images in seconds. See the model here: http…30
2026-11-01 21:55originalCreated a new 3D model using @tripoai, and I'm seriously impressed. Generate production-ready 3D models from text or images in seconds. See the model here: http…50
2026-11-01 02:00repostRT @pidotdev: “Machines are tools, not persons”. - Pope Leo
2026-10-31 01:02originalAnthropic support just told me, in writing: "Claude is allowed to decide a guideline doesn't apply." That's the answer to Claude Code ignoring the rules I gave…350
2026-10-30 18:05reply to @opencode@opencode @bot add a p1 for this please200
2026-10-30 02:14originalWant to report a bug in Claude Code? The feedback form says it will include "the current session transcript." No opt-out, no redaction, just your whole session …831
2026-10-30 01:27reply to @benswerd@benswerd You don’t have to convince me. I’ll have my steak medium rare please.460
2026-10-27 17:56reply to @DennisonBertram@DennisonBertram @AnthropicAI really needs to dial down their bullshit.210
2026-10-27 10:17reply to @laravelnews@laravelnews @ylynfatt @bot you know what to do1830
2026-10-27 01:32reply to @ForwardEditor@ForwardEditor @bot remind me to try this later today550
2026-10-27 01:29reply to @thdxr@thdxr Self hosted gitea.14,07467
2026-10-27 01:27reply to @petergyang@petergyang @bot @bot let me know your thoughts on this800
2026-10-26 16:13reply to @acdlite@acdlite Just tried it on one of my convos (without the re-apply) and it's awesome! Thanks for that!2910
2026-10-26 09:21reply to @Teknium@Teknium This is so cool! I already have the Hermes Agent. All I need is the Mustang and an adapter. Maybe I can find my old adapter.640
2026-10-26 00:25reply to @xiaomovps@xiaomovps https://t.co/5qsgm2cqlC80
2026-10-26 00:08reply to @GraciousVik@GraciousVik You know what’s funny? I feel like the opposite. But you’re right, we need more than one for serious work.421
2026-10-26 00:06reply to @lglabgreg@lglabgreg Hi, software engineer and AI padawan. Let’s connect!41
2026-10-25 21:46reply to @Da7_Tech@Da7_Tech @NousResearch Hermes1231

Niche trends: AI coding agents

Daily post counts per topic (UTC days). Last 3 full days vs the 3 before; within 10% is steady. No topic qualifies as rising. None of the 150 worldwide, US and Brazil trends is about AI or coding.

Topic (query)Oct 28Oct 29Oct 30Oct 31Nov 1Nov 23d vs prior 3dMon vs Wed7-day totalLabel
Claude Code11,41811,55814,07211,52011,02312,451−5.5%+9.0%84,046steady
Codex13,96416,53215,41312,26914,47015,168−8.7%+8.6%101,925steady
Grok coding/agent8,2108,1747,7577,4087,4768,815−1.8%+7.4%55,554steady
Grok Bot20,20922,03414,85214,65815,65419,748−12.3%−2.3%125,594falling (weekday rebound)
OpenCode1,3991,6183,1233,1322,0951,498+9.5%+7.1%14,285steady (spike Oct 30–31, now fading)
Agent-built software6,7327,0086,3535,1585,3246,392−16.0%−5.1%43,566falling (mostly weekend)
Indie hackers + agents1,049982838803628866−19.9%−17.4%6,071falling
Cursor1,1731,1991,8268611,116898−31.5%−23.4%8,627falling
Devin484760637277144194−67.3%−59.9%3,015falling

Routines

RoutineSchedule (São Paulo)What it does
Daily growth learningWeekdays, about 6:30 AMChecks X algorithm commits and growth reports, adds new findings to the learning log
Daily original postWeekdays, about 7:30 AMSends the next original from the post queue
Reply feedEvery 2 hours, weekdays 8 AM to 6 PMSends fresh posts from the reply-target lists with reply drafts
Daily snapshotWeekdays, about 10 PMRecords followers, following, posts and median impressions; saves the follower list
Weekly reviewMondays, about 8 AMReviews the past week's posts and followers and sets next week's queue