Thanks @nolim1t. Unless this change is backported to 0.21.1, by the time 22.0 (the next release) is out tor v2 will be EOL, so maybe the existing release notes are enough. It may be good to squash your commits down to one when you are finished.

Thanks @nolim1t. Unless this change is backported to 0.21.1, by the time 22.0 (the next release) is out tor v2 will be EOL, so maybe the existing release notes are enough. It may be good to squash your commits down to one when you are finished.

Squashed into one. Yep I recognize that it may be deprecated too, hence not recommended mention

We're on the trailing edge of TorV2 support here, and this is a really hacky workaround. I too think that the mention in the release notes is enough. No strong objection though.

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

Reviewers, this pull request conflicts with the following ones:

• doc: tor.md and -onlynet help updates #20757 (doc: tor.md and -onlynet help updates by jonatack)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

🐙 This pull request conflicts with the target branch and needs rebase.

_{Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".}

I'm going to close this, sorry. Everyone is at most ~0 on this, which makes it unlikely that this will be merged. It doesn't seem worth the hassle to rebase .