tg-bulk-leave is something you run when you remember to. You notice the clutter, you run a dry run, you leave 40 groups, and six months later you're back where you started.
The obvious next thing is the version that just keeps your account tidy on its own — leaving stale groups on a schedule without you thinking about it. Something like "anything with no activity in 60 days that I've never posted in", checked weekly.
That needs an always-on machine, which the CLI deliberately isn't. So rather than build it and hope, I'd like to find out whether anyone actually wants it.
If you'd use it
- 👍 this issue — that alone is a useful signal and costs you nothing.
- Better: open a recurring-cleanup issue. It's four short fields: how often, how many chats, what rule, and whether you'd pay.
- Or just reply here in your own words. Describing why the keyword approach doesn't fit your situation is more useful than filling in the form.
"I wouldn't use it" is worth saying too. Right now I can't tell the difference between nobody wanting this and nobody having found the project, and those call for opposite decisions.
What won't change
The CLI stays free, open source, and local-first. Your session never leaves your machine, and no amount of interest in a hosted version changes that — it would be a separate, opt-in thing.
Worth being upfront about the catch, since it's the reason this isn't already built: Telegram has no scoped permissions. There's no "this app may leave groups" grant — it's a full account session or nothing. Any hosted service therefore has to hold a credential equivalent to your account. That's a real cost, it's why the local-first CLI exists, and if a hosted version is ever built that trade-off gets documented on the front page rather than buried.
This issue stays open on purpose — it's where the answer gets collected, not a task.
tg-bulk-leaveis something you run when you remember to. You notice the clutter, you run a dry run, you leave 40 groups, and six months later you're back where you started.The obvious next thing is the version that just keeps your account tidy on its own — leaving stale groups on a schedule without you thinking about it. Something like "anything with no activity in 60 days that I've never posted in", checked weekly.
That needs an always-on machine, which the CLI deliberately isn't. So rather than build it and hope, I'd like to find out whether anyone actually wants it.
If you'd use it
"I wouldn't use it" is worth saying too. Right now I can't tell the difference between nobody wanting this and nobody having found the project, and those call for opposite decisions.
What won't change
The CLI stays free, open source, and local-first. Your session never leaves your machine, and no amount of interest in a hosted version changes that — it would be a separate, opt-in thing.
Worth being upfront about the catch, since it's the reason this isn't already built: Telegram has no scoped permissions. There's no "this app may leave groups" grant — it's a full account session or nothing. Any hosted service therefore has to hold a credential equivalent to your account. That's a real cost, it's why the local-first CLI exists, and if a hosted version is ever built that trade-off gets documented on the front page rather than buried.
This issue stays open on purpose — it's where the answer gets collected, not a task.