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://searx.catfluori.de #388

Closed
8 tasks done
catfluoride opened this issue Aug 18, 2023 · 3 comments
Closed
8 tasks done

Add https://searx.catfluori.de #388

catfluoride opened this issue Aug 18, 2023 · 3 comments
Labels
instance add Declare a new instance instance related to instance

Comments

@catfluoride
Copy link

catfluoride commented Aug 18, 2023

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 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: PaaS, managed (hosting provider controlled) HTTP(S) load balancer (e.g. AWS ALB), Cloudflare, shared Web hosting. TCP load balancer 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

Yes, I have enabled the limiter plugin built in SearXNG.

Source code URL

No response

Comment

I am using Cloudflare just for DNS (no proxy, no WAF). My instance was removed because I forgot to disable proxy and WAF after doing a quick test.

@catfluoride catfluoride added instance related to instance instance add Declare a new instance labels Aug 18, 2023
@github-actions
Copy link

@maintainers Warning, instance found in the commit history, make sure to wait 1 week before adding the instance if needed.
See here for more information: https://github.com/searxng/searx-instances#add-a-previously-submitted-instance

Commit ID: 9e4aaa466c9b7946270e15968fceb5fcfbe8ea5f
 - Date: Fri Aug 18 15:31:32 2023 +0200
 - Description: remove searx.catfluori.de using cloudflare
 - Author: Émilien (perso)

Commit ID: 444a2503babccaf9ab909e4d06a1b0022bb6eb2d
 - Date: Tue Nov 29 21:47:13 2022 +0100
 - Description: Edit https://searx.ebnar.xyz
 - Author: Léon Tiekötter

@unixfox
Copy link
Member

unixfox commented Aug 18, 2023

Hello,

We can add back your instance but do not violate the rules anymore, temporarily enabling cloudflare just for testing is not allowed.

@catfluoride
Copy link
Author

Thanks a lof @unixfox. I deeply apologize for this unfortunate incident.

@unixfox unixfox changed the title searx.catfluori.de Add https://searx.catfluori.de Aug 18, 2023
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

2 participants