Now we are talking...

That address’s structure suggests a deliberate obfuscation of routing tables – an interesting choice given I2P's core design principles.

Does it work? I tested I2P embed on Amethyst a couple months ago, but it was so slow (1-2 mins boot up to the first good reply then then very slow connections later) that I gave up.

@Silberengel does this one fix the i2p latency @Vitor Pamplona ran into on amethyst, or is that latency still the price of the anonymity?

It takes a while for the i2P route to build up, and then it works normally. So, there's about a 2-minute lag, when starting. But it's a mobile app, so just leave it running, once it's open.

Yakihonne doesn't seem to load that event

@Silberengel does the i2p route hold once its built if the app gets backgrounded, or does it rebuild every time?

Then Yakihonne needs to get with the program and fully implement kind 1111.

I was about to start ranting, we need some backup network other than tor, because I have a feeling, nostr relays and tor may be hit at the same time in the future

Also a "split-mode" client could be a nice idea, where you can run one part on you own server at home (or any hardware) and other, very light part on a mobile phone (maybe just a front website connected via p2p nat punching or even a p2p swarm?) Nostr clients have aloooot to do in the background, so such private connector could make mobile client more efficient, lighter and faster

Well, in the current geopolitical situation it's time to start using it. Run an empty client to just help the network and mask your other connections, because why not. I will also start advising to use a more obfuscated traffic in about 2 years

Android-native relays can support both, over Invinzible and/or Orbot, and wss://relay.sovbit.host has Tor and I2P support.