The indie web is arguing over the humble donation button

A June 10 HakkerBlog post titled No, I Won't Buy You A Coffee caught a familiar mood in developer circles: fatigue with the idea that every creative act online should come with a payment prompt. The post is not mainly about one service, even though Buy Me a Coffee is the symbol in the headline. It is about a broader tension inside the indie web, open source, and personal blogging culture. People want creators to be paid, but they also want a corner of the web that does not feel like another marketplace.

The interesting part is that both instincts are common among developers. Software communities have spent years arguing that maintainers, writers, and tool builders should not be expected to subsidize everyone else with unpaid labor. At the same time, many of the same people have retreated to personal sites, RSS feeds, static blogs, and federated networks because the commercial web became exhausting. The donation button sits right at that contradiction. It can be a small sign of reader support. It can also feel like the same monetization reflex that pushed people away from large platforms in the first place.

Trend observation

The post lands because personal publishing has become a quiet counterculture again. Developers are rebuilding blogs with static site generators, publishing notes through RSS, syndicating posts through the IndieWeb, and experimenting with standards like Webmention and microformats2. This movement is partly technical, but it is also emotional. A personal site promises fewer metrics, fewer prompts, fewer feeds tuned for engagement, and less pressure to convert attention into revenue.

That promise gets complicated when the blog footer starts to resemble a checkout page. A coffee link is small, but small things carry cultural meaning. In a minimalist blog, a donation button can be the only explicitly commercial element on the page. For readers who arrive through RSS, Hacker News, Mastodon, or a personal blogroll, the prompt can feel less like patronage and more like ambient advertising.

The HakkerBlog argument is sharper than a general complaint about creators asking for money. The author accepts that hosting has costs and that creative work has value. The objection is about proportionality and setting. A tiny personal blog with a cheap domain and modest hosting bill is not the same thing as a full-time publication, a critical open source dependency, or a community service with real infrastructure costs. When every hobby project adopts the language of sustainability, the word can start to lose precision.

This is where the post reflects a broader pattern in developer culture. Developers often build tools for independence, then import the incentives of the systems they wanted to escape. A personal site becomes an analytics target. A blog becomes a funnel. A hobby project gets a sponsor deck. An open source repo gains badges for GitHub Sponsors, Open Collective, Liberapay, Ko-fi, or Patreon. Each tool can be reasonable on its own. In aggregate, the web starts to feel like a series of tiny asks.

Evidence and adoption signals

There are clear reasons these payment prompts spread. The tooling has become easy. A creator can add a button from Buy Me a Coffee, set up recurring support through Patreon, collect project funds on Open Collective, or use Liberapay for recurring donations with an open source-friendly identity. GitHub also made sponsorship part of the developer workflow through GitHub Sponsors, which means funding is now visible in the same place as issues, pull requests, and releases.

That visibility matters. For open source maintainers, funding links are not merely decorative. They can signal that a project has real maintenance costs, that the maintainer is open to support, and that users should not treat unpaid labor as infinite. The same applies to technical writers who publish high-quality tutorials, benchmarks, security research, or migration guides. A well-researched post can take days. A useful tool can take years. The old norm, where the work was free and the costs were private, had its own unfairness.

The adoption signal is not only buttons. It is the language around them. Developers now talk about sustainability, burnout, dependency funding, and maintainer health in ordinary project discussions. The Open Source Guides section on getting paid exists because the question is no longer fringe. Project pages increasingly include funding metadata. Package managers and repository hosts surface sponsorship links. The community has accepted, at least in principle, that software work needs economic support.

Personal publishing, though, follows a different emotional contract. A blog is often framed as a gift, a public notebook, or a way to participate in a conversation. The IndieWeb idea of owning your domain and publishing from your own site grew partly as a rejection of centralized platforms and their business models. When a personal blog asks for coffee money, some readers see a harmless tip jar. Others see the first step back toward the attention economy, where every interaction is measured by its potential to produce payment.

The HakkerBlog post also points at a practical asymmetry. Many developer blogs are cheap to run. A domain can be inexpensive. Static hosting can be free or low cost through options like GitHub Pages, Netlify, Cloudflare Pages, or Vercel. A small self-hosted VPS costs more, but still often sits within hobby spending. The author's argument is not that costs do not exist. It is that the cost of a small blog may not justify treating every reader as a potential payer.

That argument resonates because developers recognize the gamification of breaking even. A hobby service that pays for itself feels satisfying. It turns a cost center into proof that the project has value. But this can distort motivation. If the actual income is a few cents or a few euros, the payment link may be less about material support than about validation. The donation button becomes a counter, a badge, or a tiny market test. That is not morally wrong, but it changes the texture of the page.

Counter-perspectives

The strongest counter-argument is that readers can ignore the button. A donation link is not a paywall. It does not block access, inject tracking scripts by default, or force a subscription. Compared with ads, affiliate links, sponsored posts, newsletter funnels, or algorithmic promotion, a small voluntary tip link is one of the least intrusive ways to fund work. For many creators, it is a cleaner alternative to the commercial patterns critics dislike.

There is also a class issue hidden in the anti-tip-jar position. Telling people that hobbies cost money is easy when the costs are trivial to them. Not every writer, student, maintainer, artist, or independent developer experiences those costs the same way. A domain, hosting plan, test device, cloud bill, or paid API subscription can be minor for one person and meaningful for another. A culture that treats asking for support as tacky may unintentionally favor people who can afford to publish without support.

Open source adds another complication. The line between hobby and infrastructure is blurry. A tiny blog may not need funding, but a tiny library might sit inside thousands of production systems. A personal tutorial might become the reference everyone uses for a difficult migration. A one-person project can quietly become community infrastructure before anyone has a funding model for it. If the norm is that asking is shameful, maintainers may wait until they are burned out before saying they need help.

There is a better distinction to make: not all asks are the same. A quiet funding link on an about page is different from a pop-up. A transparent explanation of costs is different from vague guilt language about keeping the lights on. A project with real expenses is different from a blog that costs less than a streaming subscription. The question is not whether creators may ask for support. They can. The question is whether the ask matches the scale, context, and spirit of the work.

That distinction is why tools like Open Collective and Liberapay appeal to parts of the developer community. They can frame funding as shared maintenance rather than personal branding. Open Collective, in particular, makes budgets, expenses, and contributors visible for many projects. Liberapay emphasizes recurring donations and open source values. These models do not erase the discomfort around money, but they can make the transaction feel less like a sales prompt and more like civic infrastructure.

Buy Me a Coffee and Ko-fi occupy a different cultural space. They are lightweight, friendly, and intentionally casual. That is their strength. It is also why they irritate some readers. The coffee metaphor softens a payment request, but it can also make the economics feel unserious. A blog asking for coffee money is not necessarily asking for sustainability. It may be asking for applause in payment form. Some readers are fine with that. Others came to personal blogs precisely to avoid that kind of conversion layer.

The emerging consensus may be less stable than it looks. Developer communities broadly support paying maintainers, but they are less united on monetizing every personal artifact. The next phase is likely to involve more etiquette than tooling. People will keep adding funding links, but readers will become more sensitive to placement, language, transparency, and whether the request fits the work.

A practical norm is already visible: make the work readable first, make the ask optional, and be specific when money truly matters. A footer link to a funding page is different from a plea inside every post. A short note saying what donations cover is different from generic scarcity language. For larger projects, publish budgets and expenses. For personal blogs, consider whether the button serves readers, supports the work, or simply imports platform-era habits into a space meant to feel independent.

The HakkerBlog post is useful because it questions a consensus that had become too easy. Support creators, yes. Pay maintainers, yes. Fund shared infrastructure, yes. But also preserve places where publishing is not a pitch, where a post can just be a post, and where the value of a personal web page is not measured by whether it can pay for itself. The indie web will probably keep both impulses, the gift economy and the tip jar. The healthier version will be honest about which one it is choosing, and why.