Conversation
Notices
-
@navigium @theru I’d expect #Seeks to be more popular simply because it doesn’t lock up your system like #YaCy does.
- Roland Häder likes this.
- Roland Häder repeated this.
-
@lnxw48 Development has almost stopped on it. Time to reboot it. And it is not a crawler, like #YaCy is.
-
@lnxw48 @navigium I run a public #seeks node now: https://seeks.mxchange.org/search.php
-
@roland @lnxw48 @navigium great! but I can't find much information (e.g. no results if I search "duck", but it can be for my browser configuration)
-
@moshpirit I do not believe it is your browser configuration. I do not receive any results from any search there. @roland perhaps you should check #Seeks connection to search backend? // CC: @navigium.
-
@lnxw48 @moshpirit @navigium I think it is because of the project's main site is no longer working. I had to change the cf-config file to point to my instance and now I get results. :-)
-
@lnxw48 @moshpirit @navigium do this in cf-config:
cf-peer http://seeks.mxchange.org/search.php bsn
Or try #HTTPS:
cf-peer https://seeks.mxchange.org/search.php bsn
It is self-signed. :-)
-
@roland @lnxw48 @navigium i cant understand why most of the listed nodes changed to searx. all of them starting own engines instead of peering a nice alternative..
-
@pagsheathenman @lnxw48 @navigium Both #Seeks and #Searx are meta search engines. This means they don't crawl on their own and rely on other engines. Having an own index, in my view, has both pros and cons. Pro: you (or the #p2p network) depend on your own index and can enrich it with results (crawls again) from other #OpenSearch engines, con: increase storage and maybe RAM usage. !yacy attempted this but in my view it fails because it eats up your system (RAM usage).
-
@lnxw48 I'm getting this:
May 20 19:06:22.648 xxx Error: failed deserializing query halo
May 20 19:06:22.648 xxx Error: failed deserializing query halo
May 20 19:06:22.648 xxx Error: 4002 in plugin udb-service caught in top-level handler
-
@roland @lnxw48 @navigium and yacy peers still varies much, some fetched nothing and some dozens.
https://gitlab.com/HeathenMan/SimpleMultiMetaSearch
i thought about this script to search trough different yacy nodes cause the php api is still broken- as i focused on other engines first there are still problems that makes it unusable yet. what about seeks or yacy , is it possible to add engines?
-
@roland I agree that #YaCy will consume all the RAM and CPU you can throw at it. I tried putting it on its own #VPS for a while, but it did not respond to search queries or anything else during crawling and indexing. @pagsheathenman @navigium @moshpirit
-
@pagsheathenman you can add other search engine's results to #yacy for crawling them as long as they provide an #OpenSearch descriptor. This is a really nice and universal way, even my RSS news feed can now be a "search engine" as it provides such descriptor.