On Thursday, June 22, 2017 at 8:40:50 AM UTC-7, Ryan Tate wrote: > (Has anyone figured out a better approach?)
keep your twitter passphrase in vault, use a dispvm. if your low on resources and want to make a dedicated vm that will be used for twitter and other things, you could use firejail --home, and maybe --x11 as well for isolation. for this to be effective, you'll also need to add "-nolisten local" to your templates qubes-run-xorg.sh https://firejail.wordpress.com another isolation you can use is firefox containers, which are not enforced sandboxes, but more of a privacy and organizational separation. this feature is in testing. https://testpilot.firefox.com/experiments/containers/ the two work fine together if you want to use them both. if have the resources, i think its better to use a dispvm or dedicated twittervm. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/893a9518-2404-4017-b6e8-ec956da2c91b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
