Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add https://search.xmr.st #612

Closed
10 tasks done
xmrst opened this issue Nov 9, 2024 · 3 comments
Closed
10 tasks done

Add https://search.xmr.st #612

xmrst opened this issue Nov 9, 2024 · 3 comments
Labels
instance add Declare a new instance instance related to instance

Comments

@xmrst
Copy link

xmrst commented Nov 9, 2024

Requirements (make sure to read all of them)

  • It is my instance. I bought the domain myself and I own this domain. Free domains (e.g. Freenom) and shared domains (e.g. noip.com) are not allowed.
  • I'll keep my instance up to date, at the very least 1 week old. Example program for keeping up to date: watchtower, cron, ouroboros.
  • I give the right to check.searx.space to check my instance (every 3 hours for the response times, every 24 hours for the other tests).
  • I acknowledge that managing a public instance is not an easy task and require spending time to keep the instance in good health. E.g. look after your instance by using a monitoring system.
  • I guarantee to keep an uptime per month of my instance at minimum 90%. Please ask for a removal of your instance if there is a planned long downtime or notify us here for a short downtime.
  • I do not track the users of my instance with any analytics or tracking software.
  • I won't try to manipulate the ranking of my instance in a way that give an unfair advantage over the other public instances in the list. (e.g. caching requests for searx.space server)
  • I control the final webserver (software) that is serving the requests to the users of my instance. Here is a non-exhaustive list of forbidden hosting types: Cloudflare, PaaS, managed (hosting provider controlled) HTTP(S) load balancer (e.g. AWS ALB), shared Web hosting. TCP load balancer is fine. Cloudflare DNS only (grey cloud) is fine.
  • If needed, I can restrict users from accessing my instance for the only sole reason of keeping my instance in working conditions for the other users (detailed description - evidence need to be provided when asked). Other means of restriction is forbidden.

Bot protection requirement

  • Yes I have configured the server.public_instance parameter.

Source code URL

No response

Comment

No response

@xmrst xmrst added instance related to instance instance add Declare a new instance labels Nov 9, 2024
Copy link

github-actions bot commented Nov 9, 2024

Please consider joining our Matrix room for public instance maintainers by joining our Matrix room: https://matrix.to/#/#searxng:matrix.org
then pinging @ unixfox, @ dalf and @ mrpaulblack for asking to be invited to the Matrix room.
We discuss troubles managing a public instance, sharing some advices (like how to protect against bots), announcing big changes in searxng and more.

@xmrst
Copy link
Author

xmrst commented Nov 9, 2024

Private instance ran just fine, but I've ran into some issues when switching to public instance. I will be troubleshooting this.

Edit: all good now.

@xmrst
Copy link
Author

xmrst commented Nov 18, 2024

After some time of consideration, I have decided against listing the instance as public. It'll remain live, but the public variables will be removed. Disregard my request here.

Thank you.

@xmrst xmrst closed this as completed Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
instance add Declare a new instance instance related to instance
Projects
None yet
Development

No branches or pull requests

1 participant