Urgent.News

What's breaking now, across thousands of outlets.

Tech

Writing Online for 30 Days: What Actually Brings Readers (It's Not Posting More)

Thirty days of publishing will teach you things that thirty articles about writing never will. The main lesson is uncomfortable: the writing is maybe half of it. Distribution habits, headline choices, and what you do between posts move the numbers more than one more post does. Here is what held up after a month of paying attention. Lesson 1: The headline is a contract, not a label My weakest…

Online publication for a 30-day span reveals truths about attracting readers that go beyond simply posting more content. The true secret appears to lie in the quality and execution of distribution strategies. Headlines act as contracts, making specific promises with numbers or testable claims to entice clicks. Posts focusing on one idea, developed deeply, tend to perform better than those laden with various topics.

Engaging in thoughtful discussions on others' work often garners more attention than creating new posts, as it places your name in relevant conversations. Maintaining a running notebook or note file helps capture ideas and prevent writer's block, ensuring a steady flow of content. Admitting the limitations of your advice or method in a post can build credibility and earn more engagement compared to selling a solution as all-encompassing.

When crafting a post, including a specific number, result, or failure will make the headline more appealing. Editing the post aloud before publishing helps refine the content. Ultimately, posting daily for the sake of posting can be detrimental, leading to empty or poorly executed content. The goal should be to produce one true, specific, well-titled piece at a time, while participating in discussions on other posts to establish credibility and visibility.

In the long run, the accumulation of such work will compound, creating a sustainable presence and audience base.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Fence the Human-Owned Paragraphs: A Markdown Contract for Model-Assisted Docs

The cheapest control you can put on a documentation generator is not a stricter prompt. It is a file format that gives the model no legal place to write except the prose blocks you hand it.

  • Human-authored paragraphs fenced to prevent model rewriting
  • Three block classes: Facts, Prose, Deprecations
  • Each block fenced with owner attribute and unique id

Blind RSA in circl ignored the reader you passed it

Cloudflare's circl has a partially blind RSA signer. Its Blind method takes an io.Reader. The blinding factor used that reader. The salt did not. It read from crypto/rand directly.

  • Circl library's partially blind RSA signer accepts io.Reader
  • Salt generated directly from crypto/rand, not from reader
  • Fix involves generating salt with io.ReadFull(random, salt)

More from Thursday 5 November →