Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary GNUnet AGPL-3.0 0% 0 0 0 0 0 0 0
Website AGPL-3.0 1% 42% 378 14,858 113,858 340 1 5 0

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 660 21,486 156,388
Approved 1% 2 1% 3 1% 22
Waiting for review 42% 280 30% 6,625 27% 42,508
Translated 42% 282 30% 6,628 27% 42,530
Needs editing 5% 38 3% 747 3% 5,491
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 1% 2 1% 11
Strings with suggestions 1% 5 1% 97 1% 623
Untranslated strings 51% 340 65% 14,111 69% 108,367
Last 12 months Previous

Activity in last 12 months

16 changes 0 changes 7 changes 0 changes 0 changes 8 changes 0 changes 33 changes 20 changes 0 changes 0 changes 0 changes 42 changes 61 changes 0 changes 6 changes 32 changes 0 changes 1 change 17 changes 0 changes 0 changes 50 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

21,486
Hosted words
660
Hosted strings
42%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+42%
Translated
—
—
Contributors
—
User avatar Stefan

Resource updated

  1. GNUnet
  2. Website
  3. Spanish
The “locale/es/LC_MESSAGES/messages.po” file was changed. 3 months ago
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. Spanish
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
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. Spanish
See revisions from <a href="https://git.gnunet.org/gnunet-android.git/commit/android_studio?id=e843c5ca17b859b9e8b78320bd77d6329fdb66a5">e843c5c</a> to <a href="https://git.gnunet.org/gnunet-android.git/commit/android_studio?id=8044aa27a72525dfdb28918a2fd1f151db60691f">8044aa2</a> in the gnunet-android repo, and <a href="https://git.gnunet.org/gnunet-android.git/commit/android_studio?id=c5b44d67c15f2f61a6195c13361f71e6675aa174">c5b44d6</a> to <a href="https://git.gnunet.org/gnunet-android.git/commit/android_studio?id=af4ce4dac3568b44506301498cd5c6cd59ed1b01">af4ce4d</a> in the dev/t3ss/monolith-android branch of the gnunet repo.
 
3 months ago
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. Spanish
With this milestone, we wanted to ensure that we could use the GNUnet event loop. This is done by calling the GNUnet utitlity function GNUNET_PROGRAM_run in native-lib.ccp. To let the event loop do something meaningful the very simple server from milestone 6 was made running from inside the event loop.<br/><br/> The biggest effort to make these few lines of code work was to solve the problems with the cross-compiling dependencies. This effort has been documented in this <a href="https://github.com/commercetest/cross-compiling-gnunet">repository</a>. One can find these cross compiled dependencies in the directory distribution in the android studio project.<br/><br/>
 
3 months ago
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. Spanish
See revision <a href="https://git.gnunet.org/gnunet-android.git/commit/android_studio?id=ccb81ca8add3c2298e67f7da558e785039a709db">ccb81ca</a>, <a href="https://git.gnunet.org/gnunet-android.git/commit/android_studio?id=9fc64f347ea6ea402eb37d811cb4f214af7c3a28">9fc64f3</a>
 
3 months ago
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. Spanish
A new repository was created for porting the library to Android.<br/><br/> This repository contains an Android app, as a feasibility study. The app is based on a code <a href="https://developer.android.com/studio/projects/add-native-code">example</a> for the integration of native C code in Android Studio. The main starting points for the integration of the GNUnet utility library are the files CMakeLists.txt for all the dependencies the use of the GNUnet utility library entails, and native-lib.ccp where we call functions of the GNUnet utility library. <br/><br/> With this milestone, we wanted to ensure that we could achieve file and network access via the GNUnet utility library. The file access was simply tested with the call of GNUNET_DISK_mktemp("test"), which created a directoy . A very simple server was implemented in the run function of native-lib.ccp. <br/><br/> The biggest effort to make these few lines of code work was to solve the problems with cross-compiling dependencies. This effort has been documented in this <a href="https://github.com/commercetest/cross-compiling-gnunet">repository</a>. One can find these cross compiled dependencies in the directory distribution in the android studio project.<br/><br/> The original plan to run the GNUnet test framework on an Android emulator could not be realized because the Android prototype app could not be made to run on an emulator. Therefore, we did not even try to run the test framework additionally. Tests were made manually on real Android devices.
 
3 months ago
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. Spanish
See revision <a href="https://git.gnunet.org/gnunet-android.git/commit/android_studio?id=c21617466bd0d2ca7cfd1179323025e7480de135">c216174</a>, <a href="https://git.gnunet.org/gnunet-android.git/commit/android_studio?id=571f33dfda632a8c1f5791056b9b3322b592a883">571f33d</a>, <a href="https://git.gnunet.org/gnunet-android.git/commit/android_studio?id=f99b713620cc6fb49e17e57431ae2716f0d5f46f">f99b713</a>
 
3 months ago
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. Spanish
We decided to refactor our complete testing framework, because the existing one was not capable to test more complex test setups needed to test the NAT traversal. Now the test framework is capable to simulate complete GNUnet peers and not just specific parts of it. Additionally the network topology can be more complex to simulate carrier grade NAT.<br/><br/> The refactoring started with revision 6ec23eefb5cde3fe1a329321d149ab312bd23bf5 and ended with rev. 8e441bf379774656caf8949cadc00fd0c2745b77<br/><br/> The main implemention of the burst logic is done here: 8e441bf379774656caf8949cadc00fd0c2745b77 and d6925db2ef45db61fcc24e411432ddd889c4c225<br/><br/> Make the test framework work to run full peers: 86fc39f560cbfddbe4826decb2848648f8665f4a<br/><br/> Fixed Generic and specific test setup and code: ecbec010c90fbcd1ea3542eee5c91b50ad2845b9<br/><br/> Fixed bug adding global addresses to nat service: 30549860678cb9abc48d6d4efb6ef311bd094361<br/><br/> Make hole punch socket available, and some bug fixes: 227acb2c84956bebcb7e942df01221322b66caa9<br/><br/> The API for the burst logic was added to the protocol <a href="api.html">here</a>.<br/><br/> Milestone 3 was not implemented completely. Only UDP burst was implemented, and the integration into GNUnet still has bugs.<br/><br/> If one starts the test case in directory<br/><br/> src/service/arm by typing<br/><br/> typing<br/><br/> GNUNET_FORCE_LOG=';;;;DEBUG' GNUNET_FORCE_LOGFILE=test.out make check TESTS="test_arm_probnat.sh"<br/><br/> one sees messages like<br/><br/> INFO Received a burst message on local port 14234 36!<br/><br/> indicating the hole punch.<br/><br/> There needs to be optimization, because at the moment it takes too long (10 to 20 Minutes). But the optimization milestone was exchange with the milestone to get the NAT traversal running on Android.
 
3 months ago
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. Spanish
Test case testing the same functionality as in milestone 1 - 4 running on Android. <a href="mile8.html">Details</a>
 
3 months ago
User avatar None

String added in the repository

  1. GNUnet
  2. Website
  3. Spanish
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. <a href="mile7.html">Details</a>
 
3 months ago
Browse all changes for this language