To expand on this, there are two settings you can put in user.js
/ prefs.js
(desktop) or via about:config (mobile), documented on the Mozilla Wiki:
user_pref("media.autoplay.default", 5);
user_pref("media.autoplay.blocking_policy", 2);
Two bonus settings if you want to get rid of the “do you want to enable DRM?” pop-in bar when hitting one of those sites:
user_pref("media.gmp-widevinecdm.enabled", false);
user_pref("media.gmp-widevinecdm.visible", false);
hth
If you have access to some sort of basic Linux system (cloud server, local server whatever works for you) you can run a program on a timer such as https://isync.sourceforge.io/ (Debian package:
isync
) which reads email from one source and clones it to another. Be careful and run it in a security context that meets your needs (I use a local laptop w/encryption at home that runs headless 24/7, think raspberry Pi mode).This includes IMAP (1) -> IMAP (2) as well as IMAP -> Local and so on; as with any app you’ll need to spend a bit learning how to build the optimum config file for your needs, but once you get it going it’s truly a “set and forget” little widget. Use an on-fail service like https://healthchecks.io in your wrapper script to get notified on error, then go about your life.
Edit: @mike_wooskey@lemmy.thewooskeys.com glanced at your comments and see you have a lot of self-hosting chops, here’s a markdown doc of mine to use isync to clone one IMAP provider (domain1.com) to another IMAP provider (domain2.com) subfolder for archiving. (using a subfolder allows you to go both ways and use both domains normally)
----
Sync email via IMAP from host1/domain1 to a subfolder on host2/domain2 via a cron/timer. Can be reversed as well, just update
Patterns
to exclude the subfolders from being cross-replicated (looped).isync
package:apt-get update && apt-get install isync
Passwords for IMAP must be left on disk in plain text
${HOME}/.secure
contents on encrypted volume unlocked manuallyThe
mbsync
program keeps it’s transient index files in${HOME}/.mbsync/
with one per IMAP folder; these are used to keep track of what it’s already synced. Should something break it may be necessary to delete one of these files to force a resync.By design,
mbsync
will not delete a destination folder if it’s not empty first; this means if you delete a folder and all emails on the source in one step, a sync will break with an error/warning. Instead, delete all emails in the folder first, sync those deletions, then delete the empty folder on the source and sync again. See: https://sourceforge.net/p/isync/mailman/isync-devel/thread/f278216b-f1db-32be-fef2-ccaeea912524%40ojkastl.de/#msg37237271Simple crontab to run the script:
Main config for the
mbsync
program:${HOME}/.mbsyncrc
This script leverages healthchecks.io to alert on failure; replace XXXXX with the UUID of your monitor URL.
${HOME}/bin/hasync.sh