clav88

11 ms·

1.
by clav88 1y ago
Thanks very much! There is some rate limiting being applied so that costs don’t explode. If people are willing to pay for it, the rate limiting can of course be reduced a lot. I was thinking that sharing and monitoring progress is more usef
2.
by clav88 1y ago
Thanks very much! A minimal approach is indeed one of the goals.
3.
by clav88 1y ago
I agree, many of the monitoring tools are much more powerful than this, but also a lot harder to set up. The goal was to build something with as little friction as possible that you can set up in under a minute, which makes it viable for an
4.
by clav88 1y ago
No plans at this point, but I'm planning to open source it soon, so you can add the MCP API if you like and start building the "social layer for progress bars" ;)
5.
by clav88 1y ago
Interesting! I agree that nested / hierarchical progress is not straightforward. Even if all child problems are known, the weighting between their individual progress to compute the overall, aggregated parent progress is not easy to de
6.
by clav88 1y ago
Yes, definitely. The service could easily be scaled and rate limits can be increased if users are willing to pay for. Self-hosting is a good alternative, as you already suggested. I'll work on cleaning up the code, adding some dev docu
7.
by clav88 1y ago
It's a Next.js app currently deployed on vercel with a Postgres DB running on supabase. Both are fairly scalable, but not in an optimal way in terms of costs. I'd either have to introduce a Pro pricing plan or get some donations f
8.
by clav88 1y ago
Thanks for trying it! The link works for me. The progress bar shows 1% now that there's 1 comment and should update to 2% after my reply ;) I'm happy to clean up the source a bit and put it on GitHub if people like it and prefer t
9.
Show HN: Pbar.io – Distributed progress bars that work in terminals and browsers(pbar.io)
25 points by clav88 1y ago|19 comments