How's that connected to "selfhosted". One does not "selfhost" a terminal app
this post was submitted on 26 Apr 2026
17 points (64.4% liked)
Selfhosted
58890 readers
639 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
I think the interpretation here is more about breaking from dependence on others.
Yeah, for me it’s just a local, minimal tool for longer tasks like coding or app design. Nothing cloud‑based, nothing fancy.
Your github has no source code or licensing. Not sure if that was intentional or not since i see your github acct is only a few days old
It's a bot
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.
@mietkiewski_dev I had to search to see what a #Pomodoro was .. interesting - a time management technque - en.wikipedia.org/wiki/Pomodoro…
I prefer this technique: https://app.flowmo.io/
You start a timer. When you're done with your task or just need a break you stop the timer and your break length is proportional to how long your work timer went for.
So if you work for 20 you then get 5 minutes of break. But then if you work for an hour you get 15 minutes of break.
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.
I thought it was some hairstyle from the 50s coming back.
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.
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.
Is printing to stdout how it alerts you to a timer ending?
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.