Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary GNUnet AGPL-3.0 0 0 0 0 0 0 0
Website AGPL-3.0 0 0 0 0 232 0 1

Overview

Project website www.gnunet.org
Project maintainers User avatar grothoff User avatar skuegel User avatar Eintritt User avatar Stefan
Translation license AGPL-3.0 GNUnet Website
5 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 704 21,938 159,356
Approved 0% 0 0% 0 0% 0
Waiting for review 0% 0 0% 0 0% 0
Translated 100% 704 100% 21,938 100% 159,356
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 704 100% 21,938 100% 159,356
Failing checks 32% 232 42% 9,388 44% 71,028
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

13 changes 0 changes 6 changes 0 changes 0 changes 8 changes 0 changes 34 changes 15 changes 0 changes 0 changes 0 changes 40 changes 23 changes 0 changes 5 changes 31 changes 0 changes 1 change 25 changes 0 changes 0 changes 50 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

21,938
Hosted words
704
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+100%
Translated
—
—
Contributors
—
User avatar None

Source string added

  1. GNUnet
  2. Website
  3. English
Test case testing the same functionality as in milestone 1 - 4 running on Android.
3 months ago
User avatar None

Source string added

  1. GNUnet
  2. Website
  3. English
The deliverable of this milestone is twofold: the scripts for automation and the automated tests themselves, and a report on the outcome of these tests. If the test case testing the same functionality as in milestone 6, but using the GNUnet event loop, will not work as expected, the task includes an overview of potential approaches for achieving the desired outcomes in other ways.
3 months ago
User avatar None

Source string added

  1. GNUnet
  2. Website
  3. English
The deliverable of this milestone is twofold: the scripts for automation and the automated tests themselves, and a report on the outcome of these tests. If the test case starting an Android app on two nodes doing network communication between those two apps and each app accessing its own filesystem will not work as expected, the task includes an overview of potential approaches for achieving the desired outcomes in other ways.
3 months ago
User avatar None

Source string added

  1. GNUnet
  2. Website
  3. English
The protocol implementation will be integrated into the GNUnet stack, one Test case will test two peers are finaly connected (UDP case), another test case for TCP tests if both peers end up at the same port and the protocol will be documented.
3 months ago
User avatar None

Source string added

  1. GNUnet
  2. Website
  3. English
Deliverable of this milestone is integrating the protocol implementation into the GNUnet stack, a test case which tests that two peers successfully exchange the messages of the implemented protocol until the condition is reached that both nodes are ready for the burst mode. Additionally there will be a protocol documentation.
3 months ago
User avatar None

Source string added

  1. GNUnet
  2. Website
  3. English
This task is to implement the protocol that is doing the signaling for synchronizing two peers which do like to connect to each other. <a href="mile2.html">Details</a> <ul> <li>Two peers which got connected via DV signaling each other being behind a NAT.</li> <li>Learning the external IP address+port from already connected peers, exchange with the peers that want to connect.</li> <li>Set a common start time. One peer is selected to be leading (comparing peer ids like it is done in CADET)</li> </ul>
3 months ago
User avatar None

Source string added

  1. GNUnet
  2. Website
  3. English
Test case which tests the new testing functionality. Adding documentation.
3 months ago
User avatar None

Source string added

  1. GNUnet
  2. Website
  3. English
Extending the testing framework, which was already designed and implemented for the L2O project. <a href="mile1.html">Details</a> <ul> <li>Enhance the testing framework with a new kind of component (NAT component).</li> <li>Implement logic to keep ports open used during network translation.</li> <li>Extend the test framework configuration to configure the new components.</li> </ul></br>
3 months ago
User avatar Stefan

Resource updated

  1. GNUnet
  2. Website
  3. English
The “locale/messages.pot” file was changed. 3 months ago
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. English
With this milestone, we wanted to get a minimal set of GNUnet service running to test our NAT traversal library. Therefore it was necesarry to cross compile more dependencies (sqlite).<br/><br/> Additional GNUnet utility shared libraries that were cross compiled:<br/><br/> <ul> <li>libgnunethello</li> <li>libgnunetsq</li> </ul> GNUnet services that were cross compiled:<br/><br/> <ul> <li>libgnunetarm</li> <li>libgnunetpeerstore</li> <li>libgnunetstatistics</li> <li>libgnunettransportapplication</li> <li>libgnunettransportcommunicator</li> <li>libgnunettransportcore</li> <li>libgnunettransportmonitor</li> </ul><br/><br/> This attempt to get GNUnet running on Android failed, because - which was already expected before, it was not possible to start all those independent processes on Android. Solution to this problem was to build a monolitic version of GNUnet. Having only two shared libraries libgnunetutil and libgnunet.<br/><br/> After this big change we had to fix several problems:<br/><br/> <ul> <li>Adding Sqlite C to Java linking code (see android_studio/app/src/main/java/org/sqlite).</li> <li>Changing the service macro to get external configuration handle.</li> <li>Load GNUnet configuration from Android assets folder.</li> <li>Fix all GNUnet paths to point to the directory under control of the Android app.</li> <li>Setting the ltdl search path.</li> <li>Preload the GNUnet sqlite plugin.</li> <li>Adding a precompiled private key file to load from asset folder.</li> <li>Several smaller configuration issues.</li> <li>Finish the code for the daemon macro to start the GNUnet communicator components.</li> </ul> Because the automated GNUnet tests are not working on Android, which we found out during Milestone 6 and 7, we again did manual tests between one Android device and two GNU/Linux boxes. Here is a log entry indicating that the Android box (1XNB) send some message to AWZB via QG2V and received an answer from AWZB.<br/><br/> 08-21 08:26:06.840 17084 17116 D GNUNET : 2024-08-21T08:26:06.840469+0100 libgnunet-17084 DEBUG Received DVInit via 1XNB-->QG2V-->AWZB-->1XNB<br/><br/> To complete Milestone 8 the testing of the unfished Milestone 3 code is missing. This is by far the smaller part of the effort that had to be made for this milestone
With this milestone, we wanted to get a minimal set of GNUnet service running to test our NAT traversal library. Therefore it was necesarry to cross compile more dependencies (sqlite).<br/><br/> Additional GNUnet utility shared libraries that were cross compiled:<br/><br/> <ul> <li>libgnunethello</li> <li>libgnunetsq</li> </ul> GNUnet services that were cross compiled:<br/><br/> <ul> <li>libgnunetarm</li> <li>libgnunetpeerstore</li> <li>libgnunetstatistics</li> <li>libgnunettransportapplication</li> <li>libgnunettransportcommunicator</li> <li>libgnunettransportcore</li> <li>libgnunettransportmonitor</li> </ul><br/><br/> This attempt to get GNUnet running on Android failed, because - which was already expected before, it was not possible to start all those independent processes on Android. Solution to this problem was to build a monolitic version of GNUnet. Having only two shared libraries libgnunetutil and libgnunet.<br/><br/> After this big change we had to fix several problems:<br/><br/> <ul> <li>Adding Sqlite C to Java linking code (see android_studio/app/src/main/java/org/sqlite).</li> <li>Changing the service macro to get external configuration handle.</li> <li>Load GNUnet configuration from Android assets folder.</li> <li>Fix all GNUnet paths to point to the directory under control of the Android app.</li> <li>Setting the ltdl search path.</li> <li>Preload the GNUnet sqlite plugin.</li> <li>Adding a precompiled private key file to load from asset folder.</li> <li>Several smaller configuration issues.</li> <li>Finish the code for the daemon macro to start the GNUnet communicator components.</li> </ul> Because the automated GNUnet tests are not working on Android, which we found out during Milestone 6 and 7, we again did manual tests between one Android device and two GNU/Linux boxes. Here is a log entry indicating that the Android box (1XNB) send some message to AWZB via QG2V and received an answer from AWZB.<br/><br/> 08-21 08:26:06.840 17084 17116 D GNUNET : 2024-08-21T08:26:06.840469+0100 libgnunet-17084 DEBUG Received DVInit via 1XNB-->QG2V-->AWZB-->1XNB<br/><br/> To complete Milestone 8 the testing of the unfished Milestone 3 code is missing. This is by far the smaller part of the effort that had to be made for this milestone
3 months ago
Browse all changes for this language