O

Ota

I just also ran into this issue and no idea how to solve it, besides using a different browser. It would be lovely if this can be tackled for a browser that considers privacy and security first.

Vlad That makes sense. Would it be possible to have an option that allows selecting domain or subdomain matching?

Please consider that in midterm an overview or list of configurations would be helpful. Maybe that is combinable with an overall overview for "website settings": Having a list of domains in a table view and the selected custom options.

Vlad Hey, as posted by @junukwon7 the app Velja does an OK job to manage the rules.

The interface should consist of three parts: Rules overview, Rule definition and pattern matching.
Besides the interface, there should be a quick way to add a rule. E.g. by right-clicking the URL in the search bar and selecting "Always open in $profile" which would create a domain matching rule.

Interface description:

Rules overview

Overview of all rules that gives a bird's-eye view of what exists.

1. Showing the rule name and the profile the rule is assigned too.
2. It should be possible to filter rules based on profile or configured session to only see rules that apply to these.

Rule definition

Interface to create a new rule or to edit an existing one.

1. Name of the rule for user-friendly naming.
2. Profile (or later on also session) to be used for this rule. This is the profile in which the URL will be opened when the URL matches.

Pattern matching

A list of patterns, that would trigger the rule (Velja calls these matchers). Most likely a child element of the rule definition.
There can be multiple patterns in a rule that are OR chained.

1. Sample URL to test your pattern against.
2. Pattern style, that defines how to detect if the rule would match.
   (Domain, Full domain matching including subdomain, Prefix, Contains and Regex)
3. Pattern value.
   Value to match the visited URL against to trigger the rule.

Playing together

As soon as a rule matches, the given URL will be opened in the configured profile/session. In case the profile is not active, a new window for the profile will be created. If the profile window is not focused, the focus would switch to the appropriate window.

Velja example

Here is an image from Velja when adding a new rule.

I hope this helps.

junukwon7 I am aware of Veljia or choosy. The limitation of these tools is that they only work for visits initiated from third-party apps, e.g. clicking a link in Slack.

When you are inside Orion, tools like Veljia do not intercept the call. This means you would still open the desired website in the active profile.

Vlad I will come back when i have gathered a few examples.

Vlad Thanks for getting back to me. I understand that prioritization is hard. As this issue is under review since over a year, I just hoped this was on its way to be resolved.

Is there something that we can do to identify the problem, that would help to address the issue?

With Orion profiles, it is possible to be only logged in into services that match the profiles' intention.

A "private" profile could be used for one's personal paid <music streaming service> account or to shop on <favourite shopping website>. As on the other hand, the <developer platform service> is only relevant for the "work" related profile.

Mixing those services across profiles (being logged in multiple times with the same account) would undermine the intention of clear separation (exceptions might exist) and should not be the best practise.

To take profiles to the next level, I would like to suggest having an option that enables me to define that certain services (websites) should always be opened in a specified profile.

Example: When configuring that <music streaming service> should open in my private profile, each time I enter the URL, the website will be forcibly opened in my private profile. Preventing of unintentional mixing of services and making the users' life easier.

Hey, I just switched to Orion and noticed that the ClearUrls extension UI is not working as described in this thread.

Is there maybe any update on the topic? Is an extension like ClearUrls even needed when using Orion?

https://orionfeedback.org/d/798-clearurls-settings-ui-issue seems to be an older duplicate of this issue.