Acquiring and installing

In order to acquire Ninterserial, you just have to follow those steps:

Firefox

1. Using Firefox browser, browse to the addons’s page at AMO (addons.mozilla.org).
2. Click on "Add to Firefox" button.
3. Done! The addon is already instaled in your browser.

Chromium

1. Unfortunately, for a while, you must install it manually in Chromium (have a look in the section "buiding from sorce code").

---

Building from source code

In order to build SafeSearch enforcer from source, you just have to follow those steps:

Firefox

1. Open the project’s repository available at: https://github.com/Nintersoft/SafeSearch-Enforcer/
2. Clone the whole project (Link to the project’s archive master).
3. Open a terminal emulator (or cmd/powershell on Windows) – You may skip to the 7th step if you do not want to build the compressed file.
4. On terminal, browse to the directory named "Firefox" which must be in the respository’s root.
5. Type the command web-ext build and hit enter.
6. You may notice that a new directory has been created and there is a new zip file in it (SafeSearch Enforcer).
7. Open the Firefox browser.
8. Browse to about:debugging.
9. Enable the option Enable add-on debugging.
10. Click on Load Temporary Add-on....
11. Select the file which has been generated during the step #6 (or the file manifest.json, if you have skipped the build steps).
12. Done! SafeSearch Enforcer is already loaded!

Should you want to use it permanently, have a look in the Mozilla’s article about signing and distributing addons.

Chromium

1. Open the project’s repository available at: https://github.com/Nintersoft/SafeSearch-Enforcer/
2. Clone the whole project (Link to the project’s archive master).
3. Browse to chrome://extensions.
4. Enable the option Developer mode.
5. Click on Load unpacked extension....
6. Select the file named manifest.json available in the folder "Chrome", which must be in the repository’s root.
7. Done! SafeSearch Enforcer is already loaded!

Note [1]

Sometimes, versions of the extension in the repository are a bit outdated for Chromium in comparison to Firefox. It happens due to the addon’s update cycle and to the lack of developers available to port it to Chromium.

Note [2]

Should any error occur, do not hesitate in contacting our team at any moment. We will try to resolve your problem as soon as possible.

Warning!

Please, make sure that you meet the minimal requirements as specified in "Characteristics and requirements".