Recent comments

cumlord wrote (edited )

Reply to comment by Oaloo in Methods for creating torrents to seed? by Oaloo

tuckit can be used to do this sort of thing http://git.simp.i2p/simp/TuckIt

it uses either mktorrent or torf to hash torrents. if you just need that functionality to automate things maybe seeing what's going on http://git.simp.i2p/simp/TuckIt/src/branch/main/modules/torrent_functions.py could help.

you could check a directory every so often and give one of these things the location of any new files, then have it symlink the data files to the torrent client directory then move the .torrent file in. http://git.simp.i2p/simp/i2music/src/branch/main/updateplaylists.py is doing other things, but this is what it does starting line 678

1

z3d wrote (edited )

Reply to Methods for creating torrents to seed? by Oaloo

Any I2P-capable torrent client should be able to create torrents. If you're running i2pd, try I2PSnark Standalone, either the + or "vanilla" version. If you're running a Java-based I2P, you'll already have I2PSnark available.

2

Chronic wrote (edited )

Reply to comment by j8810kkw in A curious thing about tube.i2p by j8810kkw

You're Welcome, I haven't heard of this project before, so I can't say if you should use it or not. I usually just use Invidious/Piped instances, and sometimes Freetube as well, however It's still a good thing that there are alternatives. For Tube, If you already compiled it and it works well with you, let me know if it's worth the build.

Curiously, I was wondering if there were any clients written in Rust, and I found this. It uses Tauri and I like the fact this it is way less bloated and more efficient than Electron clients (e.g. Freetube). Though, the RustyTube project is still in its early stages, but still sounds cool to give it a try nonetheless.

1

Chronic wrote

Reply to A curious thing about tube.i2p by j8810kkw

Well, you just answered your own question. Tube.i2p used to be an anonymous YT frontend, but in reality it was so slow and unreliable, so don't even bother.

If you need to, you can simply use an outproxy and connect directly to any YT frontend of your choice that is near you; would be more reliable than an eepsite/hidden-service. It's also a good idea to create a separate profile for your outproxy use-cases, especially for installing extensions like Libredirect, Sponsorblock, etc..

1

libertas0ether wrote

Reply to Chinese law enforcement places NSA operatives on wanted list over alleged cyberattacks by righttoprivacy

we're at a lvl far removed from the inner workings. evrything could be propaganda lies, west and east. the tidbit about "unknown encrypted data packets" triggering "pre-implanted backdoors" in windows is funny. thnk these are target based or exist widely on every windows installation? waiting for a neutral security auditor to find and expose?

i wonder what incentives lie in wait for such an auditor.. $$$ and recognition, or something more sinister

1

cumlord wrote (edited )

Reply to comment by blueraspberryesketimine in De-anon risk on I2P with consumer firewall products? by blueraspberryesketimine

it probably could, to me that along with traffic analysis are things that fall more into state sponsored level attack. guess avoiding those chipsets is the way or disabling it, but only 3 people are going to do that. like i'd think that at least with intel it's basically a backdoor, probably would take a fair amount of effort for someone outside of them to exploit it. but i guess that doesn't stop intel from gathering intel, lol

there's a surprising amount of low-lying fruit that can be way easier to do for non state actors. Best to assume your ip address is known to be running i2p as public knowledge, and like just poking around the netdb will give info that can sometimes lead to deanon if not careful

1

blueraspberryesketimine OP wrote (edited )

Reply to comment by cumlord in De-anon risk on I2P with consumer firewall products? by blueraspberryesketimine

I wonder how the intel management engine and AMD PSP could be used to track I2P users. They make up the majority of the nodes on this network. We really don't have a way to fight that unless we all jump to RISC-V right? Also, that article is interesting but incredibly outdated. It's from 2010. Id imagine the security posture of i2p has improved dramatically since then.

1