1. 20 May, 2020 4 commits
  2. 19 May, 2020 2 commits
  3. 12 May, 2020 4 commits
  4. 07 May, 2020 2 commits
  5. 04 May, 2020 2 commits
  6. 01 May, 2020 1 commit
  7. 30 Apr, 2020 1 commit
  8. 28 Apr, 2020 16 commits
  9. 24 Apr, 2020 1 commit
  10. 21 Apr, 2020 2 commits
  11. 20 Apr, 2020 2 commits
    • Ivan Vilata-i-Balaguer's avatar
      Release v0.7.1. · ebc798c3
      Ivan Vilata-i-Balaguer authored
      Features:
      
        - Automatic, periodic garbage collection of local cache entries older than
          the maximum cache age.
        - Ability to purge the local cache via client API and front-end.
        - Approximate local cache size can be retrieved via the client API and
          front-end.
      
      Enhancements:
      
        - Unify client endpoints to `127.0.0.1:8077` (HTTP proxy) and
          `127.0.0.1:8078` (front-end) by default and enable both by default.
        - Update readme to remove obsolete information and better help testing.
        - More efficient URI swarm name computations.
        - Use newer OpenSSL library.
        - Use a non-dummy version number in the client API, and have proper release
          notes. `;)`
      
      Bugfixes:
      
        - Avoid issues with BitTorrent bootstrap nodes resolving to an IPv6 address
          first.
        - Avoid the agent from furiously retrying when there is no fresh mechanism
          available.
        - Other fixes for Android and asynchronous operations, timeouts and
          cancellations.
      ebc798c3
    • Ivan Vilata-i-Balaguer's avatar
      Merge branch 'default-client-ports'. · 298f0361
      Ivan Vilata-i-Balaguer authored
      This unifies endpoints used by the client in the different current scenarios:
      standalone binary, Docker container, Android library.
      
      Now the default HTTP proxy endpoint is `127.0.0.1:8077`, and the default
      front-end endpoint is `127.0.0.1.:8078`, with both enabled by default.
      
      The reason for `127.0.0.1` and not something less prone to clashes like
      `127.7.2.1` (as we do in the injector) is that the client is expected to run
      on many platforms (while we can assume GNU/Linux for the injector), and not
      all of them support binding to addresses in `127.0.0.0/8` other than
      `127.0.0.1` (e.g. macOS and other BSD-based systems).  Thus it becomes more
      reasonable to choose a less crowded port (8077 and the following one in this
      case).
      
      Documentation and other references in code and other files have been updated
      as well.
      298f0361
  12. 17 Apr, 2020 3 commits