From f298c481fd08b58a26e17b1c36ced8128440dbf7 Mon Sep 17 00:00:00 2001 From: davidovski Date: Fri, 21 Jul 2023 11:05:15 +0200 Subject: move non-executables to site subdir --- site/entries/librex.html | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100755 site/entries/librex.html (limited to 'site/entries/librex.html') diff --git a/site/entries/librex.html b/site/entries/librex.html new file mode 100755 index 0000000..c78c2cd --- /dev/null +++ b/site/entries/librex.html @@ -0,0 +1,9 @@ +#!./entries.sh + +# LibreX - a metasearch engine + +My instance: [search.davidovski.xyz](https://search.davidovski.xyz/) + +For a while now I have been using [SearX](https://github.com/searx/searx) as my search engine, a meta search engine that cumulates search results from multiple different sites. While this is a great idea in theory, making the best of all search engines through one *privacy respecting* interface, in reality it ends up meaning that search results are quite slow. Couple this with the fact that most SearX instances are hosted by volunteers, and often have downtime, I was in the situation where I was hopping between various instances to try and find ones that worked. I always wanted to self host one myself, but the whole system seemed very bloated and complicated, and honestly I just couldn't be bothered to mess around with it. + +That's where [LibreX](https://github.com/hnhx/librex) comes in, a very small and simple meta search engine. Its still in development, but currently it has just enough functionality to actually be somewhat useful. Currently it only really supports google searches, but it still is a good layer for privacy, since all of your queries are anonymised, with google only seeing that they came from LibreX. I am curious to see how well it will handle larger amounts of search queries and if Google will limit them or something. If you want to support development, feel free to use it, find bugs and request features: [View the github repo](https://github.com/hnhx/librex) -- cgit v1.2.1