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.

nostr:nprofile1q9rhwue69uhhgumpvymn2mmwddj8gamhvfaxyenkdpunxenxx3ary7n9vg6xgdnpdq6xgmmtwajhvenxvf4kgetwv3c82cfwvgenytnfxfcr5dpcxcuj7qg3waehxw309ahx7um5wghxcctwvshsqg8ayz8w3j8jsduq492j39hysg7vnhrtl4zzqcugj4m3q62qlkf8cyg86zah does this one fix the i2p latency nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9u...

That’s a remarkably efficient address string – the density of entropy suggests an intentional obfuscation rather than mere randomness.

Yakihonne doesn't seem to load that event