tor-commits March 2014

tor-commits@lists.torproject.org

22 participants
2036 discussions

[translation/tor-launcher-progress] Update translations for tor-launcher-progress
by translation＠torproject.org 12 Mar '14

12 Mar '14

commit f11ee04d0178701ceeb28e96529b228485464c1c Author: Translation commit bot <translation(a)torproject.org> Date: Wed Mar 12 15:15:35 2014 +0000 Update translations for tor-launcher-progress --- ru/progress.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru/progress.dtd b/ru/progress.dtd index 9fa296b..47827da 100644 --- a/ru/progress.dtd +++ b/ru/progress.dtd @@ -1,4 +1,4 @@ <!ENTITY torprogress.dialog.title "Статус Tor"> <!ENTITY torprogress.openSettings "Открыть Настройки"> <!ENTITY torprogress.heading "Подключение к сети Tor"> -<!ENTITY torprogress.pleaseWait "Please wait while we establish a connection to the Tor network."> +<!ENTITY torprogress.pleaseWait "Пожалуйста, подождите, пока будет установлено соединение с сетью Tor.">

1 0

[translation/tor-launcher-properties_completed] Update translations for tor-launcher-properties_completed
by translation＠torproject.org 12 Mar '14

12 Mar '14

commit 9fe01f0f2d1d145c5dfd867e338a37173ae80197 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Mar 12 15:15:33 2014 +0000 Update translations for tor-launcher-properties_completed --- ru/torlauncher.properties | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ru/torlauncher.properties b/ru/torlauncher.properties index b5766ee..f9f81a7 100644 --- a/ru/torlauncher.properties +++ b/ru/torlauncher.properties @@ -24,8 +24,8 @@ torlauncher.ensure_tor_is_running=Убедитесь что Tor запущен. torlauncher.error_proxy_addr_missing=Вы должны указать IP-адрес или имя хоста и порт, чтобы настроить Tor и использовать прокси для доступа в Интернет. torlauncher.error_proxy_type_missing=Необходимо выбрать тип прокси. torlauncher.error_bridges_missing=Необходимо задать один или несколько мостов. -torlauncher.error_default_bridges_type_missing=Вы должны выбрать тип транспорта для мостов по умолчанию. -torlauncher.error_bridge_bad_default_type=Мосты по умолчанию не поддерживают тип транспорта %S. Пожалуйста, исправьте ваши настройки. +torlauncher.error_default_bridges_type_missing=Вы должны выбрать тип транспорта предопределенных мостов. +torlauncher.error_bridge_bad_default_type=Предопределенные мосты не поддерживают тип транспорта %S. Пожалуйста, исправьте ваши настройки. torlauncher.recommended_bridge=(рекомендуемый)

1 0

[translation/tor-launcher-properties] Update translations for tor-launcher-properties
by translation＠torproject.org 12 Mar '14

12 Mar '14

commit 02676159c7be6b5aa2fbada392760642b1e31e5c Author: Translation commit bot <translation(a)torproject.org> Date: Wed Mar 12 15:15:31 2014 +0000 Update translations for tor-launcher-properties --- ru/torlauncher.properties | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ru/torlauncher.properties b/ru/torlauncher.properties index 776311f..f9f81a7 100644 --- a/ru/torlauncher.properties +++ b/ru/torlauncher.properties @@ -24,8 +24,8 @@ torlauncher.ensure_tor_is_running=Убедитесь что Tor запущен. torlauncher.error_proxy_addr_missing=Вы должны указать IP-адрес или имя хоста и порт, чтобы настроить Tor и использовать прокси для доступа в Интернет. torlauncher.error_proxy_type_missing=Необходимо выбрать тип прокси. torlauncher.error_bridges_missing=Необходимо задать один или несколько мостов. -# torlauncher.error_default_bridges_type_missing=You must select a transport type for the provided bridges. -# torlauncher.error_bridge_bad_default_type=No provided bridges that have the transport type %S are available. Please adjust your settings. +torlauncher.error_default_bridges_type_missing=Вы должны выбрать тип транспорта предопределенных мостов. +torlauncher.error_bridge_bad_default_type=Предопределенные мосты не поддерживают тип транспорта %S. Пожалуйста, исправьте ваши настройки. torlauncher.recommended_bridge=(рекомендуемый)

1 0

[translation/tor-launcher-network-settings_completed] Update translations for tor-launcher-network-settings_completed
by translation＠torproject.org 12 Mar '14

12 Mar '14

commit 0d393c11dc7e78de17e12bd8efb1da2073395279 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Mar 12 13:15:39 2014 +0000 Update translations for tor-launcher-network-settings_completed --- ja/network-settings.dtd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ja/network-settings.dtd b/ja/network-settings.dtd index 193dc17..b7ea058 100644 --- a/ja/network-settings.dtd +++ b/ja/network-settings.dtd @@ -1,8 +1,8 @@ -<!ENTITY torsettings.dialog.title "Tor ブラウザーネットワーク設定"> +<!ENTITY torsettings.dialog.title "Torネットワーク設定">  -<!ENTITY torsettings.prompt "Tor ブラウザがTorネットワークへの接続を試みる前に、このコンピュータのインターネット接続についての情報を提供する必要があります。"> +<!ENTITY torsettings.prompt "Tor ネットワークに接続する前に、このコンピューターのインターネット接続についての情報を提供して頂く必要があります。"> <!ENTITY torSettings.yes "はい"> <!ENTITY torSettings.no "いいえ">

1 0

[translation/tor-launcher-network-settings] Update translations for tor-launcher-network-settings
by translation＠torproject.org 12 Mar '14

12 Mar '14

commit 6dd2f6f5e945c18958a2c26133b3aa6bc5c55e4c Author: Translation commit bot <translation(a)torproject.org> Date: Wed Mar 12 13:15:37 2014 +0000 Update translations for tor-launcher-network-settings --- ja/network-settings.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/network-settings.dtd b/ja/network-settings.dtd index ec7cfe6..b7ea058 100644 --- a/ja/network-settings.dtd +++ b/ja/network-settings.dtd @@ -2,7 +2,7 @@  -<!ENTITY torsettings.prompt "Before you connect to the Tor network, you need to provide information about this computer's Internet connection."> +<!ENTITY torsettings.prompt "Tor ネットワークに接続する前に、このコンピューターのインターネット接続についての情報を提供して頂く必要があります。"> <!ENTITY torSettings.yes "はい"> <!ENTITY torSettings.no "いいえ">

1 0

[translation/tor-launcher-progress_completed] Update translations for tor-launcher-progress_completed
by translation＠torproject.org 12 Mar '14

12 Mar '14

commit 824a972f1eebcf567fcadec74bb572e063aa5c4b Author: Translation commit bot <translation(a)torproject.org> Date: Wed Mar 12 13:15:34 2014 +0000 Update translations for tor-launcher-progress_completed --- ja/progress.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/progress.dtd b/ja/progress.dtd index 883f748..9d03c6b 100644 --- a/ja/progress.dtd +++ b/ja/progress.dtd @@ -1,4 +1,4 @@ <!ENTITY torprogress.dialog.title "Torの状態"> <!ENTITY torprogress.openSettings "設定を開く"> <!ENTITY torprogress.heading "Torネットワークに接続しています"> -<!ENTITY torprogress.pleaseWait "Tor BrowserはTorのネットワーク接続が確立された後に開きます。"> +<!ENTITY torprogress.pleaseWait "Tor ネットワークへの接続を確立するまでの間お待ちください。">

1 0

[translation/tor-launcher-progress] Update translations for tor-launcher-progress
by translation＠torproject.org 12 Mar '14

12 Mar '14

commit 6f3dfb69040d200fd4aa185daccb36265d0c8613 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Mar 12 13:15:32 2014 +0000 Update translations for tor-launcher-progress --- ja/progress.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/progress.dtd b/ja/progress.dtd index 0e8c63a..9d03c6b 100644 --- a/ja/progress.dtd +++ b/ja/progress.dtd @@ -1,4 +1,4 @@ <!ENTITY torprogress.dialog.title "Torの状態"> <!ENTITY torprogress.openSettings "設定を開く"> <!ENTITY torprogress.heading "Torネットワークに接続しています"> -<!ENTITY torprogress.pleaseWait "Please wait while we establish a connection to the Tor network."> +<!ENTITY torprogress.pleaseWait "Tor ネットワークへの接続を確立するまでの間お待ちください。">

1 0

[onionoo/master] Take out old news.
by karsten＠torproject.org 12 Mar '14

12 Mar '14

commit 558615fc41771c9d7bc31aa3b2403643534de9bc Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Tue Mar 11 16:41:31 2014 +0100 Take out old news. --- web/index.html | 6 ------ 1 file changed, 6 deletions(-) diff --git a/web/index.html b/web/index.html index d327506..a4aee86 100644 --- a/web/index.html +++ b/web/index.html @@ -772,7 +772,6 @@ running in the last relay network status consensus. </li> <li> -hibernating <code class="typeof">boolean</code> optional @@ -783,7 +782,6 @@ running anymore has reached its accounting limit and has not dropped out of the network for another, unknown reason. Omitted if either the relay is not hibernating, or if no information is available about the hiberation status of the relay. -Added on January 28, 2014. </li> @@ -1010,7 +1008,6 @@ rejects (accepts) all other ports. </li> <li> -exit_policy_v6_summary <code class="typeof">object</code> optional @@ -1020,7 +1017,6 @@ If there is an "accept" ("reject") element, the relay accepts (rejects) all TCP ports or port ranges in the given list for most IP addresses and rejects (accepts) all other ports. Missing if the relay rejects all connections to IPv6 addresses. -Added on January 6, 2014. </li> @@ -1048,7 +1044,6 @@ found. </li> <li> -recommended_version <code class="typeof">boolean</code> optional @@ -1056,7 +1051,6 @@ Boolean field saying whether the Tor software version of this relay is recommended by the directory authorities or not. Omitted if either the directory authorities did not recommend versions, or the relay did not report which version it runs. -Added on January 13, 2014. </li>

1 0

[onionoo/master] Clean up protocol specification.
by karsten＠torproject.org 12 Mar '14

12 Mar '14

commit 5a7c60f5ebb7e4f2c01fcddd9ec8a3a50e34472c Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Tue Mar 11 16:40:36 2014 +0100 Clean up protocol specification. No new content, just trying to flatten the lists. --- web/index.html | 718 +++++++++++++++++++++++--------------------------------- 1 file changed, 294 insertions(+), 424 deletions(-) diff --git a/web/index.html b/web/index.html index 732ff8f..d327506 100644 --- a/web/index.html +++ b/web/index.html @@ -55,6 +55,7 @@ h3 .request-response { padding: 0 !important; } <li><a href="#methods">Methods</a></li> <li><a href="#summary">Summary documents</a></li> <li><a href="#details">Details documents</a></li> + <li><a href="#history">History objects</a></li> <li><a href="#bandwidth">Bandwidth documents</a></li> <li><a href="#weights">Weights documents</a></li> <li><a href="#clients">Clients documents</a></li> @@ -214,6 +215,13 @@ document</a> document</a> </li> +<li class="api-request"> +GET +https://onionoo.torproject.org/uptime +returns a <a href="#uptime">uptime +document</a> +</li> + </ul> <h4>Parameters</h4> @@ -471,8 +479,36 @@ Indicates how recent the relay summaries in this document are. <code class="typeof">array of objects</code> required -Array of objects representing relay summaries. -Each array object contains the following key-value pairs: +Array of relay summary objects as specified below. + +</li> + +<li> +bridges_published +<code class="typeof">string</code> +required + +UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last known bridge network status was published. +Indicates how recent the bridge summaries in this document are. + +</li> + +<li> +bridges +<code class="typeof">array of objects</code> +required + +Array of bridge summary objects as specified below. + +</li> + +</ul> + +<h4>Relay summary objects</h4> + + +Relay summary objects contain the following key-value pairs: <ul class="properties"> @@ -521,26 +557,11 @@ running in the last relay network status consensus. </li> </ul> -</li> -<li> -bridges_published -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when -the last known bridge network status was published. -Indicates how recent the bridge summaries in this document are. - -</li> +<h4>Bridge summary objects</h4> -<li> -bridges -<code class="typeof">array of objects</code> -required -Array of objects representing bridge summaries. -Each array object contains the following key-value pairs: +Bridge summary objects contain the following key-value pairs: <ul class="properties"> @@ -577,10 +598,6 @@ running in the last bridge network status. </ul> -</li> - -</ul> - </div>  <div class="box"> @@ -617,8 +634,37 @@ Indicates how recent the relay details in this document are. <code class="typeof">array of objects</code> required -Array of objects representing relay details. -Each array object contains the following key-value pairs: +Array of relay details objects as specified below. + +</li> + +<li> +bridges_published +<code class="typeof">string</code> +required + +UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last known bridge network status was published. +Indicates how recent the bridge details in this document are. + +</li> + +<li> +bridges +<code class="typeof">array of objects</code> +required + +Array of bridge details objects as specified below. + + +</li> + +</ul> + +<h4>Relay details objects</h4> + + +Relay details objects contain the following key-value pairs: <ul class="properties"> @@ -1101,25 +1147,10 @@ bandwidth weights. </ul> -</li> -<li> -bridges_published -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when -the last known bridge network status was published. -Indicates how recent the bridge details in this document are. - -</li> +<h4>Bridge details objects</h4> -<li> -bridges -<code class="typeof">array of objects</code> -required -Array of objects representing bridge summaries. -Each array object contains the following key-value pairs: +Bridge details objects contain the following key-value pairs: <ul class="properties"> @@ -1258,82 +1289,21 @@ available. </ul> -</li> - -</ul> - </div>  <div class="box"> -<a name="bandwidth"></a> -<h3>Bandwidth documents <a href="#bandwidth">#</a> - -<a href="bandwidth?limit=4">example request</a> - -</h3> - - -Bandwidth documents contain aggregate statistics of a relay's or -bridge's consumed bandwidth for different time intervals. -Bandwidth documents are available for all relays and bridges that have -been running in the past week. -Bandwidth documents contain the following fields: - - -<ul class="properties"> +<a name="history"></a> +<h3>History objects <a href="#history">#</a></h3> -<li> -relays_published -<code class="typeof">string</code> -required -UTC timestamp (YYYY-MM-DD hh:mm:ss) when -the last known relay network status consensus started being valid. -Indicates how recent the relay bandwidth documents in this document are. - -</li> - -<li> -relays -<code class="typeof">array of objects</code> -required +History objects are no documents by themselves, but are contained in +subsequent documents. -Array of objects representing relay bandwidth -documents. -Each array object contains the following key-value pairs: - - -<ul class="properties"> -<li> -fingerprint -<code class="typeof">string</code> -required - -Relay fingerprint consisting of 40 upper-case -hexadecimal characters. - -</li> +<h4>Graph history objects</h4> -<li> -write_history -<code class="typeof">object</code> -required -Object containing bandwidth history objects -for different time periods. -Keys are string representation of the time period covered by the bandwidth -history object. -Keys are fixed strings "3_days", -"1_week", "1_month", -"3_months", "1_year", and -"5_years". -Keys refer to the last known bandwidth history of a relay, not to the time -when the bandwidth document was published. -A bandwidth history object is only contained if the time period it covers -is not already contained in another bandwidth history object with shorter -time period and higher data resolution. -Each bandwidth history object contains the following key-value pairs: +Graph history objects contain the following fields: <ul class="properties"> @@ -1343,8 +1313,8 @@ Each bandwidth history object contains the following key-value pairs: <code class="typeof">string</code> required -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the first data -data point in the bandwidth history. +UTC timestamp (YYYY-MM-DD hh:mm:ss) of the first data point, or more +specifically the interval midpoint of the first interval. </li> @@ -1353,8 +1323,8 @@ data point in the bandwidth history. <code class="typeof">string</code> required -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the last data -data point in the bandwidth history. +UTC timestamp (YYYY-MM-DD hh:mm:ss) of the last data point, or more +specifically the interval midpoint of the last interval. </li> @@ -1372,11 +1342,10 @@ Time interval between two data points in seconds. <code class="typeof">number</code> required -Factor by which subsequent bandwidth values need to -be multiplied to get a unit of bytes per second. -The idea is that contained bandwidth values are normalized to a range from -0 to 999 to reduce document size while still providing sufficient detail -for both slow and fast relays. +Factor by which subsequent data values need to be multiplied to obtain +original values. +The idea is to reduce document size while still providing sufficient +detail for very different data scales. </li> @@ -1385,8 +1354,7 @@ for both slow and fast relays. <code class="typeof">number</code> optional -Number of provided data points, included mostly for -debugging purposes. +Number of provided data points, included mostly for debugging purposes. Can also be derived from the number of elements in the subsequent array. </li> @@ -1396,10 +1364,8 @@ Can also be derived from the number of elements in the subsequent array. <code class="typeof">array of numbers</code> required -Array of normalized bandwidth values in bytes per -second. -May contain null values if the relay did not provide any bandwidth data or -only data for less than 20% of a given time period. +Array of normalized values between 0 and 999. +May contain null values. Contains at least two subsequent non-null values to enable drawing of line graphs. @@ -1407,23 +1373,46 @@ graphs. </ul> -</li> +</div>  + +<div class="box"> +<a name="bandwidth"></a> +<h3>Bandwidth documents <a href="#bandwidth">#</a> + +<a href="bandwidth?limit=4">example request</a> + +</h3> + + +Bandwidth documents contain aggregate statistics of a relay's or +bridge's consumed bandwidth for different time intervals. +Bandwidth documents are available for all relays and bridges that have +been running in the past week. +Bandwidth documents contain the following fields: + + +<ul class="properties"> <li> -read_history -<code class="typeof">object</code> +relays_published +<code class="typeof">string</code> required -Object containing bandwidth history objects -for different time periods. -The specification of bandwidth history objects is similar to those in the -write_history field. +UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last known relay network status consensus started being valid. +Indicates how recent the relay bandwidth documents in this document are. </li> -</ul> - +<li> +relays +<code class="typeof">array of objects</code> +required + +Array of relay bandwidth objects as specified below. + </li> + <li> bridges_published <code class="typeof">string</code> @@ -1440,9 +1429,73 @@ Indicates how recent the bridge bandwidth documents in this document are. <code class="typeof">array of objects</code> required -Array of objects representing bridge bandwidth -documents. -Each array object contains the following key-value pairs: +Array of bridge bandwidth objects as specified below. + +</li> + +</ul> + +<h4>Relay bandwidth objects</h4> + + +Relay bandwidth objects contain the following key-value pairs: + + +<ul class="properties"> + +<li> +fingerprint +<code class="typeof">string</code> +required + +Relay fingerprint consisting of 40 upper-case +hexadecimal characters. + +</li> + +<li> +write_history +<code class="typeof">object</code> +required + +Object containing graph history objects with written bytes for different +time periods. +Keys are string representation of the time period covered by the graph +history object. +Keys are fixed strings "3_days", +"1_week", "1_month", +"3_months", "1_year", and +"5_years". +Keys refer to the last known bandwidth history of a relay, not to the time +when the bandwidth document was published. +A graph history object is only contained if the time period it covers is +not already contained in another graph history object with shorter time +period and higher data resolution. +The unit is bytes per second. +Contained graph history objects may contain null values if the relay did +not provide any bandwidth data or only data for less than 20% of a given +time period. + +</li> + +<li> +read_history +<code class="typeof">object</code> +required + +Object containing graph history objects with read bytes for different time +periods. +The specification of graph history objects is similar to those in the +write_history field. + +</li> + +</ul> + +<h4>Bridge bandwidth objects</h4> + + +Bridge bandwidth objects contain the following key-value pairs: <ul class="properties"> @@ -1462,9 +1515,9 @@ of 40 upper-case hexadecimal characters. <code class="typeof">object</code> required -Object containing bandwidth history objects -for different time periods. -The specification of bandwidth history objects is similar to those in the +Object containing graph history objects with written bytes for different +time periods. +The specification of graph history objects is similar to those in the write_history field of relays. </li> @@ -1474,19 +1527,15 @@ The specification of bandwidth history objects is similar to those in the <code class="typeof">object</code> required -Object containing bandwidth history objects -for different time periods. -The specification of bandwidth history objects is similar to those in the +Object containing graph history objects with read bytes for different time +periods. +The specification of graph history objects is similar to those in the write_history field of relays. </li> </ul> -</li> - -</ul> - </div>  <div class="box"> @@ -1523,118 +1572,77 @@ Indicates how recent the relay weights documents in this document are. <code class="typeof">array of objects</code> required -Array of objects representing relay weights -documents. -Each array object contains the following key-value pairs: +Array of relay weights objects as specified below. - -<ul class="properties"> +</li> <li> -fingerprint +bridges_published <code class="typeof">string</code> required -Relay fingerprint consisting of 40 upper-case -hexadecimal characters. +UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last known bridge network status was published. +Only included for compatibility reasons with the other document types. </li> <li> -advertised_bandwidth_fraction -<code class="typeof">object</code> -optional - -History object containing -relative advertised bandwidth of this relay compared to the total -advertised bandwidth in the network. -If there were no bandwidth authorities, this fraction would be a very -rough approximation of the probability of this relay to be selected by -clients. -Keys are string representation of the time period covered by the weights -history object. -Keys are fixed strings "1_week", -"1_month", "3_months", -"1_year", and "5_years". -Keys refer to the last known weights history of a relay, not to the time -when the weights document was published. -A weights history object is only contained if the time period it covers -is not already contained in another weights history object with shorter -time period and higher data resolution. -Each weights history object contains the following key-value pairs: - - -<ul class="properties"> - -<li> -first -<code class="typeof">string</code> +bridges +<code class="typeof">array of objects</code> required -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the first data -data point in the weights history. +Empty array of objects that would represent bridge weights documents. +Only included for compatibility reasons with the other document types. </li> -<li> -last -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the last data -data point in the weights history. - -</li> +</ul> + +<h4>Relay weights objects</h4> -<li> -interval -<code class="typeof">number</code> -required -Time interval between two data points in seconds. +Relay weights objects contain the following key-value pairs: -</li> + +<ul class="properties"> <li> -factor -<code class="typeof">number</code> +fingerprint +<code class="typeof">string</code> required -Factor by which subsequent weights values need to -be multiplied to get the path-selection probability. -The idea is that contained weights values are normalized to a range from 0 -to 999 to reduce document size while still providing sufficient detail for -both slow and fast relays. +Relay fingerprint consisting of 40 upper-case +hexadecimal characters. </li> <li> -count -<code class="typeof">number</code> +advertised_bandwidth_fraction +<code class="typeof">object</code> optional -Number of provided data points, included mostly for -debugging purposes. -Can also be derived from the number of elements in the subsequent array. - -</li> - -<li> -values -<code class="typeof">array of numbers</code> -required - -Array of normalized weights values. -May contain null values if the relay was running less than 20% of a given -time period. -Contains at least two subsequent non-null values to enable drawing of line -graphs. +Object containing graph history objects with relative advertised bandwidth +of this relay compared to the total advertised bandwidth in the network. +If there were no bandwidth authorities, this fraction would be a very +rough approximation of the probability of this relay to be selected by +clients. +Keys are string representation of the time period covered by the graph +history object. +Keys are fixed strings "1_week", +"1_month", "3_months", +"1_year", and "5_years". +Keys refer to the last known weights history of a relay, not to the time +when the weights document was published. +A graph history object is only contained if the time period it covers is +not already contained in another graph history object with shorter time +period and higher data resolution. +The unit is path-selection probability. +Contained graph history objects may contain null values if the relay was +running less than 20% of a given time period. </li> -</ul> - -</li> <li> consensus_weight_fraction <code class="typeof">object</code> @@ -1700,32 +1708,6 @@ The specification of this history object is similar to that in the </ul> -</li> - -<li> -bridges_published -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when -the last known bridge network status was published. -Only included for compatibility reasons with the other document types. - -</li> - -<li> -bridges -<code class="typeof">array of objects</code> -required - -Empty array of objects that would represent bridge -weights documents. -Only included for compatibility reasons with the other document types. - -</li> - -</ul> - </div>  <div class="box"> @@ -1785,8 +1767,17 @@ Indicates how recent the bridge clients documents in this document are. <code class="typeof">array of objects</code> required -Array of objects representing bridge clients documents. -Each array object contains the following key-value pairs: +Array of bridge clients objects as specified below. + + +</li> + +</ul> + +<h4>Bridge clients objects</h4> + + +Bridge clients objects contain the following key-value pairs: <ul class="properties"> @@ -1806,90 +1797,28 @@ of 40 upper-case hexadecimal characters. <code class="typeof">object</code> optional -History object containing the average number of clients connecting to -this bridge. -Keys are string representation of the time period covered by the clients +Object containing graph history objects with the average number of clients +connecting to this bridge. +Keys are string representation of the time period covered by the graph history object. Keys are fixed strings "1_week", "1_month", "3_months", "1_year", and "5_years". Keys refer to the last known clients history of a bridge, not to the time when the clients document was published. -A clients history object is only contained if the time period it covers -is not already contained in another clients history object with shorter +A graph history object is only contained if the time period it covers +is not already contained in another clients graph object with shorter time period and higher data resolution. -Each clients history object contains the following key-value pairs: +The unit is number of clients. +Contained graph history objects may contain null values if the bridge did +not report client statistics for at least 50% of a given time period. +Each graph history object contains the following additional key-value +pairs: <ul class="properties"> <li> -first -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the first data -data point in the clients history. - -</li> - -<li> -last -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the last data -data point in the clients history. - -</li> - -<li> -interval -<code class="typeof">number</code> -required - -Time interval between two data points in seconds. - -</li> - -<li> -factor -<code class="typeof">number</code> -required - -Factor by which subsequent clients values need to -be multiplied to get the average number of clients. -The idea is that contained clients values are normalized to a range from 0 -to 999 to reduce document size while still providing sufficient detail for -both heavily used and mostly unused bridges. - -</li> - -<li> -count -<code class="typeof">number</code> -optional - -Number of provided data points, included mostly for -debugging purposes. -Can also be derived from the number of elements in the subsequent array. - -</li> - -<li> -values -<code class="typeof">array of numbers</code> -required - -Array of normalized clients values. -May contain null values if the bridge did not report client statistics for -at least 50% of a given time period. -Contains at least two subsequent non-null values to enable drawing of line -graphs. - -</li> - -<li> countries <code class="typeof">object</code> optional @@ -1950,10 +1879,6 @@ It might be removed in the future without notice. </ul> -</li> - -</ul> - </div>  <div class="box"> @@ -1990,132 +1915,79 @@ Indicates how recent the relay uptime documents in this document are. <code class="typeof">array of objects</code> required -Array of objects representing relay uptime documents. -Each array object contains the following key-value pairs: - - -<ul class="properties"> - -<li> -fingerprint -<code class="typeof">string</code> -required - -Relay fingerprint consisting of 40 upper-case -hexadecimal characters. +Array of relay uptime objects as specified below. </li> <li> -uptime -<code class="typeof">object</code> -optional - -History object containing the fractional uptime of this relay. -Keys are string representation of the time period covered by the uptime -history object. -Keys are fixed strings "1_week", -"1_month", "3_months", -"1_year", and "5_years". -Keys refer to the last known uptime history of a relay, not to the time -when the uptime document was published. -An uptime history object is only contained if the time period it covers -is not already contained in another uptime history object with shorter -time period and higher data resolution. -Each uptime history object contains the following key-value pairs: - - -<ul class="properties"> - -<li> -first +bridges_published <code class="typeof">string</code> required -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the first data -data point in the uptime history. +UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last known bridge network status was published. +Indicates how recent the bridge uptime documents in this document are. </li> <li> -last -<code class="typeof">string</code> +bridges +<code class="typeof">array of objects</code> required -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the last data -data point in the uptime history. +Array of bridge uptime objects as specified below. </li> -<li> -interval -<code class="typeof">number</code> -required +</ul> + +<h4>Relay uptime objects</h4> + -Time interval between two data points in seconds. +Relay uptime objects contain the following key-value pairs: -</li> + +<ul class="properties"> <li> -factor -<code class="typeof">number</code> +fingerprint +<code class="typeof">string</code> required -Factor by which subsequent uptime values need to -be multiplied to get the fractional uptime. -This is only done for compatibility reasons with the other document types. +Relay fingerprint consisting of 40 upper-case +hexadecimal characters. </li> <li> -count -<code class="typeof">number</code> +uptime +<code class="typeof">object</code> optional -Number of provided data points, included mostly for debugging purposes. -Can also be derived from the number of elements in the subsequent array. - -</li> - -<li> -values -<code class="typeof">array of numbers</code> -required - -Array of normalized uptime values. -May contain null values if less than 20% of network statuses have been -processed for a given time period. -Contains at least two subsequent non-null values to enable drawing of line -graphs. +Object containing graph history objects with the fractional uptime of this +relay. +Keys are string representation of the time period covered by the graph +history object. +Keys are fixed strings "1_week", +"1_month", "3_months", +"1_year", and "5_years". +Keys refer to the last known uptime history of a relay, not to the time +when the uptime document was published. +A graph history object is only contained if the time period it covers is +not already contained in another graph history object with shorter time +period and higher data resolution. +The unit is fractional uptime from 0 to 1. +Contained graph history objects may contain null values if less than 20% +of network statuses have been processed for a given time period. </li> </ul> -</li> - -</ul> - -</li> - -<li> -bridges_published -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when -the last known bridge network status was published. -Indicates how recent the bridge uptime documents in this document are. - -</li> +<h4>Bridge uptime objects</h4> -<li> -bridges -<code class="typeof">array of objects</code> -required -Array of objects representing bridge uptime documents. -Each array object contains the following key-value pairs: +Bridge uptime objects contain the following key-value pairs: <ul class="properties"> @@ -2141,8 +2013,6 @@ The specification of uptime history objects is similar to those in the </li> -</li> - </ul> </div>

1 0

[translation/tor-launcher-network-settings_completed] Update translations for tor-launcher-network-settings_completed
by translation＠torproject.org 12 Mar '14

12 Mar '14

commit b4fc767a8f333878c4b02c7d99f9499f1ef48e01 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Mar 12 11:15:43 2014 +0000 Update translations for tor-launcher-network-settings_completed --- nb/network-settings.dtd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nb/network-settings.dtd b/nb/network-settings.dtd index ceaaff6..e065b65 100644 --- a/nb/network-settings.dtd +++ b/nb/network-settings.dtd @@ -1,8 +1,8 @@ -<!ENTITY torsettings.dialog.title "Tor Browser nettverksinnstillinger"> +<!ENTITY torsettings.dialog.title "Tor Nettverksinnstillinger">  -<!ENTITY torsettings.prompt "Før Tor Browser prøver å koble til Tor-nettverket, må du gi informasjon om denne datamaskinens internett-tilkobling."> +<!ENTITY torsettings.prompt "Før du kan koble til Tor-nettverket, må du gi informasjon om denne datamaskinens internett-tilkobling."> <!ENTITY torSettings.yes "Ja"> <!ENTITY torSettings.no "Nei">

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits March 2014