my unofficial static arm build for i2pd 2.18.0 is up here.
make sure to check the signature or verify the hash
b2sum:
8f5fb682725273685370a0c839b75413914974f9e3030d112f44dfb1490fe1fcd623b911ede7148595d3d4a9de28309290b8623b1197489d71fdc75b17dca439 i2pd
sha256sum:
535197a7e06af4a6fc56bc1c6944c2571116c4575927fc060bc86e7213098326 i2pd
i2pd (I2P Daemon) is a full-featured C++ implementation of I2P client.
I2P (Invisible Internet Protocol) is a universal anonymous network layer. All communications over I2P are anonymous and end-to-end encrypted, participants don't reveal their real IP addresses.
I2P client is a software used for building and using anonymous I2P networks. Such networks are commonly used for anonymous peer-to-peer applications (filesharing, cryptocurrencies) and anonymous client-server applications (websites, instant messengers, chat-servers).
I2P allows people from all around the world to communicate and share information without restrictions.
i2pd is licensed under the 3-clause BSD license, binary packages are available for Debian, Ubuntu, OS X, FreeBSD, Android and Windows.
Changelog for i2pd version 2.18:
I have been writing an i2pd compatable bittorrent client called XD in golang. It has reached an almost end user ready state. 0.1.0 will be the first "official" release of it. Before that happens I need some beta testers.
If you want to help test it you can do the following
There are some bugfixes that are applicable to XD that are not in 2.17 yet.
If you don't know how to build from source the documentation is here
latest release here
right now XD uses the current working directory as the data directory so make a new directory and put the executable there.
On Unix systems you can do something like this:
$ mkdir ~/XD/
$ cd ~/XD/
$ cp /path/to/downloaded/XD .
then make a symlink for XD-cli
$ ln -s XD XD-cli
on windows you can copy XD.exe …
Rejoice, nntpchan 0.6.0 has been tagged.
This release contains lots of inane bug fixes.
Download on github here and join us on IRC to peer into the main network.
2hu-ch.org nntpchan is offline until it's not.
We're on the following networks:
rizon: irc.rizon.net #nntpchan
freenode: irc.freenode.org #nntpchan
My NNTPChan nodes will be offline for a bit while I quit the internet for a bit.
Estimated date of return TBD.
Email me if you need to contact me otherwise I'll be offline.
i2pd (I2P Daemon) is a full-featured C++ implementation of I2P client.
I2P (Invisible Internet Protocol) is a universal anonymous network layer. All communications over I2P are anonymous and end-to-end encrypted, participants don't reveal their real IP addresses.
I2P client is a software used for building and using anonymous I2P networks. Such networks are commonly used for anonymous peer-to-peer applications (filesharing, cryptocurrencies) and anonymous client-server applications (websites, instant messengers, chat-servers).
I2P allows people from all around the world to communicate and share information without restrictions.
i2pd is licensed under the 3-clause BSD license, binary packages are available for Debian, Ubuntu, OS X, FreeBSD, Android and Windows.
Changelog for i2pd version 2.17:
This quick blog was requested by someone on IRC and it details how to set up an outproxy on i2p.
If this is too quick a guide or you feel like you don't know what you're doing then I'd suggest against running an outproxy.
Software used:
debian stable
i2pd
tinyproxy
The setup process goes as follows:
install i2pd and tinyproxy
edit tinyproxy.conf to have sane defaults
have tinyproxy deny access to loopback
create an i2p server tunnel pointing to 127.0.0.1:8888
publish destination of outproxy
/etc/tinyproxy/tinyproxy.conf
User tinyproxy
Group tinyproxy
Port 8888
Listen 127.0.0.1
Timeout 600
DefaultErrorFile "/usr/share/tinyproxy/default.html"
MaxClients 100
LogLevel Warning
PidFile "/run/tinyproxy/tinyproxy.pid"
MinSpareServers 5
MaxSpareServers 20
StartServers 10
MaxRequestsPerChild 0
Allow 127.0.0.1/8
ViaProxyName "tinyproxy"
Filter "/etc/tinyproxy/filter"
FilterExtended On
ConnectPort 443
/etc/tinyproxy/filters
^127\.
^10 …In which I show you how to use Syncthing over I2P for secure, self-hosted, file synchronization.
Syncthing is an open source, self-hosted file synchronization tool. Instead of trusting a third party (e.g. Dropbox) to host your files, and synchronize files between your machines, you can use an open source alternative.
By default, syncthing is not truly decentralized, and relies on third party relay servers and discovery servers. While I am sure the syncthing protocol is safe enough, and the people hosting these services have good intentions, wouldn't it be nice if we don't have to trust either?
I2P is a decentralized, peer to peer, anonymous network layer. By relaying your computer traffic by a volunteer ran network spread around the world, following the path of traffic becomes nearly impossible.
I2P has the added benefit that you can bypass limitations on hosting imposed by …
I'd like to preface this going in as being clear that I like monero project and think they make a damn fine coin. Yes, they have a rather elitist community but such comes with the territory. I have interfaced with the kovri codebase in the past and I can say that the project left me rather disapointed. To really get a good grasp of the sitatuon I need to go back to 2014 (?).
In the begininning there was i2pcpp, a decent partially working i2p router written in C++ 11 for FreeBSD by a guy with the nym orion. Orion was originally funded by the monero community but discontinued i2pcpp after i2p's protocols left a sour taste in his mouth. My only role in i2pcpp was trying to compile it on Linux as at the time my C++ was pretty much non existent. Orion is …
After over a year I am proud to release nntpchan version 0.5.0.
The daemon has gone through a lot as well as the build system, we have many many new things added.
Many features were also gutted:
I think this covers everything, so much changed I probably forgot something or a few other things ...
Download on github here and join us on IRC to peer into the main network.
We're on the following networks:
rizon: irc.rizon.net #nntpchan
freenode: irc.freenode.org #nntpchan
irc2p: irc.dg.i2p #overchan