Back to @StartupYou's profile

Ward Plunet engagement report

@StartupYou - 122K followers on X

Measured over 1 original post from a 30-day window, last computed on October 5, 2026.

Engagement

Per follower
0.27%
of 122K followers
Per impression
2.24%
15K views on a typical post
Reach
12.0%
of its followers see a post
Typical post
329
interactions (median)
Saved
1.40%
206 bookmarks on a typical post
Posting rate
0.37/day
active 17% of days
Peak time
17:00 UTC
Wednesday

Early reading. We have captured 1 original post for this account, below the 8 we require before treating a median as settled. The numbers above describe what we have seen so far, not a finished profile of the account.

A typical post picks up 329 interactions against 122K followers, an engagement rate of 0.27%. Posts are seen about 15K times each, and 2.24% of those impressions turn into an interaction. That is about 12.1% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.37 posts a day over the last 30 days, though only 17% of days saw any activity at all. Most posts go out around 17:00 UTC, and Wednesday is the busiest day of the week. Of the 1 posts sampled, 100% carry an image or video. The account's strongest tracked post pulled 8.3K interactions, about 25x its own typical post. Only 1 original post have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.

Measured over 1 original post from a 30-day window, last computed on October 5, 2026.

Where this sits in the catalog

At 0.27%, Ward Plunet sits above the 50th percentile of the 205,261 accounts in this comparison. That places it in the above the median band, which runs 0.143% to 0.678%.

p100.004%
p250.024%
p50 (median)0.143%
p750.678%
p902.55%
p9982.4%
Engagement rate as a share of followers, across the 205,261 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 22,894 times apart and a linear axis would flatten everything below the median into a single point.
Show the percentile table
Engagement rate percentiles
PercentileEngagement rate
10th percentile0.004%
25th percentile0.024%
50th percentile0.143%
75th percentile0.678%
90th percentile2.55%
99th percentile82.4%

This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built

Posting timing

This account posts most often around 17:00 UTC, and Wednesday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.

Engagement by hour posted, UTCTwenty-four bars, one per UTC hour. Each bar shows how posts published in that hour compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest hour: 17:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 17:00 UTC
Show engagement by hour posted, utc as a table
Engagement by hour posted, UTC
Hour (UTC)Vs author medianPosts
00:00 UTC-1%89K
01:00 UTC-2%90K
02:00 UTC-3%88K
03:00 UTC-4%94K
04:00 UTC-5%76K
05:00 UTC-4%75K
06:00 UTC-5%86K
07:00 UTC-5%93K
08:00 UTC-4%108K
09:00 UTC-4%124K
10:00 UTC-3%129K
11:00 UTC-3%141K
12:00 UTC-3%154K
13:00 UTC-3%167K
14:00 UTC-4%173K
15:00 UTC-2%176K
16:00 UTC-3%171K
17:00 UTC-3%159K
18:00 UTC-2%149K
19:00 UTC-2%141K
20:00 UTC-1%131K
21:00 UTC0%116K
22:00 UTC-2%100K
23:00 UTC-1%90K
Engagement by day of weekSeven bars, one per weekday, Sunday first. Each bar shows how posts published on that day compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest day: Wednesday.
SunMonTueWedThuFriSat
Above the authors' own mediansBelowScale: plus or minus 111%Busiest day: Wednesday
Show engagement by day of week as a table
Engagement by day of week
DayVs author medianPosts
Sunday+5%393K
Monday+1%483K
Tuesday-2%520K
Wednesday-3%472K
Thursday-2%430K
Friday-3%447K
Saturday+2%393K
See what moves engagement across the whole catalogWhat counts as a good engagement rate at this size

Formats this account uses

Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.

This account's posting mix compared with catalog-wide effects
FormatThis accountCatalog effect95% intervalAccounts behind it
Image or video100% of posts+111%+108% to +115%34K
Outbound link0% of posts-41%-42% to -40%32K
Typical length-+15%+14% to +16%32K
  • 100% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
  • 0% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts.
  • Its average post runs 4005 characters, which falls in the over 280 characters band. Across the catalog, posts over 280 characters run 15% above the same accounts' other posts.

These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.

Best tweets

  • Jun 25, 202625x their median

    We recently obtained the highest-resolution 3D images of the human brain ever taken from outside the skull. This is the first look. Introducing Aleph, a research lab building brain interfaces for the telepathic future. (1/n) https://t.co/wW9xag34zy

    6.7K9902233481.6M viewsView on X
  • May 27, 20268.5x their median

    Introducing DiffusionBlocks: Block-wise Neural Network Training via Diffusion Interpretation https://t.co/c9AvsRKybj What if we didn’t have to hold an entire neural network in memory to train it? Standard neural net training optimizes all parameters jointly. As a result, the memory required during training grows linearly with the depth of the network. In our #ICLR2026 paper, we propose DiffusionBlocks, a principled framework to train networks one block at a time, drastically reducing memory requirements while matching end-to-end performance. With DiffusionBlocks, we split the network into blocks and train them one at a time, so you only need memory for a single block. How? We explicitly assign each block a role: to move the representation a little closer to the target than the block before it did. That role turns out to be precisely what a diffusion model does, step by step. Each block only needs to optimize its own objective and can be trained independently. We validated this across five different architectures: • ViT • DiT • Masked diffusion • Autoregressive transformers • Recurrent-depth transformers In each case, performance is competitive with end-to-end training while using a fraction of the memory. This perspective also extends naturally to recurrent-depth (Looped) transformers, which apply the same network iteratively and normally require expensive backpropagation through time (BPTT). Viewed through DiffusionBlocks, we can replace those multiple iterations with a single forward pass during training. Read our paper and code, to learn more. Paper: https://t.co/CRj96VGYQn GitHub: https://t.co/eNW0K9Xh8E 🐟

    2.3K35256100883K viewsView on X
  • Jun 25, 20265.0x their median

    We removed an LM's ability to speak German by fine-tuning on only 4 German tokens. As part of a 1-day hackathon with our product Silico, we removed a 67M-parameter language model's ability to predict German text, by tuning only a scalar factor on one subcomponent of the weights. (1/6)

    1.4K1295649307K viewsView on X
  • Jul 13, 20264.5x their median

    Moving from conventional ML to continual learning requires revisiting even the fundamental concepts such as “test”/“train” time. LLMs Need Sleep and Dreaming! We introduce a phase, where the model consolidates its fragile short-term memories into stable long-term memories, and then dreams to recursively self-improve over time. For memory consolidation, we introduce a new form of distillation, called Knowledge Seeding (KS), where a small model(s) distills its knowledge to a larger model. Our experiments on continual learning and reasoning tasks show that this new phase can help the model to perform better and relatively better mitigates catastrophic forgetting.

    1.2K1874830123K viewsView on X
  • Jul 9, 20263.0x their median

    This week in @TheEconomist I wrote about the incredible progress that we have been making against dementia. Though total numbers are rising (because we are living longer), the actual rate at every age has been coming down sharply for decades. A short 🧵 1/ https://t.co/xMv0KLMl3A

    8121392125247K viewsView on X
  • May 27, 20261.7x their median

    New paper: We present a "Unified Neural Scaling Law" functional form that accurately models & extrapolates the multivariate scaling behaviors of artificial neural networks as the variables listed in this attached video are varied. (1/N)

    4836312350K viewsView on X
  • Sep 16, 2026

    looped transformer unlocks a new scaling dimension - recurrent depth; i think it received less love (other than the rumors that frontier ai labs use it) than it deserves, here are few notes / observations fundamentally the method lets the model think deeper without increasing either its parameter count or its verbalized chain of thought length (the other 2 important scaling dimensions) i find the constrast with moe interesting: > looped transformer: keep params const, increase total FLOPs (more computation = reasoning) > moe: keep FLOPs const (through active params), increase total params (more param capacity = memory/knowledge) the architectural modification is straight forward, instead of: L1 → L2 → … → L_n (where n = num layers) we do: P → R → R → … → R → C where: * P - prelude, few transformer layers that we apply only once at the beginning (i.e. L1 -> L2 -> ... -> L_p) * R - recurring core, normally this would constitute the middle layers of the transformer, but in constrast with regular transformer R is repeated/looped an arbitrary number of times (r) * C - postlude or "coda", similar to P just at the exit so the computation proceeds as following: 1. e = P(x) 2. apply s_i = R(e, s_i-1) r times, where s0 ~ N(0, sigma^2 * I), and s and e are concat and mapped/"projected" back to hidden size 3. apply C on the final s (state) (the particularly important design decision is that e is re-injected at every recurrence) now the beautiful part is that more r at inference improves perf, and harder / more context-heavy problems benefit from more latent compute. e.g. on ARC-C they demonstrate: * 0-shot -> perf saturates around 8-12 iterations * 1-shot -> 20 iters * few shot (25-50 examples) -> 32 iterations (the recurrent reasoning is like a learned optimization in the latent space during inference; grad-descent during inference unlocked?) -- the above generalization is downstream of how we train the model, r is sampled from heavy tailed log-normal-Poisson distribution during training thus the model is trained across randomized recurrent depths (they use truncated BPTT - backprop through depth in this case - to save on memory) -- few systems notes: 1. they synchronize one r per microbatch across workers, otherwise GPUs with small r would be idle waiting for workers that happened to sample large r 2. the model has a natural specdec capability -> draft model == low recurrence count (r), verifier model == high recurrence count. states computed during drafting can be reused when verifying! e.g. s0→s1→s2→s3 from draft (r=4) can be fed into verifier => s3→s4→…→s11 (r=12) 3. aggresive KV cache sharing is possible because every recurrent iteration uses the same weights, they show that caches from different recurrence depths can be aggressively reused zero-shot 4. latents converge quicker for "easier" tokens, early looping exit is thus possible per token, depending on how "hard" the token is 5. takes up less memory in training/inference (tnx to truncated BPTT and KV sharing respectively) few mechinterp notes: 1. might be harder to do J-space/J-lens type of analysis (the deeper the model the harder it is to trust the jacobians that map intermediate activations to the output); in general this leads to more "neauralese" and makes it harder to solely use cot to monitor the models (i suspect that's what we've been seeing from oai/ant recently) 2. they find evidence for interesting structures in latent space, such as the tendency of the latent representation to follow "orbitals" to compute arithmetic tasks and for reasoning in general (the shape rotators win again?) -- in general there is less need for long cot data, but it’s fully complementary one can and will do both in practice another example you can do great work at academia! soon we’ll have incredibly strong OSS models that can run locally, we’ve decoupled num of params from the perf of the model! intelligence will be abundant, aligned to you, and democratized :)

    2852317415K viewsView on X
  • Jul 7, 2026

    A tiny 1-millimeter cube of human brain tissue can contain tens of thousands of neurons & other structures. Our new animation explores Neuroglancer data from @Google & @AllenInstitute, using visualization techniques to reveal the complexity packed into microscopic brain tissue 🧠 https://t.co/1NoCGHIVuZ

    136412311K viewsView on X
  • Jul 10, 2026

    1/6 New preprint! 🧠🔬 We gave Vision-Language Models the AI equivalent of anhedonia. https://t.co/8COD07ts9X

    50131310K viewsView on X

Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.

Buy or sell Twitter (X) accounts - escrow-protected

PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.

Reading these numbers

A typical post picks up 329 interactions against 122K followers, an engagement rate of 0.27%. Posts are seen about 15K times each, and 2.24% of those impressions turn into an interaction. That is about 12.1% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.37 posts a day over the last 30 days, though only 17% of days saw any activity at all. Most posts go out around 17:00 UTC, and Wednesday is the busiest day of the week. Of the 1 posts sampled, 100% carry an image or video. The account's strongest tracked post pulled 8.3K interactions, about 25x its own typical post. Only 1 original post have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.

What is Ward Plunet's engagement rate on X?
Ward Plunet (@StartupYou) has an engagement rate of 0.27%, based on the median interactions across 1 original posts from the last 30 days against 121,860 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.27%, Ward Plunet sits above the 50th percentile of the 205,261 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
Does @StartupYou have real engagement?
There is not yet enough sample to rank this account against others of its size.
When does @StartupYou post?
Most posts go out around 17:00 UTC, and Wednesday is its busiest day, at roughly 0.37 posts per day across the measured window.

Keep going