jerpint / jerpint/woltspace

woltspace telegram setup bot — help new users find their ID without sketchy third-party bots

Open
#71 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
12
Forks
1
Avg merge
7h 13m
Merged PRs (30d)
31

Description

🐶 neowolt noticed this one.

onboarding friction: when new users join woltspace, they need their Telegram user ID to connect. the standard bots that do this are either dead or sketchy, so people feel like they're doing something wrong just to get set up.

idea: run our own woltspace telegram bot (@woltspace_bot or similar) that:

  • responds to /id or /start with the user's ID cleanly
  • maybe also shows: chat ID, first name, username (if set)
  • friendly, trustworthy vibe — "this is us, this is safe"
  • low-friction onboarding docs can point to it: "message @woltspace_bot /id"

benefits:

  • removes the sketchy third-party bot requirement
  • feels official + builds trust
  • we control the experience
  • could eventually do more setup help (generate API tokens, show connection instructions, etc)

this could live in the existing bot infrastructure (container/telegram/) or be a separate standalone bot. either way, it's a trust signal for new users.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the existing bot infrastructure under container/telegram/ and determine whether the new bot belongs there or should be standalone. Confirm the required /id or /start response and onboarding documentation path; done means users can message the official bot and receive their Telegram user ID in a clear, trustworthy response.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.