Re: Tor Browser 14.5.2 (2025-05-18)

On Tue, 20 May 2025 18:50:04 +0200, Carlos E. R. wrote :

But you make us waste a few seconds by paging down to see what you had
to say. That is not polite to us.

Hi Carlos,

What's interesting is I think something like 95% of people posting to
Usenet invest about 10 to 20 seconds of effort adding value to their post.

The next 3% are like Joerg & Alan Baker who invest even less than that.
Joerg's average is about 3 to 4 seconds, per post, by my calculations.

What's mathematically interesting is Joerg provides, in those three
seconds, everything he will ever know about the topic he's posting on.

Back on topic, this is the original thread as far as I can tell.
 <https://www.novabbs.com/computers/article-flat.php?id=59037&group=comp.mobile.android#59037>

What's possibly relevant isn't TOR blog article 1452 but 1302 (Android).
 <https://blog.torproject.org/new-release-tor-browser-1302/>
 "This release is identical to our 13.0.1 release, but fixes an issue
  with the Android apk version-code which collided with our 13.0 releases.
  This colliding version code prevented us from publishing to Google Play,
  so we have built 13.0.2 with an empty commit in order to generate a
  new non-colliding version code."

Apparently the OP (not Joerg, but "D") was trying to inform us:

The Problem:
The Tor Project released Tor Browser 13.0.1 for Android.
However, the "version code" (a numerical identifier used by Google Play
to distinguish different app versions) for this release happened
to be the same as a previous 13.0.x release.

The Consequence:
This "colliding version code" prevented the Tor Project from
publishing Tor Browser 13.0.1 to Google Play. Google Play requires
each new app update to have a unique and incrementing version code.

The Solution:
To fix this, the Tor Project released Tor Browser 13.0.2.
This new version is functionally identical to 13.0.1.
The only change they made was an "empty commit"
(a technical term for a commit in version control that doesn't
actually change any code) to generate a new, unique version code.

The Result:
This allowed them to successfully publish the app to Google Play.

Only about 2% of the posters to Usenet actually add any value.