-
Notifications
You must be signed in to change notification settings - Fork 29
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
Delete non SearXNG instances #330
Comments
… list 1. remove old / unmaintained instances from the list 2. remove support of searx from the issue templates Closes: searxng#330 Signed-off-by: Markus Heiser <[email protected]>
… list 1. remove old / unmaintained instances from the list 2. remove support of searx from the issue templates Closes: searxng#330 Signed-off-by: Markus Heiser <[email protected]>
… list 1. remove old / unmaintained instances from the list 2. remove support of searx from the issue templates Closes: searxng#330 Signed-off-by: Markus Heiser <[email protected]>
… list 1. remove old / unmaintained instances from the list 2. remove support of searx from the issue templates Closes: searxng#330 Signed-off-by: Markus Heiser <[email protected]>
… list 1. remove old / unmaintained instances from the list 2. remove support of searx from the issue templates Closes: searxng#330 Signed-off-by: Markus Heiser <[email protected]>
I have also been thinking of renaming this repository name from what do you think @return42 @dalf @tiekoetter @mrpaulblack @Bnyro? GitHub keeps the compatibility with the old repository name, so this won't break existing "git clone" installations. |
Don't forget setup.py : Line 64 in 33f6b24
searxinstances --> searxng-instances .
The package might be rename too. In this case, the minimal change on |
Let us remove non SearXNG instances (the old searx instances) from the list.
We (the community of SearXNG) should not care about unmaintained and broken searx instances any longer.
The text was updated successfully, but these errors were encountered: