Thank you very much /u/not_bob/, I appreciate. However, as of now this feature is not working on my side. There is blank space in place of the counter rectangle. What can be the possible issue? How do you think?

That is an interesting console I never heard of! Looks a lot like a small arcade. Pretty neat.

I have written a counter you can use in a static site.

To use the counter just include the following code in your html.

<img src="http://5gn3ca4z4occksx2cnwbcrun2mum2eg2c7zgfi7k7fetruwzmdiq.b32.i2p/counter.cgi?site=123842384" height=30>

Change the site number to a random number, and that will be your site number. Feel free to adjust the height to anything you want, the output is a svg file, so it will scale.

You could even use a different site number for each page on your site. Each site has it's own unique count.

As for logging. That server logs access just as any other normal webserver does. I do not share the data with anyone, and the only identifying information that is collected by the server is the b32 of the client who hits the site and the time/date.

We already have mirrors of quite a few useful sites and working outproxies.

Also, you are welcome. I work hard to be a useful member of the community.

Very good, but it should really use flock for file locking to prevent possible race conditions.

But, so long as the site isn't getting a really large number of hits, this is unlikely to be a problem even if you don't use it.

With the default I2P webserver (Jetty), assuming you have perl installed, you can run perl scripts from eepsite/cgi-bin. Something like the following will provide a basic pagecounter when embedded in a iframe:

#!/usr/bin/perl

use strict;
use warnings;

# File to store the page counter
my $counterFile = "counter.txt";

# Read current counter value from file
my $counter = 0;
if (-e $counterFile) {
open(my $fh, '<', $counterFile);
$counter = <$fh>;
chomp($counter);
close($fh);
}

# Increment the counter
$counter++;

# Save updated counter value to file
open(my $fh, '>', $counterFile);
print $fh $counter;
close($fh);

# Generate HTML page counter span
print "Content-Type: text/html\n\n";
print "<span id=\"counter\">$counter</span>\n";

Looks like I2P usage and content is growing. I hope we will have most of the internet available on I2P in a few years.

Thanks for hosting your valuable service for all this time, you are a trooper.

The only other one I use is irc.ilita.i2p.

Though, there are quite a few that are active.

http://notbob.i2p/cgi-bin/defcon.cgi?search=irc

I can't vouch for how active or useful they are though.

If you have a static site, you are limited to using someone else's counter. There is no way to run PHP code from a static site. Also, even if you were to use JavaScript, there is no way for your static site to store that data. So, still not an option.

The only real solution with such a site is to use someone else's counter as you mention in #2.

Not all I2P users have a clearnet outproxy configured. So, using a clearnet service is not the best option. Possible privacy issues aside.

I have a counter on the front of my notbob page. If you mouse over the van on the upper left side you will see a little box with a green graph. While it does not currently show the count, it still counts.

It would not be hard to write a multi-user count. I could likely code one up that would work for anyone pretty quickly. Something basic that just displays a number.

You would embed it into the html code with <img src="http://countersite.i2p/cgi-bin/counter.cgi?site=324832483">

Note the random number. There would be no need for me to even know what site it's counting for.

And, that would all you would have to do on your end. That is if you just want a count. If you want graphs and more complex breakdowns, that's another story.

But, a simple one would be easy. And, as for privacy, so long as you trust the person who's counter you are using, then you are good.

Feel free to hit me up on IRC if you want to discuss this further.

As for discussion, this is a good place to do it.

Thank you, gentlemen raincoat and Rambler, for discussing this issue. Even though I am a random guy passing by, the concerns you raise do touch me. I feel that free speech issues should never be forgotten here. It would be of my great pleasure to try raising this topic from ashes and encourage other forum users having a look and thinking about it one more time.

Meanwhile, I will try to help in increasing the awareness, despite the smallness of my resource. Absolute freedom of speech must exist not only for the sake of conspiracy giggling.

I have a typical firewall up (router) that is difficult to punch a hole in.

If you're talking about a hardware router, you should be able to port forward from the router's internet facing interface to an internal IP address that's hosting your I2P/I2P+ router. You only need to do that for the public I2P port, for both TCP and UDP. You'll find your router operates much, much better if you can overcome the firewalling of your I2P port. The assigned port is indicated on: http://127.0.0.1:7657/confignet

Regarding general activity, I2P+ is much more aggressive in blocking, banning or otherwise ignoring routers on the network that may be participating in attacks or are poorly configured and maintained, so that's probably why you're seeing a difference in network traffic. Keep an eye on the banned peers counter and the tunnel build success percentage in the sidebar in I2P+, these will give you some idea of the network health.

I've been tinkering with I2P and I2P+ lately. I have a typical firewall up (router) that is difficult to punch a hole in. I read that I2P+ is better with firewalled routers.

Are the recent attacks likely to cause problems in this regard?

I ask because, behind a firewall, my stats are much more active on regular I2P currently than my tests with I2P+.

I consider myself a bit of an I2P/+ noob, though I have tinkered with it a lot on and off for over a decade. I finally have a dedicated home server that I'm trying to setup. So far so good, except for this oddity.

Thank you all guys, and especially to whyO, who pointed me exactly to the right thing. Indeed I had to discover this hidden folder and then found all the necessary directories and an index.html file that does recognize changes! Finally...

As stated by other people, you should use the Java installer. Don't use the package that's in whatever repo you are using. Those tend to be outdated. Also, I2P+ for the win.

I use it to lurk the official sub and other privacy subs that the site maker has good taste in featuring. I should note that teddit isn't down but being BLOCKED by reddit.

As a sidenote the .i2p folder is a hidden file folder so you need to tick show hidden files.

Personally I'd always opt for the Java installer over the repo/deb installation because installing it yourself gives you much more flexibility, for example if you want to sidegrade from I2P to I2P+, or if you want to test development builds, in addition to having all your configuration files in a single location (as mentioned).

You can stop the I2P service and try out the java installer if you don't want to fully commit before you've got comfortable. You could always try the I2P+ installer, details at: http://skank.i2p

Back to your original question, given you're currently running a repo installation, and you appear to be editing files in the correct location, the only thing I can think of that may be causing issues is your browser cache retaining the default index.html file which redirects to /help. You can test this theory by creating a separate file in docroot/ and browsing directly to that instead, e.g. testpage.html .. if this works, clear your browser cache and try accessing the site again. And be mindful of the file permissions on any new files you create.

I checked and double-checked, my ~/ dir does not have the .i2p folder, it comes only as an installed package at /var/lib/i2p/i2p-config/...

Do you think it's a good idea to perform a full re-install and get it manually in the ~/.i2p folder? I'm prety satisfied for now with the /var/lib/i2p/i2p-config/ directory, it seems quite equivalent for an i2p-newbie...

Thank you for the channel recommendation, I'll definitely pay attention to it.

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.

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?

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.

Looks like the official Docker image has been updated to 2.4.0 as well.

/u/idk Appreciate your hard work.

Isn't that basically what this is? Anyway this is nice.

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.

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%.