Hi! Below is my March’24 report!
In March, I resolved 571 tickets:
On Telegram (@TorProjectSupportBot) - 405
On RT (frontdesk@tpo) - 154
On WhatsApp (+447421000612) - 11
and on Signal (+17787431312) - 1.
My main focus remains the same - I help Russian-speaking users use Tor
Browser and circumvent internet censorship; I also test and report bugs
that users find and share with me.
There were presidential elections in March in Russia, so to prepare for
the event, I reviewed and improved existing user support templates we
use on Frondesk, Telegram, WhatsApp, Signal, and the guide in Russian in
the Torforum.
Also, at the beginning of March, I helped to find an issuewith
Snowflakefront domains[1] and prepared a workaroundtemplatein Russianto
help users fix the problem manually before the problem was solved in
aTor Browseremergency release [2].
I reportedthe issue of Tor Browser for macOS not working after being
downloaded from our telegram bot (https://t.me/
<https://t.me/gettor_bot>gettor_bot <https://t.me/gettor_bot>) by
gathering users' feedback and testing myself [3].
[1] https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/135
[2] https://blog.torproject.org/new-release-tor-browser-13011/
[3]
https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4…
Hi all :)
This is my monthly status report for March 2024 with the main relevant
activities I have done during the period.
## 0. Research
* Tor Browser Quality Assurance for Onion Services (TB .onion QA) - 2024.Q1:
* In the 2024.Q1 period, the TB .onion QA had the following output:
* 9 Tor Browser versions were formally tested.
* No serious issues were found affecting onionsites.
* A few minor issues were identified and need further investigation or be
reported to the browser team.
* Versions tested ranged from 13.09 to 13.0.13 and from 13.5a3 to 13.5a6.
* Did some internal Onion Planning.
## 1. Development
* The Onion Services Ecosystem documentation is now available at
the Community Portal: https://community.torproject.org/onion-services/ecosystem
An alternative URL is still available at
https://tpo.pages.torproject.net/onion-services/ecosystem
Details at https://gitlab.torproject.org/tpo/onion-services/ecosystem/-/issues/1
* Onionspray.
* Released the 1.6.1 version:
* https://lists.torproject.org/pipermail/tor-announce/2024-March/000313.html
* https://forum.torproject.org/t/onionspray-release-1-6-1/12083
* Onionspray Log Parser:
* Renamed eotk-log-parser to onionspray-log-parser:
https://gitlab.torproject.org/tpo/onion-services/onionspray-log-parser/-/is…
* Added support for aggregating page hits with the same circuit ID.
* Launched version 1.0.0 (nothing special with this number, it just means that
there was a backward-incompatible change from previous versions).
## 2. Support
* Ongoing sponsored work with deployment, maintenance and monitoring of Onion
Services.
* Did some other support related to setting up Onion Services.
## 3. Organization
Time spent (from the total available for Tor-related work):
| Category | Percentage
|---------------|------------
| Research | 21
| Development | 2
| Support | 54
| Organization | 23
|---------------|------------
| Total | 100
--
Silvio Rhatto
pronouns he/him
Hi everyone, here is my status report for March 2024.
This month, I continued the rebase on the Firefox Rapid Release channel.
I've arrived on par with mozilla-beta, i.e., I have a branch based on
Firefox 125b, and I'm following that channel. I'm trying to rebase my
branch onto each beta tag.
I've also fixed the various build and runtime errors, and the branch can
be built and used (even though this is seriously discouraged as it
hasn't been reviewed and we haven't done our audit work yet).
However, this is quite reassuring because it reduces the uncertainty of
our ESR transition work.
I've opened an issue [0] to document this process and all the conflicts
I had to merge manually, both trivial and non-trivial.
At a certain point, while working on this task, I implemented a script
that act as a helper for our usual rebase review procedures [1].
I'm sure it has a lot of margin for improvement, but it should handle
our most common cases.
My idea is to use it also for the script to perform continuous automatic
rebases of our branches. I wrote a proof of concept in 30 minutes, but
nothing was ready for production and/or publication. Still, I'm very
excited by the possibilities of automation we could implement.
Apart from that, I worked on refactoring our TorConnect module [2]. I
started it to fix an issue detected by the linter we've had for one year
and a half [3]. It was not trivial to fix, and eventually, I ended up
reorganizing the whole file, even though the contents haven't changed much.
At the end of the month, I also opened another merge request
specifically for error handling [4].
Together, they should hopefully help the further Android developments
other apps team members are working on.
Finally, I worked on some issues about fingerprinting vectors and helped
with our March releases.
Best,
Pier
[0]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42441
[1]
https://gitlab.torproject.org/pierov/lazy-scripts/-/blob/main/diff-of-diffs…
[2]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests…
[3]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41114
[4]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests…