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

Allow users to add Explore to Search view #2102

Open
theAdhocracy opened this issue May 16, 2023 · 5 comments · May be fixed by #3196
Open

Allow users to add Explore to Search view #2102

theAdhocracy opened this issue May 16, 2023 · 5 comments · May be fixed by #3196
Labels
c: feature Request for new feature c: parity Parity with Mastodon web app s: accepted Accepted feature / Confirmed bug

Comments

@theAdhocracy
Copy link

I see that a recent PR (#2075) has removed the Explore functionality from the Search view. I'm requesting an option in the settings to revert that change, so that this decision can be determined by the user.

Whilst I understand the reasoning given (mainly expanded on here: #1301 (comment)) this was/is a core feature of Mastodon. Explore is the primary method on the platform for keeping up with breaking news, engaging in community discussions, and facilitating content discovery. This is particularly the case if you're on a mid-to-large-sized instance, where the Local and Federated timelines are often too busy to provide meaningful value.

Locking that functionality away behind a multi-step menu – particularly on mobile – is problematic.

I see that there is already ongoing discussion around making the mobile navigation (and perhaps all Homepage navigation) more customisable in the future (#641), but as this is a much larger change (with little interaction since January), I'd suggest a toggle would be a more immediate, beneficial solution.

This can be defaulted to "off" to preserve the original concerns around doomscrolling and cluttering up the Search interface, and would make sense to nest within the Wellbeing section of the Preferences panel. But for those of us who actively use, and benefit from, this feature, simply removing it feels like a regressive step to take.

@theAdhocracy theAdhocracy added the s: pending triage Pending Triage label May 16, 2023
@stackblitz
Copy link

stackblitz bot commented May 16, 2023

Solve in StackBlitz Codeflow Start a new pull request in StackBlitz Codeflow.

@heaths
Copy link

heaths commented May 29, 2023

I appreciate the original reason it was removed as well, but a dedicated search button for a feature I almost never use (since searching on Mastodon is quite limited by design) is a bit of a waste of screen real estate. I'd rather replace the search button with explore, but also appreciate that is part of a much larger change to customization. A setting as a temporary compromise sounds like a great idea.

@shuuji3 shuuji3 added c: feature Request for new feature and removed s: pending triage Pending Triage labels Apr 5, 2024
@shuuji3
Copy link
Member

shuuji3 commented Apr 12, 2024

#2761 implemented the bottom nav buttons customization to allow users more flexible options in their preference. So we can now add both the Search button and the Explore/Local/Federated button to the bottom nav bar.

It doesn't directly include the explore view within the search page, I hope this customization can cover the different users' use cases.

@ayoayco
Copy link
Member

ayoayco commented Dec 8, 2024

Looks like people expect this because when on mobile screens in the Mastodon web client, tapping the 'search' and 'explore' icons both go to the same #Explore page with a search field and tabs showing trending posts.

Due to this, I think there's good reason to allow an opt-in setting for showing trending posts in the 'search' page.

@ayoayco ayoayco added the c: parity Parity with Mastodon web app label Dec 8, 2024
@ayoayco
Copy link
Member

ayoayco commented Dec 8, 2024

I think the setting could be a toggle "Use Explore page for Search" then we can embed the search field in the Explore page. Users can then hide the search icon via interface settings.

@shuuji3 shuuji3 added the s: accepted Accepted feature / Confirmed bug label Feb 8, 2025
@shuuji3 shuuji3 linked a pull request Feb 8, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: feature Request for new feature c: parity Parity with Mastodon web app s: accepted Accepted feature / Confirmed bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants