this post was submitted on 04 Apr 2024
153 points (96.4% liked)

Firefox

17952 readers
437 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] isVeryLoud@lemmy.ca 4 points 7 months ago (2 children)

Honestly, I set up SearxNG on my own server, and it's not very nice to use, not very configurable and doesn't return high quality results. It's also kinda slow. Maybe I'm missing something?

[–] hash0772@sh.itjust.works 6 points 7 months ago

It is recommended to use a public instance because it makes it harder to fingerprint you off of your searches. It gets most results from Google and Bing, so you will have similar search results. I haven't experienced any slowness yet, so I can't say anything about that.

[–] BeamMeOut@mastodon.social 2 points 7 months ago (1 children)

@isVeryLoud @hash0772 I had similar experience. I was able to resolve the slowness by enabling swap on the vps. What was worst is that over time Bing and Google API changed and it stopped working, took quite long troubleshooting. Occasionaly I would hit some kind of rate limit and got nothing from Google. It was too much hassle and not worth the vps cost.

[–] isVeryLoud@lemmy.ca 1 points 7 months ago (1 children)

Cost is whatever since this VPS is being used for other things.

I'm a bit confused about swap solving things though since it's unlikely to be a memory issue.

[–] BeamMeOut@mastodon.social 0 points 7 months ago (1 children)

@isVeryLoud It was for me, I monitored the server and each query would bump up the memory quite a bit. But that sucker had only 512 MB I think. It could've been some issue that's already fixed with newer Searx versions.

[–] isVeryLoud@lemmy.ca 1 points 7 months ago

Ah that would definitely be it, my VPS has 4 GB of RAM and runs other services just fine. I set it up about a month ago.

You can try it yourself: https://searx.veryloud.ca/