--------------------------IronVest---------------------------
Preview: Send anti-censorship-team mailing list submissions to anti-ce -->
SPAM? CLICK to BLOCK:
https://ironvest.com/app/0/#emails/r8196gs9ev5p@opayq.com/toggle

This email is Masked using Ironvest - it was sent from duck.com to
r8196gs9ev5p@opayq.com (your reply stays Masked). To protect your privacy, do
not forward this message, or add new recipients like CCs or BCCs.

Thanks for being an IronVest customer!
--------------------------IronVest---------------------------

Send anti-censorship-team mailing list submissions to
	anti-censorship-team@lists.torproject.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.torproject.org/cgi-bin/mailman/listinfo/anti-censorship-team

or, via email, send a message with subject or body 'help' to
	anti-censorship-team-request@lists.torproject.org

You can reach the person managing the list at
	anti-censorship-team-owner@lists.torproject.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of anti-censorship-team digest..."


Today's Topics:

   1. onbasca and rdsys (meskio)


----------------------------------------------------------------------

Message: 1
Date: Fri, 24 Feb 2023 12:47:19 +0100
From: meskio <meskio@torproject.org>
To: anti-censorship-team <anti-censorship-team@lists.torproject.org>
Subject: [anti-censorship-team] onbasca and rdsys
Message-ID: <167723923930.1535.1605523355422205109@localhost>
Content-Type: text/plain; charset="utf-8"

Hello,

Onbasca[0], a relay bandwidth, has just added support for testing bridges. I 
have modified rdsys to use it[1]. onbasca produces a bandwidth ratio, on how 
fast is a bridge compared to the rest of bridges (1 is the median), and rdsys 
decides if distribute a bridge if the ratio is higher than a configured 
threshold (right now 0.75) or if is jet untested. rdsys does ignore the onbasca

results if there is less then 50% of bridges with high enough ratio to be 
distributed.

As this was needed by a sponsor I have already deployed it in production. I 
wrote a survival guide:
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Onbasca-Survival-Guide

I tested it and I don't expect much problems, but as I will be AFK next week if

rdsys gives any problem is easy to roll back to the previous version of rdsys 
without onbasca support. I left the previous binary of rdsys backend in 
~/bin/rdsys-backend.old, so rolling back will be running as rdsys user in 
polyanthum:
  systemctl --user stop rdsys-backend
  mv ~/bin/rdsys-backend.old ~/bin/rdsys-backend
  systemdl --user start rdsys-backend


[0] https://gitlab.torproject.org/tpo/network-health/onbasca/
[1]
https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/merge_requests/76

-- 
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL:
<http://lists.torproject.org/pipermail/anti-censorship-team/attachments/20230224/bd2a542c/attachment-0001.sig>

------------------------------

Subject: Digest Footer

_______________________________________________
anti-censorship-team mailing list
anti-censorship-team@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/anti-censorship-team


------------------------------

End of anti-censorship-team Digest, Vol 43, Issue 1
***************************************************