vineflower VS ricochet

this is kind of a silly point, but the quilt community is just nicer to be around than any of the other ones in my experience, which has real effects: e.g., you attract people really really good at decompiler tech and create quiltflower which is a decompiler so good Java professionals use it. inclusivity matters! the cutting edge happens on quilt

The only way is to reverse-engineer it. Use something like quiltflower or javap if you want to be extra sure, and have a look through the Java code

Firstly, we have to decompile the JAR, turning the bytecode back into Java. This is a very difficult job: a lot of work has been put into the tools to make this happen.

Alternatively, there's this new project that I haven't tried yet: https://github.com/QuiltMC/quiltflower

The decompiler they used to view that code is not very good, that output is garbled.

If you're going to take apart JVM bytecode, you're better off using Recafe or Quiltflower.

https://github.com/Col-E/Recaf

https://github.com/QuiltMC/quiltflower

They are community contributed (through using decompilers to see what the classes do) and decompiler toolchains have ways of instrumenting classes with javadoc. They are also incomplete, you really can't write a mod using only a javadocs page

runs nice with jbang https://github.com/QuiltMC/quiltflower/releases/download/1.8.1/quiltflower-1.8.1.jar

This looks like a much more polished alternative to Ricochet: https://github.com/ricochet-im/ricochet

Ricochet seems dead. It's been five years since its last commit to their git repo, and their website's certificate expired last year. This is probably why you can't find much information.

I think something like Ricochet (if it were still actively maintained) could be a good solution.

https://github.com/ricochet-im/ricochet

Every user is their own Tor onion service, so you get E2E encryption and no centralized servers. The whole thing hinges on the security of Tor itself which is probably a safe enough bet.

With that being said, if I had just one piece of advice - try to avoid ostentatious phrases like Speek is by far the most secure way to converse or 100% anonymous. Tor itself is not 100% anonymous, so that should immediately make anyone cautious. One of the things that I admired about the original Ricochet was that the developers never made brazen claims about their software. In fact, quite the opposite.

Check out https://github.com/ricochet-im/ricochet/blob/master/doc/prot.... It is metadata-free. It does not require a centralized server. It uses Tor.

[1] https://cwtch.im/ [2] https://ricochet.im/

Abandoned, unmaintained, deprecated or unreleased: Ricochet, TOR Messenger, Cwtch

ricochet.im website not working (??)

> there isn't a currently easily available obvious way to have private secure conversations.

Ricochet[1] works really well. It uses Tor hidden services to communicate. Your Ricochet ID is your onion address. To add a contact, you input their Ricochet ID and a short message, and Ricochet connects to their onion address and sends a contact request. If the contact request is accepted then you'll each show up as a contact on each other's client and can chat whenever you want.

Tor is really perfect for this, you can't get more private or censorship-resistant than Tor.

The UI is currently not great, but that's not a protocol problem.

The biggest problem with Ricochet is that hardly anyone is using it.

[1] https://ricochet.im/