pull down to refresh
The comment on bitcointalk re: the onion link is kind-of valid. This is what it looks like for me, when I'm not running in anal-security-mode:
which is a good-(ish) fail because it would need exit nodes otherwise, and that would be bad:
@k00b - #813 on the repo sets out a requirement for AWS copilot - but that issue is over a year old. Is that still the requirement?
It's not a requirement. To get proper onion support we need parallel infrastructure for auth. This is just a CORs issue by the looks of it. I can fix it with some config changes.
I think the CORS is good - we shouldn't want to use mixed hidden/exit-noded domains on an onion
I agree. Going to need parallel infra then unless the proper hack eluded me when I was working on it a year ago.
The comment on bitcointalk re: the onion link is kind-of valid. This is what it looks like for me, when I'm not running in anal-security-mode:
which is a good-(ish) fail because it would need exit nodes otherwise, and that would be bad:
@k00b - #813 on the repo sets out a requirement for AWS copilot - but that issue is over a year old. Is that still the requirement?