Alright so it's been a while, I figured I might as well say this:
I have a build of MuWire's 2nd last commit with the libs exposed. There is a "muwirelibs" folder where all the libraries are visible as .jar archives and by overwriting the following:
i2p-1.9.0.jar
mstreaming-1.9.0.jar
router-1.9.0.jar
streaming-1.9.0.jar
with the ones from I2P's "lib" folder(libraries must be renamed and appended "-1.9.0" to the name), it is possible to keep MuWire running on the latest version of I2P. In addition the "certificates" and "geoip" folders from I2P should also override the ones in the MuWire folder.
The package is portable and intended for Windows x64. It is also portable as it redirects the profile folder to an internal one, meaning it's possible to instantiate multiple nodes on the same user profile with minimal hassle by just putting multiple copies in different folders.
If anyone is interested, I am willing to put up a download for it.
It is mandatory at this point in the application's development that one or more trusted hosts are added to Contacts since the developer no longer hosts trackers. Automatic updates should also be disabled since not only has zlatin taken the private key with him but this build is run as a java application through runtime instead of being a standalone .exe(app is launched via a vbs script and JRE is included in the package, don't worry).
The big reason I've been hesitating bringing this up is because I am of course a nobody and very much trying to keep it that way, and both security and anonimity are at big risk by running random binaries somebody puts up online. When zlatin imploded, a fake version was already making quick rounds on torrents. I want to gauge the overall interest of people in this and hear opinions before I proceed.
I don't know how to make these packages myself. This was apparently compiled by git's pipeline and the artifacts are long gone. With a bit of public involvement it would at least be possible to create an automated script that builds these so people can automatically pull and make their own builds without having to rely on trusting me, and then just add the extra scripts that make it all work which are themselves small and easy to audit.
The application is quite very usable at this point and distribution and continued I2P node updates are all that's missing. Sure it won't get any meaningful development until someone adopts it but it would at least be staying up to date with I2P node versions.
I have a build of MuWire's 2nd last commit with the libs exposed. There is a "muwirelibs" folder where all the libraries are visible as .jar archives and by overwriting the following:
i2p-1.9.0.jar
mstreaming-1.9.0.jar
router-1.9.0.jar
streaming-1.9.0.jar
with the ones from I2P's "lib" folder(libraries must be renamed and appended "-1.9.0" to the name), it is possible to keep MuWire running on the latest version of I2P. In addition the "certificates" and "geoip" folders from I2P should also override the ones in the MuWire folder.
The package is portable and intended for Windows x64. It is also portable as it redirects the profile folder to an internal one, meaning it's possible to instantiate multiple nodes on the same user profile with minimal hassle by just putting multiple copies in different folders.
If anyone is interested, I am willing to put up a download for it.
It is mandatory at this point in the application's development that one or more trusted hosts are added to Contacts since the developer no longer hosts trackers. Automatic updates should also be disabled since not only has zlatin taken the private key with him but this build is run as a java application through runtime instead of being a standalone .exe(app is launched via a vbs script and JRE is included in the package, don't worry).
The big reason I've been hesitating bringing this up is because I am of course a nobody and very much trying to keep it that way, and both security and anonimity are at big risk by running random binaries somebody puts up online. When zlatin imploded, a fake version was already making quick rounds on torrents. I want to gauge the overall interest of people in this and hear opinions before I proceed.
I don't know how to make these packages myself. This was apparently compiled by git's pipeline and the artifacts are long gone. With a bit of public involvement it would at least be possible to create an automated script that builds these so people can automatically pull and make their own builds without having to rely on trusting me, and then just add the extra scripts that make it all work which are themselves small and easy to audit.
The application is quite very usable at this point and distribution and continued I2P node updates are all that's missing. Sure it won't get any meaningful development until someone adopts it but it would at least be staying up to date with I2P node versions.
Statistics: Posted by FreefallHeavens — 20 Dec 2023 14:29