-
Notifications
You must be signed in to change notification settings - Fork 27
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
low data mode / poor connectivity #195
Comments
Motivation
|
Adding new 'data' label, and tagging with 'android' as this is particularly important to mobile users |
context Things that could reduce bandwidth: -no images pre-loaded Realized that mutiny blastr relay will be the most data economical outbound relay with the most reach wss://nostr.mutinywallet.com |
If low data mode is on/there is poor connectivity, it becomes more important to communicate this to the damus user. For instance instead of a no context loading spinner, consider: |
user story
As a Damus pleb who uses app on the go (cellular), I want to have a setting where I can turn down Damus data needs (data saver mode), so that I don't surpass my celullar carrier's data throttling threshold, AND so that my events post thereby avoiding poor Damus experience(s).
Acceptance Criteria
-damus does not auto-load new images
-damus does not auto-load new videos
-damus does not auto-load new link previews (does this use significant data?)
-damus does not load new profile banners
-damus does not load new pfps
questions
-design: does the new note / feed refresh mechanism change in low data mode?
-design: @robagreda what does "low data mode" status look like? how might we display low data mode to the user when it is on? should low data mode icon be displayed all the time?
-design: @robagreda how might we allow user to change low data mode setting (when not on wi-fi) without having to send user deep in the settings menus?
-design: does user have a mechanism to manually load an image as a one off, video while in low data mode?
The text was updated successfully, but these errors were encountered: