-
Notifications
You must be signed in to change notification settings - Fork 63
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
Enable Automatic Mode by default #432
Comments
Maybe you can add one per domain rule by default or resolve some other way: STR: Cheers |
What you're describing sounds more like a general feature request for Automatic Mode? However, I was thinking about enabling some sort of isolation by default, but I feel like the learning curve might be too steep, because it'd basically behave like FPI by default then. On the other hand, for me personally, the actual value of TC comes from isolation, hm. In this rare case some sort of telemetry would actually be helpful, I think, to see who enables isolation together with automatic mode - not that I ever plan to add telemetry, just a thought. |
In as much as I've learnt to use Temporary Containers over the months & years it occured to me only the other day that a simplified way of looking at things is like having private tabs without having to open a private window. Perhaps I'm pointing out the obvious, but while I absolutely loved Temporary Containers and wondered where it had been all my container based browsing life after discovering it, it felt like a continuation/expansion of my use of containers, with everything else ending up in temporary containers. From a UX perspective perhaps it might be an idea to consider whether it would help understanding and adoption if users were introduced to it as being 'Private Containers'. Browsing via these private ephemeral containers is the default and users can make exclusions for sites they want to log in to by making them a permant container (which could be done via the touch of a button). The only real problem I've noticed with the extension is when sites redirect to a payment gateway before returning to the original domain. This has required me to add expections. The least obstrusive and most user frinedly way of handling this for users would be to build a filter list of payment gateways and banking domains. Sites open in a new container by default unless parsed as one of the exceptions where upon it would show a message asking if the user wanted to enable filtering of payment domains. Alternatively, could show a message when a site redirects to a different domain in same window asking:
Just some thoughts on the matter, hope they prove useful. Ps. Agree about Automatic Mode. Turned it on straight away after first installing. |
There are not only payment gateways but also identity/authentication providers. There are two ways to mitigate it as far as I see. Left Mouse Click - Same Container method:
This method I am using, since it must be bullet-prof. I have a test users... and those are my folks, who are not tech savvy and breakages makes them nervous, which means I get nervous.... and I don't like to get nervous. 😄 Here is my TC configuration, if you care to test. Dynamic target decision method
This rule need to have exclude target domain pattern set to I do not like this method, since anytime there might be a surprise/brekage and it needs to be maintained, which can be a real burden. Cheers 😄 |
Glad you enjoy the extension!
True, that might make sense in terms of making it easier to grasp the main intended use case for TC. My only concern would be the term "Private", since even Private Windows have to explain what "Private" in that context actually means. But given that Private Windows already try to educate users about the term in the context of the browser, it might be the right choice after all. The other thing that might be an issue is that "Private Container" might imply that history isn't saved either by default - which isn't the case.
(and login/oauth URLs as mentioned by @crssi) That's an really interesting idea! There was a bit of brainstorming on this topic in #407 - but a list of domains / domain-chains sounds useful and doable.
I agree, the "convert to permanent container" button should probably be more prominently placed, especially when going to Automatic Mode or even Isolation by default. (related: #396, #342) |
Thank you for resolving in 1.9 ❤️ |
Given that I intended TC to be a tool for privacy and I mostly see it used in that context, I think it makes sense to rethink the decision made in #48, namely
Depends on #397 and #396
This would probably supersede/deprecate #201
Something that'd be nice if the first time after installation, when opening the preference page, it'll let you choose between "privacy" and "web developer" - as kind of preference presets. If nothing is selected it defaults to "privacy"
The text was updated successfully, but these errors were encountered: