Skip to content

adapt broadcast lists behaviour to reality #1124

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

Merged
merged 2 commits into from
Jun 3, 2025

Conversation

r10s
Copy link
Member

@r10s r10s commented May 28, 2025

if we force re-translation because of #1123 , we should also strike the other out-of-date claims.

once this is merged, we can push strings to translators.

(in general, i do not think, it makes much sense to explain experimental features in details in the faq, it seems better to link to a forum entry or to a PR - or just say nothing and move things a bit more out of sight in the UI, with a warning. experimental things should mostly be used when ppl are know what they're doing by other sources. as of 2025, we do not really want to play avg users play around with that :)

@r10s r10s requested a review from missytake May 28, 2025 11:12
Copy link

github-actions bot commented May 28, 2025

@r10s r10s requested a review from adbenitez May 28, 2025 11:14
Copy link
Contributor

@missytake missytake left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, I see how we should fix "users can reply to broadcast lists".

But removing all the other content... I don't see how that helps anyone? And I think it triggers a retranslation, or is that triggered anyway? Maybe we should wait until the new feature is ready...

overall I'm +- 0 on this change.

Co-authored-by: missytake <[email protected]>
@r10s
Copy link
Member Author

r10s commented Jun 2, 2025

But removing all the other content... I don't see how that helps anyone?

it is wrong and misleading:

  • "you get the reply in your direct 1:1 chat with them." -> wrong, it creates own chats EDIT: ah, that is meant for replies, not for receiving. still, iirc this comes from a time where received was also in 1:1
  • "technically, it is an E-Mail with many recipients in BCC." -> we do not want to talks about email, bcc etc. this is not helpful
  • Messages sent to broadcast lists are not encrypted. -> wrong
  • Explanation "why not encrypted" -> outdated
  • the remaining things will be outdated soon as well

i think, we should just say as few as possible about experiments, it is too fast outdated and no one takes care.

or is that triggered anyway

yes, it will be triggered by #1123 which i did not pushed yet to transifex to not force retranslation of wrong / outdated things

@missytake
Copy link
Contributor

yes, it will be triggered by #1123 which i did not pushed yet to transifex to not force retranslation of wrong / outdated things

Ah, we would need empty lines between the bullet points I guess :/ good to know for the future.

@r10s r10s merged commit 95223af into main Jun 3, 2025
3 checks passed
@r10s r10s deleted the r10s/broadcasts-are-encrypted-as-usual branch June 3, 2025 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants