3

storing CSS in local storage would allow to be able to keep the same customization from regular search.

just save the CSS in local storage, and make the page use that for rendering, in both regular search and privacy pass search

    7 days later

    This is in our immediate roadmap. Should be available soon.

    what about filtering and reordering ? (personalized results)
    Is that even possible given your current architecture ?

      ak42

      The way that it would have to work is that your client would send up the domains you want to change rankings of - since we don't know who you are.
      I suppose technically it could client-side re-order the results but that may be odd/not work as well.

      But any server-side things require far more consideration because any bit we add contributes to your fingerprint and may de-anonymize you.

      Local things like custom css, themes, etc are all fine since it doesn't require any server interactions.

          @pixel

          Yes, I was thinking about filtering/reordering locally. isn't the reordering algorithm your own ? couldn't that be implemented locally ? how I see this (but that may have extra costs, financial and technical) is that instead of requesting the usual N results, you'd request like 2N results, use that for reordering and filtering, than just display N results. ditching the rest that have not been displayed. and take that into account for next results pages.
          But honestly I'm not sure people ever go to the second page given the quality of kagi's search results.

            also, just my two cents, for this to work with any hardened (or paranoid) browser setup, it would be nice to store domain list and CSS in the extension, not in kagi.com local storage. I, for one, heavily use temporary containers which get destroyed after tab close.

              We could implement re-ordering based on domain rules locally, yes.
              It really depends on how many people are interested in that and the feasibility of it.
              As you mention, it would probably require fetching more results to make it worth while in some cases, since we don't have as much control over it this way so we can't optimize how we do it like we do server-side for those types of things.

              We do have a proof of concept implementation of the local settings already, but it does store it in local storage and not within the extension itself.
              We would need to see how difficult it is to put it into the extension but I think that is something we can definitely explore.

              ak42 changed the title to Store Personalized results and CSS customisation in local storage for kagi pass to be able to work as well as before .
                No one is typing