search

searxng / searx-instances

SearXNG instances list
https://searx.space
GNU Lesser General Public License v3.0
119 stars 30 forks source link

Offer a different submission option #75

Open unixfox opened 2 years ago

unixfox commented 2 years ago

Copying the discussion from https://github.com/searx/searx-instances/issues/149 and created by @tacerus

By @tacerus

Hi,

I appreciate your services, however wonder how being directed to GitHub helps in providing anonymous searx instances. Providers wanting to ensure full anonymity for their users are unable to do so if a GitHub accounts refers back to them.

I suggest the implementation of a submission form that is accessible directly from your instance site, which is already accessible anonymously through Tor.

Cheers, Georg

unixfox commented 2 years ago

That's a very good idea, but we tend to prefer GitHub because it allows us to contact the maintainer in case of issues with his instance. I think I wouldn't mind creating an email address for submitting instances, but the issue is that this process would be private, and I like the idea of having open submissions like on GitHub where everyone can see and react to them. Not sure if there are other ways of submitting public posts without having to create an account, maybe something like 4chan...

unixfox commented 2 years ago

By @return42

my 2cent: I think the idea is to protect privacy of the user not of the provider. At least the domain under which a service is provided needs contact data. We also encourage providers to set a contact_url.

if a GitHub accounts refers back to them.

IMO that is the real drawback, that a github account is needed to participate. There are a lot of DevOps out there who leaved github for their own good reasons.

unixfox commented 2 years ago

By @tacerus

By leaking privacy of the provider, indirectly users are being affected too. Whilst not always having to be the case, an infiltrated instance operator could feel pressured to leak users data for their own safety. If the instance operator themselves remain anonymous however, this situation cannot occur in the first place.

Since you prefer to gather things on GitHub, possibly something in the direction of this (not tested) could be of interest: gist.github.com/travstoll/d6d72855b4184fbfc30f3a20a9adbb4c

--

We also encourage providers to set a contact_url

Which can be an anonymous email address, no?

unixfox commented 2 years ago

Since you prefer to gather things on GitHub, possibly something in the direction of this (not tested) could be of interest: gist.github.com/travstoll/d6d72855b4184fbfc30f3a20a9adbb4c

We aren't going to do something like that because without any restriction, the associated GitHub account with an access token could get his account banned/blocked due to potential spam/bad actors sending emails to the email address. I have no desire spending my time to introduce a system that filter spams/bad actors.

It's a good idea, but I would prefer a separate platform which is not related to GitHub. I don't really mind having to check it out from time to time.

unixfox commented 2 years ago

By @tacerus

A separate platform, possibly integrated with the directory page, would of course be even better.

unixfox commented 2 years ago

By @return42

Which can be an anonymous email address, no?

It does not have to be an email address, it is an optional URL.

unixfox commented 2 years ago

I have been thinking that we could use this service for automatically creating a new github issue whenever a new email is sent to an email address for submitting a new searx(ng) instances: https://fire.fundersclub.com/

This would satisfy both parties because we can keep a public record, we can keep managing the public instances from a single point (github) and the submitters just have to use the good old email protocol for adding a new public instance. Each reply would be forwarded by email.

One major possible issue is that we could get SPAM into the github issues, see https://github.com/FundersClub/fire/issues/392

iotalol commented 1 year ago

Maybe a Matrix server for submission?

CameronMunroe commented 1 year ago

I'd personally like a "Less-Privacy" related option that had Cloudflare support.

return42 commented 1 year ago

I'd personally like a "Less-Privacy" related option that had Cloudflare support.

Then you are wrong here .. SearXNG is made for privacy!

CameronMunroe commented 1 year ago

I'd personally like a "Less-Privacy" related option that had Cloudflare support.

Then you are wrong here .. SearXNG is made for privacy!

I understand it is made for privacy. I am not asking for the privacy options to be removed. Just an option to list options that hopefully come with some other benefits beyond just privacy. If this lists only option is "privacy" we may remove other beneficial setups that could also have their own niche.

unixfox commented 1 year ago

I'd personally like a "Less-Privacy" related option that had Cloudflare support.

How is this related to the initial issue? This is about other way of submitting new searx instances, not suggesting modifying the rules for the new instances.

If you want to discuss the rules please open a github discussion for that: https://github.com/searxng/searx-instances/discussions/categories/ideas

unixfox commented 1 year ago

I think I've a simple idea for submission using email.

We use github actions.

Each email is associated with a github issue, it is not possible to have multiple issues for the same email address, this make the implementation much easier. And also someone is not going to need to request multiple instances.

The subject of the email is the subject of the issue.

We use github labels for knowing to which address we should send the email to when a reply is done on github. Or put the email inside the title of the issue.