多个Telegram 账号对应同一个 memos 账号

[cuiyanjie]

Is your feature request related to a problem?

多个Telegram用户的User ID 填入 Memos同一个账号中，便于多人共同往同一个Memos 账号下记录内容。

Describe the solution you'd like

Additional context

No response

[Issues-translate-bot]

Issue is not in English. It has been translated automatically.

---

Title: Multiple Telegram accounts correspond to the same memos account

[jkjoy]

你这个要求有点离谱,一个人一个账户不好么...不明白你这样的需求是什么

[Issues-translate-bot]

Issue is not in English. It has been translated automatically.

---

Your request is a bit outrageous, isn’t it good for one account per person... I don’t understand what your demand is

[cuiyanjie]

因为每个Memos账号只能看到自己的卡片，想要多人共同看彼此发的卡片就得设置成公共可见还得切换成探索模式。 这个需求其实场景挺多的，比如：1.几个家长共同记录孩子成长，如果分不同账号，就看不到别人记录的。2.定向运动几个人共同打卡同一场次目标 3.一个项目组共同写一个日志。还有很多场景。虽然分账号1对1也可以，但不如多对1方便。 其实模型类似，公司大群，里面有项目组小群，又有几个关系好的再拉私群。多对1可以实现，几个人共同记录，且设置成私有可见，这样其他人在这里用别的账号记录就看不到了。还有其他原因，本质就是一个排列组合问题，如果有了这个多对一，应用领域又可以拓展很多。

[Issues-translate-bot]

Issue is not in English. It has been translated automatically.

---

Because each Memos account can only see its own cards, if multiple people want to see each other’s cards together, they must be set to public visibility and switched to explore mode.

[jkjoy]

那你使用web共享账号直接发不就好了?更何况还有各种API,何必用TG呢.为了你想拥有的功能去开发一堆对其他人而言没实用性的功能我觉得不大可能

[Issues-translate-bot]

Issue is not in English. It has been translated automatically.

---

Then you can use the web sharing account to send it directly? What’s more, there are various APIs, why use TG? I don’t think it’s a big deal to develop a bunch of functions that are not practical for others for the functions you want. possible

[cuiyanjie]

作者让我这里提一下的哦

[Issues-translate-bot]

Issue is not in English. It has been translated automatically.

---

The author asked me to mention it here

[athurg]

因为每个Memos账号只能看到自己的卡片，想要多人共同看彼此发的卡片就得设置成公共可见还得切换成探索模式。 这个需求其实场景挺多的，比如：1.几个家长共同记录孩子成长，如果分不同账号，就看不到别人记录的。2.定向运动几个人共同打卡同一场次目标 3.一个项目组共同写一个日志。还有很多场景。虽然分账号1对1也可以，但不如多对1方便。 其实模型类似，公司大群，里面有项目组小群，又有几个关系好的再拉私群。多对1可以实现，几个人共同记录，且设置成私有可见，这样其他人在这里用别的账号记录就看不到了。还有其他原因，本质就是一个排列组合问题，如果有了这个多对一，应用领域又可以拓展很多。

「家长记录孩子成长」

这种场景，其实用「登录模式可见」或者「公开可见」是能满足需求的。

「定向运动」或者「小组日志记录」

这种背后的逻辑，其实并不是「多个人一起记录」，而是希望将可见范围，从「全体」、「登录用户」、「自己」三个固定的类别进行拓展，拓展为可配置的、指定范围的「用户组」。

这就不光是「Telegram账号多对一」，而是对整个权限系统需要重新设计。这样一来，不光是Telegram发送的消息，包括网页上发送的消息都应该有对应的支持和改造。

虽然我们可以只在或者先在Telegram实现，但是毕竟是一个半成品。如果设计上完善，实现上可以分步做。但如果设计上没有完善，不建议动手。

建议

就现阶段来讲，我建议这种共享账号发送的场景，有两种办法：

• 可以自己调用API；
• 或者通过共享一个账号/密码/AccessKey

其中第二种方案也不存在敏感信息泄露的问题。因为如果多个人都能发同样的Memo和看同样的Memo，那他们本质上就是一样的了。

[Issues-translate-bot]

Issue is not in English. It has been translated automatically.

---

Because each Memos account can only see its own cards, if multiple people want to see each other’s cards together, they must be set to public visibility and switched to explore mode. There are actually many scenarios for this requirement, for example: 1. Several parents record the growth of their children together. If they are divided into different accounts, they will not be able to see other people's records. 2. Several people in orienteering work together to punch in the same goal. 3. A project team writes a log together. There are many more scenes. Although 1-to-1 with sub-accounts is also possible, it is not as convenient as multi-to-1. In fact, the model is similar, with a large company group, a small project team group, and several private groups with good relationships. Many to 1 can be achieved, several people record together, and set it as private and visible, so that other people can't see it when they record with other accounts here. There are other reasons. The essence is a permutation and combination problem. If there is this many-to-one, the application field can be expanded a lot.

h2. "Parents record children's growth" In this scenario, the practical "login mode visible" or "publicly visible" can meet the needs.

h2. "Orienteering" or "Group Journaling" The logic behind this is not actually "multiple people record together", but to expand the scope of visibility from three fixed categories of "all", "login users", and "self" to configurable, Specify a range of User Groups.

This is not just "many-to-one Telegram accounts", but the entire permission system needs to be redesigned. In this way, not only the messages sent by Telegram, but also the messages sent on the webpage should have corresponding support and transformation.

Although we can implement it only or first in Telegram, it is a semi-finished product after all. If the design is perfect, the implementation can be done step by step. But if the design is not perfect, it is not recommended to do it.

h2. Recommendation As far as the current stage is concerned, I suggest that there are two methods for this shared account sending scenario:

• You can call the API yourself;
• or by sharing an account/password/AccessKey

The second option also does not have the problem of sensitive information leakage. Because if multiple people can post the same Memo and watch the same Memo, then they are essentially the same.