Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[question] recommendations for an invidious setup #821

Closed
return42 opened this issue Jan 25, 2022 · 6 comments
Closed

[question] recommendations for an invidious setup #821

return42 opened this issue Jan 25, 2022 · 6 comments
Labels
question Further information is requested

Comments

@return42
Copy link
Member

return42 commented Jan 25, 2022

I open this issue to exchange invidious experience / not to say I have zero experience :-)

In the SearXNG default setup we have ..

searxng/searx/settings.yml

Lines 778 to 785 in 81453a0

- name: invidious
engine: invidious
base_url:
- https://invidious.tube/
- https://invidious.snopyta.org/
shortcut: iv
timeout: 5.0
disabled: true

  • My experience is, that a timeout of 5 sec is not need, I got fast response >1sec on my instance.
  • Do you recommend different base_url .. is your recommendation related to the continent where the instance is hosted or to the location where the majority of your users are from?

Do you redirect (replace hostname / further see) youtube links to invidious?

searxng/searx/settings.yml

Lines 177 to 179 in 81453a0

# hostname_replace:
# '(.*\.)?youtube\.com$': 'invidious.example.com'
# '(.*\.)?youtu\.be$': 'invidious.example.com'

Do you miss any feature in our invidious engine or do you have suggestion for improvements?


Here are my /etc/searxng/settings.yml settings (EDIT no longer needed, already added to the sources 10c9b97):

  - name: invidious
    engine: invidious
    # Instances will be selected randomly, see https://api.invidious.io/ for
    # instances that are stable (good uptime) and close to you.
    base_url:
      - https://invidious.snopyta.org
      - https://vid.puffyan.us
      - https://invidious.kavin.rocks
      - https://invidio.xamh.de
      - https://inv.riverside.rocks
    shortcut: iv
    timeout: 3.0
    disabled: true

The instances are used randomly, but all results (incl. yahoo) are redirected to an instance in DE where the majority of my users is located:

hostname_replace:
  '(.*\.)?youtube\.com$': 'invidio.xamh.de'
  '(.*\.)?youtube-nocookie\.com$': 'invidio.xamh.de'
  '(.*\.)?invidious\.snopyta\.org$': 'invidio.xamh.de'
  '(.*\.)?vid\.puffyan\.us': 'invidio.xamh.de'
  '(.*\.)?invidious\.kavin\.rocks$': 'invidio.xamh.de'
  '(.*\.)?inv\.riverside\.rocks$': 'invidio.xamh.de'
@return42 return42 added the question Further information is requested label Jan 25, 2022
return42 added a commit to return42/searxng that referenced this issue Jan 25, 2022
- My experience is, that a timeout of 5 sec is not need, I got fast response
  less tha a second.

- https://invidious.tube/ redirects to http://ww25.invidious.tube/
  - in SearXNG defaults the http protocol is unsafe and raise an error
  - https://ww25.invidious.tube has SSL_ERROR_UNSAFE_NEGOTIATION

Related-to: searxng#821
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
return42 added a commit to return42/searxng that referenced this issue Jan 25, 2022
- My experience is, that a timeout of 5 sec is not need, I got fast response
  less than a second.

- https://invidious.tube/ redirects to http://ww25.invidious.tube/
  - in SearXNG defaults the http protocol is unsafe and raise an error
  - https://ww25.invidious.tube has SSL_ERROR_UNSAFE_NEGOTIATION

Related-to: searxng#821
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
@return42
Copy link
Member Author

@unixfox do you have any suggestions for us?

@unixfox
Copy link
Member

unixfox commented Jan 25, 2022

I don't really replace the hostname, but that's a good idea I should do on my instance!
About which instance to add in the base_url, it's difficult to say, I would recommend using an instance that is stable (good uptime) and close to you.

The 5 seconds can be useful when the default instance is overloaded for a short moment and takes time to reply.

I've nothing to really add.

return42 added a commit to return42/searxng that referenced this issue Jan 25, 2022
- My experience is, that a timeout of 5 sec is not need, I got fast response
  less than a second.

- https://invidious.tube/ redirects to http://ww25.invidious.tube/
  - in SearXNG defaults the http protocol is unsafe and raise an error
  - https://ww25.invidious.tube has SSL_ERROR_UNSAFE_NEGOTIATION

Related-to: searxng#821
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
@unixfox
Copy link
Member

unixfox commented Feb 19, 2022

Safe to close now that the questions has been answered?

@return42
Copy link
Member Author

I think it is better placed somewhere in the discussions .. I don't know how to move it there.

@unixfox
Copy link
Member

unixfox commented Feb 19, 2022

If you have the right access there is a button on the right side under "participants".

@return42
Copy link
Member Author

🤦 .. thanks!

@searxng searxng locked and limited conversation to collaborators Feb 19, 2022
@return42 return42 converted this issue into discussion #911 Feb 19, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants