TESTING: Related Queries

[Josh]

Hello @all, we’ve got something new to share for testing, currently via a cookie. I’ll explain the functionality first, then put the method for how to try it out.

What this is

This functionality adds a selection of Related Queries to the right-hand side of the Search Engine Results Page, allowing you to quickly narrow down or change a search based upon what Mojeek interprets to be ways in which your search could produce better results.

How to test it out:

Much like with Focus, you can access this functionality with an FFID cookie using the value 8FsVK0uk on path / like so:

Browser methods are in the Focus How To Set Up - changing the value to 8FsVK0uk, obviously.

After that, the related queries should pop up on a refresh and search, and you should be all good to go.

What we are looking for:

• general bugs/outputs by the tool which seem broken
• examples of where this has helped you to find something
• examples of where the related searches seem off related to the query
• any other comments you may have

[mike]

TESTING: Mojeek Summary

Hi @mike, just regarding the comment about being kicked out of other experiments, if you comma separate your FFID cookie values, you can have multiple tests enabled. For maps and summary, you’d need the value of the FFID cookie to be eiSoh7ii,B9FX3DK3. Hope this helps! Cheers, Ash

---

@Josh Is this covered by the Mojeek privacy policy? Or, is there a third party involved?

[gnome]

I noticed Mojeek fetches the related queries dynamically after the page loads, so Javascript needs to be enabled for this to work.

I suspected these related queries were generated from an LLM (based on the dynamic nature of it and the wording of the responses), and looking at the JS code, that seems to be the case.

I think it could be a good idea but I’m not sure if I specifically will get much use out of it. My limited testing so far has been really weird/unrelated queries, or even SEO results? One “Related Query” was simply the letter N.

+1 for @mike 's question.

[Josh]

Lepton is used in order to generate the related queries; a similar process to what happens when someone is using Mojeek Summary. The user is not connecting to any third party during this process, just Mojeek on the backend.

@gnome

My limited testing so far has been really weird/unrelated queries, or even SEO results? One “Related Query” was simply the letter N.

If you’re able to let us know what these were, here or via the usual channels, then it would be greatly appreciated

[mike]

I thought this earlier comment on Summaries was more clear than the blog post:

@Josh

This uses an external model/API and requests to it include the query and results; no other personal data is sent, and all of the requests which are made come from our own Mojeek IP addresses. For now this is an experiment so we’re considering options on the way in which it will be offered up to the general public, full transparency about this will be given with the release.

[gnome]

@Josh

If you’re able to let us know what these were, here or via the usual channels, then it would be greatly appreciated

Done, using the feedback button!

---

Probed a bit deeper and these Related Queries seem pretty effective at surfacing more useful results, but the later queries tend to surface SEO-optimized pages that are not useful at best. I think it’s a good idea and could be great with a lot of refining.

I’ll test it some more. I’ll probably go back to turning JS off at some point though…