aboutsummaryrefslogtreecommitdiff
path: root/src/rps/rps.conf.in
Commit message (Collapse)AuthorAge
* RPS: Return peers to client after many observed idsJulius Bünger2019-04-04
|
* Use new terminology in configJulius Bünger2018-09-27
|
* Start rps in any caseJulius Bünger2018-09-26
| | | | | | | | | | | | | | Starting rps makes sense as - it is still experimental. It will only run for the persons having configured with --enable-experimental and be quite useful for developement. - starting rps on-demand does not make sense in production as the service can already participate in the gossip meaning that it is already represented at other peers and already gathers information about other peers. The earlier it starts participating in the gossip, the more secure the gossiping will be for all participants. - it only consumes few resources (at least it should).
* AUTOSTART renamed into START_ON_DEMAND (#4547a)psyc://loupsycedyglgamf.onion/~lynX1984-04-04
|
* rps service: rename option in configJulius Bünger2018-06-06
|
* add PORT to NAT configuration, generate nat.conf from nat.conf.in, implement ↵Christian Grothoff2016-12-16
| | | | more of new NAT service
* -rps _peers: add disable option to peer storageJulius Bünger2016-07-01
|
* add missing options to rps.conf.inJulius Bünger2016-05-15
|
* -fix rps configChristian Grothoff2014-12-08
|
* Import RPSBart Polot2014-12-05