Comment by ☯️ dragfyre
Re: "Is there a smolnet search engine/search aggregator for…"
@clseibold are there significant changes that need to be done to get it searching on gopher, or is it more about flipping the right switches and running the crawler?
2025-06-22 · 10 months ago
1 Later Comment
🚀 clseibold [🛂] · 2025-06-22 at 22:50:
@dragfyre Aside from writing a gopher client and gopehrmap parser in Golang, the only other thing is to figure out how I'm going to store the info in the database.
Some gopher search engines will store all of the itemtypes of a gophermap in the db, but that's a different model from how my db works for gemini, nex, scroll, and spartan.
Currently, I save every *url* and details of its content, one row for each url. Whereas a gopher search engine might save multiple rows of gophermap items per path. So it's definitely a little different, particularly because a gophermap item doesn't necessarily correlate to a URL, let alone a gopher resource (there are other itemtypes like text and WAIS, etc.).
But I think I can adapt the gopher model into the current model that I use. Idk, we'll see.
Original Post
Is there a smolnet search engine/search aggregator for multiple protocols at once? (gemini, gopher, nex, etc) — I was wondering if there were a multi smolnet protocol search engine I could set as default for Lagrange.