Tags

Resources persitence and email distributor

* core: same distributor if bridges have the same IP or fingerprint
* core: add persitent storage for resources
* i18n: add a script to fetch translations
* moat: add captcha moat support
* moat: add prometheus metrics
* email: add email distributor
* persistence: add journaling to json persistence
* doc: document all the bridge distribution mechanisms

A new HTTPS distributor

* limit the side of web requests bodies on all distributors
* backend: distribute non-speedrejected resources
* backend: fail tests for bridges with invalid addresses
* backend: export tests restuls on assignments.log
* backend: test bridges every 3 hours
* HTTPS: fully implemented distributor
* telegram: distribute lox invites
* moat: add trust-proxy config option

Multiconfig files and whatsapp improvements

* add support for multiple config files
* add a moat integration test
* backend: add a /resource API to poll working/not working resources
* whatsapp: add metrics support
* whatsapp: code refactor and clean up
* gettor: update email instructions

Authentcation for bridge testing and improve development

* Add authentication token for onbasca and bridgestrap
* Generate fake descriptors for development
* Don't reject bridges with errors in onbasca
* moat: use content-type 'application/json'

Add i18n support

* Add i18n support
* Internationalize the telegram bridges bot
* Ignore functional/ratio based on the number resources
* Distribute resources with speed untested
* Add a basic whatsapp bridges distributor

Rework bridge testing and metrics

* Ignore the running flag on bridges
* Rework resources metrics to one single one with their test status
* Retry tests for failing resources
* Mark resources that fail tests gone
* Add LastPassed field to resource
* gettor: Only update the S3 existence file if missing

Webtunnel support

* Add support to distribute webtunnel bridges
* Treat unkown BridgeDistributionRequest as "none"
* Add metrics for flickering bandwidth and ratios seen
* Display the location where the bridge is blocked in the status page
* Use renovate to update dependencies

Test resources bandwidth with onbasca and distribute apks with gettor

* Test resource bandwidth with onbasca
* Add authentication to resource registration
* gettor: Distribute android apks
* moat: use pt_config.json to fetch builtin bridges from Tor Browser
* telegram: Fix segfault on handler configuration
* whatsapp: A dummy implementation

telegram and gettor bugfixes

* Mark backend full updates to distributors
* Propagate prunned resources to distributors
* Use https for backend connections
* Unauthenticated SMTP support
* telegram: improve usability
* telegram: upgrade the telegram library version
* gettor: support multilocale Tor Browser
* gettor: several bug fixes (github versions, short subject, imap
  iddle errors)
* moat: refresh builtin bridges periodically
* moat: support multiple shim tokens

Gettor feature complete

* Add a gitlab gettor updater
* Add prometheus metrics to gettor distributor
* Fix multiple gettor issues
* Distribute only bridgestrap tested and functional resources
* Ignore bridge authority updates without running bridges
* Include the location of the request to the Circumvention Settings API
* Add support to bridgelines in Circumvention map
* Circumvention Settings distributes dummy bridges if not valid
  shim-token provided
* Add an API to update Telegram dynamic bridges
* UX improvements in Telegram distributor

Telegram improvements for deployment

* Use both dynamic and bridge authority bridges for old telegram
  accounts
* Add tests to telegram distributor

Circumvention Settings API and Telegram distributors

* Add Circumvention settings API
* Add Telegram distributor
* Fix the use of the distibution request for bridges

First rdsys version

* Full support for bridges in the backend
* Using BridgeDB as distributor