About https://searx.space

[dalf]

In response to searx/searx#1853 (comment)

For now, the searx-stats2 project has collaborators: asciimoo and return42 (not sure how to open).

For now, I'm the one who host searx.space (Kimsufi host). Currently it hosts some other website for my personnal usage.

searx.space log contains: timestamp, method, url, proto, status, size (no IP, no user agent, no referrer). Most probably can remove completely, but I don't think there is a privacy problem here and it helps to know some information (bandwidth, ratio between the 200 and 304 http status code).

It runs the master branch of https://github.com/dalf/searx-stats2 (git pull && make docker-build are executed by me).
In /etc/cron.d/searx-stats2:

0 1,4,7,10,13,16,19,22 * * *   root cd /srv/searx-stats2 && make docker-run &> /tmp/searx-stats2.log || exit 0

It can be interesting to display the result of searx-stats2 from different location but IHMO the actual fetch should be done only once to avoid to hammer the different instances. Related to https://github.com/dalf/searx-stats2/issues/1

I thought about different things:

• use custom domains and GitHub Pages.
• run searx-stats2 in a VM, and always run the master branch (or a "searx-space" branch). Not sure if different root user is good idea (?).
• allow searx to download and display instances.json. Additional benefit: at the same time, each instance could ping searx-stats2 to say "hey I'm a public instance".
• spread instance.json using P2P networks.

---

It is difficult to combine everything:

• fetch HTTPS / CSP / HTML grades only once.
• get response time from only different location.
• AND avoid a the single point of failure / one central location
• AND User agreement #20 : how an ops can know some requests come from searx-stats2 if the check is run multiple times in different locations.

FYI, searx.me seems to be ban in China according to https://viewdns.info/ (it wasn't the case in 2016).