-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is TorChat dead? #88
Comments
no |
Main hasn't been touched for 8 years... Things are breaking... Been that way for several years... Remains untouched. That kinda suggests to me it's abandoned/dead... Running into a problem on modern distros... Arch, for example. Since the invention of HSv3, Arch's Tor package defaults to HSv3. See what happens when TorChat tries to run in that environment, with the assumption that HSv2 is being returned, but it's getting an HSv3. It's unpretty... A quick fix would be updating TorChat to specify that it needs HSv2... The need for this didn't exist 8 years ago. Of course, long term, support for HSv3 would be preferred... Perhaps both are trivial. I can't say. I'm bad at this. |
Unless this gets updated to V3 this is very our of date and for your own safety don't use it, soon v2 traffic wont even work so this tool will no longer work. |
Yep. I know. |
...looks pretty darned dead...
The text was updated successfully, but these errors were encountered: