Fresh installation of search plugin on start

[infinite_recursion]

To prevent centralization of search engines, I'm creating a searx plugin which will randomly select an online searx instance for the user for a uxp based browser session. While the logic is fully done, I have absolutely no idea where to start with respect to installation on start of browser session.

https://notabug.org/sagaracharya/random ... uxp_plugin

In the above repo, I want to run the start.js script on browser startup, set the temp variable as the search url in the xml file and install the xml file to the browser 'without prompt'.

I need help wrt, which scripts run at system startup in a plugin? How can I install an xml file at the start of a session without any notification to the user?

Alternatively, if I can change OpenSearchDescription backend such that instead of static xml file, it automatically updates the search engine, that would be great.

Please help.
Thanks in advance.

[New Tobin Paradigm]

Well you can't. You cannot bypass a prompt for installation of a search plugin else it could be abused.

[moonbat]

Also, browser plugins are a completely different thing from search plugins so this post needs to be moved elsewhere.

[infinite_recursion]

Well you can't. You cannot bypass a prompt for installation of a search plugin else it could be abused.

That's why it's free software. To make sure that it is not abused and the user can cross-check the logic. And at max and xml file will steal query words which are still 1000x less abusive than today's javascripts on most sites.

What about the 2nd question? How to update xml file on start of browser session? So the browser starts, fetch, change xml, and plugin loads. Boom. Done.

Tell me more about browser start scripts

[New Tobin Paradigm]

Nah. You can cross-check the logic for your self.

[infinite_recursion]

Come on, New Tobin Paradigm. I'm not the adversary here. Would you not have a more decentralized system instead of winner takes all?

[moonbat]

Come on, New Tobin Paradigm. I'm not the adversary here. Would you not have a more decentralized system instead of winner takes all?

I don't know how many years you have spent developing end user software, but the bottom line is that you always respect the user's choices and leave them in control. That includes not installing random shit on startup without their permission as you want to do. While your intentions are benign, allowing this exactly lets smarmy advertisers to flood a user's list of search engines with their own ones and this behavior taken from the original Firefox was made keeping in mind what a dumpster fire Internet Explorer was in comparison.

You can only detect browser startup/shutdown events when developing an extension, so you'll have to make a separate extension that can dynamically select a searx instance to query, it won't be able to integrate with the existing search plugin mechanism.

[infinite_recursion]

I don't know how many years you have spent developing end user software, but the bottom line is that you always respect the user's choices and leave them in control.

But who told you that the user will not be able to remove the plugin. Obviously if he chooses to remove the plugin, there will be an option(super easy one) and the scripts will be gone. User is in control. For user, installing and uninstalling will be easy. It's just the structure of search code internally which is different.

You can only detect browser startup/shutdown events when developing an extension, so you'll have to make a separate extension that can dynamically select a searx instance to query, it won't be able to integrate with the existing search plugin mechanism.

This will not work through default address bar. People are already into typing everything in address bar. My usage audience will be considerably reduced if I make a separate box or take some keyword for triggering search, etc. Changing habits are one of the most difficult things and we shouldn't strive for it.

I've thought about it. It's the only way.

[Moonchild]

The only way is using an extension to manipulate search engines, I think. The browser itself does not permit scripted install of searchplugins without a prompt.
On top, you have to think really carefully if you aren't violating the redistribution license, depending on how you want to use this setup -- since you aren't actually providing details how you want to use this; if distributing to any audience with this kind of setup baked in, you aren't allowed to use the official binaries. See http://www.palemoon.org/redist.shtml points 3c, 3e, 3f.

[moonbat]

But who told you that the user will not be able to remove the plugin

That is not the issue here. The issue here is the attitude of 'Better to ask for forgiveness than permission' by silently installing it in the first place. This is what Mozilla does now - randomly resetting preferences and removing features and 'oh you can always change it back from about:config' till the ability to do so is pushed down to ESR and finally out altogether (mandatory extension signing for example).

You do not mess around with the user's installation or settings without permission, period.