{"action":"created","issue":{"url":"https://api.github.com/repos/meejah/txtorcon/issues/181","repository_url":"https://api.github.com/repos/meejah/txtorcon","labels_url":"https://api.github.com/repos/meejah/txtorcon/issues/181/labels{/name}","comments_url":"https://api.github.com/repos/meejah/txtorcon/issues/181/comments","events_url":"https://api.github.com/repos/meejah/txtorcon/issues/181/events","html_url":"https://github.com/meejah/txtorcon/issues/181","id":173776776,"number":181,"title":"Tor client endpoint should be able to use UNIX domain sockets for it's SOCKS connection","user":{"login":"david415","id":50611,"avatar_url":"https://avatars.githubusercontent.com/u/50611?v=3","gravatar_id":"","url":"https://api.github.com/users/david415","html_url":"https://github.com/david415","followers_url":"https://api.github.com/users/david415/followers","following_url":"https://api.github.com/users/david415/following{/other_user}","gists_url":"https://api.github.com/users/david415/gists{/gist_id}","starred_url":"https://api.github.com/users/david415/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/david415/subscriptions","organizations_url":"https://api.github.com/users/david415/orgs","repos_url":"https://api.github.com/users/david415/repos","events_url":"https://api.github.com/users/david415/events{/privacy}","received_events_url":"https://api.github.com/users/david415/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/meejah/txtorcon/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-29T13:39:28Z","updated_at":"2016-08-29T22:06:42Z","closed_at":null,"body":"\r\nIdeally the tor client endpoint should be able to connect to a UNIX domain socket if that's tor's SOCKS port. I'm actually not so concerned about how the endpoint parser will deal with this... because for the tahoe tor integration use case we really do not need to use the endpoint parser; we just need an api that works."},"comment":{"url":"https://api.github.com/repos/meejah/txtorcon/issues/comments/243272557","html_url":"https://github.com/meejah/txtorcon/issues/181#issuecomment-243272557","issue_url":"https://api.github.com/repos/meejah/txtorcon/issues/181","id":243272557,"user":{"login":"warner","id":27146,"avatar_url":"https://avatars.githubusercontent.com/u/27146?v=3","gravatar_id":"","url":"https://api.github.com/users/warner","html_url":"https://github.com/warner","followers_url":"https://api.github.com/users/warner/followers","following_url":"https://api.github.com/users/warner/following{/other_user}","gists_url":"https://api.github.com/users/warner/gists{/gist_id}","starred_url":"https://api.github.com/users/warner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/warner/subscriptions","organizations_url":"https://api.github.com/users/warner/orgs","repos_url":"https://api.github.com/users/warner/repos","events_url":"https://api.github.com/users/warner/events{/privacy}","received_events_url":"https://api.github.com/users/warner/received_events","type":"User","site_admin":false},"created_at":"2016-08-29T22:06:42Z","updated_at":"2016-08-29T22:06:42Z","body":"[Foolscap#265](https://foolscap.lothar.com/trac/ticket/265) is where we need this. It looked like there might be a way to hack this into `txtorcon.TorClientEndpoint` (by abusing the private `_proxy_endpoint_generator=`), but I don't want to do something so obviously fragile as that.\r\n\r\nMaybe a `TorClientEndpoint` constructor that just takes an endpoint for the SOCKS port as an argument? I don't remember how reusable endpoints are.. if for some reason it's not legal to call `.connect()` multiple times, then we could pass in a no-argument function that returns endpoints on demand..\r\n"}}
{"actor":{"display_login":"warner"}}