I knew Tor Project has been shifting away from "hidden services" for a while but I missed the email where teor clarified things for blog posts and such in late April [0]. Also, I wanted to avoid using "onion resolver" as it would be a worse misnomer than "hidden resolver."
Re. OnionBalance: we're working on a few ideas for this, but nothing conclusive yet.
> I knew Tor Project has been shifting away from "hidden services" for a while
I read the article after your correction, and on reading the `What are Tor onion services?` section, I thought “How nice, they’re using the new terminology to go with the new v3 service address”.
This is a v3 onion service, it should be easier to find prefixes, plus CF (and other companies like FB) have done pretty long prefixes via brute force (they have a lot of computers)
For OnionBalance, on the mailing list they mentioned that while it is more difficult on v3, they are implementing HSFETCH/HSPOST[0]. I'm not sure of any other load balancing approaches outside of this. In the meantime I figure y'all have this all going through one hidden service endpoint or maybe share some priv keys or wrote some custom code or something.
I knew Tor Project has been shifting away from "hidden services" for a while but I missed the email where teor clarified things for blog posts and such in late April [0]. Also, I wanted to avoid using "onion resolver" as it would be a worse misnomer than "hidden resolver."
Re. OnionBalance: we're working on a few ideas for this, but nothing conclusive yet.
0. https://lists.torproject.org/pipermail/tor-dev/2018-April/01...