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
It would be nice to have a "low data mode" available for Tusky, where if enabled, media files embedded in posts would not be loaded by default when the user is browsing on a cellular data connection. Presumably profile pictures are small enough and would be loaded.
Ideally a blurry preview of the media would be available, I think this is already built in to Tusky for when media can't be loaded?
This feature is comparable to settings available in Signal or WhatsApp.
Motivation
This would benefit users browsing the fediverse on limited data plans, by allowing them to choose whether to download larger files rather than it happening automatically.
The text was updated successfully, but these errors were encountered:
Thanks, I guess that covers most of what I was looking for. The only other part would be a setting that automatically turns off media previews when the user is on a cellular connection. But feel free to close this issue if you think that's not worth it / too small.
Its not as easy as it sounds though, because networks can switch quickly and if we leave the post layout like it is now (with major differences between previews on and off) it would jump around horribly.
Pitch
It would be nice to have a "low data mode" available for Tusky, where if enabled, media files embedded in posts would not be loaded by default when the user is browsing on a cellular data connection. Presumably profile pictures are small enough and would be loaded.
Ideally a blurry preview of the media would be available, I think this is already built in to Tusky for when media can't be loaded?
This feature is comparable to settings available in Signal or WhatsApp.
Motivation
This would benefit users browsing the fediverse on limited data plans, by allowing them to choose whether to download larger files rather than it happening automatically.
The text was updated successfully, but these errors were encountered: