ricochet
ricochet copied to clipboard
ricochet-im
Ricochet stops working in October 2021
onion v2 addresses are deprecated and will stop working by the end of September. (See publication here).
This means that ricochet (which uses the old v2 addresses) will stop working at that point.
The title of this repository literally says "NOT FOR PRODUCTION USE" and the first paragraph says that it's currently not using v3 either and that this is still a work in progress, so sounds like migrating at this point is not worth it yet.
Hi, ricochet-refresh dev/maintainer here. As usual documentation lags behind code. Ricochet-Refresh does use v3 and has since last summer/fall (see commit: https://github.com/blueprint-freespeech/ricochet-refresh/commit/55d29d7dec664099d9a00227b94bcd88f07a2f1f )
Our latest release (3.0.10) can be found here: https://github.com/blueprint-freespeech/ricochet-refresh/releases
There is no migration path between Ricochet-IM and Ricochet-Refresh, as there is no way to migrate v2 onion services to v3 onion services, so you'll need to manually go and re-add all your contacts.
I've filed https://github.com/blueprint-freespeech/ricochet-refresh/issues/105 to track updating the README.
Any way it v3 support can be backported to ricochet and to Debian, please?
@angry17e0 please read the thread. "Ricochet" is dead. "Ricochet Refresh" is the new one: https://github.com/blueprint-freespeech/ricochet-refresh/releases
Any way it v3 support can be backported to ricochet and to Debian, please?
Probably not backported, but you can likely generate a v3 address using another tor instance and then copy the keys over.
@angry17e0 please read the thread. "Ricochet" is dead. "Ricochet Refresh" is the new one: https://github.com/blueprint-freespeech/ricochet-refresh/releases
making this repo more obviously dead (ie. changing the readme or description and archving it) might help with this...
@cypherbits
Time to migrate to https://www.ricochetrefresh.net/
Ricochet is dead but Ricochet Refresh is not an option for me as it uses Code of Conduct and I do not want to have anything in common with such idiocy and lunacy.
@smaragdus every project and organization has a code of conduct like that. And it's for the developers and contributors, not users... I don't see the "oh my god" you see in that code of conduct, can you please enlighten me?
Why all say Ricochet is dead ? Only one thing what do you need is -> Download the newest tor browser , copy the tor.exe to the ricochet folder and all works fine.
Why all say Ricochet is dead ? Only one thing what do you need is -> Download the newest tor browser, copy the tor.exe to the ricochet folder and all works fine.
This is incredibly not the case and if it somehow works for you you're way off into undefined behaviour land. You will likely be able to bootstrap but unable to connect to or verify connecting clients.
The cryptographic handshake used to verify that a connecting client owns the private keys of the onion service they say they do is tightly coupled with the type of key used (ed25519 for v3 onion services, i forget what for v2). As mentioned above, Ricochet-Refresh is the current semi-actively maintained fork, and Gosling is where active backend/protocol development is happening for an eventual Ricochet-Refresh version 4 with improved privacy guarantees.
Feel free to @ me on issues over there if you're interested in getting involved.