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

User profile: Dont show private discussions in the Discussions list #125

Open
pflstr opened this issue Jun 7, 2020 · 3 comments
Open

User profile: Dont show private discussions in the Discussions list #125

pflstr opened this issue Jun 7, 2020 · 3 comments
Assignees

Comments

@pflstr
Copy link

pflstr commented Jun 7, 2020

The idea that private messages in a Flarum forum are foremost discussions with added privacy is already difficult to sell to many users, most expect PM's to be something fundamentally different. For this reason, I put all private discussions in a dedicated tag and hide that tag from the All Discussions page.

In the user profile however, the Discussions list shows private discussions next to public ones despite the above mentioned setting. I suggest to either apply this setting (hide that tag from the All Discussions page) to the user profile as well or, probably less confusing, introduce a new setting for Byobu: Show private discussions in All Discussions and the Discussions section of the user profile.

@sibidharan

This comment has been minimized.

@ayyilmaz
Copy link

Is there any news?

@DavideIadeluca DavideIadeluca self-assigned this Jun 15, 2024
@DavideIadeluca
Copy link
Member

Thanks @pflstr for your issue. In the meantime, we actually implemented a new setting called "Hide PDs from "All Discussions" page" which resolves some of the concerns you have. Private discussions will still show up in the discussions list in the user profile currently. I see two ways how to proceed here:

  1. Remove Private discussions from the discussions list in the user profile.
  2. Add a new Link on the user profile to only show private discussions, while also implementing the first option
  3. Leave the logic as it is

I would tend to implement option 2, as I can understand the potential confusion described by @pflstr very well. Opinions @luceos @clarkwinkelmann ?

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

No branches or pull requests

4 participants