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
This is not a priority right now, but mindful of our user's experience, we should only require login where an interaction with the database is required. A register/sign in dailogue should replace login notices for unauthenticated users for all instances where a login notice is currently given (e.g. "You must be logged in to edit a new third party profile. You may view other people's public profiles while not logged in.")
The text was updated successfully, but these errors were encountered:
Everything you can do on the app requires interaction with the database.
As of now, login is only required for operations that can write to the database. The login notices show up when nothing has been opened, letting you know what you can do (in the example, open will work; there is no new button). A registration/login control can be included with those notices. Is that the feature request?
This is not a priority right now, but mindful of our user's experience, we should only require login where an interaction with the database is required. A register/sign in dailogue should replace login notices for unauthenticated users for all instances where a login notice is currently given (e.g. "You must be logged in to edit a new third party profile. You may view other people's public profiles while not logged in.")
The text was updated successfully, but these errors were encountered: