Like we have discussed internally in the past, I do not want to remove them before giving a very long warning to all the programs that are using the searx.space API.

Could you rebase your PR? I did remove one SearX instance here: 45d4fbb

Could you rebase your PR? I did remove one Sear

Thanks for pointing out .. done.

This need a double check because some instances are not "searx" anymore and switched to searxng.

List of instances that have switched to SearXNG:

• https://search.trom.tf: have a strange version number but using an unknown searxng version
• https://searx.bissisoft.com: now searxng but quite outdated
• https://searx.divided-by-zero.eu: now searxng
• https://sx.catgirl.cloud/: now searxng
• https://suche.tromdienste.de/: now searxng but using an unknown searxng version

By the way, some in the list were removed due to bad uptime or down or doesn't serve searx anymore.

List of instances that have switched to SearXNG:

• https://search.trom.tf: have a strange version number but using an unknown searxng version
• https://suche.tromdienste.de/: now searxng but using an unknown searxng version

I vote to remove suche.tromdienste.de and search.trom.tf .. both are not vanilla (IDK what state they have) --> "Remove instances that have broken functionalities or broken resources (CSS or/and JS). Like instances that return no results by default, example: https://nibblehole.com/ (I'm removing it). Or instances with broken CSS and JS resources: https://suche.tromdienste.de/ and https://search.trom.tf/"

• https://searx.bissisoft.com: now searxng but quite outdated

I vote to remove: IIRC comes from a old searx list --> we do not have ticket -> declaration of conformity is not available for this instance

• https://searx.divided-by-zero.eu: now searxng
• https://sx.catgirl.cloud/: now searxng

Yeah updated 👍

By the way, some in the list were removed due to bad uptime or down or doesn't serve searx anymore.

Cleaned up in line with a git re-base :)

I vote to remove: IIRC comes from a old searx list --> we do not have ticket -> declaration of conformity is not available for this instance

searx/searx-instances#119

Not the last form, but I guess as many other instances (?).

Not the last form, but I guess as many other instances (?).

Oops .. I mixed with other instance 👍 / fixed --> diff

List of instances that have switched to SearXNG:

• search.trom.tf: have a strange version number but using an unknown searxng version
• suche.tromdienste.de: now searxng but using an unknown searxng version

I vote to remove suche.tromdienste.de and search.trom.tf .. both are not vanilla (IDK what state they have) --> "Remove instances that have broken functionalities or broken resources (CSS or/and JS). Like instances that return no results by default, example: https://nibblehole.com/ (I'm removing it). Or instances with broken CSS and JS resources: https://suche.tromdienste.de/ and https://search.trom.tf/"

When searching on them, both works and returns results. If we want to remove instances like we have always done, we should remove based on the rules.

If we want to remove these instances, we must create a rule that state out of date instances can't be kept in the list, this includes unknown versions which probably indicate an out of date instance.

So until we have such a rule, both of these instances qualify for staying in the list.

https://search.trom.tf/ is broken and we do not have an issue entry --> we can't contact the maintainer:

same with https://suche.tromdienste.de/ .. we should not recommend broken instances at searx.space I think.

https://search.trom.tf/ is broken and we do not have an issue entry --> we can't contact the maintainer:

I am the maintainer. What is broken about it? We use it daily.

same with https://suche.tromdienste.de/ .. we should not recommend broken instances at searx.space I think.

are you sure, these are broken?

For me both instances are working. Tested from different browsers.

Look at the screenshot, you modified the instances to include CSS an JS but the urls can't be loaded --> for what are these CSS and JS injection are intended?

Look at the screenshot, you modified the instances to include CSS an JS but the urls can't be loaded --> for what are these CSS and JS injection are intended?

These are Yunohost packages https://github.com/YunoHost-Apps/searxng_ynh they add those CSS and JS for all of their packages to allow admins to have a way to go back to the Yunohost panel quickly.

EDIT: Also I keep my instance very up to date, only now when I had to travel for a week I was unable to update it but it is still at version 2023.08.06.14.39.00

EDIT: Also I keep my instance very up to date, only now when I had to travel for a week I was unable to update it but it is still at version 2023.08.06.14.39.00

@tio-trom: Why did your customization hides this info from the users?

@aarontrom: you instance show wrong version info to the user

these are Yunohost packages https://github.com/YunoHost-Apps/searxng_ynh

But its broken .. why not removing or fix broken stuff?

search.trom.tf is broken and we do not have an issue entry --> we can't contact the maintainer:
same with suche.tromdienste.de .. we should not recommend broken instances at searx.space I think.

Missing CSS resource != broken instance

If the instance still works fine, with the current rules, I see no objection in removing them.

If there are additional CSS or JS resources, the instance will be ranked lower as such, that's it.

@tio-trom: Why did your customization hides this info from the users?

No special reason, more than having it more clean and user friendly. I can add it back if that's an issue.

But its broken .. why not removing or fix broken stuff?

I am not sure why these resources do not load sometime. This must be a YNH issue.

EDIT: I added the footer back and I will leave it there from now on.

Anyway, I'm not against adding rules for removing such instances. But like I said, we do not remove instances based on personal opinion.