[Tails-dev] Help needed with screenshots of Mac boot menu with Tails

[Spencer]

Hi,

intrigeri wrote:

Hi,

[shall we go on cross-posting forever, or?]



I will keep this in dev since you seem to like reading this kind of 
stuff :)




Do you need tests on another Mac?



All should perform the same based on their Boot ROM Version; here[0] is 
a list.  An OSXpert, or someone with access every Boot ROM Version, 
would need to fully confirm the subtle differences in each.


[0]: https://support.apple.com/en-gb/HT201518

---



sajolida:
Do you confirm that the DVD appears with a hard disk icon on



I cannot.  The disk icon image is what shows :(

Here [1] :)



Does it make any difference if the USB Stick is installed
using the command line?



Nope.  Tail 1.6 prompts the same screen and icon set on startup from USB 
Sticks that have Tails cloned via both the Tails Installer and Bash.


Direct USB Stick install might differ, but maybe not since I think the 
startup icons are driven by the firmware on whatever device is in 
question.




Well, now I'm wondering ...



No worries.  Although Cheetah, Panther, Leopard, and Lion introduce 
major graphic updates, it seems that there are only two major startup 
screens Mac users will be presented with today:


- One for Yosemite & El Capitan.
- One for Lion to Mavericks.

The differences here are icons and background colors; minor enough that 
it isn't confusing (unless they have the bug that shows a ghost volume, 
but an update would resolve that).


We could do a user driven image swap on the Mac instructions for higher 
accuracy.


Wordlife,
Spencer
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Desktop Camouflage

[intrigeri]

anonym wrote (21 Oct 2015 08:50:21 GMT) :
> http://gnome-look.org/content/show.php/Windows+10+Theme?content=171327

I'm glad there's a good starting point for anyone willing to take care
of it.

(But dear existing contributors, if you want Jessie stuff to
procrastinate on, by all means let me know: I probably have other
matters, that are release blockers, to point you to.)
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] T410 Was: Computer Help

[u]

Hi,

> I was wondering is a ThinkPad T410 was usable with Tails? It is
> listed as a computer that will not work but I read that other
> computers on that list DID work.

It has been reported not to work with a USB stick that was created using
Tails Installer:
https://tails.boum.org/support/known_issues/index.en.html#index16h2  but
can be used with one that was created manually or with a Tails DVD.

Please note that this is the Tails *development* mailinglist. In the
future, please direct support questions to the mailing lists indicated
here: https://tails.boum.org/support/

Cheers,
u.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] T410 Was: Computer Help

[u]

u:
> Hi,
> 
>> I was wondering is a ThinkPad T410 was usable with Tails? It is
>> listed as a computer that will not work but I read that other
>> computers on that list DID work.
> 
> It has been reported not to work with a USB stick that was created using
> Tails Installer:
> https://tails.boum.org/support/known_issues/index.en.html#index16h2  but
> can be used with one that was created manually or with a Tails DVD.
> 
> Please note that this is the Tails *development* mailinglist. In the
> future, please direct support questions to the mailing lists indicated
> here: https://tails.boum.org/support/

Oh and BTW, I *cannot* confirm that this does not work :)

At least using the version of the installer that I am currently working
on and the Tails 1.6 the T410 does perfectly boot from USB.

Cheers.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Releasing automated tests

[sajolida]

anonym:
> [Moving discussion to tails-dev@]

Meta: I really don't want to understand everything that's in this email
but I felt you would want me to answer this one. But if you think that
you can have this discussion without me I would be super happy as well.

> Given the trimming that has happened, some context may have been lost.
> The discussion is about that we now, in our Jenkins setup, automatically
> test images built from doc/ and web/ branches, which wastes a lot of
> time on our isotesters.
> 
>> From: intrigeri 
>> Date: Tue, 20 Oct 2015 13:08:31 +0200
>>
>>> From: bertagaz 
>>> Date: Mon, 19 Oct 2015 12:29:26 +0200
>>
 From: anonym 
>>>
 Still, once we release 1.7, then all doc/ and web/ branches will become
 tested. I suspect we will need a permanent fix for only building (not
 testing) these branches -- it's useless to test them 99.9% of the time,
 and they will block (for ~5 hours) test runs from relevant branches that
 got something pushed to them right after them.
>>
>>> That's something we didn't decide when during the design round. Sounds
>>> doable, but I wonder if there are still some valid points to still test
>>> that branches.
> 
> True, but there's an overwhelming amount of them, and their
> modifications are limited to something that is completely isolated from
> most of Tails, the OS, meaning that a huge part of each test run on them
> is just a (possibly out-dated) re-run of master/devel/stable depending
> on which branch it was based on. That is unlike feature/, bugfix/ and
> test/ branches, that need a full run in general. Perhaps you can see
> where I'm going:
> 
> As an optimization, we could introduce @web and @doc tags, and run the
> test suite with `--tag @web` or `--tag @doc` for doc/ and web/ branches,
> respectively. Then we could even have automated tests of @web changes
> before deploying them by browsing the local wiki in Tails. :)
> 
> Note that I may not have the correct understanding of the doc/ vs web/
> distinction, so I'd like a clarification just in case so we don't design
> something stupid. I suspect that since we don't have any automated tests
> for the *website* (as opposed to the docs) we only care about doc/ and
> only need to test web/ if we want to start testing the website.
> 
>> FTR I dislike the idea of blacklisting such branches based on their
>> name. I'm not going to debate it here [...]

The prefixes doc/ and web/ are used loosely to differentiate work on the
"documentation" (/doc /support) and the "website" in general (structure,
stuff not in /doc, etc.) but the difference is not strict.

I also don't think they should be tested. Maybe you could exclude them
from testing by their diff to their base branch. If all the diff is
under wiki/src then don't test that branch.

> Please do it here, then! :) I guess it's related to that you want at
> least doc/ branches to be tested, since our automated test suite
> actually depend on the documentation (see two quotes below for more on
> this).
> 

[...] Skipping tons of stuff I don't understand.

>> [...] making sure that the workaround is not worst than the problem
>> it fixes
> 
> The only effect should be that we won't get automated tests of the few
> scenarios that looks at the wiki shipped inside Tails. I think that
> currently is one scenario: The Report an Error launcher will open the
> support documentation in supported non-English locales. So, if some wiki
> change makes the 'the support documentation page opens in Tor Browser'
> step fail. The only way that can happen is if:
> 
> * the url to the "Help and Support" section changes so the desktop
> shortcut is wrong
> 
> * there's a change to the "Help and Support" section, or its German
> translation
> 
> * we change the website layout of the "parentlinks" thing, or the "home"
> icon there
> 
> Only in the first case would our test suite find an actual error, the
> other two just implies that our test is now out of sync and must be
> updated. Clearly it's not worth wasting that much isotester time on this
> at the moment.

Agreed. If I understand correctly, these scenarios have a *dependency*
on what is on the local copy of the website, but they are actually
testing the Tails software (the "Report an Error" launcher for example).
They are not testing the content of the local copy of the website itself.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Augmentez facilement votre chiffre d'affaire

[L'équipe d'Iziflux]

Vous appr?ciez notre newsletter. Pour ?tre s?r(e) de ne pas la manquer, nous 
vous conseillons d'ajouter l'adresse de l'exp?diteur ? votre carnet d'adresses.

[32% des internautes ont achet? sur des places de march? ces 6 derniers mois] 
Combien d'entre eux auraient
pu ?tre un de vos clients ? [Iziflux] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
[Iziflux] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
 [Iziflux] utm_source=iziflux20150928 Parce que l'optimisation et la diffusion 
de vos catalogues demande du temps et une grande expertise. [Iziflux] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
[Iziflux] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
 [Iziflux] utm_source=iziflux20150928 IZIFLUX met ? votre service une ?quipe de 
sp?cialistes pour vous accompagner dans l'interfa?age entre votre site et les 
diff?rents supports de vente. [Iziflux] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
[Iziflux] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
 Diffusez et personnalisez vos catalogues produits vers vos diff?rents 
partenaires.

Rentabilisez votre pr?sence sur les comparateurs de prix en optimisant votre 
visibilit? et votre R.O.I.

D?veloppez vos ventes sur les places de march? gr?ce aux conseils d'un expert 
pour optimiser vos campagnes. [G?rer et exporter, augmentez vos ventes, conseil 
et actions] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
[Iziflux] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
 [Acc?dez ? tous les supports de vente] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
 Acc?dez ? tous les supports de vente ? partir de 49€HT/mois
[Acc?dez ? tous les supports de vente] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
 D?couvrez de nombreux conseils sur les strat?gies
marketing ? mettre en ?uvre sur le Blog Iziflux.

6 fa?ons de tirer pleinement parti de Google Shopping ! 
http://www.qbcsinnq.com/kdsge/AwQWDoMGkQ3FQ7lj92LS2voeROpPsg8RCKcAEDgaUjNBRIixPIBjgiwGJxQLopEczRMgGgYel5bY2Ofy7gfKhPGROEtEQK6HJrHIEZxGiZm8uEbSUD8

Amazon France se diversifie avec les cat?gories ??alimentation?? et ??boisson?? 
http://www.qbcsinnq.com/kdsge/AwQWDoMGkQ3FQ7lj92LS2voeROqPyHsIAMyQcTQ4haglAqKRSjFAVEn0kmIsHEB1CMlySGcBTIvBEUEPBGBZmKYxtdE4C4dYRdAgpHA0BY9LS2zsq5P3A2XC~EicJSIg10OTWOQITqPETF5cI2moHw

Infographie Twenga : Le M-commerce en Europe en 2015 
http://www.qbcsinnq.com/kdsge/AwQWDoMGkQ3FQ7lj92LS2voeROqPqHsIEI2CwxABPA4IAmdiHQ0D0CyrYAaBc8ITrYIbmlJQIo73OnFpbX0Pkdho89T9QJkwPhJniQjI9dAkFjmC0ygxkxfXSBrqBw

Iziflux sera ? la Formidable Soir?e du E-commerce ce Jeudi 15 Octobre 
http://www.qbcsinnq.com/kdsge/AwQWDoMGkQ3FQ7lj92LS2voeROqPUA_x5HAkhAiQxrCUouCIMBDDE1gQOBIHIlqhGVAlDQIHE5ZoFbytT~E0UxGIEB~XltjYl9d2P1AmjI_E2Ue_HprEIkdwGiVm8uIaSUP9

Notre partenaire monEchelle.fr devient ManoMano et se lance en Europe ! 
http://www.qbcsinnq.com/kdsge/AwQWDoMGkQ3FQ7lj92LS2voeROqHcIUPQcMxiRA4DyC1pUnQA8FwXiI4iiUUnEJUDEsFKRrTwwAS9wlwCFMhnWIBaAhrjVQKSsTxpI5LS2zsk233A2XC~EicJSIg10OTWOQITqPETF5cI2moHw

Auchan pr?t ? lancer sa marketplace ! 
http://www.qbcsinnq.com/kdsge/AwQWDoMGkQ3FQ7lj92LS2voeROqHcIEPAYAiOI4G5xEhTOkNS9EQEKJGagVTGgVh8lgaYeFxaYmNfW3mfqBMGB~Js0QE5HpoEoscwWmUmMmLayQN9QM


 
[Iziflux] 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyxe4EgBQAExxAlE6qVf~ZHvR_PhPGROEtEQK7neePS2vpUo00cwUFQYiYvrpE01A8
 www.iziflux.com 
http://www.qbcsinnq.com/kdsge/A1sgsqGwoNyx~4EyLR~Js0QE5HqeOC6trU812sQRHAQlZvLiGklD_Q

Transf?rez ce message 
mailto:?subject=Un%20ami%20vous%20conseille%20une%20offre=Un%20ami%20vous%20invite%20%20dcouvrir%20l'offre%20de%20CW%20sur%20http://www.crea-news-01.com/mailing/mailing_cib_leweb/2015_09_16_iziflux/newsletter_besonews.htm

Si vous ne souhaitez plus recevoir d'informations de la part de CW par e-mail, 
d?sabonnez vous 
http://www.qbcsinnq.com/kdsge/AyhkXZppNHFoFAiGhFLk2L2cHwOCBBBwNPFYGIg1RBAQKj~3TgEYRAhSqOthAkAsJJwBoR4QAQeFzZ0JggWC0JiPjsCO4CAoMZMX10ga6gc
Cet e-mail commercial est conforme ? la l?gislation en vigueur et aux 
d?lib?rations de la CNIL des 22 et 30 mars 2005 sur la prospection
par courrier ?lectronique dans le cadre professionnel. Conform?ment ? l'article 
34 de la loi 78-17 du 6 janvier 1978
relative ? l'informatique, aux fichiers et aux libert?s,vous disposez d'un 
droit d'acc?s, de rectification de donn?es nominative vous concernant.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send 

Re: [Tails-dev] Redmine maintainence Oct. 28, 9:30am EST - Oct. 30

[sajolida]

BitingBird:
> micah:
>>
>> Hello!
>> [...]
>> We came up with Oct. 28th (wednesday) at 9:30am eastern US time for
>> starting the upgrade process. This was the best time for us to come
>> together and work on this. We are expecting the work to not last very
>> long, but with redmine we have found it best to expect the unexpected,
>> so we want to schedule the outage for two days, through the 30th, to get
>> everything worked out before we are done.
>>
>>  micah
>>
> Noted... and thanks very, very much to you and all the others riseup
> birds for your amazing work!

Yeap, thanks for the notice and for all the work!

What's the preferred communication channel if we want to have updates on
the process either to lurk or to give a hand? #riseup on
irc.indymedia.org? or maybe you don't do that kind of stuff...
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Native English fixes to pages linked from about.mdwn

[Jesse W]

Yet another native English fix branch, here:

https://gitlab.com/JesseW/tails/commits/doc_fixes4

14 files changed, 66 insertions(+), 66 deletions(-)

sajolida, thanks for merging all my previous changes!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] [Tails-testers] Help needed with screenshots of Mac boot menu with Tails

[sajolida]

Spencer:
> Hi,
> 
>> Spencer:
>> [Something close to correct]
> 
> Actually, here[0] is the DVD startup screen, and here[1] is the USB
> Stick startup screen.

Thanks for the fast reply. These are great!

Do you confirm that the DVD appears with a hard disk icon on [0]!?
That's weird, but so be it :) Because on this one I see a DVD icon, but
maybe Tails acts different:

http://www.mactrast.com/wp-content/uploads/2011/09/install-os-x-lion-dvd-drive.jpg

On [1] I guess this was a Tails USB stick installed using Tails
Installer? Does it make any difference if the USB stick is installed
using dd and the command line? Like instructed on
https://tails.boum.org/doc/first_steps/installation/manual/mac/

If you don't know how to do that don't worry...

> These are a hybrid of Yosemite, El Capitan, and whatever came on the
> 2009 macs in this library (depreciated startup disk and USB icons appear
> at boot).
> 
> Let me know if you would like these adjusted in any way.

Well, now I'm wondering whether we should put these screenshots in the
Mac instructions. If they differ greatly from one Mac to another or if
the icons don't make much sense (like a hard disk instead of a DVD
sometimes), then maybe we should instead document to select whatever
option is not "Macintosh HD" (or "on the right") or just let the people
figure out which one is the good one, without giving partially confusing
instructions (or screenshots) in some cases.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Redmine maintainence Oct. 28, 9:30am EST - Oct. 30

[micah]

sajolida  writes:

> BitingBird:
>> micah:
>>>
>>> Hello!
>>> [...]
>>> We came up with Oct. 28th (wednesday) at 9:30am eastern US time for
>>> starting the upgrade process. This was the best time for us to come
>>> together and work on this. We are expecting the work to not last very
>>> long, but with redmine we have found it best to expect the unexpected,
>>> so we want to schedule the outage for two days, through the 30th, to get
>>> everything worked out before we are done.
>>>
>>>  micah
>>>
>> Noted... and thanks very, very much to you and all the others riseup
>> birds for your amazing work!
>
> Yeap, thanks for the notice and for all the work!
>
> What's the preferred communication channel if we want to have updates on
> the process either to lurk or to give a hand? #riseup on
> irc.indymedia.org? or maybe you don't do that kind of stuff...

Usually when we have a work party, we will form a temporary channel
where we can spam each other, without disrupting the main #riseup
channel. But come there if you are interested, and we can hook you into
the right place!

micah
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] [Tails-testers] Help needed with screenshots of Mac boot menu with Tails

[intrigeri]

Hi,

[shall we go on cross-posting forever, or?]

sajolida wrote (22 Oct 2015 15:39:30 GMT) :
> If they differ greatly from one Mac to another [...]

Do you need tests on another Mac?

Cheers,
-- 
intrigeri
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Fwd: [tor-dev] Status of Open Hidden Service Proposals (October 2015)

[intrigeri]

Hi,

those of us who don't follow tor-dev closely may be interested in this
nice summary of the hidden^Wonion services improvements that are in
the works.

[Jurre: you'll understand why I'm forwarding this and Cc'ing you.]

--- Begin Message ---
Greetings,

it's well known that hidden services need some love:
 https://blog.torproject.org/blog/hidden-services-need-some-love

For the past 2 years we've been busy designing the upcoming hidden service
protocol with improved cryptography, security, and performance. During this time
we've written a good amount of improvement proposals and specifications, that
have now been floating around our git repositories. In this mail I aim to
collect and briefly explain all these proposals in one place so that researchers
and developers have easier access to them. Ideally we would also make a wiki
page tracking them.

Similar efforts have been done for the set of all Tor proposals by Nick:
 
https://blog.torproject.org/blog/tor-design-proposals-how-we-make-changes-our-protocol
 https://gitweb.torproject.org/torspec.git/tree/proposals/proposal-status.txt

This might also make for an informative blog post if I clean it up a bit. Please
let me know if I should try to get it posted on the blog so that it reaches a
greater audience.

Let's start walking over each proposal in a hopefully reasonable order:



== Proposal 250: Random Number Generation During Tor Voting ==

   [Prerequisite proposal]

   URL: 
https://gitweb.torproject.org/torspec.git/tree/proposals/250-commit-reveal-consensus.txt
   Status: [Under development - 
https://trac.torproject.org/projects/tor/ticket/16943]

   This is a prerequisite for the proposals that follow. It specifies how the 
Tor
   directory authorities can produce a fresh and unpredictable random value
   every day.

   We plan to use this value to randomize the responsible HSDirs of hidden
   services and make them unpredictable. This will help defend against attacks 
that
   require the attacker to become the HSDir of a hidden service.
   
== Proposal 224: Next-Generation Hidden Services in Tor ==

   [Main proposal!]

   URL: 
https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt
   Status: [Under development - 
https://trac.torproject.org/projects/tor/ticket/12424]

   This is the master proposal of the "Next Generation Hidden Services" project.

   It outlines a more or less completely revised version of the Tor hidden
   services protocol, improved to accomodate better cryptography and defenses
   for several attacks we'd never considered when we did the original design!

   The following proposals plug into the protocol specified by this proposal.

== Proposal 246: Merging Hidden Service Directories and Introduction Points ==

   [Performance improvement]

   URL: 
https://gitweb.torproject.org/torspec.git/tree/proposals/246-merge-hsdir-and-intro.txt
   Status: [Research Phase - 
https://lists.torproject.org/pipermail/tor-dev/2015-July/009079.html]

   This document describes a modification to proposal 224, which simplifies and
   improves the architecture by combining hidden service directories and
   introduction points at the same relays. It will speed up the initial
   connection to hidden services considerably since only two circuit
   establishments will be needed instead of three.

== Proposal 247: Defending Against Guard Discovery Attacks using Vanguards ==

   [Security improvement]

   URL: 
https://gitweb.torproject.org/torspec.git/tree/proposals/247-hs-guard-discovery.txt
   Status: [Research Phase - 
https://lists.torproject.org/pipermail/tor-dev/2015-July/009066.html]

   This document describes a modification to the path selection for hidden
   service circuits. It aims to defend against attacks where clients try to 
discover the
   hidden service's guard relay(s).

   This proposal also depends on having better and more robust algorithms for
   guard node selection. This requires another mini-proposal:
https://lists.torproject.org/pipermail/tor-dev/2015-August/009297.html

== Proposal 255: Controller features to allow for load-balancing hidden 
services ==

   [Scalability improvement]

   URL: 
https://gitweb.torproject.org/torspec.git/tree/proposals/255-hs-load-balancing.txt
   Discussion thread: 
https://lists.torproject.org/pipermail/tor-dev/2015-September/009597.html
   Status: [Under Development - 
https://trac.torproject.org/projects/tor/ticket/17254]

   We have plans for bringing hidden services to the next level. We are talking
   hidden services with 100x the clients they can currently handle, and with
   mechanisms that allow operators to load balance and achieve high 
availability.

   This proposal defines a way for hidden services to _load balance_ their
   clients by allowing *multiple hosts* to do the actual rendezvous with the
   clients. This is something that busy hidden service operators need