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

Offer a different submission option #149

Closed
tacerus opened this issue Jun 9, 2021 · 7 comments
Closed

Offer a different submission option #149

tacerus opened this issue Jun 9, 2021 · 7 comments
Labels
enhancement New feature or request

Comments

@tacerus
Copy link

tacerus commented Jun 9, 2021

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
Copy link
Member

unixfox commented Jun 9, 2021

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...

@return42
Copy link
Contributor

return42 commented Jun 9, 2021

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.

@tacerus
Copy link
Author

tacerus commented Jun 9, 2021

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:
https://gist.github.com/travstoll/d6d72855b4184fbfc30f3a20a9adbb4c

--

We also encourage providers to set a contact_url

Which can be an anonymous email address, no?

@unixfox
Copy link
Member

unixfox commented Jun 9, 2021

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.

@tacerus
Copy link
Author

tacerus commented Jun 9, 2021

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

@return42
Copy link
Contributor

return42 commented Jun 9, 2021

Which can be an anonymous email address, no?

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

@unixfox
Copy link
Member

unixfox commented Jun 5, 2022

Moving the discussion to the searxng repo: searxng/searx-instances#75

@unixfox unixfox closed this as completed Jun 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants