I2P support forum

Posted: **22 Aug 2024 07:06**

Phithue7 wrote: ↑31 Jul 2024 13:12
Code: Select all
# CONFIG
snarkurl="http://127.0.0.1:7657/i2psnark/"

I mean, the built-in version uses a different port than the free-standing version. If you think it's right, you could extend your script with a corresponding check. Here is an example snippet for clarification:

Code: Select all

# CONFIG
# snarkurl="http://127.0.0.1:7657/i2psnark/"
# Port build-in ./. stand-alone
for j in 7657 8002
do
    curl --silent http://127.0.0.1:${j}/i2psnark/ 1>/dev/null && {
        snarkurl="http://127.0.0.1:${j}/i2psnark/"
        break
    }
done
test -z "${snarkurl}" && {
    printf "I2PSnark was not found under the named ports.\n"
    exit 1
}
printf "I2PSnark: %s\n" "${snarkurl}"

Posted: **27 Aug 2024 13:53**

none of i2plus 's versions work for me with a proper official i2psnark. not even a proper error message. simply nuthin'

Posted: **27 Aug 2024 16:41**

stay at my 1st version

Phithue7 wrote: ↑17 Aug 2024 17:36 v1 published, waiting for further feedback.
Contains also a screenshots and a readme.

http://tracker2.postman.i2p/index.php?v ... l&id=79456

if a future i2p/i2psnark version breaks anything, I will most probably bring a tested v2 out.

Posted: **28 Aug 2024 16:41**

Additional tip, posted on postman also:

how to deal with mass magnet url's:

- put the magnet links in a plain text file, one url per line.
- Save the file as magnet.txt
- use xargs (usually present in your Linux system already):

Code: Select all

xargs --arg-file=magnet.txt --delimiter=\\n --max-args=1 magnet.sh

I2P support forum

fixing i2psnarks new form with pythonscript

Re: fixing i2psnarks new form with pythonscript

Re: fixing i2psnarks new form with pythonscript

Re: fixing i2psnarks new form with pythonscript

Re: fixing i2psnarks new form with pythonscript