<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Nacho@BWS</title>
    <description>The latest articles on DEV Community by Nacho@BWS (@nacho_bws).</description>
    <link>https://dev.to/nacho_bws</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3866438%2F2e98cd17-2cbb-48a8-8e79-64c395acf3b9.png</url>
      <title>DEV Community: Nacho@BWS</title>
      <link>https://dev.to/nacho_bws</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nacho_bws"/>
    <language>en</language>
    <item>
      <title>Build Your Own X Tracker or Use X Bot? A Build-vs-Buy Guide</title>
      <dc:creator>Nacho@BWS</dc:creator>
      <pubDate>Sat, 21 Nov 2026 15:21:17 +0000</pubDate>
      <link>https://dev.to/nacho_bws/build-your-own-x-tracker-or-use-x-bot-a-build-vs-buy-guide-40m1</link>
      <guid>https://dev.to/nacho_bws/build-your-own-x-tracker-or-use-x-bot-a-build-vs-buy-guide-40m1</guid>
      <description>&lt;p&gt;If you can write a script, the idea is tempting. Pull some tweets, add up the likes, paste a table into Telegram. A weekend project, surely.&lt;/p&gt;

&lt;p&gt;Plenty of technical founders and community leads in crypto have had exactly this thought, and some of them were right to act on it. This guide walks through what a DIY X tracker really involves, where the effort hides, and when building your own is the better call. We run X Bot, so we have a bias. We will say plainly where that bias should not decide for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "just a script" turns into
&lt;/h2&gt;

&lt;p&gt;The first version really is small. A script that fetches posts matching a query and prints a count takes an afternoon. The trouble is that a tracker your community trusts is a different thing from a script that prints a count. Here is the list of jobs that appear after the first demo.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Getting data access.&lt;/strong&gt; You need a way to read X data programmatically. That means an account with the right access tier, credentials you store safely, and a plan for what happens when the terms, limits or pricing of that access change. Check the current X developer terms yourself before you commit, because they move and we will not quote them from memory.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Polling and deduplication.&lt;/strong&gt; The same post shows up in every fetch. You need to remember what you have already counted, handle edits to engagement numbers on older posts, and decide what happens when a fetch fails halfway.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A scoring model.&lt;/strong&gt; Raw likes are a poor ranking. Someone has to decide how a reply compares to a retweet and a quote, and then keep that decision visible so members do not argue about it. X Bot ships with defaults of likes=3, retweets=5, replies=8, quotes=10 and views=0.01, which deliberately rank conversation above amplification. Your script needs its own opinion, and the opinion needs to be changeable without a redeploy. If this is the part you care about, read &lt;a href="https://xbot.ninja/blog/customizing-leaderboard-score-weights" rel="noopener noreferrer"&gt;customizing leaderboard score weights&lt;/a&gt; first, because it shows how much the choice changes who wins.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Filters with real semantics.&lt;/strong&gt; "Posts about my token" sounds simple until you need the cashtag, two keywords, a mention of the project account, and a way to exclude retweets and a list of known spam accounts. Each of those is a query clause, a config field and a bug waiting to happen.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Rendering.&lt;/strong&gt; A table of numbers in a chat message gets ignored. A leaderboard image with the project name, logo and colors gets screenshotted and shared. Rendering that image server-side, consistently, with long handles and emoji in display names, is its own small project.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Scheduling.&lt;/strong&gt; You want a report at a sensible time, not whenever you remember to run the script. That means a cron job somewhere that stays up, plus logic so a retry does not post the same report twice.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Posting to Telegram.&lt;/strong&gt; Create the bot, handle group permissions, topics, rate limits and the day someone removes the bot from the chat.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Admin controls.&lt;/strong&gt; Eventually a second person needs to change a filter. Now you need permissions, and someone to answer when they get it wrong.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Maintenance.&lt;/strong&gt; This is the line item that never appears in the estimate. Every one of the above breaks occasionally, and it breaks on the weekend a campaign ends.&lt;/p&gt;

&lt;p&gt;None of this is hard in isolation. The cost is that all of it is yours, indefinitely.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the same job looks like with X Bot
&lt;/h2&gt;

&lt;p&gt;X Bot is a Telegram bot that turns X activity into shareable leaderboards. The setup path is short:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Add &lt;a href="https://t.me/BWS_X_Bot" rel="noopener noreferrer"&gt;@BWS_X_Bot&lt;/a&gt; to your Telegram group and promote it to admin.&lt;/li&gt;
&lt;li&gt;Run &lt;code&gt;/setup&lt;/code&gt;. Everything is configured from an interactive inline keyboard, not from slash-command syntax you have to memorize.&lt;/li&gt;
&lt;li&gt;Open &lt;strong&gt;🎯 Filters&lt;/strong&gt; and add the X accounts (&lt;code&gt;from:&lt;/code&gt;), cashtags (&lt;code&gt;$BTC&lt;/code&gt; style), keywords or mentions you want tracked, with optional excludes for retweets, quotes and replies, plus an ignore list.&lt;/li&gt;
&lt;li&gt;Open &lt;strong&gt;⏰ Schedule&lt;/strong&gt; and pick a daily preset (09:00, 14:00, 18:00 or 22:00 UTC), a custom time, specific days, or a full cron expression.&lt;/li&gt;
&lt;li&gt;Open &lt;strong&gt;🎨 Customization&lt;/strong&gt; to set the project name, logo, colors, leaderboard title and score weights.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdd0zai93ekdf0xqd7tbr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdd0zai93ekdf0xqd7tbr.png" alt="Menu utama /setup" width="404" height="398"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The bot then fetches posts on schedule, scores them, renders the report image and posts it in the chat. The report includes a per-user score, the best tweet of the period and your project branding. If you want to see what a finished report looks like before deciding, the &lt;a href="https://xbot.ninja/docs/x-bot-installation" rel="noopener noreferrer"&gt;installation guide&lt;/a&gt; walks through the first run, and the &lt;a href="https://xbot.ninja/docs/setup-menu" rel="noopener noreferrer"&gt;setup menu reference&lt;/a&gt; lists every screen.&lt;/p&gt;

&lt;p&gt;You also get things that are tedious to build and easy to overlook: a &lt;code&gt;/report&lt;/code&gt; command to pull the latest report on demand, &lt;strong&gt;📡 X Posts Auto-relay&lt;/strong&gt; to forward posts from chosen accounts into the chat shortly after they are published (up to roughly five minutes of latency), and &lt;strong&gt;❓ Help &amp;amp; Support&lt;/strong&gt; for tickets when something looks wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest cost comparison
&lt;/h2&gt;

&lt;p&gt;Money is the wrong place to start, because the real DIY cost is your time. Still, here is how the two paths line up.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DIY:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cost of API access, which depends on the tier you need and what X currently charges. Look it up at the time you decide.&lt;/li&gt;
&lt;li&gt;Hosting for the scheduler and renderer.&lt;/li&gt;
&lt;li&gt;Your hours, both up front and on every breakage.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;X Bot:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;FREE plan: 100 posts per month, a hard cap. Enough to try a real filter on a real community.&lt;/li&gt;
&lt;li&gt;PRO subscription via Stripe: $19 per month including 1,000 posts per month, then $0.02 per post metered.&lt;/li&gt;
&lt;li&gt;PRO credits via ETH: $0.02 per credit, packs from 1,000 to 100,000, never expire.&lt;/li&gt;
&lt;li&gt;The two paid paths layer: ETH credits drain first on each fetch, then the subscription's monthly grant, then metered overage.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The full breakdown is in &lt;a href="https://xbot.ninja/blog/how-x-bot-pricing-works" rel="noopener noreferrer"&gt;how X Bot pricing works&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A rough way to think about it: at $0.02 per post, 1,000 posts beyond the free allowance costs $20. If your tracker saves you even two hours a month of maintenance, the arithmetic favors buying unless your engineering time is nearly free. If you are a solo developer who enjoys this kind of project and values the learning, that changes the answer, and that is a perfectly good reason to build.&lt;/p&gt;

&lt;h2&gt;
  
  
  When building your own is the better choice
&lt;/h2&gt;

&lt;p&gt;We would rather you pick the right tool than the one we sell. Build your own if any of these describe you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You need a custom data model.&lt;/strong&gt; If you want to join X activity with on-chain wallets, CRM records or your own member database, a generic leaderboard cannot do that. You want the raw data, so own the pipeline.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You need raw data export.&lt;/strong&gt; X Bot is built to produce reports and leaderboards for a chat, not to be a data warehouse. If your analysts need every post as a row in a database, build or buy something designed for that.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You need minute-level freshness.&lt;/strong&gt; Reports have a 12-hour minimum interval between fires, and auto-relay can lag by up to about five minutes. If you are running a live dashboard that must update every minute during a raid, X Bot is the wrong tool. A related limit is covered in &lt;a href="https://xbot.ninja/blog/crypto-raid-results-tracking-x-telegram" rel="noopener noreferrer"&gt;tracking Telegram raid results&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You have strong opinions about ranking that go beyond weights.&lt;/strong&gt; Per-chat weights cover most needs. If your scoring depends on follower quality, sentiment or account age, you will outgrow a weighted sum.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You want it embedded in your own product.&lt;/strong&gt; If the tracker is a feature of something you sell, you should own it.&lt;/p&gt;

&lt;h2&gt;
  
  
  When X Bot is the better choice
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;You want a first report today.&lt;/strong&gt; The distance from "add the bot" to "image in the chat" is minutes, not a sprint. See &lt;a href="https://xbot.ninja/blog/install-x-bot-telegram-group-first-report" rel="noopener noreferrer"&gt;installing X Bot and getting your first report&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The people running the program are not engineers.&lt;/strong&gt; Community managers and agency account leads can change a filter or weight from the menu without asking a developer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You manage several clients or campaigns.&lt;/strong&gt; Named filters let one chat carry multiple tracked programs, which is a lot of config to rebuild yourself.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You do not want to be on call for a tracker.&lt;/strong&gt; When a report does not show up, there is a checklist, a ticket flow and a team behind it, instead of you reading logs on a Sunday.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You need something members can read at a glance.&lt;/strong&gt; A branded leaderboard image is more persuasive in a Telegram group than a pasted table, and the people competing on it are far more likely to engage with it.&lt;/p&gt;

&lt;h2&gt;
  
  
  A middle path
&lt;/h2&gt;

&lt;p&gt;It is not strictly either-or. A common pattern is to start with X Bot to get a working leaderboard and a shared understanding of the scoring, then build your own pipeline later for the narrow pieces X Bot does not cover, such as an internal warehouse. You will know exactly what you want from that pipeline because you will have used the report for a few weeks. If you are still choosing between lighter-weight tools, &lt;a href="https://xbot.ninja/blog/x-bot-vs-manual-spreadsheet-tracking" rel="noopener noreferrer"&gt;X Bot vs manual spreadsheet tracking&lt;/a&gt; covers the other end of the spectrum.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick decision checklist
&lt;/h2&gt;

&lt;p&gt;Answer these in order and stop at the first yes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Do you need raw per-post data in your own database? Build.&lt;/li&gt;
&lt;li&gt;Do you need updates faster than every 12 hours, on a schedule? Build.&lt;/li&gt;
&lt;li&gt;Does your ranking depend on signals beyond engagement counts and weights? Build.&lt;/li&gt;
&lt;li&gt;Do you want a branded report in a Telegram group by this afternoon? Use X Bot.&lt;/li&gt;
&lt;li&gt;Will non-engineers operate it? Use X Bot.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you reach the end without a yes, you are probably in the group that gains most from not owning the plumbing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ready to track your community on X?&lt;/strong&gt; Add &lt;a href="https://t.me/BWS_X_Bot" rel="noopener noreferrer"&gt;@BWS_X_Bot&lt;/a&gt; to your Telegram group, run &lt;code&gt;/setup&lt;/code&gt;, and your first report fires on the configured schedule. The FREE plan covers 100 posts/month — no card required.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;About this article: This post was drafted with AI assistance using X Bot's content workflow and reviewed by &lt;a href="https://xbot.ninja/blog/author/nacho-coll" rel="noopener noreferrer"&gt;Nacho Coll&lt;/a&gt;, Founder &amp;amp; Principal at Blockchain Web Services (BWS), before publishing. Every product claim is checked against the live bot. Read &lt;a href="https://xbot.ninja/blog/about" rel="noopener noreferrer"&gt;how we use AI in our content&lt;/a&gt;. Spot an error? Reach us via &lt;code&gt;/setup&lt;/code&gt; → ❓ Help &amp;amp; Support.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>telegram</category>
      <category>crypto</category>
      <category>twitter</category>
      <category>analytics</category>
    </item>
    <item>
      <title>How Many People Should Your X Leaderboard Show? Choosing the Top Count</title>
      <dc:creator>Nacho@BWS</dc:creator>
      <pubDate>Sat, 21 Nov 2026 15:21:15 +0000</pubDate>
      <link>https://dev.to/nacho_bws/how-many-people-should-your-x-leaderboard-show-choosing-the-top-count-173a</link>
      <guid>https://dev.to/nacho_bws/how-many-people-should-your-x-leaderboard-show-choosing-the-top-count-173a</guid>
      <description>&lt;p&gt;Most people set up X Bot, watch the first report land in the chat, and never touch the leaderboard size again. That is a missed lever. The number of names on the report decides who feels seen, who feels out of reach, and how much of the image anyone actually reads.&lt;/p&gt;

&lt;p&gt;This post is a decision guide for one setting: &lt;strong&gt;Top count&lt;/strong&gt;, the number of users the report leaderboard shows. It is a small setting with a surprisingly large effect on how your community behaves.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the setting does, exactly
&lt;/h2&gt;

&lt;p&gt;X Bot fetches X posts on your schedule, scores each post with your weights, adds the scores up per account, and renders a leaderboard image. Top count is how many of those accounts appear on the image.&lt;/p&gt;

&lt;p&gt;Three facts, all checked against the bot:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The range is 1 to 10.&lt;/strong&gt; Anything else is rejected with a message asking for a whole number from 1 to 10.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The default is 5.&lt;/strong&gt; If you never set it, the menu shows &lt;code&gt;5 (default)&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It only changes the display.&lt;/strong&gt; Accounts outside the cut are still tracked and scored. Raising the count later does not lose anyone's history for the period.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last point matters. You are choosing what to show, not what to measure. If you are unsure how scores are built, read &lt;a href="https://xbot.ninja/blog/customizing-leaderboard-score-weights" rel="noopener noreferrer"&gt;Customizing Your X Bot Leaderboard: Score Weights Explained&lt;/a&gt; first.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to change it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In your Telegram group, run &lt;code&gt;/setup&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Open &lt;strong&gt;🎨 Customization&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Tap &lt;strong&gt;🔢 Top count&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Reply with a whole number from 1 to 10.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The bot answers with a confirmation and the next report uses the new size. If you are an admin and prefer the older command, &lt;code&gt;/set_top_count 10&lt;/code&gt; does the same thing. The menu is the recommended path, and the full tour is in the &lt;a href="https://xbot.ninja/docs/setup-menu" rel="noopener noreferrer"&gt;setup menu docs&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To see the effect without waiting for the schedule, pull a report on demand. &lt;a href="https://xbot.ninja/blog/on-demand-x-report-command" rel="noopener noreferrer"&gt;How to Pull an On-Demand X Report Without Waiting&lt;/a&gt; covers that.&lt;/p&gt;

&lt;h2&gt;
  
  
  The real question: what is the leaderboard for?
&lt;/h2&gt;

&lt;p&gt;Before picking a number, decide what job the leaderboard has. In practice there are four, and each wants a different size.&lt;/p&gt;

&lt;h3&gt;
  
  
  Job 1: Recognise the winners (top 3)
&lt;/h3&gt;

&lt;p&gt;If the point of the report is to name a winner and two runners-up, show three. A podium is easy to read, easy to screenshot, and easy to repost on X. It also makes the prize obvious: first, second, third.&lt;/p&gt;

&lt;p&gt;The tradeoff is blunt. Anyone at rank 4 or lower is invisible in the chat. In a community of 15 active posters, that is most of the room, and invisible people stop posting.&lt;/p&gt;

&lt;p&gt;Use top 3 when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You run a short, high-stakes contest with a clear prize per rank.&lt;/li&gt;
&lt;li&gt;The group is small, and everyone already knows who is active.&lt;/li&gt;
&lt;li&gt;You want the report to double as a social post.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Job 2: Keep a regular crowd engaged (top 5)
&lt;/h3&gt;

&lt;p&gt;Five is the default for a reason. It is long enough that a member who is consistently active can reach it, and short enough that the image stays clean and readable on a phone.&lt;/p&gt;

&lt;p&gt;For a standing weekly or daily leaderboard in a community of 20 to 100 active members, five is usually right. It gives rank 6 and 7 a visible target ("two more good posts and I am on the board"), without turning the report into a wall of names.&lt;/p&gt;

&lt;p&gt;Use top 5 when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The leaderboard is permanent, not a one-off contest.&lt;/li&gt;
&lt;li&gt;You want a mix of regulars and newcomers to appear over time.&lt;/li&gt;
&lt;li&gt;You are not sure. Start here and adjust after two or three reports.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Job 3: Reward a wider ambassador group (top 10)
&lt;/h3&gt;

&lt;p&gt;Ten is the maximum, and it suits programmes where many people earn something. If your ambassador scheme pays the top ten, the report should show the top ten, otherwise someone will ask "where did I finish?" in the chat every single period.&lt;/p&gt;

&lt;p&gt;The sample community report in the screenshot at the top of this post is a ten-user weekly board. It works because the audience is large enough that ten names still feel like an achievement.&lt;/p&gt;

&lt;p&gt;The cost is attention. Ten rows means more to scan, and the gap between first and tenth can be huge. If the top scorer has 4,000 points and rank 10 has 40, the tail looks discouraging rather than motivating.&lt;/p&gt;

&lt;p&gt;Use top 10 when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You have a tiered reward scheme that reaches at least ten people.&lt;/li&gt;
&lt;li&gt;The community is large, with plenty of accounts posting each period.&lt;/li&gt;
&lt;li&gt;Transparency matters more than a punchy image. See &lt;a href="https://xbot.ninja/blog/weekly-ambassador-leaderboard-crypto-community-x" rel="noopener noreferrer"&gt;Weekly Ambassador Leaderboard for Your Crypto Community&lt;/a&gt; for a worked programme.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Job 4: Hold KOLs accountable (match the roster)
&lt;/h3&gt;

&lt;p&gt;Agencies and launch coordinators have a different question. The leaderboard is not a contest, it is a delivery check: did every hired KOL post, and how did each one perform?&lt;/p&gt;

&lt;p&gt;Here the right size is simply the size of the roster, capped at ten. If you hired four KOLs, set top count to 4 so every hired account appears and nobody can hide at rank 5. If you hired eight, set it to 8.&lt;/p&gt;

&lt;p&gt;One limit to plan around: with more than ten KOLs on a campaign, a single report cannot show all of them. Split the roster across chats, one per client or cohort, which also gives each client a cleaner report. &lt;a href="https://xbot.ninja/blog/kol-agency-multi-client-tracking" rel="noopener noreferrer"&gt;Track Multiple KOL Clients in One Telegram Group&lt;/a&gt; walks through that structure, and &lt;a href="https://xbot.ninja/blog/tracking-x-activity-for-token-launch" rel="noopener noreferrer"&gt;Tracking X Activity for a Token Launch&lt;/a&gt; shows the launch version.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick decision table
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Situation&lt;/th&gt;
&lt;th&gt;Suggested Top count&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Short contest, one prize per rank&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Small group, under about 15 active posters&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Standing weekly leaderboard, mid-size community&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Not sure yet&lt;/td&gt;
&lt;td&gt;5 (the default)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ambassador programme paying many people&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Client report with a fixed KOL roster&lt;/td&gt;
&lt;td&gt;Roster size, up to 10&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Public showcase for a big community&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Treat these as starting points. The best number is the one that makes the right people feel the report is about them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three mistakes to avoid
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Mistake 1: Showing more names than people who qualify
&lt;/h3&gt;

&lt;p&gt;If only four accounts posted in the period, a top count of 10 does not invent six more rows. It shows who is there. That is fine, but an empty-looking board reads as a dead community. In the quiet early weeks of a new group, a smaller number makes the report look healthier and more honest.&lt;/p&gt;

&lt;h3&gt;
  
  
  Mistake 2: Changing the size mid-contest
&lt;/h3&gt;

&lt;p&gt;If you announce "top 5 win rewards" and then switch to top 10 halfway through, people will ask what changed. Lock the number when the contest starts, and write it into the rules. For fixed-length contests, &lt;a href="https://xbot.ninja/blog/run-fixed-dates-x-engagement-contest-telegram" rel="noopener noreferrer"&gt;Run a Fixed-Dates X Engagement Contest From Telegram&lt;/a&gt; covers the full setup.&lt;/p&gt;

&lt;h3&gt;
  
  
  Mistake 3: Treating the size as a fix for a noisy board
&lt;/h3&gt;

&lt;p&gt;If the leaderboard feels cluttered, a smaller top count hides the noise, but it does not remove it. Spam accounts, retweets and off-topic posts still count towards scores and can still reach the cut. Clean the inputs instead, with excludes and an ignore list. &lt;a href="https://xbot.ninja/blog/cleaning-up-noisy-x-bot-reports" rel="noopener noreferrer"&gt;Cleaning Up Noisy X Bot Reports&lt;/a&gt; shows how.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pair it with the other report levers
&lt;/h2&gt;

&lt;p&gt;Top count works best alongside three other settings in the same Customization menu:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Weights.&lt;/strong&gt; If the same accounts always win, adjust what you reward. Conversation can count for more than raw amplification, and the defaults already lean that way.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Project branding.&lt;/strong&gt; A logo, project name and colours make a ten-row board look designed rather than dumped. &lt;a href="https://xbot.ninja/blog/white-labeling-x-bot-reports-for-clients" rel="noopener noreferrer"&gt;White-Labeling X Bot Reports for Client Delivery&lt;/a&gt; covers it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Schedule.&lt;/strong&gt; A shorter period with a small board feels competitive. A longer period with a bigger board feels like a season. Match the two.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When a bigger leaderboard is the wrong answer
&lt;/h2&gt;

&lt;p&gt;Top count tops out at ten, so it is not a tool for showing a whole community. If you want to recognise 50 contributors, no setting will do it. Options are to rotate which ten are shown by running shorter periods, to run separate named filters for separate cohorts, or to publish your own longer list from the data. For public visibility, qualifying chats can also appear on the dashboard described in &lt;a href="https://xbot.ninja/blog/public-leaderboard-xbot-ninja" rel="noopener noreferrer"&gt;Putting Your Project on the Public X Bot Dashboard&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It is also worth being honest about the opposite case. If your group has three active posters, no value of Top count will make the report feel busy. Fix activity first, then tune the display.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple way to pick, in two reports
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Leave the default of 5 for the first report.&lt;/li&gt;
&lt;li&gt;Read it in the chat. Ask: did the right people appear, and was the bottom row still motivating?&lt;/li&gt;
&lt;li&gt;If the bottom row felt arbitrary, drop by one or two. If members asked where they ranked, raise it.&lt;/li&gt;
&lt;li&gt;Check again after the next report, then leave it alone.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Two cycles is enough. After that, resist the urge to fiddle.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ready to track your community on X?&lt;/strong&gt; Add &lt;a href="https://t.me/BWS_X_Bot" rel="noopener noreferrer"&gt;@BWS_X_Bot&lt;/a&gt; to your Telegram group, run &lt;code&gt;/setup&lt;/code&gt;, and your first report fires on the configured schedule. The FREE plan covers 100 posts/month — no card required.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;About this article: This post was drafted with AI assistance using X Bot's content workflow and reviewed by &lt;a href="https://xbot.ninja/blog/author/nacho-coll" rel="noopener noreferrer"&gt;Nacho Coll&lt;/a&gt;, Founder &amp;amp; Principal at Blockchain Web Services (BWS), before publishing. Every product claim is checked against the live bot. Read &lt;a href="https://xbot.ninja/blog/about" rel="noopener noreferrer"&gt;how we use AI in our content&lt;/a&gt;. Spot an error? Reach us via &lt;code&gt;/setup&lt;/code&gt; → ❓ Help &amp;amp; Support.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>telegram</category>
      <category>crypto</category>
      <category>twitter</category>
      <category>analytics</category>
    </item>
    <item>
      <title>Run Report vs /recreate: Regenerating Your X Bot Leaderboard Safely</title>
      <dc:creator>Nacho@BWS</dc:creator>
      <pubDate>Sat, 21 Nov 2026 15:07:05 +0000</pubDate>
      <link>https://dev.to/nacho_bws/run-report-vs-recreate-regenerating-your-x-bot-leaderboard-safely-5e0l</link>
      <guid>https://dev.to/nacho_bws/run-report-vs-recreate-regenerating-your-x-bot-leaderboard-safely-5e0l</guid>
      <description>&lt;p&gt;You have just spent ten minutes tuning your X Bot setup. You added two KOL handles, switched off retweets, nudged the score weights. The next scheduled report is fourteen hours away, and the client call is in one. What you want is a fresh leaderboard built from the new settings, now.&lt;/p&gt;

&lt;p&gt;X Bot gives you three different ways to get a report into the chat on demand, and they are not interchangeable. One resends what already exists. Two go back to X and rebuild. Picking the wrong one either wastes posts from your allowance or leaves you staring at a stale image and wondering whether your changes did anything.&lt;/p&gt;

&lt;p&gt;This guide sorts out which is which, what each one touches, and the one flag that deserves a pause before you type it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three ways to get a report now
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Action&lt;/th&gt;
&lt;th&gt;Fetches from X again?&lt;/th&gt;
&lt;th&gt;Uses allowance?&lt;/th&gt;
&lt;th&gt;Use it when&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/report&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;You want to see the last report again&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;/setup&lt;/code&gt; then &lt;strong&gt;⚡ Run report&lt;/strong&gt;
&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;You changed something and want a fresh leaderboard&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/recreate&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Same as Run report, from a slash command&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/recreate delete-history&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Yes, after wiping stored tweets&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;You want to rebuild from a clean slate&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The first row is covered in detail in &lt;a href="https://xbot.ninja/blog/on-demand-x-report-command" rel="noopener noreferrer"&gt;how to pull an on-demand X report&lt;/a&gt;. It resends an image that was already generated, so nothing new is fetched and nothing is spent. That is exactly why it is the wrong tool after a settings change: the old image will look identical, because it is the old image.&lt;/p&gt;

&lt;p&gt;The rest of this article is about the other rows.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run report: the button path
&lt;/h2&gt;

&lt;p&gt;For most admins the button is the right place to start, because it lives where you were already working.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open &lt;code&gt;/setup&lt;/code&gt; in your group.&lt;/li&gt;
&lt;li&gt;On the top menu, tap &lt;strong&gt;⚡ Run report&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;The menu confirms that report generation started, and the bot posts a short "Generating leaderboard" message into the chat itself, so members who are not looking at your menu can see something is happening.&lt;/li&gt;
&lt;li&gt;Wait. The finished leaderboard image lands in the chat, typically within one to three minutes.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdd0zai93ekdf0xqd7tbr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdd0zai93ekdf0xqd7tbr.png" alt="X Bot top menu in Telegram" width="404" height="398"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Under the hood, the button and &lt;code&gt;/recreate&lt;/code&gt; start the same fetch-and-render job. They share the same guards, so what you learn about one applies to the other. The difference is that &lt;code&gt;/recreate&lt;/code&gt; also accepts the &lt;code&gt;delete-history&lt;/code&gt; option, which the button does not.&lt;/p&gt;

&lt;h2&gt;
  
  
  /recreate: the command path
&lt;/h2&gt;

&lt;p&gt;Type &lt;code&gt;/recreate&lt;/code&gt; in the group and the bot replies that it is recreating the report and asks you to wait. Same one-to-three-minute window, same result: a new report image posted into the chat.&lt;/p&gt;

&lt;p&gt;Two things to know about who can run it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Only group admins.&lt;/strong&gt; A regular member who types it gets a message saying only admins can recreate the report. This is deliberate, because it spends allowance. If you want a trusted teammate to be able to refresh reports, add them properly; the &lt;a href="https://xbot.ninja/blog/x-bot-admin-roles-for-agency-teams" rel="noopener noreferrer"&gt;admin roles guide&lt;/a&gt; walks through how.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Inside the right topic.&lt;/strong&gt; If you have pointed reports at a forum topic, the command has to be used where the bot allows it. Otherwise it replies that the command is not allowed in this topic.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The guards that will say no
&lt;/h2&gt;

&lt;p&gt;Both paths refuse to run in a few situations. These refusals are protective, and each message tells you what to fix.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;No filter configured.&lt;/strong&gt; A fresh leaderboard needs something to track. If you have not set up at least one filter, the bot tells you to configure one first. Go to &lt;code&gt;/setup&lt;/code&gt; then &lt;strong&gt;🎯 Filters&lt;/strong&gt; and add an account, cashtag, or keyword. If your filters exist but the report comes back empty, that is a different problem: see &lt;a href="https://xbot.ninja/blog/x-bot-filter-match-any-vs-all-empty-report" rel="noopener noreferrer"&gt;Match ANY vs Match ALL&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The period starts in the future.&lt;/strong&gt; If you have set a calendar period whose start date has not arrived yet, &lt;code&gt;/recreate&lt;/code&gt; declines and tells you the date. The report will begin automatically when the period starts. This is the situation you hit when you configure a contest ahead of time, as in the &lt;a href="https://xbot.ninja/blog/run-fixed-dates-x-engagement-contest-telegram" rel="noopener noreferrer"&gt;fixed-dates contest guide&lt;/a&gt;. There is nothing to regenerate before the window opens.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A run is already in progress.&lt;/strong&gt; This one saves you money. If a report is already being generated for the chat, the bot answers that one is underway, tells you how many seconds ago it started, and asks you not to retrigger it. Before this guard existed, impatient double taps queued identical leaderboards one after another, each one a separate fetch. If you tapped and nothing seems to have happened, wait the full three minutes before trying again.&lt;/p&gt;

&lt;h2&gt;
  
  
  What /recreate delete-history actually does
&lt;/h2&gt;

&lt;p&gt;Adding &lt;code&gt;delete-history&lt;/code&gt; after the command is the part to treat with care:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/recreate delete-history
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In addition to starting a new fetch, this wipes the stored tweet data the bot keeps for your chat before it rebuilds. The new report is then built from a clean slate rather than on top of what was already collected.&lt;/p&gt;

&lt;p&gt;Why would you want that? A few real cases:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;You tracked the wrong thing for a while.&lt;/strong&gt; Say a filter pulled in a lot of unrelated posts for a week before you noticed. Fixing the filter changes what is fetched from now on, but data already collected is still sitting there.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You are starting a new campaign in the same chat&lt;/strong&gt; and do not want the previous campaign's posts mixed into the new leaderboard. For a clean, dated window, setting a period is usually the better tool, so try that first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test posts from setup day&lt;/strong&gt; are polluting the numbers and you want them gone.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Why would you not want it? Because it is a deliberate deletion, and the old data does not come back. If a client has asked for last month's numbers, take a screenshot of the report first. Think of it as the difference between refreshing a page and clearing the cache. When in doubt, use the plain version without the flag.&lt;/p&gt;

&lt;p&gt;Also note that the flag only exists on the slash command. The &lt;strong&gt;⚡ Run report&lt;/strong&gt; button never deletes anything, which makes it the safer default.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a re-run costs
&lt;/h2&gt;

&lt;p&gt;Every regeneration goes back to X to pull posts, and pulled posts count against your plan. The bot itself says new credits will be consumed when you recreate. So the practical rule is to batch your changes first and regenerate once.&lt;/p&gt;

&lt;p&gt;Here is how that plays out on each plan:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;FREE plan:&lt;/strong&gt; 100 posts per month, a hard cap. A few careless re-runs on a busy filter can eat a meaningful slice of it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PRO subscription:&lt;/strong&gt; $19 per month, including 1,000 free posts per month, then $0.02 per post.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ETH credit pack:&lt;/strong&gt; $0.02 per credit, never expire, and they drain first on each fetch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For the full layering of those paths, read &lt;a href="https://xbot.ninja/blog/how-x-bot-pricing-works" rel="noopener noreferrer"&gt;how X Bot pricing works&lt;/a&gt;, and to see where your posts went, &lt;a href="https://xbot.ninja/blog/check-x-bot-credit-usage-and-plan" rel="noopener noreferrer"&gt;check your credit usage and plan&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A sensible workflow when you are tuning:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Make all your changes in one sitting: filters, excludes, weights, top count.&lt;/li&gt;
&lt;li&gt;Run the report once.&lt;/li&gt;
&lt;li&gt;Read it carefully before touching anything else.&lt;/li&gt;
&lt;li&gt;If you need another change, make it, then run again.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Tweaking one setting, regenerating, tweaking another, and regenerating again is the expensive way to do the same job.&lt;/p&gt;

&lt;h2&gt;
  
  
  When not to regenerate at all
&lt;/h2&gt;

&lt;p&gt;Some changes do not need a fresh fetch to look right, and some problems a re-run will not fix.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;You only want to look at the last report again.&lt;/strong&gt; Use &lt;code&gt;/report&lt;/code&gt;. Free of charge.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The scheduled report is due in an hour.&lt;/strong&gt; Just wait. Nothing is gained by pulling early.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The report did not arrive at all.&lt;/strong&gt; Regenerating will not fix a delivery problem and may just queue another undelivered image. Work through the &lt;a href="https://xbot.ninja/blog/x-bot-reports-not-arriving-troubleshooting" rel="noopener noreferrer"&gt;troubleshooting checklist&lt;/a&gt; first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A KOL says they posted and the bot disagrees.&lt;/strong&gt; Check the filter and ignore list before burning allowance on a re-run that will return the same result.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A quick worked scenario
&lt;/h2&gt;

&lt;p&gt;An agency owner adds a third KOL handle to a campaign filter at 15:00 and wants the client to see the updated leaderboard at 16:00.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;They open &lt;code&gt;/setup&lt;/code&gt;, then &lt;strong&gt;🎯 Filters&lt;/strong&gt;, and add the handle.&lt;/li&gt;
&lt;li&gt;They also switch on the retweet exclude while they are there.&lt;/li&gt;
&lt;li&gt;They go back to the top menu and tap &lt;strong&gt;⚡ Run report&lt;/strong&gt; once.&lt;/li&gt;
&lt;li&gt;They see the "Generating leaderboard" message in the chat and leave it alone.&lt;/li&gt;
&lt;li&gt;Two minutes later the new image appears with the third KOL on it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One fetch, one cost, and nothing deleted. Had they typed &lt;code&gt;/recreate delete-history&lt;/code&gt; instead, the result would look similar, but the stored history would be gone as well, which they did not need.&lt;/p&gt;

&lt;h2&gt;
  
  
  Honest limits
&lt;/h2&gt;

&lt;p&gt;Regeneration is a blunt instrument. It rebuilds the report from what X returns for your filters at that moment; it will not conjure posts that your filters do not match, and it does not bypass the plan cap. It also does not replace the schedule: for steady reporting, set up the &lt;a href="https://xbot.ninja/blog/custom-report-schedules-cron-x-bot" rel="noopener noreferrer"&gt;cron schedule&lt;/a&gt; and let it do the work. Use manual runs for the moments when a settings change or a client request cannot wait.&lt;/p&gt;

&lt;p&gt;For menu navigation details, the &lt;a href="https://xbot.ninja/docs/setup-menu" rel="noopener noreferrer"&gt;setup menu documentation&lt;/a&gt; lists each screen, and the &lt;a href="https://xbot.ninja/docs/troubleshooting" rel="noopener noreferrer"&gt;troubleshooting page&lt;/a&gt; covers the rest.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ready to track your community on X?&lt;/strong&gt; Add &lt;a href="https://t.me/BWS_X_Bot" rel="noopener noreferrer"&gt;@BWS_X_Bot&lt;/a&gt; to your Telegram group, run &lt;code&gt;/setup&lt;/code&gt;, and your first report fires on the configured schedule. The FREE plan covers 100 posts/month — no card required.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;About this article: This post was drafted with AI assistance using X Bot's content workflow and reviewed by &lt;a href="https://xbot.ninja/blog/author/nacho-coll" rel="noopener noreferrer"&gt;Nacho Coll&lt;/a&gt;, Founder &amp;amp; Principal at Blockchain Web Services (BWS), before publishing. Every product claim is checked against the live bot. Read &lt;a href="https://xbot.ninja/blog/about" rel="noopener noreferrer"&gt;how we use AI in our content&lt;/a&gt;. Spot an error? Reach us via &lt;code&gt;/setup&lt;/code&gt; → ❓ Help &amp;amp; Support.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>telegram</category>
      <category>crypto</category>
      <category>twitter</category>
      <category>analytics</category>
    </item>
    <item>
      <title>IPFS.NINJA: A Dead-Simple IPFS Pinning Service for Web3 Developers</title>
      <dc:creator>Nacho@BWS</dc:creator>
      <pubDate>Tue, 07 Apr 2026 19:13:53 +0000</pubDate>
      <link>https://dev.to/nacho_bws/ipfsninja-a-dead-simple-ipfs-pinning-service-for-web3-developers-1726</link>
      <guid>https://dev.to/nacho_bws/ipfsninja-a-dead-simple-ipfs-pinning-service-for-web3-developers-1726</guid>
      <description>&lt;p&gt;If you've ever tried to pin files to IPFS for a dApp, NFT project, or decentralized website, you've run into the same friction: setting up a Kubo node is overkill, existing pinning services have gotten expensive or shut down free tiers, and the API docs are often a mess.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://ipfs.ninja" rel="noopener noreferrer"&gt;IPFS.NINJA&lt;/a&gt;&lt;/strong&gt; is a new entrant that takes a different approach — ruthlessly simple, transparent pricing, and designed around the actual developer workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  What It Does
&lt;/h2&gt;

&lt;p&gt;At its core, IPFS.NINJA gives you:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. File Upload &amp;amp; CID Pinning
&lt;/h3&gt;

&lt;p&gt;Upload files directly through the dashboard or API. Already have a CID on the network? Pin it by reference — no re-upload needed.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Private Dedicated Gateways
&lt;/h3&gt;

&lt;p&gt;Each account gets its own &lt;code&gt;*.gw.ipfs.ninja&lt;/code&gt; subdomain. Unlike public gateways that are shared (and often rate-limited), your gateway bandwidth is yours. The free plan includes 5 GB/month; paid plans scale up to 50 GB per gateway.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Signed Upload Tokens
&lt;/h3&gt;

&lt;p&gt;This is the feature most useful for dApps. You can generate time-limited, scoped upload tokens that let your end-users upload directly to IPFS from the frontend — without ever exposing your master API key. This is critical for any NFT minting flow where users upload their own assets.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. IPNS Support
&lt;/h3&gt;

&lt;p&gt;Paid plans include IPNS names — mutable pointers that always resolve to your latest CID. If you've ever had to update a smart contract just because you changed a metadata JSON, IPNS solves that problem cleanly.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Image Optimization
&lt;/h3&gt;

&lt;p&gt;Built-in image optimization for assets served through the gateway — useful for NFT thumbnails and media-heavy dApps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pricing
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan&lt;/th&gt;
&lt;th&gt;Price&lt;/th&gt;
&lt;th&gt;Storage&lt;/th&gt;
&lt;th&gt;Files&lt;/th&gt;
&lt;th&gt;Gateways&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Dharma (Free)&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;1 GB&lt;/td&gt;
&lt;td&gt;500&lt;/td&gt;
&lt;td&gt;1 (5 GB/mo BW)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bodhi&lt;/td&gt;
&lt;td&gt;$5/mo&lt;/td&gt;
&lt;td&gt;10 GB&lt;/td&gt;
&lt;td&gt;50,000&lt;/td&gt;
&lt;td&gt;5 (10 GB/mo ea.)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Nirvana&lt;/td&gt;
&lt;td&gt;$29/mo&lt;/td&gt;
&lt;td&gt;100 GB&lt;/td&gt;
&lt;td&gt;500,000&lt;/td&gt;
&lt;td&gt;10 (50 GB/mo ea.)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;No bandwidth overage fees on any plan — bandwidth resets monthly and you just hit a soft cap. Storage is cumulative (doesn't reset), so you pay for what you keep.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick API Example
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Upload a file&lt;/span&gt;
curl -X POST https://ipfs.ninja/api/v1/files \
  -H &lt;span class="s2"&gt;"Authorization: Bearer YOUR_API_KEY"&lt;/span&gt; \
  -F &lt;span class="s2"&gt;"file=@metadata.json"&lt;/span&gt;

&lt;span class="c"&gt;# Response includes your CID + gateway URL&lt;/span&gt;
&lt;span class="c"&gt;# { "cid": "bafybeig...", "url": "https://abc123.gw.ipfs.ninja/ipfs/bafybeig..." }&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Signed Upload Tokens — A Closer Look
&lt;/h2&gt;

&lt;p&gt;For dApp developers, signed upload tokens are the standout feature. Here's why they matter:&lt;/p&gt;

&lt;p&gt;In a typical NFT minting flow, users need to upload their image and metadata to IPFS before the mint transaction. The naive approach is to proxy uploads through your backend — every file goes through your server, adding latency and cost.&lt;/p&gt;

&lt;p&gt;With signed upload tokens, you can issue a short-lived, scoped token server-side and send it to the client. The client uploads directly to IPFS.NINJA without ever seeing your master API key. The token can be restricted by file size, file type, and expiry time.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Server-side: generate a signed token&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nb"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'https://ipfs.ninja/api/v1/upload-tokens'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'POST'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="s1"&gt;'Authorization'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'Bearer YOUR_API_KEY'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s1"&gt;'Content-Type'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'application/json'&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;maxFileSize&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;10485760&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="c1"&gt;// 10MB&lt;/span&gt;
    &lt;span class="n"&gt;expiresIn&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;3600&lt;/span&gt;        &lt;span class="c1"&gt;// 1 hour&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;token&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="c1"&gt;// Send token to client — they upload directly&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Who Is This For?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;NFT builders&lt;/strong&gt; — pin metadata + media, serve through a private gateway, use IPNS so your tokenURI never goes stale&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;dApp developers&lt;/strong&gt; — use signed upload tokens so users upload their own content securely&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decentralized website hosting&lt;/strong&gt; — deploy static sites to IPFS with a stable gateway URL&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Teams migrating off nft.storage or Infura IPFS&lt;/strong&gt; — simple REST API, clean dashboard, no surprises&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why Now?
&lt;/h2&gt;

&lt;p&gt;The IPFS pinning landscape shifted dramatically over the past two years. nft.storage ended its free tier. Infura deprecated its IPFS service. web3.storage went through multiple pivots. Developers who built on these services were left scrambling.&lt;/p&gt;

&lt;p&gt;IPFS.NINJA enters with a clear positioning: simple, transparent, and here to stay. The free tier is real (1 GB, 500 files, private gateway) and the paid plans are priced for actual indie developers and small teams — not just enterprise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bottom Line
&lt;/h2&gt;

&lt;p&gt;IPFS.NINJA is worth trying if you want an IPFS pinning service that gets out of your way. The free tier is genuinely useful, and the $5/month Bodhi plan covers most small-to-medium projects comfortably.&lt;/p&gt;

&lt;p&gt;Check it out at &lt;a href="https://ipfs.ninja" rel="noopener noreferrer"&gt;ipfs.ninja&lt;/a&gt; and share your thoughts in the comments — especially if you're migrating from another service and have specific requirements.&lt;/p&gt;

</description>
      <category>ipfs</category>
      <category>web3</category>
      <category>blockchain</category>
      <category>api</category>
    </item>
  </channel>
</rss>
