po

11 files changed, 1235 insertions, 17 deletions

diff --git a/locale/ar/LC_MESSAGES/messages.po b/locale/ar/LC_MESSAGES/messages.po
index a0dca494..d3b59f90 100644
--- a/locale/ar/LC_MESSAGES/messages.po
+++ b/locale/ar/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2021-05-21 14:59+0000\n"
 "Last-Translator: Shorouk Hassouna <shoroukhassuna@gmail.com>\n"
 "Language-Team: Arabic <http://weblate.taler.net/projects/gnunet/website/ar/"
@@ -2909,6 +2909,117 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr ""
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Continuous Integration"
+msgid "Contact Information"
+msgstr "الدمج المستمر"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
diff --git a/locale/de/LC_MESSAGES/messages.po b/locale/de/LC_MESSAGES/messages.po
index 3c2e8230..fa2e41f1 100644
--- a/locale/de/LC_MESSAGES/messages.po
+++ b/locale/de/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2021-08-30 19:06+0000\n"
 "Last-Translator: Stefan <eintritt@hotmail.com>\n"
 "Language-Team: German <http://weblate.taler.net/projects/gnunet/website/de/"
@@ -4140,6 +4140,119 @@ msgstr "Oh mein Gott, ihr habt mir mein Internet kaputt gemacht"
 msgid "Videos related to GNUnet"
 msgstr "Videos zu GNUnet"
 
+#: template/dev_pages/t3sserakt.html.j2:8
+#, fuzzy
+#| msgid "Developer Team"
+msgid "Developer page: t3sserakt"
+msgstr "Entwickelerteam"
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Contact information"
+msgid "Contact Information"
+msgstr "Kontaktinformation"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
@@ -5042,9 +5155,6 @@ msgstr ""
 #~ "org/'>Freier Software</a> erstellt.<br> Probleme bitte <a href='contact."
 #~ "html'>hier</a> melden."
 
-#~ msgid "Developer Team"
-#~ msgstr "Entwickelerteam"
-
 #, fuzzy
 #~| msgid "Tutorials"
 #~ msgid "Install-Tutorials"
diff --git a/locale/es/LC_MESSAGES/messages.po b/locale/es/LC_MESSAGES/messages.po
index d593d981..89d82718 100644
--- a/locale/es/LC_MESSAGES/messages.po
+++ b/locale/es/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2022-08-17 22:14+0000\n"
 "Last-Translator: Lucía López <lulopezcabrera@gmail.com>\n"
 "Language-Team: Spanish <https://weblate.taler.net/projects/gnunet/website/es/"
@@ -3749,6 +3749,119 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr ""
 
+#: template/dev_pages/t3sserakt.html.j2:8
+#, fuzzy
+#| msgid "Developer Team"
+msgid "Developer page: t3sserakt"
+msgstr "Equipo de desarrollo"
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Contact information"
+msgid "Contact Information"
+msgstr "Información de contacto"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
@@ -4629,9 +4742,6 @@ msgstr ""
 #~ msgid "Get off GNUnet"
 #~ msgstr "Qué es GNUnet?"
 
-#~ msgid "Developer Team"
-#~ msgstr "Equipo de desarrollo"
-
 #, fuzzy
 #~| msgid "C-Tutorial"
 #~ msgid "Install-Tutorials"
diff --git a/locale/fr/LC_MESSAGES/messages.po b/locale/fr/LC_MESSAGES/messages.po
index d336e59e..b655313b 100644
--- a/locale/fr/LC_MESSAGES/messages.po
+++ b/locale/fr/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2021-09-28 14:59+0000\n"
 "Last-Translator: Axelle Dimpre <axelle.dimpre@gmail.com>\n"
 "Language-Team: French <http://weblate.taler.net/projects/gnunet/website/fr/"
@@ -3175,6 +3175,117 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr "Vidéos en lien avec GNUnet"
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Contact information"
+msgid "Contact Information"
+msgstr "Nous contacter"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
diff --git a/locale/hi/LC_MESSAGES/messages.po b/locale/hi/LC_MESSAGES/messages.po
index a3cc1484..8e74c8a5 100644
--- a/locale/hi/LC_MESSAGES/messages.po
+++ b/locale/hi/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2021-03-09 18:35+0000\n"
 "Last-Translator: Jigisha Sharma <jigishas38@gmail.com>\n"
 "Language-Team: Hindi <http://weblate.taler.net/projects/gnunet/website/hi/>\n"
@@ -2906,6 +2906,117 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr ""
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Continuous Integration"
+msgid "Contact Information"
+msgstr "लगातार एकीकरण"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
diff --git a/locale/it/LC_MESSAGES/messages.po b/locale/it/LC_MESSAGES/messages.po
index 7e9f75a8..901c1f7c 100644
--- a/locale/it/LC_MESSAGES/messages.po
+++ b/locale/it/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2022-03-27 11:53+0000\n"
 "Last-Translator: Roberto Pellegrino <speekix@gmail.com>\n"
 "Language-Team: Italian <http://weblate.taler.net/projects/gnunet/website/it/"
@@ -3772,6 +3772,117 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr ""
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Contact information"
+msgid "Contact Information"
+msgstr "Contatti"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
diff --git a/locale/ja/LC_MESSAGES/messages.po b/locale/ja/LC_MESSAGES/messages.po
index 81b11643..c694a1e7 100644
--- a/locale/ja/LC_MESSAGES/messages.po
+++ b/locale/ja/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2021-04-15 10:31+0000\n"
 "Last-Translator: Kanoko Kondo <yves0625@gmail.com>\n"
 "Language-Team: Japanese <http://weblate.taler.net/projects/gnunet/website/ja/"
@@ -3410,6 +3410,117 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr ""
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Contact information"
+msgid "Contact Information"
+msgstr "お問い合わせ"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
diff --git a/locale/ko/LC_MESSAGES/messages.po b/locale/ko/LC_MESSAGES/messages.po
index 56b419fd..7a7f833b 100644
--- a/locale/ko/LC_MESSAGES/messages.po
+++ b/locale/ko/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2021-04-11 02:59+0000\n"
 "Last-Translator: Chaewon Park <wonnie0624@gmail.com>\n"
 "Language-Team: Korean <http://weblate.taler.net/projects/gnunet/website/ko/"
@@ -2918,6 +2918,117 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr ""
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Continuous Integration"
+msgid "Contact Information"
+msgstr "지속적 통합"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
diff --git a/locale/messages.pot b/locale/messages.pot
index cc5afdcf..4082e644 100644
--- a/locale/messages.pot
+++ b/locale/messages.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -2928,6 +2928,118 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr ""
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The "
+"current GNUnet TRANSPORT architecture with its pluggable transport "
+"mechanism (TCP, UDP, HTTP(S) and other protocols) together with the ATS "
+"subsystem for bandwidth allocation and choosing plugins has several "
+"issues with its design. With the Layer-2-Overlay project we like to "
+"implement the design goals of the future GNUnet TRANSPORT Next Generation"
+" (TNG) subsystem. For details have a look on the <a "
+"href=\"https://www.gnunet.org/en/l2o/\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid "The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet"
+" connectivity. There are several methods to reach peers being behind a "
+"NAT, but there are as many reasons those existing methods might fail. We "
+"will implement a new way of NAT traversal that we think of being "
+"independent from the existing network configuration, and does not require"
+" a third party which is not natted helping two peers to connect to each "
+"other. Two peers trying to connect to each other will send out a burst of"
+" connection attempts to the other peer on different ports. The sheer vast"
+" amount of connections attempts from both side will lead to a high "
+"probability that two connection attempts from both peers onto the same "
+"port will be at the same time leading to a successful connection between "
+"those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another "
+"peer B wants to connect to. Second – because inbound connections from the"
+" outside are blocked by the NAT firewall of peer A, peer A needs to be "
+"informed of a connection attempt by peer B. The most common solution for "
+"both problems is to have a third party C which is not behind a NAT. This "
+"third party C obviously knows the global IP address of natted peers, "
+"after peer A is trying to connect to C. Peer B tells C it likes to "
+"connect to peer A, and C informs A about it. Using this method for a "
+"privacy preserving network like GNUnet, this could facilitate eclipse "
+"attacks (isolating a peer) which then can be used for deanonymization "
+"attacks and cencorship. Also any additional infrastructure needed to "
+"provide some kind of functionality has to be maintained by someone, "
+"becoming a target and/or point of failure. Therefore this method is not "
+"suitable. More sophisticated methods like \"Autonomous NAT Traversal "
+"(pwnat)\" using ICMP fake message, which do not need a third party for "
+"the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the "
+"burst method for hole punching the global IP address is known. Via the "
+"distance vector protocol we are also able to communicate the \"start "
+"signal\". Also in the L2O project we introduced a new test framework for "
+"GNUnet to test network setups with peers having restricted connectivity. "
+"This test framework will be used to create test setups suitable to test "
+"possible NAT configurations. A challenge for this NAT traversal method "
+"will be how to handle the burst in terms of network load, thus we need to"
+" experiment with different frequencies and the amount of connection "
+"attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a "
+"href=\"http://secushare.org\">secushare</a> project a reality. To achieve"
+" this the GNUnet framework was the perfect match for a solution to "
+"fullfill the privacy preserving part of that vision, and we could "
+"concentrate to build a tool for social communication that deserves its "
+"name. While trying to use GNUnet, we found and fixed bugs. For example "
+"there was one <a "
+"href=\"https://bugs.gnunet.org/view.php?id=5822\">bug</a> in CADET which "
+"prevented the re-establishment of a connection after a communication "
+"partner suddenly stopped communicating. From our perspective there is no "
+"alternativ to GNUnet, which led us to first bring the parts of GNUnet "
+"needed by secushare to a state that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+msgid "Contact Information"
+msgstr ""
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
diff --git a/locale/pt/LC_MESSAGES/messages.po b/locale/pt/LC_MESSAGES/messages.po
index edd2fb02..d30eebce 100644
--- a/locale/pt/LC_MESSAGES/messages.po
+++ b/locale/pt/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: Automatically generated\n"
 "Language-Team: none\n"
@@ -2870,6 +2870,115 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr ""
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+msgid "Contact Information"
+msgstr ""
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6
diff --git a/locale/zh_Hant/LC_MESSAGES/messages.po b/locale/zh_Hant/LC_MESSAGES/messages.po
index e47db942..a81b68f4 100644
--- a/locale/zh_Hant/LC_MESSAGES/messages.po
+++ b/locale/zh_Hant/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2021-08-24 08:59+0000\n"
 "Last-Translator: Ting-Yi Fu <futingyi0215@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <http://weblate.taler.net/projects/"
@@ -3621,6 +3621,117 @@ msgstr "天哪，你們打破了我的網際網路"
 msgid "Videos related to GNUnet"
 msgstr "與 GNUnet 相關的影片"
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Contact information"
+msgid "Contact Information"
+msgstr "聯絡資訊"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6