Heapy / Heapy/kotbot

Chat families

Open
#3 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
37
Forks
2
Avg merge
1h 35m
Merged PRs (30d)
5

Description

As we maintain a group of chats, the following things are quite logical to sync across them:

  • Restrictions
  • Admins

Reports sent by users, mentioned in #2, also assume connection between several chats and admin chat.

What do you thing about adding a thing called Family, which has a list of chats and an admin chat bound to it, with accompanying family management commands and mentioned synchronization?

My high-level vision on implementation:
In a chat with bot added admin can send a message /family. In response the bot would create a new family with empty chat list and current chat as an admin chat for it.
In admin chat, one can send /family-add message. The bot would respond with https://telegram.me/[botname]?startgroup=[id] link. This deep link opens chat picker. On selecting the chat bot gets added to it, and the user sends /start@botname message there (which can be removed automatically if the bot is already there and has admin rights or manually if not). This way we can setup linking between a family and new chat.
As soon as that's done and bot is granted admin rights, bot can synchronize mentioned items between chats.

Let me know if you approve the idea and if so, whether you have any notices on the usage flow.

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

No files, tests, or entry points are named. First clarify whether the proposed Family flow is approved, then define the scope for family management and synchronization of restrictions, admins, and reports across chats.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.