tor-commits June 2014

tor-commits@lists.torproject.org

21 participants
1212 discussions

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 17 Jun '14

17 Jun '14

commit 8f9bb4c705df16ec15e5b35273e8bf9d9dc8d1fd Author: Translation commit bot <translation(a)torproject.org> Date: Tue Jun 17 09:15:02 2014 +0000 Update translations for bridgedb --- sv/LC_MESSAGES/bridgedb.po | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/sv/LC_MESSAGES/bridgedb.po b/sv/LC_MESSAGES/bridgedb.po index 3e53cdf..55ec184 100644 --- a/sv/LC_MESSAGES/bridgedb.po +++ b/sv/LC_MESSAGES/bridgedb.po @@ -13,7 +13,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'\n" "POT-Creation-Date: 2014-06-06 21:46+0000\n" -"PO-Revision-Date: 2014-06-17 08:44+0000\n" +"PO-Revision-Date: 2014-06-17 09:02+0000\n" "Last-Translator: phst <transifex(a)sturman.se>\n" "Language-Team: Swedish (http://www.transifex.com/projects/p/torproject/language/sv/)\n" "MIME-Version: 1.0\n" @@ -170,11 +170,11 @@ msgstr "Försök att berätta så mycket om problemet som du kan, bland annat vi #: lib/bridgedb/strings.py:103 msgid "Here are your bridge lines:" -msgstr "" +msgstr "Här är dina rader med bryggor:" #: lib/bridgedb/strings.py:104 msgid "Get Bridges!" -msgstr "Skaffa Bridges!" +msgstr "Skaffa Bryggor!" #: lib/bridgedb/strings.py:108 msgid "Please select options for bridge type:" @@ -241,7 +241,7 @@ msgstr "Visa detta meddelande." #. "plain-ol'-vanilla" bridges. #: lib/bridgedb/strings.py:145 msgid "Request vanilla bridges." -msgstr "" +msgstr "Leta efter vanliga bryggor." #: lib/bridgedb/strings.py:146 msgid "Request IPv6 bridges." @@ -321,7 +321,7 @@ msgstr "Steg %s3%s" #: lib/bridgedb/templates/index.html:38 #, python-format msgid "Now %s add the bridges to Tor Browser %s" -msgstr "Nu kan du %s lägga till bridges i Tor Browser %s" +msgstr "Nu kan du %s lägga till bryggor i Tor Browser %s" #. TRANSLATORS: Please make sure the '%s' surrounding single letters at the #. beginning of words are present in your final translation. Thanks! @@ -330,7 +330,7 @@ msgstr "Nu kan du %s lägga till bridges i Tor Browser %s" #: lib/bridgedb/templates/options.html:38 #, python-format msgid "%sJ%sust give me bridges!" -msgstr "%sG%se mig bridges!" +msgstr "%sG%se mig bryggor!" #: lib/bridgedb/templates/options.html:52 msgid "Advanced Options"

1 0

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 17 Jun '14

17 Jun '14

commit c750e319a4edee362935bb24840ab12414cb893e Author: Translation commit bot <translation(a)torproject.org> Date: Tue Jun 17 08:45:04 2014 +0000 Update translations for bridgedb --- sv/LC_MESSAGES/bridgedb.po | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/sv/LC_MESSAGES/bridgedb.po b/sv/LC_MESSAGES/bridgedb.po index 3576b78..3e53cdf 100644 --- a/sv/LC_MESSAGES/bridgedb.po +++ b/sv/LC_MESSAGES/bridgedb.po @@ -13,8 +13,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'\n" "POT-Creation-Date: 2014-06-06 21:46+0000\n" -"PO-Revision-Date: 2014-06-14 01:00+0000\n" -"Last-Translator: Anders Jensen-Urstad <anders(a)unix.se>\n" +"PO-Revision-Date: 2014-06-17 08:44+0000\n" +"Last-Translator: phst <transifex(a)sturman.se>\n" "Language-Team: Swedish (http://www.transifex.com/projects/p/torproject/language/sv/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -250,7 +250,7 @@ msgstr "Begär IPv6-bryggor" #. TRANSLATORS: Please DO NOT translate the word the word "TYPE". #: lib/bridgedb/strings.py:148 msgid "Request a Pluggable Transport by TYPE." -msgstr "" +msgstr "Leta efter en Pluggable Transport av en viss TYPE" #. TRANSLATORS: Please DO NOT translate "BridgeDB". #. TRANSLATORS: Please DO NOT translate "GnuPG". @@ -321,7 +321,7 @@ msgstr "Steg %s3%s" #: lib/bridgedb/templates/index.html:38 #, python-format msgid "Now %s add the bridges to Tor Browser %s" -msgstr "" +msgstr "Nu kan du %s lägga till bridges i Tor Browser %s" #. TRANSLATORS: Please make sure the '%s' surrounding single letters at the #. beginning of words are present in your final translation. Thanks! @@ -330,7 +330,7 @@ msgstr "" #: lib/bridgedb/templates/options.html:38 #, python-format msgid "%sJ%sust give me bridges!" -msgstr "" +msgstr "%sG%se mig bridges!" #: lib/bridgedb/templates/options.html:52 msgid "Advanced Options" @@ -358,4 +358,4 @@ msgstr "%sJ%sa!" #: lib/bridgedb/templates/options.html:154 #, python-format msgid "%sG%set Bridges" -msgstr "" +msgstr "%sH%sämta Bridges"

1 0

r26839: {website} Delete Onionoo project page and point to https://onionoo.tor (in website/trunk: getinvolved/en projects/en)
by Karsten Loesing 17 Jun '14

17 Jun '14

Author: kloesing Date: 2014-06-17 07:47:13 +0000 (Tue, 17 Jun 2014) New Revision: 26839 Removed: website/trunk/projects/en/onionoo.wml Modified: website/trunk/getinvolved/en/volunteer.wml website/trunk/projects/en/projects.wml website/trunk/projects/en/sidenav.wmi Log: Delete Onionoo project page and point to https://onionoo.torproject.org/ instead. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2014-06-15 20:33:55 UTC (rev 26838) +++ website/trunk/getinvolved/en/volunteer.wml 2014-06-17 07:47:13 UTC (rev 26839) @@ -749,10 +749,9 @@ <a id="project-onionoo"></a> - <h3><a href="<page projects/onionoo>">Onionoo</a> (<a - href="https://gitweb.torproject.org/onionoo.git">java codebase</a>, <a - href="https://gitweb.torproject.org/pyonionoo.git">python - codebase</a>, <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…">bug tracker</a>)</h3> + <h3><a href="https://onionoo.torproject.org/">Onionoo</a> (<a + href="https://gitweb.torproject.org/onionoo.git">code</a>, + <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…">bug tracker</a>)</h3> Onionoo is a JSON based protocol to learn information about currently Deleted: website/trunk/projects/en/onionoo.wml =================================================================== --- website/trunk/projects/en/onionoo.wml 2014-06-15 20:33:55 UTC (rev 26838) +++ website/trunk/projects/en/onionoo.wml 2014-06-17 07:47:13 UTC (rev 26839) @@ -1,131 +0,0 @@ -## translation metadata -# Revision: $Revision: 25342 $ - -#include "head.wmi" TITLE="Tor Project: Onionoo" CHARSET="UTF-8" -<div id="content" class="clearfix"> - <div id="breadcrumbs"> - <a href="<page index>">Home » </a> - <a href="<page projects/projects>">Projects » </a> - <a href="<page projects/onionoo>">Onionoo</a> - </div> - <div id="maincol"> - - <h1>Onionoo</h1> - - Onionoo is a web-based protocol to learn about currently running - Tor relays and bridges. Onionoo itself was not designed as a service - for human beings—at least not directly. Onionoo provides the - data for other applications and websites which in turn present Tor - network status information to humans. The following Onionoo clients - are currently available: - <ul> - <li><a href="https://atlas.torproject.org/">Atlas</a> is a web - application to discover Tor relays. It provides useful - information on how relays are configured along with graphics about - their past.</li> - <li><a href="https://compass.torproject.org/">Compass</a> - is a Python script and website that extracts consensus weight - information of currently running relays and aggregates weights of - relays running in the same country or same autonomous system.</li> - <li><a href="http://tor2web.org/">Tor2web</a> is a web proxy to Tor - Hidden Services. It uses Onionoo to get the list of currently running - Tor Exits to detect if the client is a Tor user and if so redirect - them to the .onion address.</li> - <li><a href="https://globe.torproject.org/">Globe</a> is a web - application - that allows you to search for Tor relays and bridges. It gives you a - detailed overview of properties and configurations of a relay or - bridge.</li> - <li>The <a href="https://nos-oignons.net/Services/index.en.html">Nos - oignons</a> website uses Onionoo to visualize bandwidth histories of - their relays.</li> - <li>The <a href="https://metrics.torproject.org/bubbles.html">metrics - website</a> visualizes diversity of the Tor network using bubble - graphs.</li> - </ul> - - The following Onionoo clients are currently unmaintained, but are - still a good idea: - <ul> - <li><a href="https://code.google.com/p/moniono/">mOnionO</a> is an - Android app that lets you add your relays or bridges to your favorites - list and keeps you always informed whether they are running or - not.</li> - </ul> - - <h2>Developing Onionoo applications</h2> - - The project pages of the Onionoo clients listed above have further - information for contacting the authors and contributing ideas or code. - The authors will be happy to hear your thoughts! - - You don't find your favorite Onionoo client above? Want to - implement your own and tell us to add it to the list? The Onionoo - clients above are backed by a web-based - <a href="http://onionoo.torproject.org/">protocol</a>, which - facilitates developing new applications displaying Tor status - information. Here are a few ideas for new Onionoo clients: - <ul> - <li>Tor controller extension: Extend - <a href="<page projects/vidalia>">Vidalia</a> and/or - <a href="<page projects/arm>">arm</a> to look up details for the bridge - that the user is running and display what pool the bridge is contained - in.</li> - <li>Social network site plugin: Add a plugin to the social network - site of your choice to show your friends what Tor relays and bridges - you're running and how that helps users around the world.</li> - <li>Desktop tray icon: Write a tray icon for your favorite desktop - environment that tells you when your relay or bridge is down and that - displays some basic usage statistics.</li> - <li>E-mail notification service: Improve our e-mail notification - service <a href="https://weather.torproject.org/">Weather</a> by - implementing its own relay search or extending it to report when a - bridge drops off the network.</li> - <li>Command-line tool: Implement a command-line tool that quickly - searches a relay or bridge and prints out some status information to - help debug problems.</li> - <li>(Insert your idea here.)</li> - </ul> - - Want to help with developing the Onionoo server that provides - Tor status data, or want to run your own Onionoo server instance? The - Onionoo server is written in Java with a tiny portion of Java - Servlets. Instructions for setting up the Onionoo server to fetch the - required data from the Tor servers is described in the INSTALL file in - the sources. For more details see the - <a href="https://gitweb.torproject.org/onionoo.git">source code</a> and - <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Oni…">issue - tracker</a>. - - <h2>Related projects</h2> - - TorStatus is the name of a nowadays - <a href="https://svn.torproject.org/svn/torstatus/trunk/">unmaintained</a> - website that displays Tor relay information similar to - <a href="http://atlas.torproject.org/">Atlas</a>. There are still a - few <a href="http://torstatus.blutmagie.de/">TorStatus</a> - <a href="https://torstatus.rueckgr.at/">websites</a> - <a href="http://tns.hermetix.org/">running</a>. - - There's another project from summer 2011 called TorStatus which is - a <a href="https://gitweb.torproject.org/torstatus.git">rewrite</a> of - the original TorStatus in Python/Django. Unfortunately, it's also - unmaintained. - - Finally, there's the - <a href="https://metrics.torproject.org/consensus-health.html">consensus-health - page</a> which has the primary purpose of indicating problems with - creating a network status consensus. As a side-effect this page lists - all currently running relays and how the directory authorities voted - on them. - - </div> -  - <div id = "sidecol"> -#include "side.wmi" -#include "info.wmi" - </div> -  -</div> - -#include <foot.wmi> Modified: website/trunk/projects/en/projects.wml =================================================================== --- website/trunk/projects/en/projects.wml 2014-06-15 20:33:55 UTC (rev 26838) +++ website/trunk/projects/en/projects.wml 2014-06-17 07:47:13 UTC (rev 26839) @@ -67,11 +67,11 @@ </div> <div class="projectbox"> -<a href="<page projects/onionoo>"><img class="icon" +<a href="https://onionoo.torproject.org/"><img class="icon" src="$(IMGROOT)/icon-TorStatus.jpg" alt="Onionoo Icon" width="75" height="75"></a> -<div class="projectdesc"><div class="name"><a href="<page -projects/onionoo>">Onionoo</a></div> +<div class="projectdesc"><div class="name"><a +href="https://onionoo.torproject.org/">Onionoo</a></div> Web-based protocol to learn about currently running Tor relays and bridges. </div></div> Modified: website/trunk/projects/en/sidenav.wmi =================================================================== --- website/trunk/projects/en/sidenav.wmi 2014-06-15 20:33:55 UTC (rev 26838) +++ website/trunk/projects/en/sidenav.wmi 2014-06-17 07:47:13 UTC (rev 26839) @@ -41,7 +41,7 @@ {'url' => 'https://trac.torproject.org/projects/tor/wiki/torbirdy', 'txt' => 'TorBirdy', }, - {'url' => 'projects/onionoo', + {'url' => 'https://onionoo.torproject.org/', 'txt' => 'Onionoo', }, {'url' => 'https://metrics.torproject.org/',

1 0

[onionoo/master] Move stylesheet to separate file.
by karsten＠torproject.org 17 Jun '14

17 Jun '14

commit 4add78dc9e19cb33d3b5cd1a1e08a5993d86080f Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Tue Jun 17 09:20:37 2014 +0200 Move stylesheet to separate file. --- web/css/style.css | 38 ++++++++++++++++++++++++++++++++++++++ web/index.html | 40 +--------------------------------------- 2 files changed, 39 insertions(+), 39 deletions(-) diff --git a/web/css/style.css b/web/css/style.css new file mode 100644 index 0000000..9649745 --- /dev/null +++ b/web/css/style.css @@ -0,0 +1,38 @@ +body { font-family: "Open Sans","lucida grande","Segoe UI",arial,verdana, + "lucida sans unicode",tahoma,sans-serif; background: #fafafa; + font-size: 13px; line-height: 22px; color: #222; } +h1 { font-size: 20px; font-weight: normal; text-align: center; } +h3 { color: #7D4698; position: relative } +a { color: #7D4698; text-decoration: none; font-weight: bold; } +ul { list-style: none; padding: 0; margin: 0; } +p { margin: 0; padding: 0; } +a[name] { padding: 0; margin: 0; } +.box { max-width: 850px; width: 100%; margin: 0 auto 30px auto; + padding-bottom: 30px; background: white; border: 1px solid #eee; } +.box > * { margin-left: 30px; margin-right: 30px; } +.box h3 a { visibility: hidden; } +.box:hover h3 a { visibility: visible; } +.api-request { border-bottom: 1px solid #eee; position: relative } +.request-url, .request-type, .request-response { padding: 8px 10px; + vertical-align: middle } +.request-type { color: #57145F; display: inline-block; } +.request-url { color: #333; font-size: 18px; } +.request-response { position: absolute; color: #666; right: 0; } +h3 .request-response { padding: 0 !important; } +.api-urls>li:last-child { border-bottom: 0; } +.required-true, .required-false, .typeof { display: inline-block; + vertical-align: middle; padding: 5px 10px; } +.required-true { color: #1d7508; } +.required-false { color: #aaa; } +.properties { margin-top: 10px; margin-bottom: 10px; + border: 1px solid #eee; } +.properties li { padding: 5px 0; } +.properties li ul { border: 1px solid #eee; margin: 10px 10px 10px 40px; + background: white; } +.properties .properties { margin-left: 10px; } +.properties li:nth-child(even) { background: #fafafa; } +.properties p { padding: 10px 15px; } +.properties b { padding: 5px 10px; display: inline-block; + vertical-align: middle; } +.api-urls{ margin-top: 30px; margin-bottom: 30px; } + diff --git a/web/index.html b/web/index.html index 9777042..3de47bc 100644 --- a/web/index.html +++ b/web/index.html @@ -2,45 +2,7 @@ <html> <head> <title>Onionoo — a Tor network status protocol</title> -<style type="text/css"> -body { font-family: "Open Sans","lucida grande","Segoe UI",arial,verdana, - "lucida sans unicode",tahoma,sans-serif; background: #fafafa; - font-size: 13px; line-height: 22px; color: #222; } -h1 { font-size: 20px; font-weight: normal; text-align: center; } -h3 { color: #7D4698; position: relative } -a { color: #7D4698; text-decoration: none; font-weight: bold; } -ul { list-style: none; padding: 0; margin: 0; } -p { margin: 0; padding: 0; } -a[name] { padding: 0; margin: 0; } -.box { max-width: 850px; width: 100%; margin: 0 auto 30px auto; - padding-bottom: 30px; background: white; border: 1px solid #eee; } -.box > * { margin-left: 30px; margin-right: 30px; } -.box h3 a { visibility: hidden; } -.box:hover h3 a { visibility: visible; } -.api-request { border-bottom: 1px solid #eee; position: relative } -.request-url, .request-type, .request-response { padding: 8px 10px; - vertical-align: middle } -.request-type { color: #57145F; display: inline-block; } -.request-url { color: #333; font-size: 18px; } -.request-response { position: absolute; color: #666; right: 0; } -h3 .request-response { padding: 0 !important; } -.api-urls>li:last-child { border-bottom: 0; } -.required-true, .required-false, .typeof { display: inline-block; - vertical-align: middle; padding: 5px 10px; } -.required-true { color: #1d7508; } -.required-false { color: #aaa; } -.properties { margin-top: 10px; margin-bottom: 10px; - border: 1px solid #eee; } -.properties li { padding: 5px 0; } -.properties li ul { border: 1px solid #eee; margin: 10px 10px 10px 40px; - background: white; } -.properties .properties { margin-left: 10px; } -.properties li:nth-child(even) { background: #fafafa; } -.properties p { padding: 10px 15px; } -.properties b { padding: 5px 10px; display: inline-block; - vertical-align: middle; } -.api-urls{ margin-top: 30px; margin-bottom: 30px; } -</style> +<link href="css/style.css" type="text/css" rel="stylesheet"> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <link href="favicon.ico" type="image/x-icon" rel="shortcut icon"> </head>

1 0

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

17 Jun '14

commit 6a668169886aeb7fc242c8dc8283df223a4780e4 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Tue Jun 17 09:17:42 2014 +0200 Take out old news. --- web/index.html | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/web/index.html b/web/index.html index ebb675a..9777042 100644 --- a/web/index.html +++ b/web/index.html @@ -300,7 +300,7 @@ Lookups are case-insensitive. </li> <li> -fingerprint +fingerprint Return only the relay with the parameter value matching the fingerprint or the bridge with the parameter value matching the hashed fingerprint. @@ -311,7 +311,6 @@ with two exceptions: not be hashed (again) using SHA-1; (2) the response will contain any matching relay or bridge regardless of whether they have been running in the past week. -Added on April 20, 2014. </li> @@ -1495,7 +1494,6 @@ 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. -As of April 20, 2014, this field is optional. </li> @@ -1508,7 +1506,6 @@ 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. -As of April 20, 2014, this field is optional. </li> @@ -1541,7 +1538,6 @@ 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. -As of April 20, 2014, this field is optional. </li> @@ -1554,7 +1550,6 @@ 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. -As of April 20, 2014, this field is optional. </li> @@ -1743,7 +1738,6 @@ The specification of this history object is similar to that in the </h3> -Added on March 10, 2014. Clients documents contain estimates of the average number of clients connecting to a bridge every day. There are no clients documents available for relays, just for bridges. @@ -1914,7 +1908,6 @@ It might be removed in the future without notice. </h3> -Added on March 10, 2014. Uptime documents contain fractional uptimes of relays and bridges. Uptime documents contain different time intervals and are available for relays and bridges. @@ -2034,7 +2027,6 @@ of 40 upper-case hexadecimal characters. Object containing uptime history objects for different time periods. The specification of uptime history objects is similar to those in the uptime field of relays. -As of April 20, 2014, this field is optional. </li>

1 0

[onionoo/master] Create real home page, move protocol to own page.
by karsten＠torproject.org 17 Jun '14

17 Jun '14

commit 39c7f613313d4eaaa54d34b5f4128b4fcb478111 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Tue Jun 17 09:29:44 2014 +0200 Create real home page, move protocol to own page. --- web/css/style.css | 4 +- web/index.html | 2092 +++-------------------------------------------------- web/protocol.html | 2003 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 2113 insertions(+), 1986 deletions(-) diff --git a/web/css/style.css b/web/css/style.css index 9649745..e3caa4a 100644 --- a/web/css/style.css +++ b/web/css/style.css @@ -1,11 +1,9 @@ body { font-family: "Open Sans","lucida grande","Segoe UI",arial,verdana, "lucida sans unicode",tahoma,sans-serif; background: #fafafa; font-size: 13px; line-height: 22px; color: #222; } -h1 { font-size: 20px; font-weight: normal; text-align: center; } h3 { color: #7D4698; position: relative } a { color: #7D4698; text-decoration: none; font-weight: bold; } -ul { list-style: none; padding: 0; margin: 0; } -p { margin: 0; padding: 0; } +p { margin: 0; padding: 10px; } a[name] { padding: 0; margin: 0; } .box { max-width: 850px; width: 100%; margin: 0 auto 30px auto; padding-bottom: 30px; background: white; border: 1px solid #eee; } diff --git a/web/index.html b/web/index.html index 3de47bc..b6b0519 100644 --- a/web/index.html +++ b/web/index.html @@ -9,1990 +9,116 @@ <body> <div class="box"> -<h3>Onionoo protocol overview</h3> - <h4>Table of contents</h4> - <ul> - <li><a href="#general">General</a></li> - <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> - <li><a href="#uptime">Uptime documents</a></li> - </ul> - -</div> -<div class="box"> - -<a name="general"></a> -<h3>General <a href="#general">#</a></h3> - - -The Onionoo service is designed as a RESTful web service. -Onionoo clients send HTTP GET requests to the Onionoo server which -responds with JSON-formatted replies. -Onionoo clients and their developers should follow a few rules: - - -<h4>Compression</h4> - -Clients should include an "Accept-Encoding: -gzip" header in their requests and handle gzip-compressed -responses. -Only requests starting at a certain size will be compressed by the -server. - - -<h4>Caching</h4> -Clients should make use of the "Last-Modified" -header of responses and include that timestamp in a -"If-Modified-Since" header of subsequent requests. - - -<h4>Response codes</h4> - -Clients should handle response codes by -distinguishing between client and server errors, and if there's a problem, -informing their users about the kind of problem. -The following response codes are used: - - -<ul class="properties"> - -<li> -200 OK - -The request was processed successfully. - -</li> - -<li> -304 Not Modified - -Server data has not changed since the -"If-Modified-Since" header included in the request. - -</li> - -<li> -400 Bad Request - -The request could not be processed either -because the requested resource could not be found or because of bad -syntax. -This is most likely a client problem. - -</li> - -<li> -500 Internal Server Error - -There is an unspecific problem with -the server which the service operator may not yet be aware of. -Please check if there's already a bug report for this problem, and if not, -file one. - -</li> - -<li> -503 Service Unavailable - -The server is temporarily down for -maintenance, or there is a temporary problem with the server that the -service operator is already aware of. -Only file a bug report if this problem persists. - -</li> - -</ul> - -<h4>Protocol changes</h4> - -There are plenty of reasons why we may have -to change the protocol described here. -Clients should be able to handle all valid JSON responses, ignoring -unknown fields and not breaking horribly in case of missing fields. -Protocol changes will be announced here by writing deprecated API parts in -red and new parts in -blue. -Deprecated parts will be removed one month after their announcement. -Let us <a href="mailto:tor-dev@lists.torproject.org">know</a> that you're -developing a client, and we're going to inform you of upcoming protocol -changes. - - -The Onionoo API is described by resource types and available methods -below. - -</div>  - -<div class="box"> - -<a name="methods"></a> -<h3>Methods <a href="#methods">#</a></h3> - - -The following methods each return a single document containing zero or -more objects of relays and/or bridges. -By default, all relays and bridges are included that have been running in -the past week. - - -<ul class="api-urls"> - -<li class="api-request"> -GET -https://onionoo.torproject.org/summary -returns a <a href="#summary">summary -document</a> -</li> - -<li class="api-request"> -GET -https://onionoo.torproject.org/details -returns a <a href="#details">details -document</a> -</li> - -<li class="api-request"> -GET -https://onionoo.torproject.org/bandwidth -returns a <a href="#bandwidth">bandwidth -document</a> -</li> - -<li class="api-request"> -GET -https://onionoo.torproject.org/weights -returns a <a href="#weights">weights -document</a> -</li> - -<li class="api-request"> -GET -https://onionoo.torproject.org/clients -returns a <a href="#clients">clients -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> - -Each of the methods can be parameterized to select only a subset of relay -and/or bridge documents that are currently running or that have been -running in the past week. -(The fingerprint parameter is special here, because it -allows selecting a specific relay or bridge, regardless of whether it has -been running in the past week.) -If multiple parameters are specified, they are combined using a logical -AND operation, meaning that only the intersection of relays and bridges -matching all parameters is returned. -If the same parameter is specified more than once, only the first -parameter value is considered. - - -<ul class="properties"> - -<li> -type - -Return only relay (parameter value -relay) or only bridge documents (parameter value -bridge). -Parameter values are case-insensitive. - -</li> - -<li> -running - -Return only running (parameter value -true) or only non-running relays and/or bridges -(paramter value -false). -Parameter values are case-insensitive. - -</li> - -<li> -search - -Return only relays with the parameter value -matching (part of a) nickname, (possibly $-prefixed) beginning of a -fingerprint, or beginning of an IP address, and bridges with (part of a) -nickname or (possibly $-prefixed) beginning of a hashed fingerprint. -Searches by relay IP address include all known addresses used for onion -routing and for exiting to the Internet. -Searches for beginnings of IP addresses are performed on textual -representations of canonical IP address forms, so that searches using CIDR -notation or non-canonical forms will return empty results. -Searches are case-insensitive. -If multiple search terms are given, separated by spaces, the intersection -of all relays and bridges matching all search terms will be returned. -Full fingerprints should always be hashed using SHA-1, regardless of -searching for a relay or a bridge, in order to not accidentally leak -non-hashed bridge fingerprints in the URL. - -</li> - -<li> -lookup - -Return only the relay with the parameter -value matching the fingerprint or the bridge with the parameter value -matching the hashed fingerprint. -Fingerprints should always be hashed using SHA-1, regardless of looking up -a relay or a bridge, in order to not accidentally leak non-hashed bridge -fingerprints in the URL. -Lookups only work for full fingerprints or hashed fingerprints consisting -of 40 hex characters. -Lookups are case-insensitive. - -</li> - -<li> -fingerprint - -Return only the relay with the parameter value matching the fingerprint -or the bridge with the parameter value matching the hashed fingerprint. -Fingerprints must consist of 40 hex characters, case does not matter. -This parameter is quite similar to the lookup parameter -with two exceptions: -(1) the provided relay fingerprint or hashed bridge fingerprint must -not be hashed (again) using SHA-1; -(2) the response will contain any matching relay or bridge regardless of -whether they have been running in the past week. - -</li> - -<li> -country - -Return only relays which are located in the -given country as identified by a two-letter country code. -Filtering by country code is case-insensitive. - -</li> - -<li> -as - -Return only relays which are located in the -given autonomous system (AS) as identified by the AS number (with or -without preceding "AS" part). -Filtering by AS number is case-insensitive. - -</li> - -<li> -flag - -Return only relays which have the -given relay flag assigned by the directory authorities. -Note that if the flag parameter is specified more than once, only the -first parameter value will be considered. -Filtering by flag is case-insensitive. - -</li> - -<li> -first_seen_days - -Return only relays or bridges which -have first been seen during the given range of days ago. -A parameter value "x-y" with x >= y returns relays or bridges that have -first been seen at least x and at most y days ago. -Accepted short forms are "x", "x-", and "-y" which are interpreted as -"x-x", "x-infinity", and "0-y". - -</li> - -<li> -last_seen_days - -Return only relays or bridges which -have last been seen during the given range of days ago. -A parameter value "x-y" with x >= y returns relays or bridges that have -last been seen at least x and at most y days ago. -Accepted short forms are "x", "x-", and "-y" which are interpreted as -"x-x", "x-infinity", and "0-y". -Note that relays and bridges that haven't been running in the past week -are not included in results, so that setting x to 8 or higher will lead to -an empty result set. - -</li> - -<li> -contact - -Return only relays with the parameter value -matching (part of) the contact line. -If the parameter value contains spaces, only relays are returned which -contain all space-separated parts in their contact line. -Only printable ASCII characters are permitted in the parameter value, -some of which need to be percent-encoded (# as %23, % as %25, & as -%26, + as %2B, and / as %2F). -Comparisons are case-insensitive. - -</li> - -</ul> - - -Response documents can be reduced in size by requesting only a subset -of contained fields. - - -<ul class="properties"> - -<li> -fields - -Comma-separated list of fields that will be -included in the result. -So far, only top-level fields in relay or bridge objects of details -documents can be specified, e.g., -nickname,hashed_fingerprint. -If the fields parameter is provided, all other fields which are not -contained in the provided list will be removed from the result. -Field names are case-insensitive. - -</li> - -</ul> - - -Relay and/or bridge documents in the response can be ordered and -limited by providing further parameters. -If the same parameter is specified more than once, only the first -parameter value is considered. - - -<ul class="properties"> - -<li> -order - -Re-order results by a comma-separated list -of fields in ascending or descending order. -Results are first ordered by the first list element, then by the second, -and so on. -Possible fields for ordering are: consensus_weight. -Field names are case-insensitive. -Ascending order is the default; descending order is selected by prepending -fields with a minus sign (-). -Relays or bridges which don't have any value for a field to be ordered by -are always appended to the end, regardless or sorting order. -The ordering is defined independent of the requested document type and -does not require the ordering field to be contained in the document. -If no order parameter is given, ordering of results is -undefined. - -</li> - -<li> -offset - -Skip the given number of relays and/or -bridges. -Relays are skipped first, then bridges. -Non-positive offset values are treated as zero and don't -change the -result. - -</li> - -<li> -limit - -Limit result to the given number of -relays and/or bridges. -Relays are kept first, then bridges. -Non-positive limit values are treated as zero and lead -to an empty -result. -When used together with offset, the offsetting step -precedes the -limiting step. - -</li> - -</ul> - -</div>  - -<div class="box"> -<a name="summary"></a> -<h3>Summary documents <a href="#summary">#</a> - -<a href="summary?limit=4">example request</a> - -</h3> - -Summary documents contain short summaries of relays with nicknames, -fingerprints, IP addresses, and running information as well as bridges -with hashed fingerprints and running information. -Summary documents contain the following fields: - -<ul class="properties"> - -<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 summaries in this document are. - -</li> - -<li> -relays -<code class="typeof">array of objects</code> -required - -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"> - -<li> -n -<code class="typeof">string</code> -optional - -Relay nickname consisting of 1–19 alphanumerical characters. -Omitted if the relay nickname is "Unnamed". - -</li> - -<li> -f -<code class="typeof">string</code> -required - -Relay fingerprint consisting of 40 upper-case hexadecimal characters. - -</li> - -<li> -a -<code class="typeof">array of strings</code> -required - -Array of IPv4 or IPv6 addresses where the relay accepts -onion-routing connections or which the relay used to exit to the Internet -in the past 24 hours. -The first address is the primary onion-routing address that the relay used -to register in the network, subsequent addresses are in arbitrary order. -IPv6 hex characters are all lower-case. - -</li> - -<li> -r -<code class="typeof">boolean</code> -required - -Boolean field saying whether this relay was listed as -running in the last relay network status consensus. - -</li> - -</ul> - -<h4>Bridge summary objects</h4> - - -Bridge summary objects contain the following key-value pairs: - - -<ul class="properties"> - -<li> -n -<code class="typeof">string</code> -optional - -Bridge nickname consisting of 1–19 alphanumerical characters. -Omitted if the bridge nickname is "Unnamed". - -</li> - -<li> -h -<code class="typeof">string</code> -required - -SHA-1 hash of the bridge fingerprint consisting of 40 -upper-case hexadecimal characters. - -</li> - -<li> -r -<code class="typeof">boolean</code> -required - -Boolean field saying whether this bridge was listed as -running in the last bridge network status. - -</li> - -</ul> - -</div>  - -<div class="box"> -<a name="details"></a> -<h3>Details documents <a href="#details">#</a> - -<a href="details?limit=4">example request</a> - -</h3> - - -Details documents are based on the network statuses published by the Tor -directories and the server descriptors published by relays and bridges. -Details documents contain the following fields: - - -<ul class="properties"> - -<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 details in this document are. - -</li> - -<li> -relays -<code class="typeof">array of objects</code> -required - -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"> - -<li> -nickname -<code class="typeof">string</code> -optional - -Relay nickname consisting of 1–19 alphanumerical characters. -Omitted if the relay nickname is "Unnamed". - -</li> - -<li> -fingerprint -<code class="typeof">string</code> -required - -Relay fingerprint consisting of 40 upper-case -hexadecimal characters. - -</li> - -<li> -or_addresses -<code class="typeof">array of strings</code> -required - -Array of IPv4 or IPv6 addresses and TCP ports -or port lists where the relay accepts onion-routing connections. -The first address is the primary onion-routing address that the relay used -to register in the network, subsequent addresses are in arbitrary order. -IPv6 hex characters are all lower-case. - -</li> - -<li> -exit_addresses -<code class="typeof">array of strings</code> -optional - -Array of IPv4 or IPv6 addresses that the -relay used to exit to the Internet in the past 24 hours. -IPv6 hex characters are all lower-case. -Only those addresses are listed that are different from onion-routing -addresses. -Omitted if array is empty. - -</li> - -<li> -dir_address -<code class="typeof">string</code> -optional - -IPv4 address and TCP port where the relay -accepts directory connections. -Omitted if the relay does not accept directory connections. - -</li> - -<li> -last_seen -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when this -relay was last seen in a network status consensus. - -</li> - -<li> -last_changed_address_or_port -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD -hh:mm:ss) when this relay last stopped announcing an IPv4 or IPv6 address -or TCP port where it previously accepted onion-routing or directory -connections. -This timestamp can serve as indicator whether this relay would be a -suitable fallback directory. - -</li> - -<li> -first_seen -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when this -relay was first seen in a network status consensus. - -</li> - -<li> -running -<code class="typeof">boolean</code> -required - -Boolean field saying whether this relay was listed as -running in the last relay network status consensus. - -</li> - -<li> -hibernating -<code class="typeof">boolean</code> -optional - -Boolean field saying whether this relay indicated that it is hibernating -in its last known server descriptor. -This information may be helpful to decide whether a relay that is not -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. - -</li> - -<li> -flags -<code class="typeof">array of strings</code> -optional - -Array of relay flags that the directory authorities -assigned to this relay. -Omitted if empty. - -</li> - -<li> -country -<code class="typeof">string</code> -optional - -Two-letter lower-case country code as found in a -GeoIP database by resolving the relay's first onion-routing IP address. -Omitted if the relay IP address could not be found in the GeoIP -database. - -</li> - -<li> -country_name -<code class="typeof">string</code> -optional - -Country name as found in a GeoIP database by -resolving the relay's first onion-routing IP address. -Omitted if the relay IP address could not be found in the GeoIP -database, or if the GeoIP database did not contain a country name. - -</li> - -<li> -region_name -<code class="typeof">string</code> -optional - -Region name as found in a GeoIP database by -resolving the relay's first onion-routing IP address. -Omitted if the relay IP address could not be found in the GeoIP -database, or if the GeoIP database did not contain a region name. - -</li> - -<li> -city_name -<code class="typeof">string</code> -optional - -City name as found in a -GeoIP database by resolving the relay's first onion-routing IP address. -Omitted if the relay IP address could not be found in the GeoIP -database, or if the GeoIP database did not contain a city name. - -</li> - -<li> -latitude -<code class="typeof">number</code> -optional - -Latitude as found in a GeoIP database by resolving -the relay's first onion-routing IP address. -Omitted if the relay IP address could not be found in the GeoIP -database. - -</li> - -<li> -longitude -<code class="typeof">number</code> -optional - -Longitude as found in a GeoIP database by -resolving the relay's first onion-routing IP address. -Omitted if the relay IP address could not be found in the GeoIP -database. - -</li> - -<li> -as_number -<code class="typeof">number</code> -optional - -AS number as found in an AS database by -resolving the relay's first onion-routing IP address. -Omitted if the relay IP address could not be found in the AS -database. - -</li> - -<li> -as_name -<code class="typeof">string</code> -optional - -AS name as found in an AS database by resolving the -relay's first onion-routing IP address. -Omitted if the relay IP address could not be found in the AS -database. - -</li> - -<li> -consensus_weight -<code class="typeof">number</code> -required - -Weight assigned to this relay by the -directory authorities that clients use in their path selection algorithm. -The unit is arbitrary; currently it's kilobytes per second, but that might -change in the future. - -</li> - -<li> -host_name -<code class="typeof">string</code> -optional - -Host name as found in a reverse DNS lookup of the -relay IP address. -This field is updated at most once in 12 hours, unless the relay IP -address changes. -Omitted if the relay IP address was not looked up or if no lookup request -was successful yet. - -</li> - -<li> -last_restarted -<code class="typeof">string</code> -optional - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when the -relay was last (re-)started. -Missing if router descriptor containing this information cannot be -found. - -</li> - -<li> -bandwidth_rate -<code class="typeof">number</code> -optional - -Average bandwidth -in bytes per second that this relay is willing to sustain over long -periods. -Missing if router descriptor containing this information cannot be -found. - -</li> - -<li> -bandwidth_burst -<code class="typeof">number</code> -optional - -Bandwidth in bytes -per second that this relay is willing to sustain in very short intervals. -Missing if router descriptor containing this information cannot be -found. - -</li> - -<li> -observed_bandwidth -<code class="typeof">number</code> -optional - -Bandwidth -estimate in bytes per second of the capacity this relay can handle. -The relay remembers the maximum bandwidth sustained output over any ten -second period in the past day, and another sustained input. -The "observed_bandwidth" value is the lesser of these two numbers. -Missing if router descriptor containing this information cannot be -found. - -</li> - -<li> -advertised_bandwidth -<code class="typeof">number</code> -optional - -Bandwidth in bytes per second that this -relay is willing and capable to provide. -This bandwidth value is the minimum of bandwidth_rate, -bandwidth_burst, and observed_bandwidth. -Missing if router descriptor containing this information cannot be -found. - -</li> - -<li> -exit_policy -<code class="typeof">array of strings</code> -optional - -Array of exit-policy lines. -Missing if router descriptor containing this information cannot be -found. - -</li> - -<li> -exit_policy_summary -<code class="typeof">object</code> -optional - -Summary -version of the relay's exit policy containing a dictionary with either an -"accept" or a "reject" element. -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. - -</li> - -<li> -exit_policy_v6_summary -<code class="typeof">object</code> -optional - -Summary version of the relay's IPv6 exit policy containing a dictionary -with either an "accept" or a "reject" element. -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. - -</li> - -<li> -contact -<code class="typeof">string</code> -optional - -Contact address of the relay operator. -Omitted if empty or if descriptor containing this information cannot be -found. - -</li> - -<li> -platform -<code class="typeof">string</code> -optional - -Platform string containing operating system and Tor -version details. -Omitted if empty or if descriptor containing this information cannot be -found. - -</li> - -<li> -recommended_version -<code class="typeof">boolean</code> -optional - -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. - -</li> - -<li> -family -<code class="typeof">array of strings</code> -optional - -Array of fingerprints or nicknames of relays in the -same family as this relay. -Omitted if empty or if descriptor containing this information cannot be -found. - -</li> - -<li> -advertised_bandwidth_fraction -<code class="typeof">number</code> -optional - -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. -Omitted if the relay is not running, or router descriptor containing this -information cannot be found. - -</li> - -<li> -consensus_weight_fraction -<code class="typeof">number</code> -optional - -Fraction of this relay's consensus weight compared to the sum of all -consensus weights in the network. -This fraction is a very rough approximation of the probability of this -relay to be selected by clients. -Omitted if the relay is not running. - -</li> - -<li> -guard_probability -<code class="typeof">number</code> -optional - -Probability of this relay to be selected for the guard position. -This probability is calculated based on consensus weights, relay flags, -and bandwidth weights in the consensus. -Path selection depends on more factors, so that this probability can only -be an approximation. -Omitted if the relay is not running, or the consensus does not contain -bandwidth weights. - -</li> - -<li> -middle_probability -<code class="typeof">number</code> -optional - -Probability of this relay to be selected for the middle position. -This probability is calculated based on consensus weights, relay flags, -and bandwidth weights in the consensus. -Path selection depends on more factors, so that this probability can only -be an approximation. -Omitted if the relay is not running, or the consensus does not contain -bandwidth weights. - -</li> - -<li> -exit_probability -<code class="typeof">number</code> -optional - -Probability of this relay to be selected for the exit position. -This probability is calculated based on consensus weights, relay flags, -and bandwidth weights in the consensus. -Path selection depends on more factors, so that this probability can only -be an approximation. -Omitted if the relay is not running, or the consensus does not contain -bandwidth weights. - -</li> - -</ul> - -<h4>Bridge details objects</h4> - - -Bridge details objects contain the following key-value pairs: - - -<ul class="properties"> - -<li> -nickname -<code class="typeof">string</code> -optional - -Bridge nickname consisting of 1–19 -alphanumerical characters. -Omitted if the bridge nickname is "Unnamed". - -</li> - -<li> -hashed_fingerprint -<code class="typeof">string</code> -required - -SHA-1 hash of the bridge fingerprint -consisting of 40 upper-case hexadecimal characters. - -</li> - -<li> -or_addresses -<code class="typeof">array of strings</code> -required - -Array of sanitized IPv4 or IPv6 addresses and -TCP ports or port lists where the bridge accepts onion-routing -connections. -The first address is the primary onion-routing address that the bridge -used to register in the network, subsequent addresses are in arbitrary -order. -IPv6 hex characters are all lower-case. -Sanitized IP addresses are always in 10/8 or -[fd9f:2e19:3bcf/48] IP networks and are only useful to -learn which -IP version the bridge uses and to detect whether the bridge changed its -address. -Sanitized IP addresses always change on the 1st of every month at 00:00:00 -UTC, regardless of the bridge actually changing its IP address. -TCP ports are not sanitized. - -</li> - -<li> -last_seen -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when this -bridge was last seen in a bridge network status. - -</li> - -<li> -first_seen -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when this -bridge was first seen in a bridge network status. - -</li> - -<li> -running -<code class="typeof">boolean</code> -required - -Boolean field saying whether this bridge was listed -as running in the last bridge network status. - -</li> - -<li> -flags -<code class="typeof">array of strings</code> -optional - -Array of relay flags that the bridge authority -assigned to this bridge. -Omitted if empty. - -</li> - -<li> -last_restarted -<code class="typeof">string</code> -optional - -UTC timestamp (YYYY-MM-DD hh:mm:ss) when the -bridge was last (re-)started. -Missing if router descriptor containing this information cannot be -found. - -</li> - -<li> -advertised_bandwidth -<code class="typeof">number</code> -optional - -Bandwidth in bytes per second that this -bridge is willing and capable to provide. -This bandwidth value is the minimum of bandwidth_rate, -bandwidth_burst, and observed_bandwidth. -Missing if router descriptor containing this information cannot be -found. - -</li> - -<li> -platform -<code class="typeof">string</code> -optional - -Platform string containing operating system and Tor -version details. -Omitted if not provided by the bridge or if descriptor containing this -information cannot be found. - -</li> - -<li> -pool_assignment -<code class="typeof">string</code> -optional - -Information of the pool that BridgeDB -assigned this bridge to, including further assignment information if -available. - -</li> - -</ul> - -</div>  - -<div class="box"> -<a name="history"></a> -<h3>History objects <a href="#history">#</a></h3> - - -History objects are no documents by themselves, but are contained in -subsequent documents. - - -<h4>Graph history objects</h4> - - -Graph history objects contain the following fields: - - -<ul class="properties"> - -<li> -first -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the first data point, or more -specifically the interval midpoint of the first interval. - -</li> - -<li> -last -<code class="typeof">string</code> -required - -UTC timestamp (YYYY-MM-DD hh:mm:ss) of the last data point, or more -specifically the interval midpoint of the last interval. - -</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 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> - -<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 values between 0 and 999. -May contain null values. -Contains at least two subsequent non-null values to enable drawing of line -graphs. - -</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 contain the following fields: - - -<ul class="properties"> - -<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 - -Array of relay bandwidth 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 bandwidth documents in this document are. - -</li> - -<li> -bridges -<code class="typeof">array of objects</code> -required - -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> -optional - -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> -optional - -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"> - -<li> -fingerprint -<code class="typeof">string</code> -required - -SHA-1 hash of the bridge fingerprint consisting -of 40 upper-case hexadecimal characters. - -</li> - -<li> -write_history -<code class="typeof">object</code> -optional - -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> - -<li> -read_history -<code class="typeof">object</code> -optional - -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> - -</div>  - -<div class="box"> -<a name="weights"></a> -<h3>Weights documents <a href="#weights">#</a> - -<a href="weights?limit=4">example request</a> - -</h3> - - -Weights documents contain aggregate statistics of a relay's probability -to be selected by clients for building paths. -Weights documents contain different time intervals and are available for -relays only. -Weights documents contain the following fields: - - -<ul class="properties"> - -<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 weights documents in this document are. - -</li> - -<li> -relays -<code class="typeof">array of objects</code> -required - -Array of relay weights 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. -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> - -<h4>Relay weights objects</h4> - - -Relay weights 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> -advertised_bandwidth_fraction -<code class="typeof">object</code> -optional - -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> - -<li> -consensus_weight_fraction -<code class="typeof">object</code> -optional - -History object containing the -fraction of this relay's consensus weight compared to the sum of all -consensus weights in the network. -This fraction is a very rough approximation of the probability of this -relay to be selected by clients. -The specification of this history object is similar to that in the -advertised_bandwidth_fraction field above. - -</li> - -<li> -guard_probability -<code class="typeof">object</code> -optional - -History object containing the probability -of this relay to be selected for the guard position. -This probability is calculated based on consensus weights, relay flags, -and bandwidth weights in the consensus. -Path selection depends on more factors, so that this probability can only -be an approximation. -The specification of this history object is similar to that in the -advertised_bandwidth_fraction field above. - -</li> - -<li> -middle_probability -<code class="typeof">object</code> -optional - -History object containing the probability -of this relay to be selected for the middle position. -This probability is calculated based on consensus weights, relay flags, -and bandwidth weights in the consensus. -Path selection depends on more factors, so that this probability can only -be an approximation. -The specification of this history object is similar to that in the -advertised_bandwidth_fraction field above. - -</li> - -<li> -exit_probability -<code class="typeof">object</code> -optional - -History object containing the probability -of this relay to be selected for the exit position. -This probability is calculated based on consensus weights, relay flags, -and bandwidth weights in the consensus. -Path selection depends on more factors, so that this probability can only -be an approximation. -The specification of this history object is similar to that in the -advertised_bandwidth_fraction field above. - -</li> - -</ul> - -</div>  - -<div class="box"> -<a name="clients"></a> -<h3>Clients documents <a href="#clients">#</a> - -<a href="clients?limit=4">example request</a> - -</h3> - - -Clients documents contain estimates of the average number of clients -connecting to a bridge every day. -There are no clients documents available for relays, just for bridges. -Clients documents contain different time intervals and are available for -bridges only. -Clients documents contain the following fields: - - -<ul class="properties"> - -<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. -Only included for compatibility reasons with the other document types. - -</li> - -<li> -relays -<code class="typeof">array of objects</code> -required - -Empty array of objects that would represent relay clients documents. -Only included for compatibility reasons with the other document types. - -</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 clients documents in this document are. - -</li> - -<li> -bridges -<code class="typeof">array of objects</code> -required - -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"> - -<li> -fingerprint -<code class="typeof">string</code> -required - -SHA-1 hash of the bridge fingerprint consisting -of 40 upper-case hexadecimal characters. - -</li> - -<li> -average_clients -<code class="typeof">object</code> -optional - -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 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. -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> -countries -<code class="typeof">object</code> -optional - -Object containing fractions of clients by country in the considered time -period. -Keys are two-letter lower-case country codes as found in a GeoIP database. -Values are numbers between 0 and 1 standing for the fraction of clients by -country. -A country is only included if at least 1% of clients came from this -country. -Omitted if the bridge did not report client statistics by country. -BETA: This field breaks compatibility -with the history objects contained in other documents pretty badly. -It might be removed in the future without notice. - -</li> - -<li> -transports -<code class="typeof">object</code> -optional - -Object containing fractions of clients by transport in the considered time -period. -Keys are transport names, or "<OR>" for the default -onion-routing transport protocol. -Values are numbers between 0 and 1 standing for the fraction of clients by -transport. -Omitted if the bridge did not report client statistics by transport. -BETA: This field breaks compatibility -with the history objects contained in other documents pretty badly. -It might be removed in the future without notice. - -</li> - -<li> -versions -<code class="typeof">object</code> -optional - -Object containing fractions of clients by IP version in the considered -time period. -Keys are either "v4" for IPv4 or "v6" -for IPv6. -Values are numbers between 0 and 1 standing for the fraction of clients by -version. -Omitted if the bridge did not report client statistics by IP version. -BETA: This field breaks compatibility -with the history objects contained in other documents pretty badly. -It might be removed in the future without notice. - -</li> - -</ul> - -</li> - -</ul> - -</div>  - -<div class="box"> -<a name="uptime"></a> -<h3>Uptime documents <a href="#uptime">#</a> - -<a href="uptime?limit=4">example request</a> - -</h3> - - -Uptime documents contain fractional uptimes of relays and bridges. -Uptime documents contain different time intervals and are available for -relays and bridges. -Uptime documents contain the following fields: - - -<ul class="properties"> - -<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 uptime documents in this document are. - -</li> - -<li> -relays -<code class="typeof">array of objects</code> -required - -Array of relay uptime 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 uptime documents in this document are. - -</li> - -<li> -bridges -<code class="typeof">array of objects</code> -required - -Array of bridge uptime objects as specified below. - -</li> - -</ul> - -<h4>Relay uptime objects</h4> - - -Relay uptime 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> -uptime -<code class="typeof">object</code> -optional - -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> - -<h4>Bridge uptime objects</h4> - - -Bridge uptime objects contain the following key-value pairs: - - -<ul class="properties"> - -<li> -fingerprint -<code class="typeof">string</code> -required - -SHA-1 hash of the bridge fingerprint consisting -of 40 upper-case hexadecimal characters. - -</li> - -<li> -uptime -<code class="typeof">object</code> -optional - -Object containing uptime history objects for different time periods. -The specification of uptime history objects is similar to those in the -uptime field of relays. - -</li> - -</ul> +<h1><a href="index.html">Onionoo</a> —</h1> +<h2>a Tor network status <a href="protocol.html">protocol</a></h2> + +Onionoo is a web-based protocol to learn about currently running +Tor relays and bridges. Onionoo itself was not designed as a service +for human beings—at least not directly. Onionoo provides the +data for other applications and websites which in turn present Tor +network status information to humans. The following Onionoo clients +are currently available: +<ul> +<li><a href="https://atlas.torproject.org/">Atlas</a> is a web +application to discover Tor relays. It provides useful +information on how relays are configured along with graphics about +their past.</li> +<li><a href="https://compass.torproject.org/">Compass</a> +is a Python script and website that extracts consensus weight +information of currently running relays and aggregates weights of +relays running in the same country or same autonomous system.</li> +<li><a href="http://tor2web.org/">Tor2web</a> is a web proxy to Tor +Hidden Services. It uses Onionoo to get the list of currently running +Tor Exits to detect if the client is a Tor user and if so redirect +them to the .onion address.</li> +<li><a href="https://globe.torproject.org/">Globe</a> is a web +application +that allows you to search for Tor relays and bridges. It gives you a +detailed overview of properties and configurations of a relay or +bridge.</li> +<li>The <a href="https://nos-oignons.net/Services/index.en.html">Nos +oignons</a> website uses Onionoo to visualize bandwidth histories of +their relays.</li> +<li>The <a href="https://metrics.torproject.org/bubbles.html">metrics +website</a> visualizes diversity of the Tor network using bubble +graphs.</li> +</ul> + +The following Onionoo clients are currently unmaintained, but are +still a good idea: +<ul> +<li><a href="https://code.google.com/p/moniono/">mOnionO</a> is an +Android app that lets you add your relays or bridges to your favorites +list and keeps you always informed whether they are running or +not.</li> +</ul> + +<h2>Developing Onionoo applications</h2> + +The project pages of the Onionoo clients listed above have further +information for contacting the authors and contributing ideas or code. +The authors will be happy to hear your thoughts! + +You don't find your favorite Onionoo client above? Want to +implement your own and tell us to add it to the list? The Onionoo +clients above are backed by a web-based +<a href="protocol.html">protocol</a>, which +facilitates developing new applications displaying Tor status +information. Here are a few ideas for new Onionoo clients: +<ul> +<li>Tor controller extension: Extend +<a href="https://www.torproject.org/projects/vidalia.html.en">Vidalia</a> and/or +<a href="https://www.torproject.org/projects/arm.html.en">arm</a> to look up details for the bridge +that the user is running and display what pool the bridge is contained +in.</li> +<li>Social network site plugin: Add a plugin to the social network +site of your choice to show your friends what Tor relays and bridges +you're running and how that helps users around the world.</li> +<li>Desktop tray icon: Write a tray icon for your favorite desktop +environment that tells you when your relay or bridge is down and that +displays some basic usage statistics.</li> +<li>E-mail notification service: Improve our e-mail notification +service <a href="https://weather.torproject.org/">Weather</a> by +implementing its own relay search or extending it to report when a +bridge drops off the network.</li> +<li>Command-line tool: Implement a command-line tool that quickly +searches a relay or bridge and prints out some status information to +help debug problems.</li> +<li>(Insert your idea here.)</li> +</ul> + +Want to help with developing the Onionoo server that provides +Tor status data, or want to run your own Onionoo server instance? The +Onionoo server is written in Java with a tiny portion of Java +Servlets. Instructions for setting up the Onionoo server to fetch the +required data from the Tor servers is described in the INSTALL file in +the sources. For more details see the +<a href="https://gitweb.torproject.org/onionoo.git">source code</a> and +<a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Oni…">issue +tracker</a>. + +<h2>Related projects</h2> + +TorStatus is the name of a nowadays +<a href="https://svn.torproject.org/svn/torstatus/trunk/">unmaintained</a> +website that displays Tor relay information similar to +<a href="http://atlas.torproject.org/">Atlas</a>. There are still a +few <a href="http://torstatus.blutmagie.de/">TorStatus</a> +<a href="https://torstatus.rueckgr.at/">websites</a> +<a href="http://tns.hermetix.org/">running</a>. + +There's another project from summer 2011 called TorStatus which is +a <a href="https://gitweb.torproject.org/torstatus.git">rewrite</a> of +the original TorStatus in Python/Django. Unfortunately, it's also +unmaintained. + +Finally, there's the +<a href="https://consensus-health.torproject.org/">consensus-health +page</a> which has the primary purpose of indicating problems with +creating a network status consensus. As a side-effect this page lists +all currently running relays and how the directory authorities voted +on them. </div>  diff --git a/web/protocol.html b/web/protocol.html new file mode 100644 index 0000000..9972f4c --- /dev/null +++ b/web/protocol.html @@ -0,0 +1,2003 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<title>Onionoo — protocol overview</title> +<link href="css/style.css" type="text/css" rel="stylesheet"> +<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> +<link href="favicon.ico" type="image/x-icon" rel="shortcut icon"> +</head> +<body> + +<div class="box"> + +<h1><a href="index.html">Onionoo</a> —</h1> +<h2>protocol overview</h2> + + <h4>Table of contents</h4> + <ul> + <li><a href="#general">General</a></li> + <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> + <li><a href="#uptime">Uptime documents</a></li> + </ul> + +</div> +<div class="box"> + +<a name="general"></a> +<h3>General <a href="#general">#</a></h3> + + +The Onionoo service is designed as a RESTful web service. +Onionoo clients send HTTP GET requests to the Onionoo server which +responds with JSON-formatted replies. +Onionoo clients and their developers should follow a few rules: + + +<h4>Compression</h4> + +Clients should include an "Accept-Encoding: +gzip" header in their requests and handle gzip-compressed +responses. +Only requests starting at a certain size will be compressed by the +server. + + +<h4>Caching</h4> +Clients should make use of the "Last-Modified" +header of responses and include that timestamp in a +"If-Modified-Since" header of subsequent requests. + + +<h4>Response codes</h4> + +Clients should handle response codes by +distinguishing between client and server errors, and if there's a problem, +informing their users about the kind of problem. +The following response codes are used: + + +<ul class="properties"> + +<li> +200 OK + +The request was processed successfully. + +</li> + +<li> +304 Not Modified + +Server data has not changed since the +"If-Modified-Since" header included in the request. + +</li> + +<li> +400 Bad Request + +The request could not be processed either +because the requested resource could not be found or because of bad +syntax. +This is most likely a client problem. + +</li> + +<li> +500 Internal Server Error + +There is an unspecific problem with +the server which the service operator may not yet be aware of. +Please check if there's already a bug report for this problem, and if not, +file one. + +</li> + +<li> +503 Service Unavailable + +The server is temporarily down for +maintenance, or there is a temporary problem with the server that the +service operator is already aware of. +Only file a bug report if this problem persists. + +</li> + +</ul> + +<h4>Protocol changes</h4> + +There are plenty of reasons why we may have +to change the protocol described here. +Clients should be able to handle all valid JSON responses, ignoring +unknown fields and not breaking horribly in case of missing fields. +Protocol changes will be announced here by writing deprecated API parts in +red and new parts in +blue. +Deprecated parts will be removed one month after their announcement. +Let us <a href="mailto:tor-dev@lists.torproject.org">know</a> that you're +developing a client, and we're going to inform you of upcoming protocol +changes. + + +The Onionoo API is described by resource types and available methods +below. + +</div>  + +<div class="box"> + +<a name="methods"></a> +<h3>Methods <a href="#methods">#</a></h3> + + +The following methods each return a single document containing zero or +more objects of relays and/or bridges. +By default, all relays and bridges are included that have been running in +the past week. + + +<ul class="api-urls"> + +<li class="api-request"> +GET +https://onionoo.torproject.org/summary +returns a <a href="#summary">summary +document</a> +</li> + +<li class="api-request"> +GET +https://onionoo.torproject.org/details +returns a <a href="#details">details +document</a> +</li> + +<li class="api-request"> +GET +https://onionoo.torproject.org/bandwidth +returns a <a href="#bandwidth">bandwidth +document</a> +</li> + +<li class="api-request"> +GET +https://onionoo.torproject.org/weights +returns a <a href="#weights">weights +document</a> +</li> + +<li class="api-request"> +GET +https://onionoo.torproject.org/clients +returns a <a href="#clients">clients +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> + +Each of the methods can be parameterized to select only a subset of relay +and/or bridge documents that are currently running or that have been +running in the past week. +(The fingerprint parameter is special here, because it +allows selecting a specific relay or bridge, regardless of whether it has +been running in the past week.) +If multiple parameters are specified, they are combined using a logical +AND operation, meaning that only the intersection of relays and bridges +matching all parameters is returned. +If the same parameter is specified more than once, only the first +parameter value is considered. + + +<ul class="properties"> + +<li> +type + +Return only relay (parameter value +relay) or only bridge documents (parameter value +bridge). +Parameter values are case-insensitive. + +</li> + +<li> +running + +Return only running (parameter value +true) or only non-running relays and/or bridges +(paramter value +false). +Parameter values are case-insensitive. + +</li> + +<li> +search + +Return only relays with the parameter value +matching (part of a) nickname, (possibly $-prefixed) beginning of a +fingerprint, or beginning of an IP address, and bridges with (part of a) +nickname or (possibly $-prefixed) beginning of a hashed fingerprint. +Searches by relay IP address include all known addresses used for onion +routing and for exiting to the Internet. +Searches for beginnings of IP addresses are performed on textual +representations of canonical IP address forms, so that searches using CIDR +notation or non-canonical forms will return empty results. +Searches are case-insensitive. +If multiple search terms are given, separated by spaces, the intersection +of all relays and bridges matching all search terms will be returned. +Full fingerprints should always be hashed using SHA-1, regardless of +searching for a relay or a bridge, in order to not accidentally leak +non-hashed bridge fingerprints in the URL. + +</li> + +<li> +lookup + +Return only the relay with the parameter +value matching the fingerprint or the bridge with the parameter value +matching the hashed fingerprint. +Fingerprints should always be hashed using SHA-1, regardless of looking up +a relay or a bridge, in order to not accidentally leak non-hashed bridge +fingerprints in the URL. +Lookups only work for full fingerprints or hashed fingerprints consisting +of 40 hex characters. +Lookups are case-insensitive. + +</li> + +<li> +fingerprint + +Return only the relay with the parameter value matching the fingerprint +or the bridge with the parameter value matching the hashed fingerprint. +Fingerprints must consist of 40 hex characters, case does not matter. +This parameter is quite similar to the lookup parameter +with two exceptions: +(1) the provided relay fingerprint or hashed bridge fingerprint must +not be hashed (again) using SHA-1; +(2) the response will contain any matching relay or bridge regardless of +whether they have been running in the past week. + +</li> + +<li> +country + +Return only relays which are located in the +given country as identified by a two-letter country code. +Filtering by country code is case-insensitive. + +</li> + +<li> +as + +Return only relays which are located in the +given autonomous system (AS) as identified by the AS number (with or +without preceding "AS" part). +Filtering by AS number is case-insensitive. + +</li> + +<li> +flag + +Return only relays which have the +given relay flag assigned by the directory authorities. +Note that if the flag parameter is specified more than once, only the +first parameter value will be considered. +Filtering by flag is case-insensitive. + +</li> + +<li> +first_seen_days + +Return only relays or bridges which +have first been seen during the given range of days ago. +A parameter value "x-y" with x >= y returns relays or bridges that have +first been seen at least x and at most y days ago. +Accepted short forms are "x", "x-", and "-y" which are interpreted as +"x-x", "x-infinity", and "0-y". + +</li> + +<li> +last_seen_days + +Return only relays or bridges which +have last been seen during the given range of days ago. +A parameter value "x-y" with x >= y returns relays or bridges that have +last been seen at least x and at most y days ago. +Accepted short forms are "x", "x-", and "-y" which are interpreted as +"x-x", "x-infinity", and "0-y". +Note that relays and bridges that haven't been running in the past week +are not included in results, so that setting x to 8 or higher will lead to +an empty result set. + +</li> + +<li> +contact + +Return only relays with the parameter value +matching (part of) the contact line. +If the parameter value contains spaces, only relays are returned which +contain all space-separated parts in their contact line. +Only printable ASCII characters are permitted in the parameter value, +some of which need to be percent-encoded (# as %23, % as %25, & as +%26, + as %2B, and / as %2F). +Comparisons are case-insensitive. + +</li> + +</ul> + + +Response documents can be reduced in size by requesting only a subset +of contained fields. + + +<ul class="properties"> + +<li> +fields + +Comma-separated list of fields that will be +included in the result. +So far, only top-level fields in relay or bridge objects of details +documents can be specified, e.g., +nickname,hashed_fingerprint. +If the fields parameter is provided, all other fields which are not +contained in the provided list will be removed from the result. +Field names are case-insensitive. + +</li> + +</ul> + + +Relay and/or bridge documents in the response can be ordered and +limited by providing further parameters. +If the same parameter is specified more than once, only the first +parameter value is considered. + + +<ul class="properties"> + +<li> +order + +Re-order results by a comma-separated list +of fields in ascending or descending order. +Results are first ordered by the first list element, then by the second, +and so on. +Possible fields for ordering are: consensus_weight. +Field names are case-insensitive. +Ascending order is the default; descending order is selected by prepending +fields with a minus sign (-). +Relays or bridges which don't have any value for a field to be ordered by +are always appended to the end, regardless or sorting order. +The ordering is defined independent of the requested document type and +does not require the ordering field to be contained in the document. +If no order parameter is given, ordering of results is +undefined. + +</li> + +<li> +offset + +Skip the given number of relays and/or +bridges. +Relays are skipped first, then bridges. +Non-positive offset values are treated as zero and don't +change the +result. + +</li> + +<li> +limit + +Limit result to the given number of +relays and/or bridges. +Relays are kept first, then bridges. +Non-positive limit values are treated as zero and lead +to an empty +result. +When used together with offset, the offsetting step +precedes the +limiting step. + +</li> + +</ul> + +</div>  + +<div class="box"> +<a name="summary"></a> +<h3>Summary documents <a href="#summary">#</a> + +<a href="summary?limit=4">example request</a> + +</h3> + +Summary documents contain short summaries of relays with nicknames, +fingerprints, IP addresses, and running information as well as bridges +with hashed fingerprints and running information. +Summary documents contain the following fields: + +<ul class="properties"> + +<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 summaries in this document are. + +</li> + +<li> +relays +<code class="typeof">array of objects</code> +required + +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"> + +<li> +n +<code class="typeof">string</code> +optional + +Relay nickname consisting of 1–19 alphanumerical characters. +Omitted if the relay nickname is "Unnamed". + +</li> + +<li> +f +<code class="typeof">string</code> +required + +Relay fingerprint consisting of 40 upper-case hexadecimal characters. + +</li> + +<li> +a +<code class="typeof">array of strings</code> +required + +Array of IPv4 or IPv6 addresses where the relay accepts +onion-routing connections or which the relay used to exit to the Internet +in the past 24 hours. +The first address is the primary onion-routing address that the relay used +to register in the network, subsequent addresses are in arbitrary order. +IPv6 hex characters are all lower-case. + +</li> + +<li> +r +<code class="typeof">boolean</code> +required + +Boolean field saying whether this relay was listed as +running in the last relay network status consensus. + +</li> + +</ul> + +<h4>Bridge summary objects</h4> + + +Bridge summary objects contain the following key-value pairs: + + +<ul class="properties"> + +<li> +n +<code class="typeof">string</code> +optional + +Bridge nickname consisting of 1–19 alphanumerical characters. +Omitted if the bridge nickname is "Unnamed". + +</li> + +<li> +h +<code class="typeof">string</code> +required + +SHA-1 hash of the bridge fingerprint consisting of 40 +upper-case hexadecimal characters. + +</li> + +<li> +r +<code class="typeof">boolean</code> +required + +Boolean field saying whether this bridge was listed as +running in the last bridge network status. + +</li> + +</ul> + +</div>  + +<div class="box"> +<a name="details"></a> +<h3>Details documents <a href="#details">#</a> + +<a href="details?limit=4">example request</a> + +</h3> + + +Details documents are based on the network statuses published by the Tor +directories and the server descriptors published by relays and bridges. +Details documents contain the following fields: + + +<ul class="properties"> + +<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 details in this document are. + +</li> + +<li> +relays +<code class="typeof">array of objects</code> +required + +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"> + +<li> +nickname +<code class="typeof">string</code> +optional + +Relay nickname consisting of 1–19 alphanumerical characters. +Omitted if the relay nickname is "Unnamed". + +</li> + +<li> +fingerprint +<code class="typeof">string</code> +required + +Relay fingerprint consisting of 40 upper-case +hexadecimal characters. + +</li> + +<li> +or_addresses +<code class="typeof">array of strings</code> +required + +Array of IPv4 or IPv6 addresses and TCP ports +or port lists where the relay accepts onion-routing connections. +The first address is the primary onion-routing address that the relay used +to register in the network, subsequent addresses are in arbitrary order. +IPv6 hex characters are all lower-case. + +</li> + +<li> +exit_addresses +<code class="typeof">array of strings</code> +optional + +Array of IPv4 or IPv6 addresses that the +relay used to exit to the Internet in the past 24 hours. +IPv6 hex characters are all lower-case. +Only those addresses are listed that are different from onion-routing +addresses. +Omitted if array is empty. + +</li> + +<li> +dir_address +<code class="typeof">string</code> +optional + +IPv4 address and TCP port where the relay +accepts directory connections. +Omitted if the relay does not accept directory connections. + +</li> + +<li> +last_seen +<code class="typeof">string</code> +required + +UTC timestamp (YYYY-MM-DD hh:mm:ss) when this +relay was last seen in a network status consensus. + +</li> + +<li> +last_changed_address_or_port +<code class="typeof">string</code> +required + +UTC timestamp (YYYY-MM-DD +hh:mm:ss) when this relay last stopped announcing an IPv4 or IPv6 address +or TCP port where it previously accepted onion-routing or directory +connections. +This timestamp can serve as indicator whether this relay would be a +suitable fallback directory. + +</li> + +<li> +first_seen +<code class="typeof">string</code> +required + +UTC timestamp (YYYY-MM-DD hh:mm:ss) when this +relay was first seen in a network status consensus. + +</li> + +<li> +running +<code class="typeof">boolean</code> +required + +Boolean field saying whether this relay was listed as +running in the last relay network status consensus. + +</li> + +<li> +hibernating +<code class="typeof">boolean</code> +optional + +Boolean field saying whether this relay indicated that it is hibernating +in its last known server descriptor. +This information may be helpful to decide whether a relay that is not +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. + +</li> + +<li> +flags +<code class="typeof">array of strings</code> +optional + +Array of relay flags that the directory authorities +assigned to this relay. +Omitted if empty. + +</li> + +<li> +country +<code class="typeof">string</code> +optional + +Two-letter lower-case country code as found in a +GeoIP database by resolving the relay's first onion-routing IP address. +Omitted if the relay IP address could not be found in the GeoIP +database. + +</li> + +<li> +country_name +<code class="typeof">string</code> +optional + +Country name as found in a GeoIP database by +resolving the relay's first onion-routing IP address. +Omitted if the relay IP address could not be found in the GeoIP +database, or if the GeoIP database did not contain a country name. + +</li> + +<li> +region_name +<code class="typeof">string</code> +optional + +Region name as found in a GeoIP database by +resolving the relay's first onion-routing IP address. +Omitted if the relay IP address could not be found in the GeoIP +database, or if the GeoIP database did not contain a region name. + +</li> + +<li> +city_name +<code class="typeof">string</code> +optional + +City name as found in a +GeoIP database by resolving the relay's first onion-routing IP address. +Omitted if the relay IP address could not be found in the GeoIP +database, or if the GeoIP database did not contain a city name. + +</li> + +<li> +latitude +<code class="typeof">number</code> +optional + +Latitude as found in a GeoIP database by resolving +the relay's first onion-routing IP address. +Omitted if the relay IP address could not be found in the GeoIP +database. + +</li> + +<li> +longitude +<code class="typeof">number</code> +optional + +Longitude as found in a GeoIP database by +resolving the relay's first onion-routing IP address. +Omitted if the relay IP address could not be found in the GeoIP +database. + +</li> + +<li> +as_number +<code class="typeof">number</code> +optional + +AS number as found in an AS database by +resolving the relay's first onion-routing IP address. +Omitted if the relay IP address could not be found in the AS +database. + +</li> + +<li> +as_name +<code class="typeof">string</code> +optional + +AS name as found in an AS database by resolving the +relay's first onion-routing IP address. +Omitted if the relay IP address could not be found in the AS +database. + +</li> + +<li> +consensus_weight +<code class="typeof">number</code> +required + +Weight assigned to this relay by the +directory authorities that clients use in their path selection algorithm. +The unit is arbitrary; currently it's kilobytes per second, but that might +change in the future. + +</li> + +<li> +host_name +<code class="typeof">string</code> +optional + +Host name as found in a reverse DNS lookup of the +relay IP address. +This field is updated at most once in 12 hours, unless the relay IP +address changes. +Omitted if the relay IP address was not looked up or if no lookup request +was successful yet. + +</li> + +<li> +last_restarted +<code class="typeof">string</code> +optional + +UTC timestamp (YYYY-MM-DD hh:mm:ss) when the +relay was last (re-)started. +Missing if router descriptor containing this information cannot be +found. + +</li> + +<li> +bandwidth_rate +<code class="typeof">number</code> +optional + +Average bandwidth +in bytes per second that this relay is willing to sustain over long +periods. +Missing if router descriptor containing this information cannot be +found. + +</li> + +<li> +bandwidth_burst +<code class="typeof">number</code> +optional + +Bandwidth in bytes +per second that this relay is willing to sustain in very short intervals. +Missing if router descriptor containing this information cannot be +found. + +</li> + +<li> +observed_bandwidth +<code class="typeof">number</code> +optional + +Bandwidth +estimate in bytes per second of the capacity this relay can handle. +The relay remembers the maximum bandwidth sustained output over any ten +second period in the past day, and another sustained input. +The "observed_bandwidth" value is the lesser of these two numbers. +Missing if router descriptor containing this information cannot be +found. + +</li> + +<li> +advertised_bandwidth +<code class="typeof">number</code> +optional + +Bandwidth in bytes per second that this +relay is willing and capable to provide. +This bandwidth value is the minimum of bandwidth_rate, +bandwidth_burst, and observed_bandwidth. +Missing if router descriptor containing this information cannot be +found. + +</li> + +<li> +exit_policy +<code class="typeof">array of strings</code> +optional + +Array of exit-policy lines. +Missing if router descriptor containing this information cannot be +found. + +</li> + +<li> +exit_policy_summary +<code class="typeof">object</code> +optional + +Summary +version of the relay's exit policy containing a dictionary with either an +"accept" or a "reject" element. +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. + +</li> + +<li> +exit_policy_v6_summary +<code class="typeof">object</code> +optional + +Summary version of the relay's IPv6 exit policy containing a dictionary +with either an "accept" or a "reject" element. +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. + +</li> + +<li> +contact +<code class="typeof">string</code> +optional + +Contact address of the relay operator. +Omitted if empty or if descriptor containing this information cannot be +found. + +</li> + +<li> +platform +<code class="typeof">string</code> +optional + +Platform string containing operating system and Tor +version details. +Omitted if empty or if descriptor containing this information cannot be +found. + +</li> + +<li> +recommended_version +<code class="typeof">boolean</code> +optional + +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. + +</li> + +<li> +family +<code class="typeof">array of strings</code> +optional + +Array of fingerprints or nicknames of relays in the +same family as this relay. +Omitted if empty or if descriptor containing this information cannot be +found. + +</li> + +<li> +advertised_bandwidth_fraction +<code class="typeof">number</code> +optional + +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. +Omitted if the relay is not running, or router descriptor containing this +information cannot be found. + +</li> + +<li> +consensus_weight_fraction +<code class="typeof">number</code> +optional + +Fraction of this relay's consensus weight compared to the sum of all +consensus weights in the network. +This fraction is a very rough approximation of the probability of this +relay to be selected by clients. +Omitted if the relay is not running. + +</li> + +<li> +guard_probability +<code class="typeof">number</code> +optional + +Probability of this relay to be selected for the guard position. +This probability is calculated based on consensus weights, relay flags, +and bandwidth weights in the consensus. +Path selection depends on more factors, so that this probability can only +be an approximation. +Omitted if the relay is not running, or the consensus does not contain +bandwidth weights. + +</li> + +<li> +middle_probability +<code class="typeof">number</code> +optional + +Probability of this relay to be selected for the middle position. +This probability is calculated based on consensus weights, relay flags, +and bandwidth weights in the consensus. +Path selection depends on more factors, so that this probability can only +be an approximation. +Omitted if the relay is not running, or the consensus does not contain +bandwidth weights. + +</li> + +<li> +exit_probability +<code class="typeof">number</code> +optional + +Probability of this relay to be selected for the exit position. +This probability is calculated based on consensus weights, relay flags, +and bandwidth weights in the consensus. +Path selection depends on more factors, so that this probability can only +be an approximation. +Omitted if the relay is not running, or the consensus does not contain +bandwidth weights. + +</li> + +</ul> + +<h4>Bridge details objects</h4> + + +Bridge details objects contain the following key-value pairs: + + +<ul class="properties"> + +<li> +nickname +<code class="typeof">string</code> +optional + +Bridge nickname consisting of 1–19 +alphanumerical characters. +Omitted if the bridge nickname is "Unnamed". + +</li> + +<li> +hashed_fingerprint +<code class="typeof">string</code> +required + +SHA-1 hash of the bridge fingerprint +consisting of 40 upper-case hexadecimal characters. + +</li> + +<li> +or_addresses +<code class="typeof">array of strings</code> +required + +Array of sanitized IPv4 or IPv6 addresses and +TCP ports or port lists where the bridge accepts onion-routing +connections. +The first address is the primary onion-routing address that the bridge +used to register in the network, subsequent addresses are in arbitrary +order. +IPv6 hex characters are all lower-case. +Sanitized IP addresses are always in 10/8 or +[fd9f:2e19:3bcf/48] IP networks and are only useful to +learn which +IP version the bridge uses and to detect whether the bridge changed its +address. +Sanitized IP addresses always change on the 1st of every month at 00:00:00 +UTC, regardless of the bridge actually changing its IP address. +TCP ports are not sanitized. + +</li> + +<li> +last_seen +<code class="typeof">string</code> +required + +UTC timestamp (YYYY-MM-DD hh:mm:ss) when this +bridge was last seen in a bridge network status. + +</li> + +<li> +first_seen +<code class="typeof">string</code> +required + +UTC timestamp (YYYY-MM-DD hh:mm:ss) when this +bridge was first seen in a bridge network status. + +</li> + +<li> +running +<code class="typeof">boolean</code> +required + +Boolean field saying whether this bridge was listed +as running in the last bridge network status. + +</li> + +<li> +flags +<code class="typeof">array of strings</code> +optional + +Array of relay flags that the bridge authority +assigned to this bridge. +Omitted if empty. + +</li> + +<li> +last_restarted +<code class="typeof">string</code> +optional + +UTC timestamp (YYYY-MM-DD hh:mm:ss) when the +bridge was last (re-)started. +Missing if router descriptor containing this information cannot be +found. + +</li> + +<li> +advertised_bandwidth +<code class="typeof">number</code> +optional + +Bandwidth in bytes per second that this +bridge is willing and capable to provide. +This bandwidth value is the minimum of bandwidth_rate, +bandwidth_burst, and observed_bandwidth. +Missing if router descriptor containing this information cannot be +found. + +</li> + +<li> +platform +<code class="typeof">string</code> +optional + +Platform string containing operating system and Tor +version details. +Omitted if not provided by the bridge or if descriptor containing this +information cannot be found. + +</li> + +<li> +pool_assignment +<code class="typeof">string</code> +optional + +Information of the pool that BridgeDB +assigned this bridge to, including further assignment information if +available. + +</li> + +</ul> + +</div>  + +<div class="box"> +<a name="history"></a> +<h3>History objects <a href="#history">#</a></h3> + + +History objects are no documents by themselves, but are contained in +subsequent documents. + + +<h4>Graph history objects</h4> + + +Graph history objects contain the following fields: + + +<ul class="properties"> + +<li> +first +<code class="typeof">string</code> +required + +UTC timestamp (YYYY-MM-DD hh:mm:ss) of the first data point, or more +specifically the interval midpoint of the first interval. + +</li> + +<li> +last +<code class="typeof">string</code> +required + +UTC timestamp (YYYY-MM-DD hh:mm:ss) of the last data point, or more +specifically the interval midpoint of the last interval. + +</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 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> + +<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 values between 0 and 999. +May contain null values. +Contains at least two subsequent non-null values to enable drawing of line +graphs. + +</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 contain the following fields: + + +<ul class="properties"> + +<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 + +Array of relay bandwidth 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 bandwidth documents in this document are. + +</li> + +<li> +bridges +<code class="typeof">array of objects</code> +required + +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> +optional + +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> +optional + +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"> + +<li> +fingerprint +<code class="typeof">string</code> +required + +SHA-1 hash of the bridge fingerprint consisting +of 40 upper-case hexadecimal characters. + +</li> + +<li> +write_history +<code class="typeof">object</code> +optional + +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> + +<li> +read_history +<code class="typeof">object</code> +optional + +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> + +</div>  + +<div class="box"> +<a name="weights"></a> +<h3>Weights documents <a href="#weights">#</a> + +<a href="weights?limit=4">example request</a> + +</h3> + + +Weights documents contain aggregate statistics of a relay's probability +to be selected by clients for building paths. +Weights documents contain different time intervals and are available for +relays only. +Weights documents contain the following fields: + + +<ul class="properties"> + +<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 weights documents in this document are. + +</li> + +<li> +relays +<code class="typeof">array of objects</code> +required + +Array of relay weights 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. +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> + +<h4>Relay weights objects</h4> + + +Relay weights 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> +advertised_bandwidth_fraction +<code class="typeof">object</code> +optional + +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> + +<li> +consensus_weight_fraction +<code class="typeof">object</code> +optional + +History object containing the +fraction of this relay's consensus weight compared to the sum of all +consensus weights in the network. +This fraction is a very rough approximation of the probability of this +relay to be selected by clients. +The specification of this history object is similar to that in the +advertised_bandwidth_fraction field above. + +</li> + +<li> +guard_probability +<code class="typeof">object</code> +optional + +History object containing the probability +of this relay to be selected for the guard position. +This probability is calculated based on consensus weights, relay flags, +and bandwidth weights in the consensus. +Path selection depends on more factors, so that this probability can only +be an approximation. +The specification of this history object is similar to that in the +advertised_bandwidth_fraction field above. + +</li> + +<li> +middle_probability +<code class="typeof">object</code> +optional + +History object containing the probability +of this relay to be selected for the middle position. +This probability is calculated based on consensus weights, relay flags, +and bandwidth weights in the consensus. +Path selection depends on more factors, so that this probability can only +be an approximation. +The specification of this history object is similar to that in the +advertised_bandwidth_fraction field above. + +</li> + +<li> +exit_probability +<code class="typeof">object</code> +optional + +History object containing the probability +of this relay to be selected for the exit position. +This probability is calculated based on consensus weights, relay flags, +and bandwidth weights in the consensus. +Path selection depends on more factors, so that this probability can only +be an approximation. +The specification of this history object is similar to that in the +advertised_bandwidth_fraction field above. + +</li> + +</ul> + +</div>  + +<div class="box"> +<a name="clients"></a> +<h3>Clients documents <a href="#clients">#</a> + +<a href="clients?limit=4">example request</a> + +</h3> + + +Clients documents contain estimates of the average number of clients +connecting to a bridge every day. +There are no clients documents available for relays, just for bridges. +Clients documents contain different time intervals and are available for +bridges only. +Clients documents contain the following fields: + + +<ul class="properties"> + +<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. +Only included for compatibility reasons with the other document types. + +</li> + +<li> +relays +<code class="typeof">array of objects</code> +required + +Empty array of objects that would represent relay clients documents. +Only included for compatibility reasons with the other document types. + +</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 clients documents in this document are. + +</li> + +<li> +bridges +<code class="typeof">array of objects</code> +required + +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"> + +<li> +fingerprint +<code class="typeof">string</code> +required + +SHA-1 hash of the bridge fingerprint consisting +of 40 upper-case hexadecimal characters. + +</li> + +<li> +average_clients +<code class="typeof">object</code> +optional + +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 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. +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> +countries +<code class="typeof">object</code> +optional + +Object containing fractions of clients by country in the considered time +period. +Keys are two-letter lower-case country codes as found in a GeoIP database. +Values are numbers between 0 and 1 standing for the fraction of clients by +country. +A country is only included if at least 1% of clients came from this +country. +Omitted if the bridge did not report client statistics by country. +BETA: This field breaks compatibility +with the history objects contained in other documents pretty badly. +It might be removed in the future without notice. + +</li> + +<li> +transports +<code class="typeof">object</code> +optional + +Object containing fractions of clients by transport in the considered time +period. +Keys are transport names, or "<OR>" for the default +onion-routing transport protocol. +Values are numbers between 0 and 1 standing for the fraction of clients by +transport. +Omitted if the bridge did not report client statistics by transport. +BETA: This field breaks compatibility +with the history objects contained in other documents pretty badly. +It might be removed in the future without notice. + +</li> + +<li> +versions +<code class="typeof">object</code> +optional + +Object containing fractions of clients by IP version in the considered +time period. +Keys are either "v4" for IPv4 or "v6" +for IPv6. +Values are numbers between 0 and 1 standing for the fraction of clients by +version. +Omitted if the bridge did not report client statistics by IP version. +BETA: This field breaks compatibility +with the history objects contained in other documents pretty badly. +It might be removed in the future without notice. + +</li> + +</ul> + +</li> + +</ul> + +</div>  + +<div class="box"> +<a name="uptime"></a> +<h3>Uptime documents <a href="#uptime">#</a> + +<a href="uptime?limit=4">example request</a> + +</h3> + + +Uptime documents contain fractional uptimes of relays and bridges. +Uptime documents contain different time intervals and are available for +relays and bridges. +Uptime documents contain the following fields: + + +<ul class="properties"> + +<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 uptime documents in this document are. + +</li> + +<li> +relays +<code class="typeof">array of objects</code> +required + +Array of relay uptime 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 uptime documents in this document are. + +</li> + +<li> +bridges +<code class="typeof">array of objects</code> +required + +Array of bridge uptime objects as specified below. + +</li> + +</ul> + +<h4>Relay uptime objects</h4> + + +Relay uptime 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> +uptime +<code class="typeof">object</code> +optional + +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> + +<h4>Bridge uptime objects</h4> + + +Bridge uptime objects contain the following key-value pairs: + + +<ul class="properties"> + +<li> +fingerprint +<code class="typeof">string</code> +required + +SHA-1 hash of the bridge fingerprint consisting +of 40 upper-case hexadecimal characters. + +</li> + +<li> +uptime +<code class="typeof">object</code> +optional + +Object containing uptime history objects for different time periods. +The specification of uptime history objects is similar to those in the +uptime field of relays. + +</li> + +</ul> + +</div>  + +</body> +</html> +

1 0

[translation/tails-iuk_completed] Update translations for tails-iuk_completed
by translation＠torproject.org 16 Jun '14

16 Jun '14

commit a9deb81618339010305d330b1cc4a56689277db5 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jun 16 23:15:51 2014 +0000 Update translations for tails-iuk_completed --- el.po | 241 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 241 insertions(+) diff --git a/el.po b/el.po new file mode 100644 index 0000000..9315f96 --- /dev/null +++ b/el.po @@ -0,0 +1,241 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) YEAR Tails developers +# This file is distributed under the same license as the PACKAGE package. +# +# Translators: +# Adrian Pappas <pappasadrian(a)gmail.com>, 2014 +# firespin <dartworldgr(a)hotmail.com>, 2014 +# ggoniotakis <ioannis.goniotakis(a)gmail.com>, 2014 +# isv31 <ix4svs(a)gmail.com>, 2014 +# kotkotkot <kotakota(a)gmail.com>, 2014 +# stratosgl <stratos_gl(a)yahoo.com>, 2014 +# Theodore Grammenos <theodorewii121(a)hotmail.com>, 2014 +msgid "" +msgstr "" +"Project-Id-Version: The Tor Project\n" +"Report-Msgid-Bugs-To: Tails developers <tails(a)boum.org>\n" +"POT-Creation-Date: 2014-05-28 22:50+0200\n" +"PO-Revision-Date: 2014-06-16 23:10+0000\n" +"Last-Translator: isv31 <ix4svs(a)gmail.com>\n" +"Language-Team: Greek (http://www.transifex.com/projects/p/torproject/language/el/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: el\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../lib/Tails/IUK/Frontend.pm:146 ../lib/Tails/IUK/Frontend.pm:523 +#: ../lib/Tails/IUK/Frontend.pm:667 +msgid "For debugging information, see /home/amnesia/.xsession-errors" +msgstr "Για λεπτομέρειςς σχετικές με λάθη, δείτε το home/amnesia/.xsession-errors" + +#: ../lib/Tails/IUK/Frontend.pm:216 +msgid "Error while checking for upgrades" +msgstr "Σφάλμα κατά τον έλεγχο για αναβαθμίσεις" + +#: ../lib/Tails/IUK/Frontend.pm:219 +msgid "" +"Could not determine whether an upgrade is available from our website.\n" +"\n" +"Check your network connection, and restart Tails to try upgrading again.\n" +"\n" +"If the problem persists, go to file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html" +msgstr "Δε μπορέσαμε να ελέγξουμε αν υπάρχει διαθέσιμη αναβάθμιση.\n\nΕλέγξτε τη σύνδεση δικτύου σας και κάντε επανεκκίνηση για να επαναληφθεί η προσπάθεια αναβάθμισης.\n\nΑν το πρόβλημα συνεχιστεί, πηγαίνετε στο file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html" + +#: ../lib/Tails/IUK/Frontend.pm:234 +msgid "no automatic upgrade is available from our website for this version" +msgstr "Δεν υπάρχει αυτόματη αναβάθμιση διαθέσιμη από τον ιστότοπο για αυτή την έκδοση." + +#: ../lib/Tails/IUK/Frontend.pm:240 +msgid "your device was not created using Tails Installer" +msgstr "η συσκευή δε δημιουργήθηκε με τον Tails Installer" + +#: ../lib/Tails/IUK/Frontend.pm:245 +msgid "Tails was started from a DVD or a read-only device" +msgstr "Το Tails εκκινήθηκε από DVD ή από μια μη-εγγράψιμη συσκευή." + +#: ../lib/Tails/IUK/Frontend.pm:250 +msgid "there is not enough free space on the Tails system partition" +msgstr "δεν υπάρχει αρκετός χώρος στο δίσκο" + +#: ../lib/Tails/IUK/Frontend.pm:255 +msgid "not enough memory is available on this system" +msgstr "το σύστημα δεν έχει αρκετή διαθέσιμη μνήμη" + +#: ../lib/Tails/IUK/Frontend.pm:261 +#, perl-brace-format +msgid "No explanation available for reason '%{reason}s'." +msgstr "Δεν υπάρχει διαθέσιμη εξηγηση για '%{reason}'." + +#: ../lib/Tails/IUK/Frontend.pm:281 +msgid "The system is up-to-date" +msgstr "Το σύστημα είναι ενημερωμένο." + +#: ../lib/Tails/IUK/Frontend.pm:286 +msgid "This version of Tails is outdated, and may have security issues." +msgstr "Αυτή η έκδοση του Tails είναι ξεπερασμένη και μπορεί να περιέχει θέματα ασφάλειας." + +#: ../lib/Tails/IUK/Frontend.pm:318 +#, perl-brace-format +msgid "" +"The available incremental upgrade requires %{space_needed}s of free space on" +" Tails system partition, but only %{free_space}s is available." +msgstr "Η διαθέσιμη μερική αναβάθμιση χρειάζεται %{space_needed}s ελεύθερου χώρου στο δίσκο του Tails, αλλά μόνο %{free_space}s είναι διαθέσιμα." + +#: ../lib/Tails/IUK/Frontend.pm:334 +#, perl-brace-format +msgid "" +"The available incremental upgrade requires %{memory_needed}s of free memory," +" but only %{free_memory}s is available." +msgstr "Η διαθέσιμη μερική αναβάθμιση χρειάζεται %{memory_needed}s ελεύθερου χώρου στο δίσκο του Tails, αλλά μόνο %{free_space}s είναι διαθέσιμα." + +#: ../lib/Tails/IUK/Frontend.pm:356 +msgid "" +"An incremental upgrade is available, but no full upgrade is.\n" +"This should not happen. Please report a bug." +msgstr "Μερική αναβάθμιση διαθέσιμη, αλλά όχι πλήρης αναβάθμιση.\nΑυτό δε θα έπρεπε να συμβαίνει. Παρακαλώ ειδοποιήστε μας για αυτό το σφάλμα." + +#: ../lib/Tails/IUK/Frontend.pm:360 +msgid "Error while detecting available upgrades" +msgstr "Πρόβλημα κατά τον έλεγχο των διαθέσιμων αναβαθμίσεων" + +#: ../lib/Tails/IUK/Frontend.pm:370 +#, perl-brace-format +msgid "" +"You should upgrade to %{name}s %{version}s.\n" +"\n" +"For more information about this new version, go to %{details_url}s\n" +"\n" +"It is recommended to close all the open applications during the upgrade.\n" +"Downloading the upgrade might take a long time, from several minutes to a few hours.\n" +"The networking will be disabled after downloading the upgrade.\n" +"\n" +"Download size: %{size}s\n" +"\n" +"Do you want to upgrade now?" +msgstr "Παρακαλώ αναβαθμίστε σε %{name}s %{version}s.\n\nΓια περισσότερες λεπτομέρειες σχετικά με αυτή τη νέα έκδοση, πηγαίνετε στο %{details_url}s\n\nΠροτείνεται να κλείσετε όλες τις εφαρμογές πριν την αναβάθμιση.\nΤο κατέβασμα της αναβάθμισης μπορεί να πάρει από λεπτά έως και ώρες.\nΗ σύνδεση στο διαδύκτιο θα διακοπέι μόλις κατεβάσουμε όλες τις ενημερώσεις .\n\nΜέγεθος: %{size}s\n\nΘέλετε να προχωρήσετε στην αναβάθμιση?" + +#: ../lib/Tails/IUK/Frontend.pm:385 +msgid "Upgrade available" +msgstr "Διαθέσιμη αναβάθμιση." + +#: ../lib/Tails/IUK/Frontend.pm:386 +msgid "Upgrade now" +msgstr "Αναβάθμιση τώρα" + +#: ../lib/Tails/IUK/Frontend.pm:387 +msgid "Upgrade later" +msgstr "Αναβάθμιση αργότερα" + +#: ../lib/Tails/IUK/Frontend.pm:395 +#, perl-brace-format +msgid "" +"You should do a manual upgrade to %{name}s %{version}s.\n" +"\n" +"For more information about this new version, go to %{details_url}s\n" +"\n" +"It is not possible to automatically upgrade your device to this new version: %{explanation}s.\n" +"\n" +"To learn how to do a manual upgrade, go to https://tails.boum.org/doc/first_steps/upgrade/#manual" +msgstr "Παρακαλώ αναναθμίστε χειροκίνητα σε %{name}s %{version}s.\n\nΓια περισσότερες πληροφορίες για αυτή την έκδοση, πηγαίνετε στο %{details_url}s\n\nΔεν είναι δυνατό να αναβαθμίσουμε τη συσκευή σας αυτόματτα στη νέα έκδοση: %{explanation}s.\n\nΓια να μάθετε πώς να κάνετε χειροκίνητες αναβαθμίσεις, επισκευθείτε το https://tails.boum.org/doc/first_steps/upgrade/#manual" + +#: ../lib/Tails/IUK/Frontend.pm:411 +msgid "New version available" +msgstr "Νέα διαθέσιμη έκδοση" + +#: ../lib/Tails/IUK/Frontend.pm:468 +msgid "Downloading upgrade" +msgstr "Λήψη αναβάθμισης" + +#: ../lib/Tails/IUK/Frontend.pm:471 +#, perl-brace-format +msgid "Downloading the upgrade to %{name}s %{version}s..." +msgstr "Κατέβασμα αναβάθμισης %{name}s %{version}s..." + +#: ../lib/Tails/IUK/Frontend.pm:512 +msgid "" +"The upgrade could not be downloaded.\\n\\nCheck your network " +"connection, and restart Tails to try upgrading again.\\n\\nIf the problem " +"persists, go to " +"file:///usr/share/doc/tails/website/doc/upgrade/error/download.en.html" +msgstr "Η αναβάθμιση δεν κατέστη δυνατό να κατέβει.\\n\\nΕλέγξτε την σύνδεσή σας στο διαδίκτυο, επανεκκινήστε το πρόγραμμα και προσπαθείστε ξανά.\\n\\nΕάν το πρόβλημα παραμένει, μεταβείτε εδώ file:///usr/share/doc/tails/website/doc/upgrade/error/download.en.html" + +#: ../lib/Tails/IUK/Frontend.pm:528 ../lib/Tails/IUK/Frontend.pm:547 +msgid "Error while downloading the upgrade" +msgstr "Σφάλμα κατά την λήψη της αναβάθμισης" + +#: ../lib/Tails/IUK/Frontend.pm:540 +#, perl-brace-format +msgid "" +"Output file '%{output_file}s' does not exist, but tails-iuk-get-target-file " +"did not complain. Please report a bug." +msgstr "Το αρχείο εξόδου '%{output_file}s' δεν υπάρχει, αλλά το tails-iuk-get-target-file δεν διαμαρτυρήθηκε. Παρακαλώ καταχωρήστε μία αναφορά προβλήματος." + +#: ../lib/Tails/IUK/Frontend.pm:559 +msgid "Error while creating temporary downloading directory" +msgstr "Σφάλμα κατά την δημιουργία προσωρινού φακέλου λήψης" + +#: ../lib/Tails/IUK/Frontend.pm:562 +msgid "Failed to create temporary download directory" +msgstr "Αποτυχία δημιουργίας προσωρινού φακέλου λήψης" + +#: ../lib/Tails/IUK/Frontend.pm:574 +msgid "" +"Your Tails device was successfully upgraded.\n" +"\n" +"Some security features were temporarily disabled.\n" +"You should restart Tails on the new version as soon as possible.\n" +"\n" +"Do you want to restart now?" +msgstr "Ο υπολογιστής Tails σας αναβαθμίστηκε επιτυχώς.\n\nΚάποιες δικλείδες ασφαλείας απενεργοποιήθηκαν προσωρινά.\nΠαρακαλώ επανεκκινήστε το Tails το συντομότερο δυνατό.\n\nΝα γίνει επανεκκίνηση τώρα;" + +#: ../lib/Tails/IUK/Frontend.pm:579 +msgid "Restart Tails" +msgstr "Επανεκκίνηση του Talis" + +#: ../lib/Tails/IUK/Frontend.pm:580 +msgid "Restart now" +msgstr "Επανεκκίνηση τώρα" + +#: ../lib/Tails/IUK/Frontend.pm:581 +msgid "Restart later" +msgstr "Επανεκκίνηση αργότερα" + +#: ../lib/Tails/IUK/Frontend.pm:592 +msgid "Error while restarting the system" +msgstr "Πρόβλημα κατά την επανεκκίνηση" + +#: ../lib/Tails/IUK/Frontend.pm:595 +msgid "Failed to restart the system" +msgstr "Αποτυχία επανεκκίνησης του συστήματος" + +#: ../lib/Tails/IUK/Frontend.pm:610 +msgid "Error while shutting down the network" +msgstr "Σφάλμα κατά την απενεργοποίηση του δικτύου" + +#: ../lib/Tails/IUK/Frontend.pm:613 +msgid "Failed to shutdown network" +msgstr "Αποτυχία απενεργοποίησης του δικτύου" + +#: ../lib/Tails/IUK/Frontend.pm:623 +msgid "Upgrading the system" +msgstr "Αναβάθμιση του συστήματος" + +#: ../lib/Tails/IUK/Frontend.pm:625 +msgid "" +"Your Tails device is being upgraded...\n" +"\n" +"For security reasons, the networking is now disabled." +msgstr "Ο υπολογιστής Tails σας αναβαθμίζεται...\n\nΓια λόγους ασφαλείας ο υπολογιστής έχει τώρα αποσυνδεθεί από το δίκτυο." + +#: ../lib/Tails/IUK/Frontend.pm:662 +msgid "" +"An error occured while installing the upgrade.\\n\\nYour Tails device" +" needs to be repaired and might be unable to restart.\\n\\nPlease follow the" +" instructions at " +"file:///usr/share/doc/tails/website/doc/upgrade/error/install.en.html" +msgstr "Σφάλμα κατά την αναβάθμιση.\\n\\nΟ υπολογιστής Tails σας χρειάζεται επισκευή και ίσως να μη μπορεί να επανεκκινήσει.\\n\\nΠαρακαλώ ακολουθήστε τις οδηγίες στο file:///usr/share/doc/tails/website/doc/upgrade/error/install.en.html" + +#: ../lib/Tails/IUK/Frontend.pm:672 +msgid "Error while installing the upgrade" +msgstr "Σφάλμα κατά την εγκατάσταση της αναβάθμισης"

1 0

[translation/tails-iuk] Update translations for tails-iuk
by translation＠torproject.org 16 Jun '14

16 Jun '14

commit 47ee55fc64e3b9c59a07fe2dd9fc5c33e4f00f37 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jun 16 23:15:49 2014 +0000 Update translations for tails-iuk --- el.po | 35 ++++++++++++++++++----------------- 1 file changed, 18 insertions(+), 17 deletions(-) diff --git a/el.po b/el.po index 5a597c8..9315f96 100644 --- a/el.po +++ b/el.po @@ -3,19 +3,20 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: -# pappasadrian <pappasadrian(a)gmail.com>, 2014 +# Adrian Pappas <pappasadrian(a)gmail.com>, 2014 # firespin <dartworldgr(a)hotmail.com>, 2014 # ggoniotakis <ioannis.goniotakis(a)gmail.com>, 2014 +# isv31 <ix4svs(a)gmail.com>, 2014 # kotkotkot <kotakota(a)gmail.com>, 2014 # stratosgl <stratos_gl(a)yahoo.com>, 2014 -# Teogramm <theodorewii121(a)hotmail.com>, 2014 +# Theodore Grammenos <theodorewii121(a)hotmail.com>, 2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: Tails developers <tails(a)boum.org>\n" -"POT-Creation-Date: 2014-04-16 17:54+0200\n" -"PO-Revision-Date: 2014-05-11 08:40+0000\n" -"Last-Translator: kotkotkot <kotakota(a)gmail.com>\n" +"POT-Creation-Date: 2014-05-28 22:50+0200\n" +"PO-Revision-Date: 2014-06-16 23:10+0000\n" +"Last-Translator: isv31 <ix4svs(a)gmail.com>\n" "Language-Team: Greek (http://www.transifex.com/projects/p/torproject/language/el/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -26,7 +27,7 @@ msgstr "" #: ../lib/Tails/IUK/Frontend.pm:146 ../lib/Tails/IUK/Frontend.pm:523 #: ../lib/Tails/IUK/Frontend.pm:667 msgid "For debugging information, see /home/amnesia/.xsession-errors" -msgstr "" +msgstr "Για λεπτομέρειςς σχετικές με λάθη, δείτε το home/amnesia/.xsession-errors" #: ../lib/Tails/IUK/Frontend.pm:216 msgid "Error while checking for upgrades" @@ -39,7 +40,7 @@ msgid "" "Check your network connection, and restart Tails to try upgrading again.\n" "\n" "If the problem persists, go to file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html" -msgstr "" +msgstr "Δε μπορέσαμε να ελέγξουμε αν υπάρχει διαθέσιμη αναβάθμιση.\n\nΕλέγξτε τη σύνδεση δικτύου σας και κάντε επανεκκίνηση για να επαναληφθεί η προσπάθεια αναβάθμισης.\n\nΑν το πρόβλημα συνεχιστεί, πηγαίνετε στο file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html" #: ../lib/Tails/IUK/Frontend.pm:234 msgid "no automatic upgrade is available from our website for this version" @@ -47,7 +48,7 @@ msgstr "Δεν υπάρχει αυτόματη αναβάθμιση διαθέσ #: ../lib/Tails/IUK/Frontend.pm:240 msgid "your device was not created using Tails Installer" -msgstr "" +msgstr "η συσκευή δε δημιουργήθηκε με τον Tails Installer" #: ../lib/Tails/IUK/Frontend.pm:245 msgid "Tails was started from a DVD or a read-only device" @@ -55,7 +56,7 @@ msgstr "Το Tails εκκινήθηκε από DVD ή από μια μη-εγγ #: ../lib/Tails/IUK/Frontend.pm:250 msgid "there is not enough free space on the Tails system partition" -msgstr "" +msgstr "δεν υπάρχει αρκετός χώρος στο δίσκο" #: ../lib/Tails/IUK/Frontend.pm:255 msgid "not enough memory is available on this system" @@ -79,20 +80,20 @@ msgstr "Αυτή η έκδοση του Tails είναι ξεπερασμένη msgid "" "The available incremental upgrade requires %{space_needed}s of free space on" " Tails system partition, but only %{free_space}s is available." -msgstr "" +msgstr "Η διαθέσιμη μερική αναβάθμιση χρειάζεται %{space_needed}s ελεύθερου χώρου στο δίσκο του Tails, αλλά μόνο %{free_space}s είναι διαθέσιμα." #: ../lib/Tails/IUK/Frontend.pm:334 #, perl-brace-format msgid "" "The available incremental upgrade requires %{memory_needed}s of free memory," " but only %{free_memory}s is available." -msgstr "" +msgstr "Η διαθέσιμη μερική αναβάθμιση χρειάζεται %{memory_needed}s ελεύθερου χώρου στο δίσκο του Tails, αλλά μόνο %{free_space}s είναι διαθέσιμα." #: ../lib/Tails/IUK/Frontend.pm:356 msgid "" "An incremental upgrade is available, but no full upgrade is.\n" "This should not happen. Please report a bug." -msgstr "" +msgstr "Μερική αναβάθμιση διαθέσιμη, αλλά όχι πλήρης αναβάθμιση.\nΑυτό δε θα έπρεπε να συμβαίνει. Παρακαλώ ειδοποιήστε μας για αυτό το σφάλμα." #: ../lib/Tails/IUK/Frontend.pm:360 msgid "Error while detecting available upgrades" @@ -112,7 +113,7 @@ msgid "" "Download size: %{size}s\n" "\n" "Do you want to upgrade now?" -msgstr "" +msgstr "Παρακαλώ αναβαθμίστε σε %{name}s %{version}s.\n\nΓια περισσότερες λεπτομέρειες σχετικά με αυτή τη νέα έκδοση, πηγαίνετε στο %{details_url}s\n\nΠροτείνεται να κλείσετε όλες τις εφαρμογές πριν την αναβάθμιση.\nΤο κατέβασμα της αναβάθμισης μπορεί να πάρει από λεπτά έως και ώρες.\nΗ σύνδεση στο διαδύκτιο θα διακοπέι μόλις κατεβάσουμε όλες τις ενημερώσεις .\n\nΜέγεθος: %{size}s\n\nΘέλετε να προχωρήσετε στην αναβάθμιση?" #: ../lib/Tails/IUK/Frontend.pm:385 msgid "Upgrade available" @@ -136,7 +137,7 @@ msgid "" "It is not possible to automatically upgrade your device to this new version: %{explanation}s.\n" "\n" "To learn how to do a manual upgrade, go to https://tails.boum.org/doc/first_steps/upgrade/#manual" -msgstr "" +msgstr "Παρακαλώ αναναθμίστε χειροκίνητα σε %{name}s %{version}s.\n\nΓια περισσότερες πληροφορίες για αυτή την έκδοση, πηγαίνετε στο %{details_url}s\n\nΔεν είναι δυνατό να αναβαθμίσουμε τη συσκευή σας αυτόματτα στη νέα έκδοση: %{explanation}s.\n\nΓια να μάθετε πώς να κάνετε χειροκίνητες αναβαθμίσεις, επισκευθείτε το https://tails.boum.org/doc/first_steps/upgrade/#manual" #: ../lib/Tails/IUK/Frontend.pm:411 msgid "New version available" @@ -186,7 +187,7 @@ msgid "" "You should restart Tails on the new version as soon as possible.\n" "\n" "Do you want to restart now?" -msgstr "" +msgstr "Ο υπολογιστής Tails σας αναβαθμίστηκε επιτυχώς.\n\nΚάποιες δικλείδες ασφαλείας απενεργοποιήθηκαν προσωρινά.\nΠαρακαλώ επανεκκινήστε το Tails το συντομότερο δυνατό.\n\nΝα γίνει επανεκκίνηση τώρα;" #: ../lib/Tails/IUK/Frontend.pm:579 msgid "Restart Tails" @@ -225,7 +226,7 @@ msgid "" "Your Tails device is being upgraded...\n" "\n" "For security reasons, the networking is now disabled." -msgstr "" +msgstr "Ο υπολογιστής Tails σας αναβαθμίζεται...\n\nΓια λόγους ασφαλείας ο υπολογιστής έχει τώρα αποσυνδεθεί από το δίκτυο." #: ../lib/Tails/IUK/Frontend.pm:662 msgid "" @@ -233,7 +234,7 @@ msgid "" " needs to be repaired and might be unable to restart.\\n\\nPlease follow the" " instructions at " "file:///usr/share/doc/tails/website/doc/upgrade/error/install.en.html" -msgstr "" +msgstr "Σφάλμα κατά την αναβάθμιση.\\n\\nΟ υπολογιστής Tails σας χρειάζεται επισκευή και ίσως να μη μπορεί να επανεκκινήσει.\\n\\nΠαρακαλώ ακολουθήστε τις οδηγίες στο file:///usr/share/doc/tails/website/doc/upgrade/error/install.en.html" #: ../lib/Tails/IUK/Frontend.pm:672 msgid "Error while installing the upgrade"

1 0

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

16 Jun '14

commit 1e72076aad56a01b5dee6bf8c6548e1f57a55389 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jun 16 22:45:41 2014 +0000 Update translations for tor-launcher-network-settings_completed --- el/network-settings.dtd | 33 ++++++++++++++++++++++----------- 1 file changed, 22 insertions(+), 11 deletions(-) diff --git a/el/network-settings.dtd b/el/network-settings.dtd index f7f3578..3df7868 100644 --- a/el/network-settings.dtd +++ b/el/network-settings.dtd @@ -1,18 +1,18 @@ -<!ENTITY torsettings.dialog.title "Tor Ρυθμίσεις Δικτύου "> +<!ENTITY torsettings.dialog.title "TorΡυθμίσεις Δικτύου ">  -<!ENTITY torsettings.prompt "Πριν από το Tor Browser Bundle να προσπαθησει να συνδεθεί με το δίκτυο Tor, θα πρέπει να παρέχθουν πληροφορίες σχετικά με τη σύνδεση διαδικτυου αυτού του υπολογιστή."> +<!ENTITY torsettings.prompt "Πριν συνδεθείτε στο δίκτυο Tor, θα χρειαστούμε λίγες πληροφορίες για το πώς συνδέεστε στο Internet."> <!ENTITY torSettings.yes "Ναι"> <!ENTITY torSettings.no "Οχι"> <!ENTITY torSettings.firstQuestion "Ποιο από τα παρακάτω περιγράφει καλύτερα την κατάστασή σας;"> <!ENTITY torSettings.configurePrompt1 "Σύνδεση στο διαδικτυο αυτού του υπολογιστή λογοκρινετε, φιλτραρετε ή εμποδιζετε γενικως. "> -<!ENTITY torSettings.configurePrompt2 "Πρέπει να διαμορφώθουν η ρυθμίσεις δικτύου."> +<!ENTITY torSettings.configurePrompt2 "Χρειάζονται ρυθμίσεις για τις γέφυρες, για το firewall, ή για τον proxy μου."> <!ENTITY torSettings.configure "Ρύθμιση "> -<!ENTITY torSettings.connectPrompt1 "Η σύνδεση στο διαδικτυο αυτού του υπολογιστή είναι μακριά από εμπόδια."> <!ENTITY torSettings.connectPrompt2 "Θα ήθελα να συνδεθεί άμεσα με το δίκτυο Tor."> +<!ENTITY torSettings.connectPrompt3 "Αυτό θα λειτουργήσει στις περισσότερες περιπτώσεις."> <!ENTITY torSettings.connect "Σύνδεση"> <!ENTITY torSettings.proxyQuestion "Μήπως αυτός ο υπολογιστής πρέπει να χρησιμοποιήση έναν διακομιστή μεσολάβησης για πρόσβαση στο Διαδίκτυο;"> @@ -22,11 +22,15 @@ <!ENTITY torSettings.firewallQuestion "Πηγαίνει μέσω ενός τείχους προστασίας που επιτρέπει μόνο συνδέσεις σε ορισμένες θύρες σύνδεσης Internet αυτού του υπολογιστή;"> <!ENTITY torSettings.firewallHelp "Εάν δεν είστε βέβαιοι πώς να απαντήσετε στο ερώτημα αυτό, επιλέξτε Όχι. Εάν αντιμετωπίζετε προβλήματα με τη σύνδεση με το δίκτυο Tor, αλλάξτε αυτή τη ρύθμιση. "> <!ENTITY torSettings.enterFirewall "Πληκτρολογήστε μια λίστα διαχωρισμένη με κόμματα των θυρών που επιτρέπονται από το firewall."> -<!ENTITY torSettings.bridgeQuestion "Εάν η σύνδεση στο διαδικτυο αυτού του υπολογιστή λογοκρίνεται, θα χρειαστεί να αποκτήσετε και να χρησιμοποιήσετε ρελέ γέφυρα.&#160; Αν όχι, απλά κάντε κλικ στο Σύνδεση."> +<!ENTITY torSettings.bridgeQuestion "Γνωρίζετε αν ο πάροχος (ISP) σας μπλοκάρει ή με οποιοδήποτε τρόπο ελέγχει συνδέσεις +στο δίκτυο Tor?"> +<!ENTITY torSettings.bridgeHelp "Αν δε ξέρετε πώς να απαντήσετε εδώ, επιλέξτε "Όχι".  Αν επιλέξετε "Ναι", θα σας ζητήσω να ρυθμίσετε γέφυρες Tor, που είναι μη ευρέως γνωστά κανάλια εισόδου στο δίκτυο Tor, που δυσκολεύουν όσους προσπαθούν να μπλοκάρουν τις συνδέσεις στο δίκτυο Tor."> +<!ENTITY torSettings.bridgeSettingsPrompt "Μπορείτε να χρησιμοποιήσετε τις προκαθορισμένες γέφυρες, ή να αποκτήσετε και εισάγετε νέες διευθύνσεις γεφυρών.">  <!ENTITY torsettings.startingTor "Αναμονή για να ξεκινήσει το Tor... "> +<!ENTITY torsettings.restart "Επανεκκίνηση"> <!ENTITY torsettings.optional "Προεραιτικα"> @@ -43,12 +47,19 @@ <!ENTITY torsettings.firewall.checkbox "Το τείχος προστασίας μου με αφήνει να συνδέομαι μόνο σε συγκεκριμένες θύρες συστήματος"> <!ENTITY torsettings.firewall.allowedPorts "Επιτρεπόμενες Θύρες:"> <!ENTITY torsettings.useBridges.checkbox "Ο πάροχος διαδικτυου (ISP) μπλοκάρει τις συνδέσεις στο δίκτυο του Tor"> -<!ENTITY torsettings.useBridges.label "Εισάγετε ένα ή περισσότερα ρελέ γέφυρων στην διεύθυνση address:port."> -<!ENTITY torsettings.useBridges.placeholder "address:port"> +<!ENTITY torsettings.useBridges.default "Σύνδεση με προκαθορισμένες γέφυρες"> +<!ENTITY torsettings.useBridges.type "Τύπος μεταφοράς:"> +<!ENTITY torsettings.useBridges.custom "Εισαγωγή άλλων γεφυρών"> +<!ENTITY torsettings.useBridges.label "Εισάγετε μια ή περισσότερες διευθύνσεις γεφυρών (μία ανά γραμμή)."> +<!ENTITY torsettings.useBridges.placeholder "τύπος διεύθυνση:πόρτα"> <!ENTITY torsettings.copyLog "Αντιγραφή στο πρόχειρο"> <!ENTITY torsettings.bridgeHelpTitle "Γεφυρες αναμεταδοτων Βοηθεια"> -<!ENTITY torsettings.bridgeHelp1 "Αν δεν είστε σε θέση να συνδεθείτε με το δίκτυο Tor, θα μπορούσε να είναι ότι η υπηρεσία παροχής διαδικτυου (ISP) μπλοκαρει το Tor.&#160; Μπορείτε να επιλύσετε αυτό το πρόβλημα, χρησιμοποιώντας Tor γέφυρες που είναι κρυμμένες στα κέντρα ενημέρωσης που είναι πιο δύσκολο να μπλοκάρισθουν."> -<!ENTITY torsettings.bridgeHelp2 "Για να αποκτήσετε κάποια ρελέ γέφυρα, χρησιμοποιήστε ένα πρόγραμμα περιήγησης διαδικτυου για να επισκεφθείτε την ακόλουθη ιστοσελίδα: https://bridges.torproject.org "> -<!ENTITY torsettings.bridgeHelp3 "Άλλος ένας τρόπος να βρειτε δημόσιες διευθύνσεις γεφυρών είναι να στείλετε ένα e-mail στο bridges(a)torproject.org, με θέμα "get bridges".&#160; Ωστόσο για να κάνουμε πιο δύσκολο σε έναν εισβολέα να μάθει πολλές διευθύνσεις γεφυρών, πρέπει να στείλετε το αίτημα σας με e-mail που να συμπεριλαμβάνεται στα παρακάτω domain names: gmail.com η yahoo.com."> -<!ENTITY torsettings.bridgeHelp4 "Μπορείτε επίσης να ζητήσετε μια ρελέ γέφυρα στέλνοντας email στην διευθυνση help(a)rt.torproject.org."> +<!ENTITY torsettings.bridgeHelp1 "Αν δε μπορείτε να συνδεθείτε στο δίκτυο Tor, ίσως ο πάροχός (ISP) σας ή κάποιος τρίτος μπλοκάρει το Tor .  Αυτό το πρόβλημα συνήθως λύνεται με τη χρήση Tor Bridges (γέφυρες), που είναι μη δημοσιευμένες διευθύνσεις από τις οποίες μπορείτε να μπείτε στο δίκτυο Tor, συνεπώς πιο δύσκολο να μπλοκαριστούν."> +<!ENTITY torsettings.bridgeHelp1B "Μπορείτε να χρησιμοποιήσετε τις προκαθορισμένες γέφυρες, ή να αποκτήσετε νέες διυθύνσεις γεφυρών με έναν από τους παρακάτω τρεις τρόπους:"> +<!ENTITY torsettings.bridgeHelp2Heading "Μέσω του Διαδικτύου"> +<!ENTITY torsettings.bridgeHelp2 "Χρησιμοποιήστε έναν φυλλομετρητή για να επισκεφτείτε το https://bridges.torproject.org"> +<!ENTITY torsettings.bridgeHelp3Heading "Μέσω της Αυτοματοποιημένης Απάντησης Email"> +<!ENTITY torsettings.bridgeHelp3 "Στείλτε email στο bridges(a)torproject.org με μόνο με τις λέξεις 'get bridges' στο κείμενο.  Για να δυσκολέψουμε τους αντιπάλους μας που θέλουν μα μάθουν πολλές διευθύνσεις γεφυρών, δεχόμαστε μηνύματα μόνο από διευθύνσεις που τελειώνουν σε gmail.com ή yahoo.com."> +<!ENTITY torsettings.bridgeHelp4Heading "Μέσω της Υποστήριξης"> +<!ENTITY torsettings.bridgeHelp4 "Αν όλα τα άλλα αποτύχουν, μπορείτε να ζητήσετε διευθύνσεις γεφυρών στέλνοντας ένα ευγενικό email στο help(a)rt.torproject.org.  Σημείωση: Κάποιος εθελοντής θα πρέπει να απαντήσει χειροκίνητα (συνεπώς η απάντηση ίσως αργήσει).">

1 0

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

16 Jun '14

commit 238c7ba1e4604fd1a3bced7319129db7f3f78628 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jun 16 22:45:39 2014 +0000 Update translations for tor-launcher-network-settings --- el/network-settings.dtd | 31 ++++++++++++++++--------------- 1 file changed, 16 insertions(+), 15 deletions(-) diff --git a/el/network-settings.dtd b/el/network-settings.dtd index fdfab94..3df7868 100644 --- a/el/network-settings.dtd +++ b/el/network-settings.dtd @@ -1,15 +1,15 @@ -<!ENTITY torsettings.dialog.title "Tor Ρυθμίσεις Δικτύου "> +<!ENTITY torsettings.dialog.title "TorΡυθμίσεις Δικτύου ">  -<!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, θα χρειαστούμε λίγες πληροφορίες για το πώς συνδέεστε στο Internet."> <!ENTITY torSettings.yes "Ναι"> <!ENTITY torSettings.no "Οχι"> <!ENTITY torSettings.firstQuestion "Ποιο από τα παρακάτω περιγράφει καλύτερα την κατάστασή σας;"> <!ENTITY torSettings.configurePrompt1 "Σύνδεση στο διαδικτυο αυτού του υπολογιστή λογοκρινετε, φιλτραρετε ή εμποδιζετε γενικως. "> -<!ENTITY torSettings.configurePrompt2 "I need to configure bridge, firewall, or proxy settings."> +<!ENTITY torSettings.configurePrompt2 "Χρειάζονται ρυθμίσεις για τις γέφυρες, για το firewall, ή για τον proxy μου."> <!ENTITY torSettings.configure "Ρύθμιση "> <!ENTITY torSettings.connectPrompt2 "Θα ήθελα να συνδεθεί άμεσα με το δίκτυο Tor."> <!ENTITY torSettings.connectPrompt3 "Αυτό θα λειτουργήσει στις περισσότερες περιπτώσεις."> @@ -22,9 +22,10 @@ <!ENTITY torSettings.firewallQuestion "Πηγαίνει μέσω ενός τείχους προστασίας που επιτρέπει μόνο συνδέσεις σε ορισμένες θύρες σύνδεσης Internet αυτού του υπολογιστή;"> <!ENTITY torSettings.firewallHelp "Εάν δεν είστε βέβαιοι πώς να απαντήσετε στο ερώτημα αυτό, επιλέξτε Όχι. Εάν αντιμετωπίζετε προβλήματα με τη σύνδεση με το δίκτυο Tor, αλλάξτε αυτή τη ρύθμιση. "> <!ENTITY torSettings.enterFirewall "Πληκτρολογήστε μια λίστα διαχωρισμένη με κόμματα των θυρών που επιτρέπονται από το firewall."> -<!ENTITY torSettings.bridgeQuestion "Does your Internet Service Provider (ISP) block or otherwise censor connections to the Tor Network?"> -<!ENTITY torSettings.bridgeHelp "If you are not sure how to answer this question, choose No.  If you choose Yes, you will be asked to configure Tor Bridges, which are unlisted relays that make it more difficult to block connections to the Tor Network."> -<!ENTITY torSettings.bridgeSettingsPrompt "You may use the provided set of bridges or you may obtain and enter a custom set of bridges."> +<!ENTITY torSettings.bridgeQuestion "Γνωρίζετε αν ο πάροχος (ISP) σας μπλοκάρει ή με οποιοδήποτε τρόπο ελέγχει συνδέσεις +στο δίκτυο Tor?"> +<!ENTITY torSettings.bridgeHelp "Αν δε ξέρετε πώς να απαντήσετε εδώ, επιλέξτε "Όχι".  Αν επιλέξετε "Ναι", θα σας ζητήσω να ρυθμίσετε γέφυρες Tor, που είναι μη ευρέως γνωστά κανάλια εισόδου στο δίκτυο Tor, που δυσκολεύουν όσους προσπαθούν να μπλοκάρουν τις συνδέσεις στο δίκτυο Tor."> +<!ENTITY torSettings.bridgeSettingsPrompt "Μπορείτε να χρησιμοποιήσετε τις προκαθορισμένες γέφυρες, ή να αποκτήσετε και εισάγετε νέες διευθύνσεις γεφυρών.">  @@ -46,19 +47,19 @@ <!ENTITY torsettings.firewall.checkbox "Το τείχος προστασίας μου με αφήνει να συνδέομαι μόνο σε συγκεκριμένες θύρες συστήματος"> <!ENTITY torsettings.firewall.allowedPorts "Επιτρεπόμενες Θύρες:"> <!ENTITY torsettings.useBridges.checkbox "Ο πάροχος διαδικτυου (ISP) μπλοκάρει τις συνδέσεις στο δίκτυο του Tor"> -<!ENTITY torsettings.useBridges.default "Connect with provided bridges"> -<!ENTITY torsettings.useBridges.type "Transport type:"> -<!ENTITY torsettings.useBridges.custom "Enter custom bridges"> -<!ENTITY torsettings.useBridges.label "Enter one or more bridge relays (one per line)."> -<!ENTITY torsettings.useBridges.placeholder "type address:port"> +<!ENTITY torsettings.useBridges.default "Σύνδεση με προκαθορισμένες γέφυρες"> +<!ENTITY torsettings.useBridges.type "Τύπος μεταφοράς:"> +<!ENTITY torsettings.useBridges.custom "Εισαγωγή άλλων γεφυρών"> +<!ENTITY torsettings.useBridges.label "Εισάγετε μια ή περισσότερες διευθύνσεις γεφυρών (μία ανά γραμμή)."> +<!ENTITY torsettings.useBridges.placeholder "τύπος διεύθυνση:πόρτα"> <!ENTITY torsettings.copyLog "Αντιγραφή στο πρόχειρο"> <!ENTITY torsettings.bridgeHelpTitle "Γεφυρες αναμεταδοτων Βοηθεια"> -<!ENTITY torsettings.bridgeHelp1 "If you are unable to connect to the Tor network, it could be that your Internet Service Provider (ISP) or another agency is blocking Tor.  Often, you can work around this problem by using Tor Bridges, which are unlisted relays that are more difficult to block."> -<!ENTITY torsettings.bridgeHelp1B "You may use the preconfigured, provided set of bridge addresses or you may obtain a custom set of addresses by using one of these three methods:"> +<!ENTITY torsettings.bridgeHelp1 "Αν δε μπορείτε να συνδεθείτε στο δίκτυο Tor, ίσως ο πάροχός (ISP) σας ή κάποιος τρίτος μπλοκάρει το Tor .  Αυτό το πρόβλημα συνήθως λύνεται με τη χρήση Tor Bridges (γέφυρες), που είναι μη δημοσιευμένες διευθύνσεις από τις οποίες μπορείτε να μπείτε στο δίκτυο Tor, συνεπώς πιο δύσκολο να μπλοκαριστούν."> +<!ENTITY torsettings.bridgeHelp1B "Μπορείτε να χρησιμοποιήσετε τις προκαθορισμένες γέφυρες, ή να αποκτήσετε νέες διυθύνσεις γεφυρών με έναν από τους παρακάτω τρεις τρόπους:"> <!ENTITY torsettings.bridgeHelp2Heading "Μέσω του Διαδικτύου"> <!ENTITY torsettings.bridgeHelp2 "Χρησιμοποιήστε έναν φυλλομετρητή για να επισκεφτείτε το https://bridges.torproject.org"> <!ENTITY torsettings.bridgeHelp3Heading "Μέσω της Αυτοματοποιημένης Απάντησης Email"> -<!ENTITY torsettings.bridgeHelp3 "Send email to bridges(a)torproject.org with the line 'get bridges' by itself in the body of the message.  However, to make it harder for an attacker to learn a lot of bridge addresses, you must send this request from a gmail.com or yahoo.com email address."> +<!ENTITY torsettings.bridgeHelp3 "Στείλτε email στο bridges(a)torproject.org με μόνο με τις λέξεις 'get bridges' στο κείμενο.  Για να δυσκολέψουμε τους αντιπάλους μας που θέλουν μα μάθουν πολλές διευθύνσεις γεφυρών, δεχόμαστε μηνύματα μόνο από διευθύνσεις που τελειώνουν σε gmail.com ή yahoo.com."> <!ENTITY torsettings.bridgeHelp4Heading "Μέσω της Υποστήριξης"> -<!ENTITY torsettings.bridgeHelp4 "As a last resort, you can request bridge addresses by sending a polite email message to help(a)rt.torproject.org.  Please note that a person will need to respond to each request."> +<!ENTITY torsettings.bridgeHelp4 "Αν όλα τα άλλα αποτύχουν, μπορείτε να ζητήσετε διευθύνσεις γεφυρών στέλνοντας ένα ευγενικό email στο help(a)rt.torproject.org.  Σημείωση: Κάποιος εθελοντής θα πρέπει να απαντήσει χειροκίνητα (συνεπώς η απάντηση ίσως αργήσει).">

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits June 2014