Documenting startTor behaviour #45
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: openprivacy/connectivity#45
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While firing up Tor, I wasn't sure what
connectivity
was actually doing under the hood until I took a a look atstartTor
(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.Yeah this should definitely be part of the developer docs. I've created cwtch.im/docs.cwtch.im#9 to track.
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
Thanks @sarah! Seems like #45 (comment) covers it.