Page 1 of 1

Per Website (Eepsite)

Posted: Tue Apr 22, 2025 5:20 pm
by lgillis
I'm not sure if this is still file sharing, but it's an alternative to the BitTorrent that is prevalent here and should not go unmentioned. The new site movies.i2p popped up in my RSS reader the other day. It is a simple directory tree with folders and files. The operators write that a simple download manager would suffice for downloading. And a download manager with the ability to re-establish broken connections will be needed, that is the nature of the network. The responsiveness of the site, by which I mean the page load, is currently very good, but this may change under load. So if anyone is looking for a way to distribute their own works autonomously, here is an example. This could possibly be supplemented with torrent files and hope that the load will be carried by others. Perhaps the operators are also reading here and can give tips?

Re: Per Website (Eepsite)

Posted: Wed Apr 23, 2025 10:06 am
by provil
checked it out, max speed I could reach was 60KBps. Which is one-third times slower than torrents in postman.

Re: Per Website (Eepsite)

Posted: Wed Apr 23, 2025 3:53 pm
by cumlord
if whoever runs the site sees this you could try separating the website itself and load balance file-serving onto different destinations, this is what i did on music.simp.i2p for streaming. the way it works there is a cookie is used to "identify" a user and they're assigned to a destination with the least amount of people, or random if any have the same user-count. You could even keep it simple and just do it round-robin

i don't usually recommend lowering hops but it was suggested by dr|z3d for that and could apply here, if it's in a safe place reducing outgoing tunnel hops to 2 could give a pretty good boost. since outgoing tunnels aren't stored in netdb (only the inbound gateways are) it's harder to track outgoing tunnels that incoming ones but up to your threat model.

Re: Per Website (Eepsite)

Posted: Fri Apr 25, 2025 10:08 am
by lgillis
And I've learned something new again, so I like that.

Are there any web servers that are particularly suitable for this, like FTP over HTTP? Or can any modern web server do the job?

When I wrote about download managers above, I should have added that not all of them work equally well. For example, Wget is well suited, but Kget (KDE/Plasma) generates defective files. For this reason, site operators should also publish the checksums for their files.

Re: Per Website (Eepsite)

Posted: Fri Apr 25, 2025 5:16 pm
by cumlord
i'd think any modern webserver would probably do fine since it's all static, if doing a lot of concurrent connections apache or nginx could handle better than some of the others. jetty might even do the job, it does good on smaller files but never tried on larger ones. I'm sure there could be settings in any of them that you could tune for this

neat little trick for anyone that doesn't know, you can make a directory in /docroot of jetty and put files there and it will make a browsable filelist for you like http://digitalsr.i2p. can't remember if that's enabled by default but there's a setting for it in the config files

Re: Per Website (Eepsite)

Posted: Fri Apr 25, 2025 5:57 pm
by COMiX
And as a graphical download manager, you can use JDownloader: https://jdownload.org/
Java lovers will be delighted! Simply open the settings tab and enter the IP address of your router's port 4444.
Uncheck 'no proxy' and you're good to go for 15 hours of downloading (with resuming if disconnected).
StormyCloud is going to hate me. :oops:

Re: Per Website (Eepsite)

Posted: Thu May 01, 2025 4:38 pm
by MrLollypants
I run this site, wondered if people might be interested lol

I am also cross-seeding a good amount of torrents (about ~6200, grows as I download more), see: http://crowsnest.i2p/announce

I'd be happy to change out my file server situation if it'd help - currently I'm just using an easy docker container to dish up my files, definitely could be better. I've got 21.7TiB of movies, and 72.6TiB of TV shows (and growing). Clearnet connection is symmetrical gigabit, so no issues there.

Re: Per Website (Eepsite)

Posted: Thu May 01, 2025 6:09 pm
by provil
MrLollypants wrote: Thu May 01, 2025 4:38 pm I run this site, wondered if people might be interested lol

I am also cross-seeding a good amount of torrents (about ~6200, grows as I download more), see: http://crowsnest.i2p/announce

I'd be happy to change out my file server situation if it'd help - currently I'm just using an easy docker container to dish up my files, definitely could be better. I've got 21.7TiB of movies, and 72.6TiB of TV shows (and growing). Clearnet connection is symmetrical gigabit, so no issues there.
Why not create another torrent website rather than creating a DDL website?
My complaint is about downloading speed which is very slow even for I2P or in comparison to I2P Torrenting.
I tried downloading vanilla & with download manager but for me speed never crossed 60-80 KBps which is far lower than torrents atleast in torrent you can get close to 180 KBps even if torrent has only single seeder.

Re: Per Website (Eepsite)

Posted: Thu May 01, 2025 8:04 pm
by MrLollypants
I'm completely new to i2p, so I've likely not configured things correctly. Testing my own site, I've gotten as high as ~300KiB/s when using 5 parallel connections, but it's been a mixed bag. I'll look into running a tracker/index.

Re: Per Website (Eepsite)

Posted: Fri May 02, 2025 7:34 pm
by cumlord
welcome then and thanks for cross seeding :) tested it the other day and was getting around 4-600 with jdownloader but it could have been good luck with fast tunnels. torrents would be good with an indexer/tracker

inbound tunnels are capped at 16 but the outbounds aren't. could be another thing to try. i opted for load balancing on other dests so i could reduce tunnel quantity individually and waste less tunnels, otherwise nothing is stopping you from having 64 outbounds on one destination but if you reduce tunnels it's all or nothing