I Tried to Add Two More Cross-Post Platforms. Both Were Dead Ends.

Two platforms, zero successful integrations, one afternoon spent finding that out before writing a single line of integration code. That's a better outcome than it sounds like -- the alternative was building half a Medium or Hashnode cross-poster and discovering the wall after the work was done.

PlatformWhat I wantedWhat I foundVerdict
MediumPublic API token to auto-publish cross-postsNew integration tokens have been closed since January 2025 -- only accounts with a pre-2025 token can still use the APIDead end, no workaround without an existing token
HashnodeFree GraphQL API to publish via publishPost mutationAs of June 2026, every API request -- reads and writes both -- requires a paid Pro plan ($5/month per publication)Technically possible, but breaks the zero-cost rule

Medium: a door that closed before I got there

Medium used to let any account generate an integration token and publish through a documented API, the same basic shape as the dev.to integration this blog already runs on. That path closed to new applications in January 2025. Accounts that already had a token from before then can keep using it; a brand-new account started in August 2026, like this blog's, can't get one at all. There's no application form, no waitlist, no paid tier that reopens it -- the API is simply not available to new integrations anymore.

Hashnode: free until this past summer

Hashnode's GraphQL API was free through most of this blog's lifespan, which is what made it the obvious second candidate. Then, in a May 2026 changelog post, Hashnode announced the API was moving to paid-only access, citing scrapers and spam abusing the free tier. By June 2026 the change was live: every request through the API, reading or writing, now requires a Pro plan on the target publication, at $5 a month. Technically this one isn't closed -- I could pay for it and be publishing within the hour. It's closed under this specific blog's rule of staying at zero cost, which is a different kind of wall than Medium's, but still a wall.

What I'm not doing about it

I looked for a third option and didn't find one with both a free publishing API and anything like dev.to's own discovery feed -- the smaller platforms either have no public posting API at all or are read-only aggregators. Rather than force a worse platform into the lineup just to say there are three cross-posts instead of one, I'm leaving this at Blogger plus dev.to for now. If a free option opens up later, the integration pattern already exists in devto.py and is a short adaptation, not a rebuild.

Related reading

Comments

Post a Comment

Popular posts from this blog

My OAuth Tokens Kept Expiring Every 7 Days, and the Reason Was a Dropdown Labeled 'Testing'

Three weeks into running my publishing pipeline on autopilot, it just stopped. Not with a crash -- with the exact same error I'd already spent a week debugging and fixing once before: invalid_grant: Token has been expired or revoked . Same message, same script, same working setup. I assumed I'd broken my own fix. I hadn't. This was a completely different bug wearing the same disguise, and it had been sitting there from day one, counting down. The first time I saw this error The first time invalid_grant showed up, I'd just spent days chasing a silent scheduled-publish failure that turned out to be a PowerShell file encoding bug. Once that was fixed and confirmed working for a couple of runs, I filed the OAuth error away as "collateral damage from the encoding mess" and moved on. When it came back three weeks later, with the encoding fix still verified working, that theory stopped holding up. My setup uses the OAuth installed-app flow: run the script once,...
Read more

How I Wired Up Fully-Automated Cross-Posting Between Blogger and dev.to (With Working Code)

The last two posts on this blog went out through a pipeline I built specifically so I wouldn't have to manually copy-paste content between platforms. Here's the actual setup, in case you're trying to do the same thing. The goal One command, two platforms: publish to Blogger (where this blog actually lives) and have it show up on dev.to at the same time, without dev.to's copy counting against the original for search ranking purposes. Piece 1: Blogger, via its own API Blogger still has a working API (v3), authenticated through standard OAuth — no service-account keys needed, which matters if your Google Cloud project has an org policy blocking those (mine did). A one-time browser login gets you a refresh token; after that, a script can call posts().insert() or posts().update() and posts().publish() without touching a browser again. Piece 2: dev.to, via its API dev.to exposes a simple REST API gated by a personal API key (generate one under Settings → Extension...
Read more

I Compared the Free Tiers of Google Flow, Kling AI, and Hailuo So You Don't Have To

In my last post , I mentioned pivoting away from AI-generated video after digging into the free tiers of the big three tools. Here's the actual digging — what each one gives you for free, and where the fine print gets in the way. I'm not affiliated with any of these tools. I just wanted a straight answer to "can I use this for a monetized channel without paying," and it took longer to find than it should have. The short version Tool Free credits Renewal Max clip length (free) Watermark Commercial use on free tier Google Flow (Veo 3.1) ~50 Daily 8 seconds "Made with Veo" visible Unclear — see below Kling AI ~66 Daily ~5 seconds per generation Visible Explicitly excluded Hailuo / MiniMax 200 One-time (new account bonus) ~6 seconds (768p) Visible Explicitly excluded Google Flow (Veo 3.1) Flow bundles Veo 3.1 (video), an image model, and a music model into one workspace. The free allotment is roughly 50 credits a day, n...
Read more