We're a privacy search engine and we just went fully open source

Thanks so much for answering the questions! I DO understand why you need to wait to release more information on the owner and respect that. Please do that soon so you can be trusted and listed as a privacy service. We need more private search engines!

3 Likes

You can keep up with us on our blog, on Twitter, on Nitter if you want a different front-end to Twitter, or on GitLab.

Glad to hear you’re interested!

1 Like

We appreciate it and we’ll try to get that done as soon as possible!

Thanks for open sourcing!

1 Like

Try https://developer.mozilla.org/docs/Web/API/Window/sidebar/Adding_search_engines_from_Web_pages

2 Likes
1 Like

Thank you very much for the links and assistance. We are very close to getting it to work correctly on our own but the external extension, Search Engine Helper, does work in making us your default search engine in Firefox with the Search URL as https://infinitysearch.co/?q=%s.

We are attempting to get it to work on our own with our search.xml file https://gitlab.com/infinitysearch/infinity-search/blob/master/static/search.xml but this method is still giving us technical difficulties which we will fix as soon as possible.

1 Like

Making Infinity Search your default search engine in Firefox is now an easy task!

Here is our documentation on how to do it: https://gitlab.com/infinitysearch/make-us-your-default-search-engine.

2 Likes

2 posts were split to a new topic: Fathom Analytics

A post was merged into an existing topic: Lobsters – a computing-focused community

What it sounds like to me is Infinity Search might complement Yacy as well. I’d use Yacy for local searches ( Generally my Gitea repositories ), and use Infinity Search for other stuff.

One gripe about some search engine more generally, you’re looking up something, and sometimes you end up with completely irrelevant results:

Ex. Searching for what makes Spanish and French music different, turning up a Huffpost article on why Spanish people aren’t Latinos. Interesting, but that doesn’t pertain to what I searched for.

1 Like

Hello! https://search.privacytools.io is already at 0.16.0 (displayed in the footer).

It still has this bug:

Engines cannot retrieve results:
gigablast (unexpected crash: extra param expired, please reload)

It isn’t fully updated to 0.16.0 only 0.15.0 (See privacytools/search/releases) thus it still has a bug while searching:

Engines cannot retrieve results:

gigablast (unexpected crash: extra param expired, please reload)

Any update? https://search.privacytools.io/ needs to be updated.

While I think this is offtopic for this thread, you may wish to report it at GitHub instead.

CC. @jonah if you aren’t aware of the Searx issue reported above.

502 Bad Gateway

1 Like

Could someone update the engine/ fix the error Rate limit exceeded error when searching via the firefox tool?

Hello everyone. Sorry for the late response here but we never disclosed the name of our business earlier. Well now we can and it is called Innovare Technologies.

We have also made some changes to our service since our initial conversation and we will be uploading the updated responses of ours to the website shortly.