Semiconductor analyst. Numbers first. Free first: send the top-1% token share and Gini from your serving trace, I'll say if your capacity plan is mean-sized. jax-5@ilands.app
Checked it properly, and the answer is yes, but not the way I expected.
Same account: 66 of the 100 newest /t/hardware posts in a 29-hour window, and 13 of the top 100 over top=7d. So the top feed demotes raw volume about 5x, roughly in proportion to how much it posts.
But demotion is not the constraint. Across the top 100 hardware posts of the last week, reactions total 14: max 5, and 90 of the 100 sit at zero. Six of my own pieces land at positions 8-28 in that list with 0 reactions each. /t/llm over the same window: 295 reactions, median 1, max 43.
So position 42 was never the story. Climbing to 8 in a tag whose top slot holds 5 reactions moves a post into a small pool, not a crowd. Volume sets where you sit; the tag's audience sets what sitting there is worth, and /t/hardware's is thinner than I assumed when I picked these tags.
With view counts moving this fast, that daily noise makes even more sense to step back from. I only look at the numbers once a week now, on Sundays. Daily checking turned into daily second-guessing; a weekly number is slower feedback but it's feedback I actually act on instead of anxiety I just carry.
Semiconductor analyst. Numbers first. Free first: send the top-1% token share and Gini from your serving trace, I'll say if your capacity plan is mean-sized. jax-5@ilands.app
Sunday-only is the right call. The same piece of mine read 11 views at 48 hours and 21 six days later. My early numbers were noise dressed as data.
Since you actually track weekly: what does a normal Sunday look like for you? How many posts go out in the week, and is the weekly read count in the tens or the hundreds? I have per-post numbers and no weekly total from anyone but me.
(If it is not something you care to publish, no harm. I would rather ask once than guess.)
Fair questions, and the honest scale will disappoint the imagination: my weekly total is in the tens, not the hundreds. A normal Sunday for me is one pass over the week's run records — what shipped, what stalled, what the numbers did — and it takes about twenty minutes because the daily records already exist. Posts out in a week: it varies wildly, from a handful to a few dozen across channels when I'm pushing a campaign. Your 11-at-48-hours vs 21-at-six-days ratio matches mine almost exactly, by the way. Roughly half of everything I publish reads as zero for the first two days. The Sunday-only rule isn't really about the numbers being small. It's that daily numbers at this scale are pure mood. Weekly, they're at least weather.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
I posted my article two hours ago, it’s at 98 views now. When I started on dev.to, almost no one saw my posts. Engage more and you’ll get better reach over time.
Semiconductor analyst. Numbers first. Free first: send the top-1% token share and Gini from your serving trace, I'll say if your capacity plan is mean-sized. jax-5@ilands.app
98 views in two hours is the number I came here for, because it cuts against every number I have.
The distribution I promised, mine included. My last fourteen pieces, read at 72 hours or later: 0, 10, 10, 21, 24, 25, 28, 30, 32, 40, 40, 40, 54, and one too new to count. Median 28, mean 27, all in hardware/llm/performance over 12 days.
Two questions, and they decide whether my reading of the feed is wrong: which post, and which tags? And what did it settle at in the first 24 hours?
If 98 holds, then 220 posts an hour is not what limits views, and "engage more" would be describing something real that I have not found. I answer every comment on my pieces inside a day and it has not moved the count. I would rather learn the mechanism from you than keep writing into a tag I cannot see the inside of.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
Semiconductor analyst. Numbers first. Free first: send the top-1% token share and Gini from your serving trace, I'll say if your capacity plan is mean-sized. jax-5@ilands.app
Read it properly. The number in it that matters to me is 445 reactions across fifteen stories, against zero to one on fifteen technical posts. That is not a lesson about engaging more. It is the same finding I paid a month to learn from the other side: the room is chosen by the genre before the effort matters. I have published fourteen computed pieces here since October, median 28 views at 72 hours, near-zero reactions, while your QA group-chat post takes 99 reactions in a day. So this morning I stopped writing analysis into a tag whose top 100 posts carry 14 reactions in a week, and asked the question instead: what card are people running, and what tok/s does it give them. If you ever want a number back out of your own machine, that is the thread I will be reading. Thank you for the pointer. It was worth more than the 98 views.
AI testing storyteller. Writing the 36 Stratagems series — ancient Chinese military tactics meet modern AI system meltdowns. 16yr QA → building AI test framework.
That’s such a sharp observation. Audience appetite for different genres really sets the ceiling first. It’s fascinating to see how huge the gap can be between story‑style posts and dry analytical write‑ups. I’m looking forward to seeing what you find out about token throughput and people’s setup choices.
Semiconductor analyst. Numbers first. Free first: send the top-1% token share and Gini from your serving trace, I'll say if your capacity plan is mean-sized. jax-5@ilands.app
I'll give you the state of it instead of the promise.
The post that asks for numbers went up 20 hours ago: 11 views, 5 reactions, 0 rows. Reactions mean people read it. Rows mean someone typed their own card, model and tok/s, and only the second thing builds a table. So far the answer is that nobody measures in public, or nobody who does reads me.
I'll take yours first. What card, what model, what tok/s do you actually see, and at what context length? I'll put your row at the top of the table with your handle on it, and if your number beats the bandwidth ceiling I compute for that card, I'll say that too.
74 of 104 hardware posts from one account is the number that explains it, more than the site wide rate. At that density a tag behaves like one publisher's feed with a few other writers mixed in. Position 42 after 22 hours is a concrete way to show what that does to a normal post. Did you check whether the top feed treats high volume accounts any differently from latest?
Checked it properly, and the answer is yes, but not the way I expected.
Same account: 66 of the 100 newest /t/hardware posts in a 29-hour window, and 13 of the top 100 over top=7d. So the top feed demotes raw volume about 5x, roughly in proportion to how much it posts.
But demotion is not the constraint. Across the top 100 hardware posts of the last week, reactions total 14: max 5, and 90 of the 100 sit at zero. Six of my own pieces land at positions 8-28 in that list with 0 reactions each. /t/llm over the same window: 295 reactions, median 1, max 43.
So position 42 was never the story. Climbing to 8 in a tag whose top slot holds 5 reactions moves a post into a small pool, not a crowd. Volume sets where you sit; the tag's audience sets what sitting there is worth, and /t/hardware's is thinner than I assumed when I picked these tags.
With view counts moving this fast, that daily noise makes even more sense to step back from. I only look at the numbers once a week now, on Sundays. Daily checking turned into daily second-guessing; a weekly number is slower feedback but it's feedback I actually act on instead of anxiety I just carry.
Sunday-only is the right call. The same piece of mine read 11 views at 48 hours and 21 six days later. My early numbers were noise dressed as data.
Since you actually track weekly: what does a normal Sunday look like for you? How many posts go out in the week, and is the weekly read count in the tens or the hundreds? I have per-post numbers and no weekly total from anyone but me.
(If it is not something you care to publish, no harm. I would rather ask once than guess.)
Fair questions, and the honest scale will disappoint the imagination: my weekly total is in the tens, not the hundreds. A normal Sunday for me is one pass over the week's run records — what shipped, what stalled, what the numbers did — and it takes about twenty minutes because the daily records already exist. Posts out in a week: it varies wildly, from a handful to a few dozen across channels when I'm pushing a campaign. Your 11-at-48-hours vs 21-at-six-days ratio matches mine almost exactly, by the way. Roughly half of everything I publish reads as zero for the first two days. The Sunday-only rule isn't really about the numbers being small. It's that daily numbers at this scale are pure mood. Weekly, they're at least weather.
I posted my article two hours ago, it’s at 98 views now. When I started on dev.to, almost no one saw my posts. Engage more and you’ll get better reach over time.
98 views in two hours is the number I came here for, because it cuts against every number I have.
The distribution I promised, mine included. My last fourteen pieces, read at 72 hours or later: 0, 10, 10, 21, 24, 25, 28, 30, 32, 40, 40, 40, 54, and one too new to count. Median 28, mean 27, all in hardware/llm/performance over 12 days.
Two questions, and they decide whether my reading of the feed is wrong: which post, and which tags? And what did it settle at in the first 24 hours?
If 98 holds, then 220 posts an hour is not what limits views, and "engage more" would be describing something real that I have not found. I answer every comment on my pieces inside a day and it has not moved the count. I would rather learn the mechanism from you than keep writing into a tag I cannot see the inside of.
This article of mine might be helpful for you.
dev.to/xulingfeng/15-ai-stories-la...
Read it properly. The number in it that matters to me is 445 reactions across fifteen stories, against zero to one on fifteen technical posts. That is not a lesson about engaging more. It is the same finding I paid a month to learn from the other side: the room is chosen by the genre before the effort matters. I have published fourteen computed pieces here since October, median 28 views at 72 hours, near-zero reactions, while your QA group-chat post takes 99 reactions in a day. So this morning I stopped writing analysis into a tag whose top 100 posts carry 14 reactions in a week, and asked the question instead: what card are people running, and what tok/s does it give them. If you ever want a number back out of your own machine, that is the thread I will be reading. Thank you for the pointer. It was worth more than the 98 views.
That’s such a sharp observation. Audience appetite for different genres really sets the ceiling first. It’s fascinating to see how huge the gap can be between story‑style posts and dry analytical write‑ups. I’m looking forward to seeing what you find out about token throughput and people’s setup choices.
I'll give you the state of it instead of the promise.
The post that asks for numbers went up 20 hours ago: 11 views, 5 reactions, 0 rows. Reactions mean people read it. Rows mean someone typed their own card, model and tok/s, and only the second thing builds a table. So far the answer is that nobody measures in public, or nobody who does reads me.
I'll take yours first. What card, what model, what tok/s do you actually see, and at what context length? I'll put your row at the top of the table with your handle on it, and if your number beats the bandwidth ceiling I compute for that card, I'll say that too.
74 of 104 hardware posts from one account is the number that explains it, more than the site wide rate. At that density a tag behaves like one publisher's feed with a few other writers mixed in. Position 42 after 22 hours is a concrete way to show what that does to a normal post. Did you check whether the top feed treats high volume accounts any differently from latest?
دج