├── .env_example ├── .gitignore ├── .vscode └── launch.json ├── LICENSE ├── QuickReplyBot ├── __init__.py └── __main__.py ├── README.en.md ├── README.md └── quick_reply.json /.env_example: -------------------------------------------------------------------------------- 1 | # 留空则不使用搭理。 2 | PROXY_URI=http://127.0.0.1:10809 3 | # 机器人Token 4 | BOT_TOKEN=8060933xxxxxxxxxxxxxxxxhUJaoxn0KSvw 5 | 6 | # 管理员ID，多个用逗号隔开 7 | ADMIN_IDS=530586633,1281631753 8 | 9 | # 激发的关键词 10 | INLINE_COMMAND=show -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Byte-compiled / optimized / DLL files 2 | __pycache__/ 3 | *.py[cod] 4 | *$py.class 5 | 6 | # C extensions 7 | *.so 8 | 9 | # Distribution / packaging 10 | .Python 11 | build/ 12 | develop-eggs/ 13 | dist/ 14 | downloads/ 15 | eggs/ 16 | .eggs/ 17 | lib/ 18 | lib64/ 19 | parts/ 20 | sdist/ 21 | var/ 22 | wheels/ 23 | share/python-wheels/ 24 | *.egg-info/ 25 | .installed.cfg 26 | *.egg 27 | MANIFEST 28 | 29 | # PyInstaller 30 | # Usually these files are written by a python script from a template 31 | # before PyInstaller builds the exe, so as to inject date/other infos into it. 32 | *.manifest 33 | *.spec 34 | 35 | # Installer logs 36 | pip-log.txt 37 | pip-delete-this-directory.txt 38 | 39 | # Unit test / coverage reports 40 | htmlcov/ 41 | .tox/ 42 | .nox/ 43 | .coverage 44 | .coverage.* 45 | .cache 46 | nosetests.xml 47 | coverage.xml 48 | *.cover 49 | *.py,cover 50 | .hypothesis/ 51 | .pytest_cache/ 52 | cover/ 53 | 54 | # Translations 55 | *.mo 56 | *.pot 57 | 58 | # Django stuff: 59 | *.log 60 | local_settings.py 61 | db.sqlite3 62 | db.sqlite3-journal 63 | 64 | # Flask stuff: 65 | instance/ 66 | .webassets-cache 67 | 68 | # Scrapy stuff: 69 | .scrapy 70 | 71 | # Sphinx documentation 72 | docs/_build/ 73 | 74 | # PyBuilder 75 | .pybuilder/ 76 | target/ 77 | 78 | # Jupyter Notebook 79 | .ipynb_checkpoints 80 | 81 | # IPython 82 | profile_default/ 83 | ipython_config.py 84 | 85 | # pyenv 86 | # For a library or package, you might want to ignore these files since the code is 87 | # intended to run in multiple environments; otherwise, check them in: 88 | # .python-version 89 | 90 | # pipenv 91 | # According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control. 92 | # However, in case of collaboration, if having platform-specific dependencies or dependencies 93 | # having no cross-platform support, pipenv may install dependencies that don't work, or not 94 | # install all needed dependencies. 95 | #Pipfile.lock 96 | 97 | # poetry 98 | # Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control. 99 | # This is especially recommended for binary packages to ensure reproducibility, and is more 100 | # commonly ignored for libraries. 101 | # https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control 102 | #poetry.lock 103 | 104 | # pdm 105 | # Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control. 106 | #pdm.lock 107 | # pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it 108 | # in version control. 109 | # https://pdm.fming.dev/latest/usage/project/#working-with-version-control 110 | .pdm.toml 111 | .pdm-python 112 | .pdm-build/ 113 | 114 | # PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm 115 | __pypackages__/ 116 | 117 | # Celery stuff 118 | celerybeat-schedule 119 | celerybeat.pid 120 | 121 | # SageMath parsed files 122 | *.sage.py 123 | 124 | # Environments 125 | .env 126 | .venv 127 | env/ 128 | venv/ 129 | ENV/ 130 | env.bak/ 131 | venv.bak/ 132 | 133 | # Spyder project settings 134 | .spyderproject 135 | .spyproject 136 | 137 | # Rope project settings 138 | .ropeproject 139 | 140 | # mkdocs documentation 141 | /site 142 | 143 | # mypy 144 | .mypy_cache/ 145 | .dmypy.json 146 | dmypy.json 147 | 148 | # Pyre type checker 149 | .pyre/ 150 | 151 | # pytype static type analyzer 152 | .pytype/ 153 | 154 | # Cython debug symbols 155 | cython_debug/ 156 | 157 | # PyCharm 158 | # JetBrains specific template is maintained in a separate JetBrains.gitignore that can 159 | # be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore 160 | # and can be added to the global gitignore or merged into this file. For a more nuclear 161 | # option (not recommended) you can uncomment the following to ignore the entire idea folder. 162 | #.idea/ 163 | -------------------------------------------------------------------------------- /.vscode/launch.json: -------------------------------------------------------------------------------- 1 | { 2 | // 使用 IntelliSense 了解相关属性。 3 | // 悬停以查看现有属性的描述。 4 | // 欲了解更多信息，请访问: https://go.microsoft.com/fwlink/?linkid=830387 5 | "version": "0.2.0", 6 | "configurations": [ 7 | { 8 | "name": "QuickReplyBot", 9 | "type": "debugpy", 10 | "request": "launch", 11 | "module": "QuickReplyBot" 12 | } 13 | ] 14 | } -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /QuickReplyBot/__init__.py: -------------------------------------------------------------------------------- 1 | import os 2 | import logging 3 | from dotenv import load_dotenv 4 | 5 | # 配置日志记录器 6 | logging.basicConfig( 7 | level=logging.INFO, 8 | format="%(asctime)s %(name)s- %(levelname)s - %(message)s", 9 | handlers=[logging.StreamHandler(), logging.FileHandler("log.txt")], 10 | ) 11 | logging.getLogger("httpx").setLevel(logging.ERROR) 12 | logger = logging.getLogger("QuickReplyBot") 13 | 14 | 15 | load_dotenv(override=True) 16 | bot_token = os.getenv("BOT_TOKEN") or exit("BOT_TOKEN not found in .env file") 17 | try: 18 | admin_ids = [ 19 | int(x.strip()) for x in os.getenv("ADMIN_IDS").replace("，", ",").split(",") 20 | ] or exit("ADMIN_IDS 未填写") 21 | log_group_id = int(os.getenv("LOG_GROUP_ID")) if os.getenv("LOG_GROUP_ID") else None 22 | except Exception as e: 23 | exit(f"ADMIN_IDS 或者 LOG_GROUP_ID 格式错误。需要是整数。{e}") 24 | proxy_uri = os.getenv("PROXY_URI") 25 | inline_cmd = os.getenv("INLINE_COMMAND", "show") 26 | -------------------------------------------------------------------------------- /QuickReplyBot/__main__.py: -------------------------------------------------------------------------------- 1 | import json 2 | 3 | from telegram import ( 4 | InlineKeyboardButton, 5 | InlineKeyboardMarkup, 6 | Update, 7 | InlineQueryResultArticle, 8 | InputTextMessageContent, 9 | ) 10 | from telegram.ext import ( 11 | ApplicationBuilder, 12 | CallbackQueryHandler, 13 | CommandHandler, 14 | InlineQueryHandler, 15 | ContextTypes, 16 | PicklePersistence, 17 | filters, 18 | ) 19 | from . import bot_token, proxy_uri, admin_ids, logger, inline_cmd 20 | import uuid 21 | 22 | 23 | async def start(update: Update, context: ContextTypes): 24 | user = update.effective_user 25 | if not user.id in admin_ids: 26 | await update.effective_chat.send_message( 27 | "⚠️ You are not allowed to use this bot." 28 | ) 29 | return 30 | await update.effective_chat.send_message( 31 | f"Hi, {user.first_name}, I am working now." 32 | ) 33 | 34 | 35 | def get_quickreply(): 36 | with open("./quick_reply.json", "r", encoding="utf-8") as f: 37 | data = json.load(f) 38 | return data 39 | 40 | 41 | async def on_inline_query(update: Update, context: ContextTypes): 42 | query = update.inline_query.query 43 | user = update.inline_query.from_user 44 | if not user.id in admin_ids: 45 | query.answer([]) 46 | if not query: 47 | return 48 | 49 | result = [] 50 | for idx, quick_reply in enumerate(get_quickreply()): 51 | params = { 52 | "id": uuid.uuid4().hex, 53 | "title": quick_reply["title"], 54 | } 55 | buttons = quick_reply.get("buttons", []) 56 | btn_matrx = [] 57 | for btn_row in buttons: 58 | row = [] 59 | for btn in btn_row: 60 | row.append(InlineKeyboardButton(btn["text"], url=btn["url"])) 61 | btn_matrx.append(row) 62 | keyboard = InlineKeyboardMarkup(btn_matrx) 63 | params["reply_markup"] = keyboard 64 | params["input_message_content"] = InputTextMessageContent( 65 | f"{quick_reply['title']}\n\n{quick_reply['msg']}", parse_mode="HTML" 66 | ) 67 | 68 | result.append(InlineQueryResultArticle(**params)) 69 | await update.inline_query.answer(result) 70 | 71 | 72 | async def error_handler(update: Update, context: ContextTypes): 73 | logger.error(f"Update: {update} caused error: {context.error}") 74 | # await update.effective_chat.send_message(f"An error occurred: {context.error}") 75 | 76 | 77 | if __name__ == "__main__": 78 | pickle_persistence = PicklePersistence(filepath=f"./cache.pickle") 79 | application = ( 80 | ApplicationBuilder() 81 | .token(bot_token) 82 | .persistence(persistence=pickle_persistence) 83 | ) 84 | if proxy_uri: 85 | application = application.proxy(proxy_uri).get_updates_proxy(proxy_uri).build() 86 | else: 87 | application = application.build() 88 | 89 | application.add_handler( 90 | CommandHandler( 91 | "start", 92 | start, 93 | filters.ChatType.PRIVATE, 94 | ) 95 | ) 96 | application.add_handler( 97 | InlineQueryHandler(on_inline_query, pattern=f"^{inline_cmd}") 98 | ) 99 | application.add_error_handler(error_handler) 100 | application.run_polling(allowed_updates=Update.ALL_TYPES) 101 | -------------------------------------------------------------------------------- /README.en.md: -------------------------------------------------------------------------------- 1 | # TelegramQuickReplyBot 2 | A Telegram bot that supports custom message sending with buttons, making quick replies very convenient. 3 | 4 | ## Introduction 5 | When chatting in a gossip group on Telegram, it’s always nice to have a quick reply option. However, due to Telegram’s policies, replying with button messages is basically impossible, even if you are a premium member. 6 | 7 | Therefore, I developed a simple InlineBot that allows for convenient message replies, along with a few URL buttons. It’s visually appealing. 8 | 9 | ### Example Effect: 10 | ![image](https://github.com/user-attachments/assets/f6bfeec2-40fd-437e-8f2b-198b47a652e8) 11 | 12 | ### Activation Method: 13 | ![image](https://github.com/user-attachments/assets/0ef91fcc-3f21-4f08-80b5-fbe76eb34429) 14 | 15 | The general format is to type @this_bot, followed by a space, and then enter the command. The commands can be configured (in the example, I used "show"). 16 | 17 | ## Prerequisites 18 | 1. Find @Botfather to create a bot. 19 | 2. Obtain the bot token. 20 | 3. Enable inline mode for the bot. 21 | 4. Configure the `.env` file (you can rename `.env_example` to get it). 22 | 5. Configure as needed. If you need IDs, you can find @GetTheirIDBot (yes, I also wrote this). 23 | 24 | ## Deployment 25 | ```bash 26 | git clone https://github.com/MiHaKun/TelegramQuickReplyBot.git 27 | cd TelegramQuickReplyBot 28 | python3 -m venv venv 29 | . venv/bin/activate 30 | pip install -r requirements.txt 31 | ``` 32 | 33 | ## Execution 34 | ```bash 35 | python -m QuickReplyBot 36 | ``` 37 | 38 | ## Quick Reply Phrase Configuration 39 | Refer to the `quick_reply.json` file. 40 | ![image](https://github.com/user-attachments/assets/ef5d0c5b-4e75-4b82-92c5-c26a655c3cb4) 41 | 42 | You can see the effect in the first image of this document. 43 | 44 | ## To-Do List 45 | - [ ] Add image and video message support. 46 | - [ ] Create a hosted version to save users from having to deploy it themselves. 47 | - [ ] Implement measures to prevent abuse. 48 | 49 | ## About 50 | 51 | - This product is open-sourced under the Apache license. 52 | - The author, Mi Ha ([@MrMiHa](https://t.me/MrMiHa)), is a struggling programmer, not a coal yard slave. Please don’t come demanding commands too assertively. 53 | - Discussion group: https://t.me/DeveloperTeamGroup. Feel free to join and have fun. 54 | - Feel free to fork, but please retain the "About" section. 55 | - The first version was completed in 2 hours. If you like it, consider donating. If you have trouble deploying, feel free to ask me in the group. 56 | - Recommended server: RackNerd. In fact, I use it myself. It’s affordable. This option is sufficient: [2 cores, 3GB - $27/year](https://my.racknerd.com/aff.php?aff=11705&pid=828). 57 | - If you really can’t manage the deployment, you can ask people in the group for help. You can also find shared servers here: https://t.me/DeveloperTeamGroup. 58 | - If you absolutely cannot handle the deployment, contact [@MrMiHa](https://t.me/MrMiHa) for paid deployment assistance. 59 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # TelegramQuickReplyBot 2 | Telegram中支持按钮的自定义消息发送机器人。作为快速回复很方便。Telegram supports custom message-sending bots with buttons, making quick replies very convenient. 3 | 4 | [English Readme](https://github.com/MiHaKun/TelegramQuickReplyBot/blob/master/README.en.md) 5 | 6 | # 简介 7 | TG八卦水群的时候，总是希望有个快捷回复。同时，受限于Telegram的政策，想回复按钮消息基本是不可能的，是的，你是高级会员也没这功能。 8 | 9 | 所以，就开发了一个简单的InlineBot，可以方便的回复消息，顺便添加几个url按钮。美观大方。 10 | 11 | 效果如图： 12 | ![image](https://github.com/user-attachments/assets/f6bfeec2-40fd-437e-8f2b-198b47a652e8) 13 | 14 | 15 | 激发方式： 16 | ![image](https://github.com/user-attachments/assets/0ef91fcc-3f21-4f08-80b5-fbe76eb34429) 17 | 18 | 19 | 大概的格式就是 @这个机器人 ， 空格，然后打入命令。命令可以自己配置（图例上，我使用show） 20 | 21 | # 准备工作 22 | 1. 找 @Botfather 申请一个机器人 23 | 2. 获取机器人token 24 | 3. 打开机器人的inline mode 25 | 4. 配置 .env 文件（可以把 .env_example 改名获得） 26 | 5. 按需配置。如果需要id，可以找 @GetTheirIDBot 获取。（没错，也是我写的） 27 | 28 | # 部署 29 | ```bash 30 | git clone https://github.com/MiHaKun/TelegramQuickReplyBot.git 31 | cd TelegramQuickReplyBot 32 | python3 -m venv venv 33 | . venv/bin/activate 34 | pip install -r requirements.txt 35 | ``` 36 | 37 | # 执行 38 | ```bash 39 | python -m QuickReplyBot 40 | ``` 41 | 42 | # 快速回复短语配置 43 | 参看文件内的 `quick_reply.json` 。 44 | ![image](https://github.com/user-attachments/assets/ef5d0c5b-4e75-4b82-92c5-c26a655c3cb4) 45 | 46 | 47 | 效果可以看看本文档第一张图。 48 | 49 | 很多伙计懒得配置相对复杂的按钮。这里提供个快速工具： 50 | 51 | 可以访问： https://miha.uk/tools/QuickReplyEditor 52 | ![image](https://github.com/user-attachments/assets/74744372-fc8b-4f8b-b694-222c31bd0684) 53 | 54 | 55 | 56 | # ToDoList 57 | - [ ] 增加图片和视频消息 58 | - [ ] 做个可以托管的，省的大家自己部署了。 59 | - [ ] 添加防止滥用的方案 60 | 61 | 62 | # 关于 63 | 64 | - 本产品基于Apache协议开源。 65 | - 作者 米哈( [@MrMiHa](https://t.me/MrMiHa) )是一个苦逼程序员，不是煤场奴工，有问题别太理直气壮的跑来下命令。 66 | - 讨论群组是 : https://t.me/DeveloperTeamGroup 欢迎加入后玩耍 67 | - 随意Fork，记得保留`关于`的内容。 68 | - 初版写了2小时。喜欢请打赏。不会部署，群里找我。 69 | - 服务器推荐RackNerd的。实际上，我也确实用这个。够便宜。这款就够：[2核3G--年27刀](https://my.racknerd.com/aff.php?aff=11705&pid=828) 70 | - 实在搞不定部署，可以群里找大家帮忙部署下。服务器也可以找大家共用： https://t.me/DeveloperTeamGroup 71 | - 实在实在实在搞不定部署，找 [@MrMiHa](https://t.me/MrMiHa) 同学付费部署…… 72 | -------------------------------------------------------------------------------- /quick_reply.json: -------------------------------------------------------------------------------- 1 | [ 2 | { 3 | "title": "简介", 4 | "msg": "米哈的群组频道信息\n群组： https://t.me/DeveloperTeamGroup\n频道： https://t.me/TGBotDevelopment\n网站： https://miha.uk ", 5 | "buttons": [ 6 | [ 7 | { 8 | "text": "米哈的频道", 9 | "url": "https://t.me/TGBotDevelopmen" 10 | }, 11 | { 12 | "text": "米哈的群组", 13 | "url": "https://t.me/DeveloperTeamGroup" 14 | } 15 | ], 16 | [ 17 | { 18 | "text": "米哈的网站", 19 | "url": "https://miha.uk" 20 | } 21 | ], 22 | [ 23 | { 24 | "text": "联络米哈", 25 | "url": "https://t.me/MrMiHa" 26 | } 27 | ] 28 | ] 29 | } 30 | ] --------------------------------------------------------------------------------