Hello, I never used Onioncat before
Well to know about it, go download compile and run it, or get it from your OS ports/packages, try it out, play with it, see how it works. It's fun and very useful for running applications across onionland... and there's a lot more apps uses and protocols and services in the world to discover and create than just boring UniDirectional Https Webservers :) https://www.onioncat.org/ What's not fun, is that as you can see from the original message, the Tor Project censors and bans all talk of this from their talk and relay lists... they are hypocrites, and are hiding things from their users, operators, and funders. They censor all sorts of messages for no good reason for many years now. This is very bad. For an org that claims to support Free Speech, this is a very big suspicious incriminating problem.
but on the website it says it is compatible with v3... can you explain me what is not compatible with v3?
v2 uses 80-bit addressing, this fits perfectly 1:1 inside IPv6 128-bit addressing RFC 48 + tor 80 = IPv6 128 v3 is far wider than v2's 80-bit, and just like i2p it cannot be represented inside IPv6's 128-bits, thus 1:1 breaks, and a lot of things get messy and apps start having limitations. OnionCat website says it's v3 compatible because you can physically by hand hardcode bidirectional IPv6 <--> v3 mappings into onioncat config. But that method obviously does not scale to P2P sized applications which can grow to many thousands of users needing to communicate at random on the fly. Among other technical problems. Bittorrent and other IPv6 enabled apps work as they should with zero user config needed in v2+onioncat onionland today, but not with v3+onioncat. Boring webservers, yes they work under v3+onioncat but not more exotic apps that need P2P / BiDir / IPv6 / UDP support. You will have to try onioncat with v2 and v3, and - compare how ping6 works in the different direction modes - compare how transmission-bt + opentracker works to begin to understand why Tor Project censoring v2 is a major problem both today, and totally forecloses on an entire class of potential future apps tomorrow. There is no legitimate reason for Tor Project Inc to shutdown the v2 onion network. And the "security risk" TPI likes to throw out, well that is obviously 100% entirely up to decision of each user and app userbase to make for themselves to consider trading that off against their app use case need, absolutely not for Tor Project Inc and its authoritarians to dictate to the user. There are even more big problems with tor, and Tor Project Inc censors those too, but you can search for them... "Tor Stinks -- NSA"