Documenting startTor behaviour #45

Closed
opened 2023-06-22 15:13:09 +00:00 by decentral1se · 2 comments

While firing up Tor, I wasn't sure what connectivity was actually doing under the hood until I took a a look at startTor (9beff8a10a/tor/torProvider.go (L484)). Would it be an idea to document the logic of looking at a system Tor / then bundling etc. somewhere?

Can take a run at it.

EDIT: Also, for alternative clients/tools, can connectivity provide bundling or that is something that clients have to organise separately? Unsure how to do that.

While firing up Tor, I wasn't sure what `connectivity` was actually doing under the hood until I took a a look at `startTor` (https://git.openprivacy.ca/openprivacy/connectivity/src/commit/9beff8a10a89d1256bcbb6624c9cf97f4889fdb0/tor/torProvider.go#L484). Would it be an idea to document the logic of looking at a system Tor / then bundling etc. somewhere? Can take a run at it. EDIT: Also, for alternative clients/tools, can `connectivity` provide bundling or that is something that clients have to organise separately? Unsure how to do that.
Owner

Would it be an idea to document the logic of looking at a system Tor / then bundling etc. somewhere?

Yeah this should definitely be part of the developer docs. I've created cwtch.im/docs.cwtch.im#9 to track.

can connectivity provide bundling

That is something that tools have to handle. Though we do have some infrastructure for that, see: https://git.openprivacy.ca/cwtch.im/cwtch-ui/src/branch/trunk/fetch-tor.sh

> Would it be an idea to document the logic of looking at a system Tor / then bundling etc. somewhere? Yeah this should definitely be part of the developer docs. I've created https://git.openprivacy.ca/cwtch.im/docs.cwtch.im/issues/9 to track. > can connectivity provide bundling That is something that tools have to handle. Though we do have some infrastructure for that, see: https://git.openprivacy.ca/cwtch.im/cwtch-ui/src/branch/trunk/fetch-tor.sh
Author

Thanks @sarah! Seems like #45 (comment) covers it.

Thanks @sarah! Seems like https://git.openprivacy.ca/openprivacy/connectivity/issues/45#issuecomment-17548 covers it.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: openprivacy/connectivity#45
No description provided.