Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: 既読拒否が動作しない #133

Closed
o935032445 opened this issue May 29, 2024 · 2 comments
Closed

[Bug]: 既読拒否が動作しない #133

o935032445 opened this issue May 29, 2024 · 2 comments
Labels
bug Something isn't working talk トーク関係

Comments

@o935032445
Copy link

提案内容

オープン
「常に既読つけない」

返信後、
受信者既読表示されます
この機能を追加することは可能でしょうか?

ごめんなさい、私の日本語は上手ではありません.

Read on/after reply (常に既読をつけない must active too)

@o935032445 o935032445 added the enhancement New feature or request label May 29, 2024
@s1204IT s1204IT added bug Something isn't working talk トーク関係 and removed enhancement New feature or request labels Jun 1, 2024
@s1204IT s1204IT changed the title [Feature Request]: 受信者既読表示されます [Bug]: 既読拒否が動作しない Jun 1, 2024
@s1204IT
Copy link
Collaborator

s1204IT commented Jun 1, 2024

Since the meaning may change if translated into Japanese, please write in English from now on.


Just to double check, even if I turn on the setting to never mark messages as read, does that mean the other person will still see the message as read?

@o935032445
Copy link
Author

Since the meaning may change if translated into Japanese, please write in English from now on.

Just to double check, even if I turn on the setting to never mark messages as read, does that mean the other person will still see the message as read?

I already understand how to use it.
Thank you for making time for me. thank you so much.

@s1204IT s1204IT closed this as completed Jun 4, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working talk トーク関係
Projects
None yet
Development

No branches or pull requests

2 participants