Feature #502
openCreate a user configurble URL modification
0%
Description
(finally able to activate my account)
I would see as a good feature to have URL manipulation done automatic by the browser, based on domain rules.
Case in point, Invidious
It could turn this: https://invidio.us/watch?v=Yw6u6YkTgQ4
into this: https://invidio.us/watch?v=Yw6u6YkTgQ4&listen=1&autoplay=1
which would make it possible to, without using cookies or javascript, always have invidious play only the sound and start playing on its own. Other options are available this is only an example. I also think other websites might have some tweaks that would be interesting to use this feature.
Also, I see it as a fitting feature for the 3.x version, since the browser already does URL manipulation (to remove facebook tracking and such). Meaning it would hardly require Privacy View. Please correct me if wrong.
Thanks.
GNUser
Updated by Soren Stoutner over 3 years ago
- Subject changed from Allow URL modification automatically by domain to Create a user configurble URL modification
- Assignee set to Soren Stoutner
Currently there are only a few preset URL modifications, and all of them remove sections of the URL. I can envision a lot of good reasons to provide for user created URL modifications, like the one you mentioned above. These would allow for both adding and removing sections of the URL, and could be domain specific.
Note that this gets quite complicated rather quickly. Beyond building a user interface to allow users to create and manage these modifications, there are also considerations about how to apply these to URLs, what to do if there are multiple modifications being applied at the same time (when there are both additions and deletions), and controlling if they are applied to resource requests as well as base URLs. All of these are surmountable problems, but it means that I will likely push this off until near the end of the 3.x series.
Updated by GNU User over 3 years ago
You are right in that this, apparently simple feature is quickly turned into a complicated mess when one starts thinking about all the possible URL modifications that the end-user might try to apply. So, I suggest thinking about the simple first steps to begin with.
Removing URL part: basically when that string is located in the URL, it is removed. It is up for the end user to be careful deciding what has to be removed.
Replacing URL part: whenever a certain string appears, it is replaced with another string.
Adding URL part: since we already covered "replacing", adding means basically at the end of the URL add some other string. It could also be done at the beginning of the URL, but maybe start with the end for now.
The same code used for removing Facebook tracking could be used to remove ANY part of the URL string and it shouldn't give any trouble (like I said, it's an advanced feature that leave up to the END USER the responsability of what he is deleting and wether or not the URL will load after).
All this would be a simple extra menu in the "Domain settings" in which you could have "add string" "remove string" and "replace string" options. For a start maybe have only ONE option available for a domain, at the same time.
Of course it's easier to say that do, but I hope this at least shows a clearer path of logic as to how this feature should work (for now at least, of course in the long run one could expect to use wildcards and such, but starting small and simple should help a lot).
Updated by Soren Stoutner about 3 years ago
This is a general implementation of the specific feature described at https://redmine.stoutner.com/issues/505. Likely one interface will be able to handle both.
Updated by Soren Stoutner about 1 year ago
There is also some discussion of this topic at https://redmine.stoutner.com/issues/844.
Updated by राही अखेराजोत 11 months ago
Allow user to use split, replace/replaceAll, slice, splice etc methods. Add this option to Domain list.
Updated by Soren Stoutner 11 months ago
I am not sure I understand what you are requesting. However, I should make two points.
1. This feature request is about URL modification, not Domain Settings. If you are referring to Domain Settings, you should create a new feature request.
2. For performance reasons, I am unlikely to implement anything that would require processing regular expressions. Some of the words you are using make me think that perhaps you are requesting something that would fall into that category.