<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi everyone,<div class=""><br class=""></div><div class="">Resurrecting this thread and adding in Emma since she’s been asking about it and anarcat since he might need to be in the loop also,</div><div class=""><br class=""></div><div class="">Let’s just go ahead and use subdomain urls for search as it seems this will be the easiest and not making a decision either way means nothing is moving forward :)</div><div class=""><br class=""></div><div class="">We can always iterate on it if other options become available.</div><div class=""><br class=""></div><div class="">Thanks!</div><div class=""><br class=""></div><div class="">Pili </div><div class=""><br class=""><div class="">
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;">—<br class="">Project Manager: Tor Browser, UX and Community teams<br class="">pili at torproject dot org <br class="">gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45</div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 12 Feb 2019, at 14:34, silvia [hiro] <<a href="mailto:hiro@torproject.org" class="">hiro@torproject.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi all!<br class=""><br class="">On 2/11/19 5:46 PM, Alison Macrina wrote:<br class=""><blockquote type="cite" class="">[snip]<br class="">I don't see any issue with doing it that way. Could the user check boxes<br class="">to select just the support portal (or another portal)?<br class=""><br class="">Alison<br class=""><br class=""></blockquote>Sure we can. The ux can be designed as we want it. The only thing is the<br class="">url.<br class=""><br class="">It would help if we can use urls in the form of<br class=""><a href="http://search.support.torproject.org" class="">search.support.torproject.org</a> and <a href="http://search.tb-manual.torproject.org" class="">search.tb-manual.torproject.org</a> and so on.<br class=""><br class="">Talk soon,<br class=""><br class="">-hiro<br class=""><br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Cheers,<br class=""><br class="">-hiro<br class=""><br class="">On 11/16/18 9:22 AM, Linus Nordberg wrote:<br class=""><blockquote type="cite" class="">emma peel <<a href="mailto:emma.peel@riseup.net" class="">emma.peel@riseup.net</a>> wrote<br class="">Fri, 16 Nov 2018 07:41:00 +0000:<br class=""><br class=""><blockquote type="cite" class="">silvia [hiro]:<br class=""><blockquote type="cite" class="">On 11/15/18 10:06 AM, emma peel wrote:<br class=""><blockquote type="cite" class="">What I like about the 'central search' idea is that you can get a<br class="">User Manual result when searching Tor Support... because we have so<br class="">many different pieces of content that I liked the idea of moving<br class="">the user from one site to the other through the searches.<br class=""><br class="">Is this still going to happen with your proposal?<br class=""></blockquote>I like that too, but I think UX wanted search results per portal?<br class=""></blockquote>I don't know about doing it project-wide, but I feel that for example<br class=""><a href="http://support.torproject.org" class="">support.torproject.org</a> and <a href="http://tb-manual.torproject.org" class="">tb-manual.torproject.org</a> could share search<br class="">results.<br class=""></blockquote>I think this is a good time for figuring out what Tor Project wants from<br class="">a search function. I've put down a couple of statements sprinkled with<br class="">questions below. Please jump in and argue against false statements and<br class="">answer questions where possible. And please add more questions.<br class=""><br class=""><br class="">- The web site support.tpo needs a search field and a button next to it<br class=""> resulting in the user seeing a list of matching url's (and their<br class=""> titles) in their browser.<br class=""><br class="">- What corpus would such a search look at? support.tpo only? support.tpo<br class=""> and tb-manual.tpo? More than that?<br class=""><br class="">- Are there other tpo sites that need/want a search function? Should<br class=""> search results include matches from other tpo sites as well, or only<br class=""> the one the user is currently visiting?<br class=""><br class="">- Sending the user to a separate site, say search.tpo, is considered not<br class=""> UX friendly enough.<br class=""><br class="">- Is search.<site>.tpo good enough?<br class=""><br class="">- Are we limited to using solr, as mentioned in #25322, or can we<br class=""> explore other options?<br class=""><br class="">- User fronting tpo web sites are "on the static rotation" because<br class=""> that's how we can keep them up and running given the resources at<br class=""> hand. Adding dynamic content, i.e. anything that is not "oh, that url<br class=""> corresponds to this file, let's send it to the user", would not be<br class=""> possible on our current set of VM's given the load we see on user<br class=""> facing tpo websites. This means that one of the proposed solutions<br class=""> with web servers proxying requests to a separate service, search.tpo,<br class=""> is not an option. Another argument against proxying is that it breaks<br class=""> the expectation of end-to-end security given by HTTPS.<br class=""><br class=""></blockquote><br class=""><blockquote type="cite" class="">Roger Dingledine:<br class=""><blockquote type="cite" class="">On Fri, Nov 16, 2018 at 10:22:24AM +0100, Linus Nordberg wrote:<br class=""><blockquote type="cite" class="">- Are we limited to using solr, as mentioned in #25322, or can we<br class=""> explore other options?<br class=""></blockquote>I have vague memories that Isa and Hiro explored other options,<br class="">like outsourcing it to duckduckgo, but apparently the user flow was<br class="">horrible. So, I don't know what constraints we want now, but there is<br class="">some history of exploring other options.<br class=""><br class=""><blockquote type="cite" class="">- User fronting tpo web sites are "on the static rotation" because<br class=""> that's how we can keep them up and running given the resources at<br class=""> hand. Adding dynamic content, i.e. anything that is not "oh, that url<br class=""> corresponds to this file, let's send it to the user", would not be<br class=""> possible on our current set of VM's given the load we see on user<br class=""> facing tpo websites. This means that one of the proposed solutions<br class=""> with web servers proxying requests to a separate service, search.tpo,<br class=""> is not an option.<br class=""></blockquote>If there's some way to limit the number of searches (proxypasses) going<br class="">at once, so a crawler doesn't take down (fill all the slots of) all of<br class="">our static webservers, this idea might still be worth exploring. I feel<br class="">a bit bad putting in place something that is so obviously going to be a<br class="">source of ongoing pain, but I don't know of amazing better options that<br class="">match all the other goals.<br class=""><br class=""><blockquote type="cite" class="">Another argument against proxying is that it breaks<br class=""> the expectation of end-to-end security given by HTTPS.<br class=""></blockquote>If we're proxying to another service running *on that same machine*,<br class="">then I think we're ok on this point. It's just if we have some central<br class="">separate search service that it would be a problem. So for example if<br class="">solr is our choice, we could run a replicated solr on each webserver.<br class=""><br class="">--Roger<br class=""><br class=""></blockquote>_______________________________________________<br class="">tor-community-team mailing list<br class=""><a href="mailto:tor-community-team@lists.torproject.org" class="">tor-community-team@lists.torproject.org</a><br class="">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team<br class=""></blockquote>_______________________________________________<br class="">tor-community-team mailing list<br class=""><a href="mailto:tor-community-team@lists.torproject.org" class="">tor-community-team@lists.torproject.org</a><br class="">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team<br class=""><br class=""></blockquote></blockquote>_______________________________________________<br class="">tor-community-team mailing list<br class=""><a href="mailto:tor-community-team@lists.torproject.org" class="">tor-community-team@lists.torproject.org</a><br class="">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team<br class=""></div></div></blockquote></div><br class=""></div></body></html>