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.
mietkiewski_dev
joined 1 week ago
Yeah, intentional — I wiped my old GitHub and started fresh for new projects. Files are distributed as PWYW 0$+, so default “all rights reserved” for now.
Yeah, for me it’s just a local, minimal tool for longer tasks like coding or app design. Nothing cloud‑based, nothing fancy.
That’s a cool approach. MPomidoro is simpler — for me it’s meant for longer tasks like coding or app design, so I kept it minimal: fixed work interval + fixed break, no adaptive logic. app.flowmo.io is more for multitasking I see.
Yeah, it’s a pretty simple time‑management method — short focused work blocks with breaks in between. I just wanted a minimal version of it that works in the terminal.
It prints the stage transitions, but the actual countdown runs in the terminal as MM:SS. When a work or break interval finishes, it marks the line in green so it’s easy to spot.
Starting is usually the hardest part for me. Curious what helps you get going — especially if you also prefer simple tools over big apps.
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.
Fair point. This one started as a personal experiment, not a stance. I’m mainly trying to understand whether the pushback is more about ethics, practicality, or just Fediverse culture.