Hi lainons, I have set an unofficial i2p proxy of lainchan.org. It is available at http://7rov2od4lmtfswthoy7tziiuixupugkrexpdvyso5yj5pgicxvga.b32.i2p/. More information can be found in the webpage.
It looks like i2p users are always the minority and i2p access is never going to be supported. I hope it can be a long-term contribution to the community. I have faithfully set this reverse proxy up.
I think this is more relevant to /sec/ but maybe this post is more suitable for /q/. If it is, sorry for posting it at wrong board, free to mod.
FAQ:
Q: It's slow, like kicking dead whales down the beach!
This is normal for i2p, also, see "trust".
Q: TL;DR, how can I access LAINCHAN using this mirror?
(included in the webpage, make sure it is http not https, see #trust section)
Q: Why did you set it up?
My motivation of setting up this mirror, is promoting the use of i2p network and providing a convenient way to access LAINCHAN, since i2p users are always the minority, I think this would help a little.
I also want to try running an eepsite with some traffic to see how it goes. More improvements to this mirror may be added in the future.
Q: Are you an admin of LAINCHAN? Who are you?
No, I'm a lainon who loves Lain. This is definitely not an official mirror. My contact information and some improvements will be added during the weekends, I don't really have more time working on this right now. Just see the quality of this webpage!
Q: How can I trust you?
Currently, this mirror is only provided through HTTPS. The HTTPS traffic is forwarded directly to lainchan.org:443 in an unalternated way, it means the HTTPS mirror is just a proxy, the same certificate is presented, you can, and should check the certificate yourself.
I don't MITM the traffic. My mirror is not able to decrypt or modify the traffic. The system does not have logs, not even a running syslog daemon. The system has reasonable security measures, cannot be pwned in seconds. DoS attacks are not mitigated anyway (see abuses).
The downside is I can't rewrite any URLs in lainchan.org, such as http://lainon.life, you still get a chance of being directed to clearnet outproxy, which is less stable and potentially less secure. Consider blocking clearnet traffic in your broswer. I can't prevent abuses neither.
Caching and merging HTTP requests are also not possible and it makes the mirror even slower, because of the huge overhead.
Let the HTTPS mirror runs for a while and see how it is going. If really needed, a MITMed HTTP version of the mirror can be added.
Q: What about abuses?
For Lain's sake, please don't abuse this mirror. Again, let's see how it is going. If there are many abuses, I request Appleman to list the IP address of this proxy to lainchan.org as read-only.