[TWN team] Recent changes to the wiki pages
Lunar
lunar at torproject.org
Tue May 20 13:20:11 UTC 2014
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/20 ===
===========================================================================
version 39
Author: karsten
Date: 2014-05-20T12:40:50+00:00
Minor language tweaks.
--- version 38
+++ version 39
@@ -73,14 +73,14 @@
[8]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006872.html
Karsten Loesing posted [9] on the Tor Blog to commemorate the tenth
-anniversary of the first Tor directory, and discussed the different ways
+anniversary of the first archived Tor directory, and discussed the different ways
in which the public archive of directory data is being used for research
and development.
[9]: https://blog.torproject.org/blog/10-years-collecting-tor-directory-data
Karsten also notified [10] the community of a change in the compression
-format used for the tarballs of archived metrics data, which has reduced
+algorithm used for the tarballs of archived metrics data, which has reduced
their total size from 212 gigabytes to 33 — an 85% gain!
[10]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006884.html
@@ -88,7 +88,7 @@
Knock [11] is a variant of port-knocking that might be useful in the
future for pluggable transports. “As Knock uses two fields in the TCP
header in order to hide information and we explicitly want to be
-compatible with machines sitting in typical home networks”, write [12]
+compatible with machines sitting in typical home networks”, writes [12]
Julian Kirsch, “we thus created a program which tests if Knock would
work in your environment.” Please give it a try [13] to help the team
figure out if Knock could be deployed in the wild.
@@ -106,7 +106,7 @@
[17]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000594.html
Michael Schloh von Bennewitz has been busy analyzing a disk leak [18] in
-Tor Browser: when one copy a significant chunk of text in the clipboard,
+Tor Browser: when one copies a significant chunk of text to the clipboard,
a temporary file is created with its content. Michael found a possible
fix and is welcoming reviews [19].
@@ -131,7 +131,7 @@
Although, dope457 reported that their provider is now giving them
troubles as an operator of a non-exit relays [23] due to a high amount
of traffic on the DNS port (53). A port used by a recently setup Tor
-relay [24], as pointed [25] by Roman Mamedov.
+relay [24], as pointed out [25] by Roman Mamedov.
[23]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
[24]: https://atlas.torproject.org/#details/44EFAF942314F756FC7EA50292D5B383E568A9BD
version 38
Author: lunar
Date: 2014-05-20T12:14:04+00:00
FREEZE
--- version 37
+++ version 38
@@ -1,6 +1,8 @@
''46th issue of Tor Weekly News. Covering what's happening from May 13th, 2014 to May 20th, 2014. To be released on May 21st, 2014.''
'''Editor:''' Lunar
+
+'''Status:''' FROZEN. Only technical and language fixes allowed. New items should go on [wiki:TorWeeklyNews/2014/21 next week's edition]. Expected publication time: 2014-05-21 12:00 UTC.
'''Subject:''' Tor Weekly News — May 21st, 2014
@@ -10,205 +12,208 @@
========================================================================
Welcome to the twentieth issue of Tor Weekly News in 2014, the weekly
-newsletter that covers what is happening in the XXX Tor community.
+newsletter that covers what is happening in the Tor community.
Tor 0.2.4.22 is out
-------------------
-A new version of Tor stable branch has been released [XXX] on May 16th:
+A new version of Tor stable branch has been released [1] on May 16th:
“Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
-alpha release series. These include blocking all authority signing
-keys that may have been affected by the OpenSSL ‘heartbleed’ bug,
-choosing a far more secure set of TLS ciphersuites by default, closing
-a couple of memory leaks that could be used to run a target relay out
-of RAM, and several others.”
-
-For more details, look at the full changelog [XXX]. The source is
-available at the usual location [XXX]. Packages should be coming shortly,
-when not already available [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032956.html
- [XXX]: https://gitweb.torproject.org/tor.git/blob_plain/2ee56e4c2:/ChangeLog
- [XXX]: https://www.torproject.org/dist/
- [XXX]: http://packages.qa.debian.org/t/tor/news/20140517T102023Z.html
+alpha release series. These include blocking all authority signing keys
+that may have been affected by the OpenSSL ‘heartbleed’ bug, choosing a
+far more secure set of TLS ciphersuites by default, closing a couple of
+memory leaks that could be used to run a target relay out of RAM, and
+several others.”
+
+For more details, look at the full changelog [2]. The source is
+available at the usual location [3]. Packages should be coming shortly,
+when not already available [4].
+
+ [1]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032956.html
+ [2]: https://gitweb.torproject.org/tor.git/blob_plain/2ee56e4c2:/ChangeLog
+ [3]: https://www.torproject.org/dist/
+ [4]: http://packages.qa.debian.org/t/tor/news/20140517T102023Z.html
Digital Restrictions Management and Firefox
-------------------------------------------
-Mozilla's decisions to support playing media with digital restrictions [XXX]
-in Firefox by implementing W3C EME specification has raised a good amount
-of controversy. Paul Crable wanted to know [XXX] what it meant for the
-Tor Browser.
-
-Mike Perry answered that, “simply removing the DRM will be trivial, and it
-will be high on our list of tasks”.
-
-But he also explained his worries regarding a “per-device unique identifier”
-that Firefox would provide as part of the implementation: “it is likely
-that this identifier will soon be abused by all sorts of entities, […]
-quickly moving on to the advertising industry (why not play a short
-device-linked DRM video with your banner ad? You get a persistent,
-device-specific tracking identifier as part of the deal!). I think
-it is also quite likely that many arbitrary sites will actually deny
-access to users who do not provide them with such a device-id,
-if only due to ease of increased revenue generation from a fully
-identified userbase.”
+Mozilla’s decisions to support playing media with digital
+restrictions [5] in Firefox by implementing W3C EME specification has
+raised a good amount of controversy. Paul Crable wanted to know [6] what
+it meant for the Tor Browser.
+
+Mike Perry answered [7] that, “simply removing the DRM will be trivial,
+and it will be high on our list of tasks”.
+
+But he also explained his worries regarding a “per-device unique
+identifier” that Firefox would provide as part of the implementation:
+“it is likely that this identifier will soon be abused by all sorts of
+entities, […] quickly moving on to the advertising industry (why not
+play a short device-linked DRM video with your banner ad? You get a
+persistent, device-specific tracking identifier as part of the deal!). I
+think it is also quite likely that many arbitrary sites will actually
+deny access to users who do not provide them with such a device-id, if
+only due to ease of increased revenue generation from a fully identified
+userbase.”
“It seems that neither Mozilla nor Google have fully thought through the
social effects of giving a unique device-id to arbitrary websites” as
Mike concludes.
- [XXX]: https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-eme/
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032947.html
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
+ [5]: https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-eme/
+ [6]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032947.html
+ [7]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032985.html
Miscellaneous news
------------------
-David Goulet reported [XXX] on the status of the development of
-Torsocks 2.0, the library for safely using applications with Tor.
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006872.html
-
-Karsten Loesing posted [XXX] on the Tor Blog to commemorate the tenth
-anniversary of the first Tor directory, and discussed the different
-ways in which the public archive of directory data is being used for
-research and development.
-
- [XXX]: https://blog.torproject.org/blog/10-years-collecting-tor-directory-data
-
-Knock [XXX] is a variant of port-knocking that might be useful in the
-future for pluggable transports. “As Knock uses two fields in the
-TCP header in order to hide information and we explicitly want to
-be compatible with machines sitting in typical home networks”, write [XXX]
-Julian Kirsch, “we thus created a program which tests if Knock would
-work in your environment.” Please give it a try to help the team figure
-out if Knock could be deployed in the wild.
-
- [XXX]: https://gnunet.org/knock
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006873.html
- [XXX]: https://gnunet.org/knock_nat_tester
-
-Karsten also notified [XXX] the community of a change in the compression
+David Goulet reported [8] on the status of the development of Torsocks
+2.0, the library for safely using applications with Tor.
+
+ [8]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006872.html
+
+Karsten Loesing posted [9] on the Tor Blog to commemorate the tenth
+anniversary of the first Tor directory, and discussed the different ways
+in which the public archive of directory data is being used for research
+and development.
+
+ [9]: https://blog.torproject.org/blog/10-years-collecting-tor-directory-data
+
+Karsten also notified [10] the community of a change in the compression
format used for the tarballs of archived metrics data, which has reduced
their total size from 212 gigabytes to 33 — an 85% gain!
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006884.html
-
-Thanks to Jesse Victors [XXX], Andrea [XXX], Nicholas Merrill [XXX], and
-Martin A. [XXX] for running mirrors of the Tor Project website!
-
- [XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000581.html
- [XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000589.html
- [XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000592.html
- [XXX]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000594.html
-
-Michael Schloh von Bennewitz has been busy analyzing a disk leak [XXX] in
+ [10]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006884.html
+
+Knock [11] is a variant of port-knocking that might be useful in the
+future for pluggable transports. “As Knock uses two fields in the TCP
+header in order to hide information and we explicitly want to be
+compatible with machines sitting in typical home networks”, write [12]
+Julian Kirsch, “we thus created a program which tests if Knock would
+work in your environment.” Please give it a try [13] to help the team
+figure out if Knock could be deployed in the wild.
+
+ [11]: https://gnunet.org/knock
+ [12]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006873.html
+ [13]: https://gnunet.org/knock_nat_tester
+
+Thanks to Jesse Victors [14], Andrea [15], Nicholas Merrill [16], and
+Martin A. [17] for running mirrors of the Tor Project website!
+
+ [14]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000581.html
+ [15]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000589.html
+ [16]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000592.html
+ [17]: https://lists.torproject.org/pipermail/tor-mirrors/2014-May/000594.html
+
+Michael Schloh von Bennewitz has been busy analyzing a disk leak [18] in
Tor Browser: when one copy a significant chunk of text in the clipboard,
-a temporary file is created with its content. Michael found a possible fix
-and is welcoming reviews [XXX].
-
- [XXX]: https://bugs.torproject.org/9701
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006875.html
-
-Nicolas Vigier has been investigating [XXX] some extra connections made
-by the Tor Browser on startup to the local resolver and the default
-port or the SOCKS proxy.
-
- [XXX]: https://lists.torproject.org/pipermail/tbb-dev/2014-May/000050.html
+a temporary file is created with its content. Michael found a possible
+fix and is welcoming reviews [19].
+
+ [18]: https://bugs.torproject.org/9701
+ [19]: https://lists.torproject.org/pipermail/tor-dev/2014-May/006875.html
+
+Nicolas Vigier has been investigating [20] some extra connections made
+by the Tor Browser on startup to the local resolver and the default port
+or the SOCKS proxy.
+
+ [20]: https://lists.torproject.org/pipermail/tbb-dev/2014-May/000050.html
Shawn Nock proved us once more that talking to ISP is key to run Tor
-relays on high-speed links. Shawn's exit node was abruptly shut down by
-its provider [XXX] on May 15th. After a well-crafted plea explaining how
-Tor was important, the provider restored the service [XXX] on the very
+relays on high-speed links. Shawn’s exit node was abruptly shut down by
+its provider [21] on May 15th. After a well-crafted plea explaining how
+Tor was important, the provider restored the service [22] on the very
same day!
- [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004553.html
- [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
-
-Although, dope457 reported that their provider is now giving them troubles
-as an operator of a non-exit relays [XXX] due to a high amount of
-traffic on the DNS port (53). A port used by a recently setup Tor relay [XXX],
-as pointed [XXX] by Roman Mamedov.
-
- [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
- [XXX]: https://atlas.torproject.org/#details/44EFAF942314F756FC7EA50292D5B383E568A9BD
- [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004563.html
-
-Now that ICANN is “selling” top-level domain name, Anders Andersson raised
-worries [XXX] about the .onion extension used by Tor. Fortunately,
-RFC6761 [XXX] defines a process regarding special-use domain names. Last
+ [21]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004553.html
+ [22]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004555.html
+
+Although, dope457 reported that their provider is now giving them
+troubles as an operator of a non-exit relays [23] due to a high amount
+of traffic on the DNS port (53). A port used by a recently setup Tor
+relay [24], as pointed [25] by Roman Mamedov.
+
+ [23]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004562.html
+ [24]: https://atlas.torproject.org/#details/44EFAF942314F756FC7EA50292D5B383E568A9BD
+ [25]: https://lists.torproject.org/pipermail/tor-relays/2014-May/004563.html
+
+Now that ICANN is “selling” top-level domain name, Anders Andersson
+raised worries [26] about the .onion extension used by Tor. Fortunately,
+RFC6761 [27] defines a process regarding special-use domain names. Last
November, Christian Grothoff, Matthias Wachs, Hellekin O. Wolf, and
Jacob Appelbaum submitted a request to reserve several TLDs used in
-peer-to-peer systems. Hellekin sent an update [XXX] about the procedure:
-“the current status quo from the IETF so far is that this issue is not
-a priority”.
-
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032974.html
- [XXX]: https://tools.ietf.org/html/rfc6761
- [XXX]: https://tools.ietf.org/html/draft-grothoff-iesg-special-use-p2p-names-02
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032983.html
+peer-to-peer systems [28]. Hellekin sent an update [29] about the
+procedure: “the current status quo from the IETF so far is that this
+issue is not a priority”.
+
+ [26]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032974.html
+ [27]: https://tools.ietf.org/html/rfc6761
+ [28]: https://tools.ietf.org/html/draft-grothoff-iesg-special-use-p2p-names-02
+ [29]: https://lists.torproject.org/pipermail/tor-talk/2014-May/032983.html
Tor help desk roundup
---------------------
-Local antivirus or firewall applications can prevent Tor from connecting
-unless they are disabled. Firewall tools that have caused usability
-issues in the past include Webroot SecureAnywhere AV, Kaspersky Internet
-Security 2012, Sophos Antivirus for Mac, and Microsoft Security Essentials.
+Local antivirus or firewall applications can prevent Tor from connecting
+unless they are disabled. Firewall tools that have caused usability
+issues in the past include Webroot SecureAnywhere AV, Kaspersky Internet
+Security 2012, Sophos Antivirus for Mac, and Microsoft Security
+Essentials.
News from Tor StackExchange
---------------------------
-The Tor StackExchange site [XXX] now provides more than 1000 answers
-to user-supplied questions. However, there are still ~130 questions [XXX]
-which need a good answer, so if you happen to know one then please
-visit the site and help out.
-
-The majority of the questions are about the Tor Browser Bundle [XXX],
-but hidden services also attract a large amount of attention [XXX].
-When it comes to operating systems, there are 42 Windows-related
-questions [XXX], while questions about Tails [XXX] and Whonix [XXX] number
-nearly 50. All your questions about Tor and related software are welcome.
-
- [XXX]: https://tor.stackexchange.com/
- [XXX]: https://tor.stackexchange.com/unanswered
- [XXX]: https://tor.stackexchange.com/questions/tagged/tor-browser-bundle
- [XXX]: https://tor.stackexchange.com/questions/tagged/hidden-services
- [XXX]: https://tor.stackexchange.com/questions/tagged/windows
- [XXX]: https://tor.stackexchange.com/questions/tagged/tails
- [XXX]: https://tor.stackexchange.com/questions/tagged/whonix
+The Tor StackExchange site [30] now provides more than 1000 answers to
+user-supplied questions. However, there are still ~130 questions [31]
+which need a good answer, so if you happen to know one then please visit
+the site and help out.
+
+The majority of the questions are about the Tor Browser Bundle [32], but
+hidden services also attract a large amount of attention [33]. When it
+comes to operating systems, there are 42 Windows-related questions [34],
+while questions about Tails [35] and Whonix [36] number nearly 50. All
+your questions about Tor and related software are welcome.
+
+ [30]: https://tor.stackexchange.com/
+ [31]: https://tor.stackexchange.com/unanswered
+ [32]: https://tor.stackexchange.com/questions/tagged/tor-browser-bundle
+ [33]: https://tor.stackexchange.com/questions/tagged/hidden-services
+ [34]: https://tor.stackexchange.com/questions/tagged/windows
+ [35]: https://tor.stackexchange.com/questions/tagged/tails
+ [36]: https://tor.stackexchange.com/questions/tagged/whonix
Blue_Pyro uses Orweb on the mobile phone and wants to save images from
-web sites [XXX]. Abel of Guardian recommended two options. First a user
-can use Firefox mobile with privacy enhanced options [XXX] or one can
-try Orfox [XXX], a development version of a Firefox-based browser.
-
- [XXX]: https://tor.stackexchange.com/q/1753/88
- [XXX]: https://guardianproject.info/apps/firefoxprivacy/
- [XXX]: https://guardianproject.info/builds/Orfox/latest/
+web sites [37]. Abel of Guardian recommended two options. First a user
+can use Firefox mobile with privacy enhanced options [38] or one can try
+Orfox [39], a development version of a Firefox-based browser.
+
+ [37]: https://tor.stackexchange.com/q/1753/88
+ [38]: https://guardianproject.info/apps/firefoxprivacy/
+ [39]: https://guardianproject.info/builds/Orfox/latest/
Easy development tasks to get involved with
-------------------------------------------
-Stem is a Python controller library for Tor. It comes with tutorials
-and generally has pretty good test coverage. The newly-added example
-scripts, however, don’t have unit tests, yet. Damian Johnson suggests
-ways for adding unit tests for example scripts in [XXX]. If you want
-to help out, learn how to get started [XXX], start writing unit tests
-for the example scripts, and then comment on the ticket.
-
- [XXX] https://trac.torproject.org/projects/tor/ticket/11335
- [XXX] https://gitweb.torproject.org/stem.git
-
-The traffic obfuscator obfsproxy should validate command-line
-arguments appropriately [XXX]. Right now, it’s printing an error and
+Stem [40] is a Python controller library for Tor. It comes with
+tutorials and generally has pretty good test coverage. The newly-added
+example scripts, however, don’t have unit tests, yet. Damian Johnson
+suggests ways for adding unit tests for example scripts in [41]. If you
+want to help out, learn how to get started [42], start writing unit
+tests for the example scripts, and then comment on the ticket.
+
+ [40]: https://stem.torproject.org/
+ [41]: https://trac.torproject.org/projects/tor/ticket/11335
+ [42]: https://gitweb.torproject.org/stem.git
+
+The traffic obfuscator obfsproxy [43] should validate command-line
+arguments appropriately [44]. Right now, it’s printing an error and
continuing, but it should really abort. This sounds like a trivial
change, but maybe there’s more to fix in the nearby code. If you like
-Python and want to give it a try, there's more information for you on
+Python and want to give it a try, there’s more information for you on
the ticket.
- [XXX] https://trac.torproject.org/projects/tor/ticket/9823
+ [43]: https://www.torproject.org/projects/obfsproxy.html
+ [44]: https://trac.torproject.org/projects/tor/ticket/9823
Upcoming events
---------------
@@ -235,12 +240,10 @@
Want to continue reading TWN? Please help us create this newsletter.
We still need more volunteers to watch the Tor community and report
-important news. Please see the project page [XXX], write down your
-name and subscribe to the team mailing list [XXX] if you want to
+important news. Please see the project page [45], write down your
+name and subscribe to the team mailing list [46] if you want to
get involved!
- [XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
- [XXX]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
+ [45]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
+ [46]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
}}}
-
-Possible items:
version 37
Author: lunar
Date: 2014-05-20T12:02:53+00:00
typography
--- version 36
+++ version 37
@@ -18,7 +18,7 @@
A new version of Tor stable branch has been released [XXX] on May 16th:
“Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
alpha release series. These include blocking all authority signing
-keys that may have been affected by the OpenSSL "heartbleed" bug,
+keys that may have been affected by the OpenSSL ‘heartbleed’ bug,
choosing a far more secure set of TLS ciphersuites by default, closing
a couple of memory leaks that could be used to run a target relay out
of RAM, and several others.”
version 36
Author: lunar
Date: 2014-05-20T12:01:50+00:00
add credit
--- version 35
+++ version 36
@@ -230,8 +230,8 @@
| http://www.stockholminternetforum.se/
-This issue of Tor Weekly News has been assembled by XXX, XXX, and
-XXX.
+This issue of Tor Weekly News has been assembled by Lunar, harmony, Matt
+Pagan, Karsten Loesing, and qbi.
Want to continue reading TWN? Please help us create this newsletter.
We still need more volunteers to watch the Tor community and report
===========================================================================
=== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/21 ===
===========================================================================
version 1
Author: lunar
Date: 2014-05-20T12:15:32+00:00
import template
---
+++ version 1
@@ -0,0 +1,82 @@
+''47th issue of Tor Weekly News. Covering what's happening from May 20th, 2014 to May 27th, 2014. To be released on May 28th, 2014.''
+
+'''Editor:'''
+
+'''Subject:''' Tor Weekly News — XXX Xth, 2014
+
+{{{
+========================================================================
+Tor Weekly News May 28th, 2014
+========================================================================
+
+Welcome to the twenty-first issue of Tor Weekly News in 2014, the weekly
+newsletter that covers what is happening in the XXX Tor community.
+
+Feature XXX
+-----------
+
+Feature 1 with cited source [XXX]
+
+ [XXX]:
+
+Monthly status reports for XXX month 2014
+-----------------------------------------
+
+The wave of regular monthly reports from Tor project members for the
+month of XXX has begun. XXX released his report first [XXX], followed
+by reports from name 2 [XXX], name 3 [XXX], and name 4 [XXX].
+
+ [XXX]:
+ [XXX]:
+ [XXX]:
+ [XXX]:
+
+Miscellaneous news
+------------------
+
+Item 1 with cited source [XXX].
+
+Item 2 with cited source [XXX].
+
+Item 3 with cited source [XXX].
+
+ [XXX]:
+ [XXX]:
+ [XXX]:
+
+Tor help desk roundup
+---------------------
+
+Summary of some questions sent to the Tor help desk.
+
+News from Tor StackExchange
+---------------------------
+
+Text with cited source [XXX].
+
+ [XXX]:
+
+Upcoming events
+---------------
+
+Jul XX-XX | Event XXX brief description
+ | Event City, Event Country
+ | Event website URL
+ |
+Jul XX-XX | Event XXX brief description
+ | Event City, Event Country
+ | Event website URL
+
+
+This issue of Tor Weekly News has been assembled by XXX, XXX, and
+XXX.
+
+Want to continue reading TWN? Please help us create this newsletter.
+We still need more volunteers to watch the Tor community and report
+important news. Please see the project page [XXX], write down your
+name and subscribe to the team mailing list [XXX] if you want to
+get involved!
+
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
+ [XXX]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
+}}}
--
Your friendly TWN monitoring script
In case of malfunction, please reach out for lunar at torproject.org
or for the worst cases, tell weasel at torproject.org to kill me.
More information about the news-team
mailing list