Recent comments

z3d wrote

It's possible that you have 2 different installations of I2P, one installed via a .deb file / repo, and the other installed manually. Check for the presence of an ~/.i2p/ folder, that would indicate you've got a manual install running somewhere.

You might just find that a manual install suits you better, not least because all files related to your configuration live in ~/.i2p/ which makes management easier.

For more realtime help, feel free to jump onto I2P IRC and visit #saltr.

2

bottticelli OP wrote

Thanks a lot for your quick answer. I am running i2p on Linux, package install, running as a service.

According to this, the instructions on the default help page of eepsite say that the proper directory for index.html file is /var/lib/i2p/i2p-config/eepsite/docroot/, which is exactly where I am editing my pagefiles. What is really bizarre that before disabling the i2prouter for the first time since it had been working very nicely, showing every change I did with both index.html files in .../docroot and .../docroot/help directory.

Now it looks like the server is getting some other default index.html files from somewhere else. That's awkward, I can't figure it out. What can be the cause? How do you think?

2

z3d wrote (edited )

Don't edit the eepsite files in your application directory, they serve as a template which is copied to your configuration directory when you first run I2P. Instead you need to edit the files in your configuration directory.

Since you still have the default help files displaying on your site, read the information there relating to the location of the eepsite folder and edit the contents in the location indicated, which varies depending on what operating system you're running I2P on. Once you've edited index.html in eepsite/docroot you may need to clear your browser's cache to see the changes.

3

z3d OP wrote (edited )

Reply to comment by Updates in I2P+ 2.4.0+ released! by z3d

The minor release updates related to cosmetic fixes for I2PSnark, and an issue with the sticky sidebar at less than 1500px viewport width; networking is unaffected.

As for build tunnel success, we appear to be under some sort of attack right now so expect things to behave abnormally. Reduced build success percentages and increased transit tunnel requests have been observed. Under normal operation, a non-firewalled I2P+ router should see around 70-80% build success after approximately 30m of uptime.

To address the varying size of the update zip files that you raised on rocksolid, the additional translations have added around 2MB to the pack200 (skank.i2p/dev/i2pupdate.zip) files, more where pack200 isn't being used. And from time to time, the GeoIP database is included in an update, which adds another 3MB or so to the size.

Regarding minor releases being pushed to the release update channel, these may happen on account of bugs, a new, stable feature being made available pre-release, or because a security issue is being addressed in an update that merits an out-of-band update.

In short, if you don't mind the occasional bug, then the /dev/ update path will give you the new stuff sooner, while the stable/release update path will only give you minor version updates when the new features are sufficiently tested and deemed robust, or to address functional or security bugs that may arise from time to time.

One last thing to mention: if you haven't previously installed I2P+ on a system running a non .deb / repo I2P, and you're performing an upgrade from I2P to I2P+ (not using the full installer), you will need to install from the release url: skank.i2p/i2pupdate.zip before enabling develoment updates from skank.i2p/dev/i2pupdate.zip to ensure you have the pack200 library, otherwise updating from the /dev/ path will fail.

1

Updates wrote

There were some wild updates 4-5 times but the version stayed to 2.4.0-2+ which was the number that was downloaded from gitlab since the Postman was the plain 2.4.0-0 and could not update at 3% build ratio. Are those peers reseeds? The build rate is very good after 24 hours 45%.
Updating from 2.3 is/was a no go. The build ratio was 2-5% plus you had interference from the official i2p. I will port to a few different test OSes and Java versions. The security is improved (I had mitigations for the fixes and did not affect me). i2pd improved too. Just by being on Ramble droped the build to 38%.

1

FreefallHeavens wrote (edited )

If you're running Windows 64-bit I've uploaded a build made from the very last commits that embeds router version 2.4.0. There's no need for relays as a list of frequently-online peers is already included, you just set up your initial profile and give it a bit and it will integrate with the rest of the network. Each peer tells the node about other peers, so as long as a few are reachable a picture of the entire network is eventually rebuilt.

In addition if you happen to also have I2P installed on your system you can run a script file from the folder that will automatically paste the modules of the current I2P install into Muwire. This isn't needed right now since 2.4.0 is the latest router, but it will keep the node easy to update on future releases, even if Muwire itself doesn't get any new updates. The last official commits had embedded router version 1.9.0.

The torrent to download this is on my website, same as my username, just add .i2p. Package is 107MB. Each install stores its profile directly in the app folder itself, be sure to read the Readme.

By its last official releases and commits the app had matured quite nicely and many of its features work very well. It would be a shame if it went to waste.

1

notme wrote

There are several ways in fooling the electric company and not pay for power. I did not it in a very long time (4 decades). There is another problem with the electrical signature of a computer plugged into the power grid. A friend of mine was a saleman for a company that made UPSes (uninterupted power supply that masked the signature to grid). There is also an electromagnetic signature (that I can mask myself). My guess is that either was a rat or the money printers starting to use this type of technology on regular bases.

1

takeheart wrote

Honestly, I see no future for online privacy. No future for online at all. No future for technology since it's becoming outright malicious. No future for civilization. There will be few decades of rapid collapse, then many centuries of slow decay dark ages. Humankind will suffer greatly for this monstrosity they have created. Degenerated racemixed genetically maimed half-human that remain will envy those who have perished, for AI implementations will suck them dry until last drop of bodily fluids, then clone and repeat again and again until the whole machine becomes inoperable.

2

iop23up wrote

I don't get it. Why would a car builder wants to have messages or any personaldata at all? Every fk corporation collects data. MS, apple. For whom or what purpose? For ads? Are you kidding me, fk ads doesn't work (50%) at least if they come as ads? So they want to develop "a friend" who thencommunicate with me to manipulate etc. ? How much does it calculate into the profit? Car is shit, but profit is good, because we have so many data now..ppfftt Do they just dump it to someone who then sells it someone else. My shitty texts? Ai does not make it better if quality of data is somewhere fk. This looks to me like the all corporation=gov goal. One part of preparation for day x, when their plan has progressed. Everybody wants to be a important part of it.

1