Then you can register a “domain” on reg.i2p with something like yourname.i2p as well.

Yes, I believe that the Syncthing protocol doesn’t bring security concerns, but some people may wish to hide their IP and device info from being “exposed”. I know Syncthing has some data collection which you can opt out of.

I think a benefit of this post is to show that you can self-host applications and use the I2P network to connect to your services while bypassing issues like CGNAT. Hopefully, it helps spark ideas to host more services on I2P as well.

CPU: remove AVX code, switch to __builtin for AES detection #1959

https://github.com/PurpleI2P/i2pd/pull/1959

Piped Link: https://piped.kavin.rocks/watch?v=VHmJP19gHAo

Invidious Link: https://yewtu.be/watch?v=VHmJP19gHAo

Love to see it. Can always use more I2P.

notbob.i2p and identiguy.i2p have been my go to as they provide uptime stats and show the reliability of that eepsite. Seems like many people set up a registered eepsite just for testing or the short-term and don’t intend for longevity, but you can find some eepsites with normal names like “git.idk.i2p” and assume it will have better uptime.

Eepsites that provide similar “stats” can be found here: http://notbob.i2p/cgi-bin/defcon.cgi?category=stats

“Alive” hosts can be found here: http://reg.i2p/alive