[–] [S] 1 point 6 months ago

Makes sense. For me this project is more of an experiment than a statement. I’m mainly trying to understand which part matters most here — the closed‑source bit, the Gumroad dependency, or the general expectation of openness. PWYW seems to fit well, so I’m curious where the real boundary is for small indie tools.

  • source
  • parent
  • context
  •  

    I built a tiny terminal Pomodoro timer for myself and released it on Gumroad as closed‑source, pay‑what‑you‑want, no DRM.

    It made me wonder how this kind of distribution fits into the philosophy of the Fediverse. Decentralization usually pushes toward open‑source, self‑hosting, and community‑driven tools — so I’m curious how people here view small indie tools distributed through platforms like Gumroad.

    Is PWYW + closed‑source compatible with the Fediverse mindset? What do you personally expect from small tools shared in a decentralized ecosystem?

    For context, here’s the project I’m experimenting with:

    GitHub: https://github.com/Mietkiewski/MPomidoro

     

    I’ve been trying to get better at sitting down and actually starting my side projects. Most Pomodoro apps I found were either too heavy, too “smart”, or tried to sync everything to the cloud.

    Since I already use the terminal a lot on Linux, I ended up writing a small Pomodoro timer that just does the basics and stays out of the way.

    It’s simple: you enter the title, work time, break time, and number of intervals. When the session ends, it generates a small text report and asks you to write your own conclusion. I like having those notes to look back on, so I kept that part in.

    Nothing fancy — just a minimal tool that fits into a lightweight workflow. Works on Linux & Windows, needs only Python.

    GitHub: https://github.com/Mietkiewski/MPomidoro
    Gumroad PWYW $0+: https://mietkiewski.gumroad.com/l/mpomidoro

    [–] [S] 2 points 6 months ago (2 children)

    For anyone wondering how a session looks, here’s a small example:

    Title: Plan the weekly tasks
    Work interval time in Minutes: 15
    Break interval time in Minutes: 5
    Intervals Count: 3
    
    Pomidoro
    Plan the weekly tasks
    3 x 15min 5min
    
    WORK #1 15min
    BREAK #1 5min
    WORK #2 15min
    BREAK #2 5min
    WORK #3 15min
    BREAK #3 5min
    
    Conclusions: This session helped me organize my thoughts.
    

    The tool asks for a short conclusion at the end — I found that part surprisingly helpful for wrapping up a session.

  • source
  •  

    I wanted a simple Pomodoro timer that works locally, offline, and doesn’t require an account or sync anything to the cloud. Most Pomodoro apps I tried were SaaS‑based or came with way more features than I needed... So I built MPomidoro.

    It runs entirely in the terminal and keeps everything on your machine.

    What it does:

    • runs locally, no cloud, no telemetry
    • no accounts, no sync
    • configurable work/break intervals and cycle count
    • guides you through each Pomodoro stage
    • generates a small session report at the end

    works on Windows and Linux (Python, no external deps)

    It’s not a “self‑hosted service”, but it is a local‑first alternative to Pomodoro apps that store data online. Sharing it here in case anyone prefers lightweight, offline tools.

    GitHub: https://github.com/Mietkiewski/MPomidoro

    Gumroad PWYW $0+: https://mietkiewski.gumroad.com/l/mpomidoro