Having autoplay as the default for videos is a REALLY bad move.
You can disable autoplay for videos — it’s in the “Accessibility Settings.”
(While you’re there you can also enable “require alt text before posting” if you haven’t yet)
You can disable autoplay for videos — it’s in the “Accessibility Settings.”
(While you’re there you can also enable “require alt text before posting” if you haven’t yet)
Reposted from
Bluesky
Quick facts:
• Each post can contain one video.
• Videos can be up to 60 seconds long.
• By default, videos will auto-play. You can turn off auto-play in Settings.
• Each post can contain one video.
• Videos can be up to 60 seconds long.
• By default, videos will auto-play. You can turn off auto-play in Settings.
Comments
Some of are here to see the art!
I don't know who to @ for that suggestion. Hopefully this is just a growing pain error.
Glad it can at least be changed. >_>
In the upside I’m able to make my own feeds and can filter out videos altogether when I don’t want to see them.
Freezing videos and gifs in the same setting kinda sucks
Can we also get an option to mute videos by default, separate from the autoplay option?
https://chromewebstore.google.com/detail/photosensitivity-video-bl/epmpnnakndnajenpfacadlkbfinbamdk?pli=1
It's made for pc based chrome browsers, I have no clue if it would work for a phone.
The core is still solid, but with every update they take 1 step forward, and 2 steps back, by not thinking things through.
Until it fell over under increased load, I was able to get by with just this for gifs: https://bsky.app/profile/nogifsplease.bsky.social
Rather than toggling the accessibility setting.
There are a few things Bluesky has failed to consider. I guess the worst is to have the app working in cache memory. It has accumulated more than 3GB “documents and data” on my iPhone. Only way to “clear cache” is reinstall.
They’re looking into it.
This seems significantly less bad.
Now... where's the button for preventing the slightly more annoying auto-loop?
Thanks for pointing it out!
Ideally settings have a 1:1 mapping to the UI so a new setting can be added just by writing the handler for it and the UI code is a general JSON parser. Having one setting in two places means a mapping must be implemented.
Also important to note that this was a general comment; I'm not familiar with bsky's codebase in particular.
I'd also like to see basic search function for settings so it's not so critical where a setting is. Just type in "autoplay" or whatever and find it.
Fixed that right quick.
I've seen very few bad missteps with their rollouts, so hopefully this gets fixed quickly.