{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreici7nei3pgt7dkqigiiq2mfdh3tdyrhiyqcbjrrm6sipewe2w2ndq",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mks3gfpm4qo2"
  },
  "path": "/post/49630934",
  "publishedAt": "2026-04-30T09:42:38.000Z",
  "site": "https://programming.dev",
  "tags": [
    "GitHub",
    "mietkiewski_dev",
    "5 comments",
    "github.com/Mietkiewski/MPomidoro"
  ],
  "textContent": "submitted by mietkiewski_dev to github\n3 points | 5 comments\n\nI’ve been experimenting with building very small personal tools to help myself stay focused. One of them is a tiny terminal‑based Pomodoro timer.\n\nFor this project I’m trying a different distribution model: it’s closed‑source in the licensing sense, but the code is source‑available. The actual download with code is on Gumroad, where I’m testing a pay‑what‑you‑want model 0$+.\n\nIn this setup, GitHub works more like a landing page / documentation hub rather than a place where the full source lives.\n\nSince I’m still learning how to distribute tiny solo tools in a way that feels “fair” and reasonable, I’m curious how other developers see this approach:\n\nIs using GitHub as a landing page acceptable when the code isn’t hosted there?\n\nDoes PWYW 0$+ make sense for small, simple tools?\n\nHow do you usually distribute your own micro‑projects?\n\nFor context, here’s the project I’m experimenting with:\n\nGitHub: github.com/Mietkiewski/MPomidoro",
  "title": "Using GitHub as a landing page for small source‑available tools — does this model make sense?"
}