You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's add an option to turn off for good the onboarding prompt.
Motivation
Last week #25267 added a new onboarding prompt that is great for newcomers. But it might be merely visual pollution for more experienced users who limit their social bubbles to a few people. These users know about all the features advertised in the new onboarding prompt but would continue to see them regardless. We can give them the option to dismiss it for good.
Possible solutions
I am happy to draft a PR with any of these options:
Cookie: we can add a “dismiss for good” (with nicer wording) link on the prompts, and upon click, we create a cookie, then we check for this cookie before rendering the prompt — pros, easier to implement (only frontend); cons, non-persistent.
User option: to be implemented in the /settings/preferences/appearance and persisted with the user settings — pros, persistent; cons, more complex implementation (backend migration, backend validation, frontend rendering)
The text was updated successfully, but these errors were encountered:
AFAIK the prompt dismissal is already persisted in localStorage, which is equivalent to 1). 2) could be nice if you use Mastodon Web on multiple devices.
I would like it to be remembered in the account. Lately I've been deleting Mastodon storage in my browser after I visit, due to a desperate lack of space on my phone, and it's annoying to be greeted with that message every time I log back in.
Pitch
Let's add an option to turn off for good the onboarding prompt.
Motivation
Last week #25267 added a new onboarding prompt that is great for newcomers. But it might be merely visual pollution for more experienced users who limit their social bubbles to a few people. These users know about all the features advertised in the new onboarding prompt but would continue to see them regardless. We can give them the option to dismiss it for good.
Possible solutions
I am happy to draft a PR with any of these options:
/settings/preferences/appearance
and persisted with the user settings — pros, persistent; cons, more complex implementation (backend migration, backend validation, frontend rendering)The text was updated successfully, but these errors were encountered: