Blog
***
Work in process ... see you soon.
*
14. jan 2009
- updating the Keyword-List in faq
- updating the examples expert; drakensang
Note! guru, minimalist, jama are not overflow fixed yet!
- preparing the zip-archiv
i2psnarkxl-20090114a.zip
*
- updating the Keyword-List in faq
- updating the examples expert; drakensang
Note! guru, minimalist, jama are not overflow fixed yet!
- preparing the zip-archiv
i2psnarkxl-20090114a.zip
14. jan 2009
- including some sort orders for the clients page
- including descending sort orders for each ↓ and ↑ see example pic
example picture
*
- including some sort orders for the clients page
- including descending sort orders for each ↓ and ↑ see example pic
example picture
14. jan 2009
briefing new clientspage
... incomplete
*
briefing new clientspage
B - Banned: whether or not "we banned us" from this client
RC - Re Connections: the count of new re-connections with this client
C - Connected: whether or not we are connected
P - Peer: whether or not we have a peer with this client
FS - First Seen: time left since we know about this client
LS - Last Seen: time left since last successful contact
LCT - Last Connection Try: time left since we try a connection to this client
CS - Connected Since: time left since we are etablished last successful
connection with this client (current session)
CT - Connected Time: time we were truly connected with this client
since FS
up T - up Total: the amount we upload to this client since FS
down T - down Total: the amount we download from this client since FS
up S - up Session: the amount we upload to this client since CS
down S - down Session: the amount we download from this client since CS
UFO - Upload From Others: the amount the client downloaded from other
clients since FS
... incomplete
14. jan 2009
- fixing the dummy string for seeders
XL sends allways a fixed dummy string for seeders. it might be to short for your display.
the size of the dummy-string depending of the user settings in default.config now
- fixing in "classic" page the overflow values for width and heigth
see same link like last message ("just as info")
*
- fixing the dummy string for seeders
XL sends allways a fixed dummy string for seeders. it might be to short for your display.
the size of the dummy-string depending of the user settings in default.config now
- fixing in "classic" page the overflow values for width and heigth
see same link like last message ("just as info")
14. jan 2009
just as info:
it seems that browsers handle the overflow tag different.
some browser ignoring the settings for the parent.element width and height.
if you suffer under elements that running out of your window size then the width and height values
have to be set in the element where the overflow tag/stylesheet is located too. (most are <div>'s)
but this made the rows and columns as strong static elements now.
to get a nice looking "table view" at least there have to be one <td > without size limits.
from now i use "a extra/the last" one <td ></td></tr> for that.
i don't like that but howlong i found no other solution i use it
bad news: i have to touch every single template file to fix that. :(
special thanks @eche|on for help and tests
*
just as info:
it seems that browsers handle the overflow tag different.
some browser ignoring the settings for the parent.element width and height.
if you suffer under elements that running out of your window size then the width and height values
have to be set in the element where the overflow tag/stylesheet is located too. (most are <div>'s)
but this made the rows and columns as strong static elements now.
to get a nice looking "table view" at least there have to be one <td > without size limits.
from now i use "a extra/the last" one <td ></td></tr> for that.
i don't like that but howlong i found no other solution i use it
bad news: i have to touch every single template file to fix that. :(
special thanks @eche|on for help and tests
14. jan 2009
- extending the faq with the new keywords for the new clientspage
in "template_html_clients.html":
{clients_template} - Placeholder for the content of "template_clients.html"
in template_clients.html
{iterator_clients_template} - Placeholder for the content of "iterator_clients_template.html"
in iterator_clients_template.html
{template_client_info} - Placeholder for the content of "template_client_info.html"
{client_isbanned} - style: boolean
{client_name} - style: String
{client_id} - style: String
{client_dest} - style: String
{client_hasbadratio} - style: boolean
{client_soft} - style: String
{client_isconnected} - style: boolean
{client_choking} - style: boolean
{client_haspeer} - style: boolean
{client_reconnections} - style: int
{client_first_seen} - style: timeFormatedString
{client_last_seen} - style: timeFormatedString
{client_last_try} - style: timeFormatedString
{client_connected_since} - style: timeFormatedString
{client_connection_time} - style: timeFormatedString
{client_torrent_name} - style: String
{client_dlrate} - style: intValue + 'Bps' or 'Kps' or 'Mps' or 'Gps'
{client_ulrate} - style: intValue + 'Bps' or 'Kps' or 'Mps' or 'Gps'
{client_ultotal} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
{client_dltotal} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
{client_ultotal_session} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
{client_dltotal_session} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
{client_ultotal_from_others} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
in template_client_info.html
{client_id} - style: String
{client_dest} - style: String
*
- extending the faq with the new keywords for the new clientspage
in "template_html_clients.html":
{clients_template} - Placeholder for the content of "template_clients.html"
in template_clients.html
{iterator_clients_template} - Placeholder for the content of "iterator_clients_template.html"
in iterator_clients_template.html
{template_client_info} - Placeholder for the content of "template_client_info.html"
{client_isbanned} - style: boolean
{client_name} - style: String
{client_id} - style: String
{client_dest} - style: String
{client_hasbadratio} - style: boolean
{client_soft} - style: String
{client_isconnected} - style: boolean
{client_choking} - style: boolean
{client_haspeer} - style: boolean
{client_reconnections} - style: int
{client_first_seen} - style: timeFormatedString
{client_last_seen} - style: timeFormatedString
{client_last_try} - style: timeFormatedString
{client_connected_since} - style: timeFormatedString
{client_connection_time} - style: timeFormatedString
{client_torrent_name} - style: String
{client_dlrate} - style: intValue + 'Bps' or 'Kps' or 'Mps' or 'Gps'
{client_ulrate} - style: intValue + 'Bps' or 'Kps' or 'Mps' or 'Gps'
{client_ultotal} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
{client_dltotal} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
{client_ultotal_session} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
{client_dltotal_session} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
{client_ultotal_from_others} - style: intValue + 'B' or 'KB' or 'MB' or 'GB'
in template_client_info.html
{client_id} - style: String
{client_dest} - style: String
11. jan 2009
- extending the infos for clients on a extra page
- making clients clickable for direct infos
- adding new class Client.class for more infos and a better performence
- adding a lot of new keywords (explaning them later ...
example picture 1
*
- extending the infos for clients on a extra page
- making clients clickable for direct infos
- adding new class Client.class for more infos and a better performence
- adding a lot of new keywords (explaning them later ...
example picture 1
08. jan 2009
- adding a rss feed on my page
Giving a try to rss feeds
*
- adding a rss feed on my page
Giving a try to rss feeds
08. jan 2009
The changing of the source for known clients seems to work well.
[see: message 3.jan 2009] -> most regular known clients added ( just in case they visit us..)
Today a client popsup with a signature of a not usually seen client at i2p.
*
The changing of the source for known clients seems to work well.
[see: message 3.jan 2009] -> most regular known clients added ( just in case they visit us..)
Today a client popsup with a signature of a not usually seen client at i2p.
7. jan 2009
- including a version string (on request of "back|up")
- adding new keyword {versionXL}
- fixing the display of interesting pieces of a peer (that we want)
(was incorrect about a own made bug)
- making a new example template for a theme "drakensang"
(since i didn't saw any new themes made by YOU, i made a new one by my own)
Remember ... i'm not a artist of webdesign ... so it become beautiful ugly - hübsch hässlich.
The colors of the example pic are darker than they are in the browser because i decrease the color-depth
to get a smaller sized png (>1mb -> 174kb). about that the letters may look to dark for you in the example pic.
in reality they are better readable and more shiny.
- including some more tooltips inside the themes.
*
- including a version string (on request of "back|up")
- adding new keyword {versionXL}
- fixing the display of interesting pieces of a peer (that we want)
(was incorrect about a own made bug)
- making a new example template for a theme "drakensang"
(since i didn't saw any new themes made by YOU, i made a new one by my own)
Remember ... i'm not a artist of webdesign ... so it become beautiful ugly - hübsch hässlich.
The colors of the example pic are darker than they are in the browser because i decrease the color-depth
to get a smaller sized png (>1mb -> 174kb). about that the letters may look to dark for you in the example pic.
in reality they are better readable and more shiny.
- including some more tooltips inside the themes.
6. jan 2009
First report/impressions about the new ratio routines.
It's working great!
First i was afraid that this might slow down the downloads howlong there are not enough other clients
that care about the ratio but it seems to be the opposite of my thoughts.
the whole thing is speeding up my downloads because it forced even the non caring clients to deliver
something for a fair share on both sides. I'm allways at the top of the tracker lists and !!! without
a bad ratio.
It's something to be proud on! ;)
see:
example picture 1 *
example picture 2 *
* - The client has 14 torrents in share. 7 as seeder and 7 as leecher.
client uptime 17:32 hours
current running 5 clients with 30 active and different torrents on my side. (just for tests!)
*
First report/impressions about the new ratio routines.
It's working great!
First i was afraid that this might slow down the downloads howlong there are not enough other clients
that care about the ratio but it seems to be the opposite of my thoughts.
the whole thing is speeding up my downloads because it forced even the non caring clients to deliver
something for a fair share on both sides. I'm allways at the top of the tracker lists and !!! without
a bad ratio.
It's something to be proud on! ;)
see:
example picture 1 *
example picture 2 *
* - The client has 14 torrents in share. 7 as seeder and 7 as leecher.
client uptime 17:32 hours
current running 5 clients with 30 active and different torrents on my side. (just for tests!)
6. jan 2009
@devs of I2PSnark (hopefully someone with mtn access read this)
In PeerCheckerTask.class is a little bug/performence problem.
In the methode run() you need to check if the peer isn't a seeder, the only one seeder
and/or/else not the only one uploader (leecher) before setting a peer to choke.
see: all routines that contains "peer.setChoking(true);"
special that one with "download == 0" and those with the "worstdownload" and "worstDownloader".
( a seeder is allways the worst downloader because he is only uploading! so he is allways the first
that would be removed. )
reason:
when we choking a snark-seeder than the seeder stop uploading to us about the download == 0 stuff
older torrents with only one seeder or just a second leecher suffering about that.
special cases are leechers of a rare OS with a small line to the web or a low system.
if the "overUpBWLimit" is reached they loss their only one connection and rather they are
trying on next "PeerCoordinator.CHECK_PERIOD" to reconnecting or unchoking.
that means they are allways stay just for a small connection time and the most time they
use for reconnections till next "PeerCoordinator.CHECK_PERIOD" or choke/unchoking
when they again calling "peer.setChoking(true/false);".
In one of the common versions of I2PSnarkXL i need this to cleanup again too.
In the current version (i2psnarkxl-20090105a) i did just a badly workaround and need to correcting
this again because i mixed up "coordinator.isCompleted()" <-> "peer.isCompleted()" in the
"download == 0" line. But it's not a important fix for XL because it fixed itself with the
the new called routines for the ratio. but it's a toDo!
greetings fwd
Zusatz
Ich wäre dafür die ganze Geschichte mit "worstDownloader" zu streichen [1].
Der Nutzen ist äusserst gering aber der Schaden extrem hoch.
Gerade die alten Torrents mit nur einem Downloader sind betroffen, in doppelter Hinsicht.
Er ist automatisch immer der "worstDownloader" aus Sicht des Seeders und meisst auch noch der
mit der schlechtesten Verbindung. Genau so umgekehrt streicht diese Routine auch noch den
einzigen Seeder aus der Sicht des Leechers selbst, da diese Leecher meistens am längsten und als
einzige in den nicht mehr aktuellen torrents stehen oder als Nachzügler reinspringen und somit
in vielen der alten torrents als dauer Leecher auftauchen und scheinbar nie fertig werden.
Diese Routine erzeugt nahezu einen Ping Pong Effekt von verbinden und trennen (choke/unChoke) zwischen
den beiden. Will der eine, lehnt der andere gerade ab und umgekehrt.
Im "normalen" Internet würde dies vermutlich nicht mal auffallen (ausser dem Betroffenen selbst) und
in der Masse untergehen, in I2P ist es die Regel (durch die kleine Community und die Beständigkeit
der Betroffenen).
Den Betroffenen kann ich z.Z nur empfehlen nur ein einziges torrent im seed/leech zu starten bis dies
in Snark behoben ist.
if you affected by this than you should only start a single torrent for seeding/leeching howlong this
isn't fixed in Snark.
[1] besser wäre eine Art von zeitlicher Rotation, so kommt jeder mal dran.
*
@devs of I2PSnark (hopefully someone with mtn access read this)
In PeerCheckerTask.class is a little bug/performence problem.
In the methode run() you need to check if the peer isn't a seeder, the only one seeder
and/or/else not the only one uploader (leecher) before setting a peer to choke.
see: all routines that contains "peer.setChoking(true);"
special that one with "download == 0" and those with the "worstdownload" and "worstDownloader".
( a seeder is allways the worst downloader because he is only uploading! so he is allways the first
that would be removed. )
reason:
when we choking a snark-seeder than the seeder stop uploading to us about the download == 0 stuff
older torrents with only one seeder or just a second leecher suffering about that.
special cases are leechers of a rare OS with a small line to the web or a low system.
if the "overUpBWLimit" is reached they loss their only one connection and rather they are
trying on next "PeerCoordinator.CHECK_PERIOD" to reconnecting or unchoking.
that means they are allways stay just for a small connection time and the most time they
use for reconnections till next "PeerCoordinator.CHECK_PERIOD" or choke/unchoking
when they again calling "peer.setChoking(true/false);".
In one of the common versions of I2PSnarkXL i need this to cleanup again too.
In the current version (i2psnarkxl-20090105a) i did just a badly workaround and need to correcting
this again because i mixed up "coordinator.isCompleted()" <-> "peer.isCompleted()" in the
"download == 0" line. But it's not a important fix for XL because it fixed itself with the
the new called routines for the ratio. but it's a toDo!
greetings fwd
Zusatz
Ich wäre dafür die ganze Geschichte mit "worstDownloader" zu streichen [1].
Der Nutzen ist äusserst gering aber der Schaden extrem hoch.
Gerade die alten Torrents mit nur einem Downloader sind betroffen, in doppelter Hinsicht.
Er ist automatisch immer der "worstDownloader" aus Sicht des Seeders und meisst auch noch der
mit der schlechtesten Verbindung. Genau so umgekehrt streicht diese Routine auch noch den
einzigen Seeder aus der Sicht des Leechers selbst, da diese Leecher meistens am längsten und als
einzige in den nicht mehr aktuellen torrents stehen oder als Nachzügler reinspringen und somit
in vielen der alten torrents als dauer Leecher auftauchen und scheinbar nie fertig werden.
Diese Routine erzeugt nahezu einen Ping Pong Effekt von verbinden und trennen (choke/unChoke) zwischen
den beiden. Will der eine, lehnt der andere gerade ab und umgekehrt.
Im "normalen" Internet würde dies vermutlich nicht mal auffallen (ausser dem Betroffenen selbst) und
in der Masse untergehen, in I2P ist es die Regel (durch die kleine Community und die Beständigkeit
der Betroffenen).
Den Betroffenen kann ich z.Z nur empfehlen nur ein einziges torrent im seed/leech zu starten bis dies
in Snark behoben ist.
if you affected by this than you should only start a single torrent for seeding/leeching howlong this
isn't fixed in Snark.
[1] besser wäre eine Art von zeitlicher Rotation, so kommt jeder mal dran.
5. jan 2009
- updating the Keyword-List in faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20090105a.zip
md5: 233638b2d4d307015f13d1eb1cd5b286
*
- updating the Keyword-List in faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20090105a.zip
md5: 233638b2d4d307015f13d1eb1cd5b286
05. jan 2009
- adding new keyword {peer_hasbadratio}
Ratio 0.5 and minimum upload > 2 pieces before the ratio limiter is active: example picture
The ratio will be ignored if the other peer has no pieces we want from it.
*
- adding new keyword {peer_hasbadratio}
Ratio 0.5 and minimum upload > 2 pieces before the ratio limiter is active: example picture
The ratio will be ignored if the other peer has no pieces we want from it.
05. jan 2009
I figured out a problem that could happens if we strict handle a ratio.
If we are a Leecher normaly all seems fine and we have a upload/download ratio that is in balance.
We receive 20mb and deliver 20mb+ for a torrent but when we connected with "bad" Leechers
(like most are at the moment) and we got a good connection to a nice Seeder than we are
looking like a bad Leecher too. we are not because we delivery everybody else more than they gave
but that that we got from the Seeder makes us looking as a bad Leecher on the tracker list.
We get 20mb's from other Leecher and 20mb's from the Seeder = 40mb's overall but even with a ratio
of 0.5 we deliver just a maximum of 30mb's to the other Leechers. That's not our fault but about that
it's possible that we are the one who seems to be the one who's stucking a torrent in the hot period.
if in common more clients out there that also care about the ratio this will not be a problem but
at the moment ...
Any suggestions how to handle this?
*
I figured out a problem that could happens if we strict handle a ratio.
If we are a Leecher normaly all seems fine and we have a upload/download ratio that is in balance.
We receive 20mb and deliver 20mb+ for a torrent but when we connected with "bad" Leechers
(like most are at the moment) and we got a good connection to a nice Seeder than we are
looking like a bad Leecher too. we are not because we delivery everybody else more than they gave
but that that we got from the Seeder makes us looking as a bad Leecher on the tracker list.
We get 20mb's from other Leecher and 20mb's from the Seeder = 40mb's overall but even with a ratio
of 0.5 we deliver just a maximum of 30mb's to the other Leechers. That's not our fault but about that
it's possible that we are the one who seems to be the one who's stucking a torrent in the hot period.
if in common more clients out there that also care about the ratio this will not be a problem but
at the moment ...
Any suggestions how to handle this?
05. jan 2009
... and this way it looks when you (make a mistake and) have a (to) strong ratio (0.9) and you didn't
seed anything.
huh, not a nice idea when just clients out there that didn't care about any ratio.
not nicely but proberly a fair share. :(
*
... and this way it looks when you (make a mistake and) have a (to) strong ratio (0.9) and you didn't
seed anything.
huh, not a nice idea when just clients out there that didn't care about any ratio.
not nicely but proberly a fair share. :(
04. jan 2009
experimenting a bit with the download and upload limits and including a strong ratio handling
and WOW ... first time i get rates like i expecting it from a BT-Client on i2p.
The complete outbound Bandwidth is used constant for the first time since i'm on i2p.
Hope this is a stabil effect and not a random thread.
*
experimenting a bit with the download and upload limits and including a strong ratio handling
and WOW ... first time i get rates like i expecting it from a BT-Client on i2p.
The complete outbound Bandwidth is used constant for the first time since i'm on i2p.
Hope this is a stabil effect and not a random thread.
03. jan 2009
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20090103a.zip
md5: 59a4d09f2c28ea7c4930eb3df9948007
*
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20090103a.zip
md5: 59a4d09f2c28ea7c4930eb3df9948007
03. jan 2009
- fixing on "classic" page some infos about the config-file
- changing the complete source for known clients
- adding new class org.i2p.i2psnarkxl.peermanager.utils.BTPeerIDByteDecoder (for client idents)
Reason:
after Robert 0.0.3 comes out i noticed that my previous added Robert id was wrong.
(The Robert id is a none static id and change with the version numbers)
so i took the time to switch the whole source. Clients are displayed Azureus-like now.
most regular known clients added ( just in case they visit us..)
*
- fixing on "classic" page some infos about the config-file
- changing the complete source for known clients
- adding new class org.i2p.i2psnarkxl.peermanager.utils.BTPeerIDByteDecoder (for client idents)
Reason:
after Robert 0.0.3 comes out i noticed that my previous added Robert id was wrong.
(The Robert id is a none static id and change with the version numbers)
so i took the time to switch the whole source. Clients are displayed Azureus-like now.
most regular known clients added ( just in case they visit us..)
30. dec 2008
- preparing the zip-archiv
- update
i2psnarkxl-20081230a.zip
md5: cd6002062c51fcea979a8ea0b9c4ed94
*
- preparing the zip-archiv
- update
i2psnarkxl-20081230a.zip
md5: cd6002062c51fcea979a8ea0b9c4ed94
30. dec 2008
- changing the limits for torrents
size from 10gb to 100gb; pieceslength from 1mb to 8mb; files in a torrent from 128 to unlimited
this needs a lot of tests now!
- adding Robert-id to known clients
Reason: torrents that are generated with Robert
see info (by Sponge):
Robert:
http://forum.i2p/viewtopic.php?t=2934
I2PSnark Limitations & Other Clients:
http://forum.i2p/viewtopic.php?t=2068
if you like a preversion of this I2PSnarkXL for testing too than leave me a message at
http://i2psnarkxl.i2p/miniserver/
since last message (30. aug 2008) i did some changes for myself and a better performence
yet i didn't descript it here ... like active seeding instead passiv waiting for leechers
and some other interesting stuff. when i got more time i might descript it but not yet.
*
- changing the limits for torrents
size from 10gb to 100gb; pieceslength from 1mb to 8mb; files in a torrent from 128 to unlimited
this needs a lot of tests now!
- adding Robert-id to known clients
Reason: torrents that are generated with Robert
see info (by Sponge):
Robert:
http://forum.i2p/viewtopic.php?t=2934
I2PSnark Limitations & Other Clients:
http://forum.i2p/viewtopic.php?t=2068
if you like a preversion of this I2PSnarkXL for testing too than leave me a message at
http://i2psnarkxl.i2p/miniserver/
since last message (30. aug 2008) i did some changes for myself and a better performence
yet i didn't descript it here ... like active seeding instead passiv waiting for leechers
and some other interesting stuff. when i got more time i might descript it but not yet.
6. sep 2008
- adding our own pieces to the stats of available pieces if our torrent is incomplete
- changing disconnect while inactive time is over 8 minuts to 20 minuts (11 minuts lifetime of a bad tunnel)
to wait 20 minuts does not hurt us but disconnecting a peer while we got a bad tunnel and waiting 1 hour
for next trackerrequest does hurt!
*
- adding our own pieces to the stats of available pieces if our torrent is incomplete
- changing disconnect while inactive time is over 8 minuts to 20 minuts (11 minuts lifetime of a bad tunnel)
to wait 20 minuts does not hurt us but disconnecting a peer while we got a bad tunnel and waiting 1 hour
for next trackerrequest does hurt!
30. aug 2008
- updating the faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080830a.zip
md5: 51d03f6549afd1dc1b16dd471974400d
*
- updating the faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080830a.zip
md5: 51d03f6549afd1dc1b16dd471974400d
30. aug 2008
- adding new Keyword {torrent_pieces_string}
- adding new Keyword for default.config key_torrent_ProgressBar_MaxPieces
this are the torrent aquivalent-settings to the peer stuff
- fixing the problem of a needed first call of the app to readout the user given name and to start torrents by
"autostart-function"
see: message-service topicident: wkazUVVH53yeLRJyHylyN-XzX7sYQCk1dBNfXyQ
thanks to "neo2k"
- setting the StartupDelayMinutes back to 3 minutes (like it was in I2PSnark)
toDo: thought here is a user setting random value a good thing to increase anonymity
(what do you think about that?)
*
- adding new Keyword {torrent_pieces_string}
- adding new Keyword for default.config key_torrent_ProgressBar_MaxPieces
this are the torrent aquivalent-settings to the peer stuff
- fixing the problem of a needed first call of the app to readout the user given name and to start torrents by
"autostart-function"
see: message-service topicident: wkazUVVH53yeLRJyHylyN-XzX7sYQCk1dBNfXyQ
thanks to "neo2k"
- setting the StartupDelayMinutes back to 3 minutes (like it was in I2PSnark)
toDo: thought here is a user setting random value a good thing to increase anonymity
(what do you think about that?)
21. aug 2008
- i2psnark fixed: snark.coordinator.getDownloadRate() shows last rate after we have stopped the torrent
- i2psnark fixed: snark.coordinator.getUploadRate() shows last rate after we have stopped the torrent
- adding new keywords {torrent_InfoHash}; {torrent_InfoHash_urlencoded}
- integrating a methode that allows to show peers of a single torrent insteed all torrents by using the new
keyword {torrent_InfoHash}
- updating the faq
- updating the examples
... working a bit on my personal message-service.
*
- i2psnark fixed: snark.coordinator.getDownloadRate() shows last rate after we have stopped the torrent
- i2psnark fixed: snark.coordinator.getUploadRate() shows last rate after we have stopped the torrent
- adding new keywords {torrent_InfoHash}; {torrent_InfoHash_urlencoded}
- integrating a methode that allows to show peers of a single torrent insteed all torrents by using the new
keyword {torrent_InfoHash}
- updating the faq
- updating the examples
... working a bit on my personal message-service.
13. aug 2008
- i2psnark: Fix OOM vulnerability by checking incoming message length
(Rev. a7524035a59d80854d131f6c9f8ead9022e4a106)
- investing some time to write a small webservlet for static eepsites to include a message-service.
*
- i2psnark: Fix OOM vulnerability by checking incoming message length
(Rev. a7524035a59d80854d131f6c9f8ead9022e4a106)
- investing some time to write a small webservlet for static eepsites to include a message-service.
12. aug 2008
- updating the faq
- updating the examples
- preparing the zip-archiv ... again
- update
i2psnarkxl-20080812b.zip
md5: 099d682ce41fb3d77a412ac82a3ddb6e
*
- updating the faq
- updating the examples
- preparing the zip-archiv ... again
- update
i2psnarkxl-20080812b.zip
md5: 099d682ce41fb3d77a412ac82a3ddb6e
12. aug 2008
renaming keyword {userClient} to {peer_userClient}
and prepare the new update version ...
*
renaming keyword {userClient} to {peer_userClient}
and prepare the new update version ...
12. aug 2008
REMOVED FROM TRACKER
- enhancing the faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080812a.zip
md5: 91db92e4798ea06048a2554b91881570
Fine! Now when i updated the faq i saw my mistake! again there is a keyword to change.
Because nobody downloaded this yet i removed it from tracker and fixed this damn bug.
*
REMOVED FROM TRACKER
- enhancing the faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080812a.zip
md5: 91db92e4798ea06048a2554b91881570
Fine! Now when i updated the faq i saw my mistake! again there is a keyword to change.
Because nobody downloaded this yet i removed it from tracker and fixed this damn bug.
12. aug 2008
work of yesterday:
- adding new keywords {my_peer_id}; {userClient}
- integrate a sort order for the peers - sorting the peers by name
- made a unique client id for XL "CwsL" instead snarks client id "AwMD"
{torrents_uploaded_total} and {torrents_downloaded_total} are deprecated!
and renamed as {torrents_total_uploaded} and {torrents_total_downloaded} to keep a redline on keywords.
{peer_total_progressbar_size} is deprecated and renamed
as {peers_total_progressbar_size}
{my_peer_id} is only shown if the client is connected because if your client didn't open a tunnel
than you haven't any id!
... thought that was it ... maybe if i forgot something then i will announce it later.
btw: if the jetty server shown are ERROR page then this is just for the templates. Your client works still and
you can get it with the classic page! If this happens then fix your errors and refresh the browser.
*
work of yesterday:
- adding new keywords {my_peer_id}; {userClient}
- integrate a sort order for the peers - sorting the peers by name
- made a unique client id for XL "CwsL" instead snarks client id "AwMD"
{torrents_uploaded_total} and {torrents_downloaded_total} are deprecated!
and renamed as {torrents_total_uploaded} and {torrents_total_downloaded} to keep a redline on keywords.
{peer_total_progressbar_size} is deprecated and renamed
as {peers_total_progressbar_size}
{my_peer_id} is only shown if the client is connected because if your client didn't open a tunnel
than you haven't any id!
... thought that was it ... maybe if i forgot something then i will announce it later.
btw: if the jetty server shown are ERROR page then this is just for the templates. Your client works still and
you can get it with the classic page! If this happens then fix your errors and refresh the browser.
11. aug 2008
i'm doing a lot stuff today but i'm to sleepy to tell something smart about it or to prepare a update.
see the example pic of theme expert on the mainpage that shows some of my daily work.
n8
*
i'm doing a lot stuff today but i'm to sleepy to tell something smart about it or to prepare a update.
see the example pic of theme expert on the mainpage that shows some of my daily work.
n8
11. aug 2008
- adding to the configuration file "default.config" the Keyword "key_Charset"
- adding new keyword {charset} to the general Keyword-List. it represents your setting
of the configuration file "default.config" see above or in worst cases "UTF-8".
The default value is "key_Charset=UTF-8".
The "key_Charset" setting would be also used to responds to the jetty-server.
It could be different to the charset setting in the templates. this is your turn.
On normal circumstances you have not to change this!
It's just for those that have problems to integrate their language with the normal charset value of the html page.
For the html charset you should still use your own ?userkey? settings!
*
- adding to the configuration file "default.config" the Keyword "key_Charset"
- adding new keyword {charset} to the general Keyword-List. it represents your setting
of the configuration file "default.config" see above or in worst cases "UTF-8".
The default value is "key_Charset=UTF-8".
The "key_Charset" setting would be also used to responds to the jetty-server.
It could be different to the charset setting in the templates. this is your turn.
On normal circumstances you have not to change this!
It's just for those that have problems to integrate their language with the normal charset value of the html page.
For the html charset you should still use your own ?userkey? settings!
10. aug 2008
- enhancing the faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080810a.zip
md5: 33c5efdffc1e934912eaefbfcfbe394b
*
- enhancing the faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080810a.zip
md5: 33c5efdffc1e934912eaefbfcfbe394b
10. aug 2008
some words to the new integrated default configuration file "default.config"
- the configuration file "default.config" is located in the main directory of a theme.
current the following settings are possible for a user defined changing:
key_ProgressBar_Piece=|
key_ProgressBar_NoPiece=
key_ProgressBar_ReqPiece=:
key_ProgressBar_MaxPieces=300
key_UserConfig=user_lang_de.config
every setting have to be one line!
... to be continue
*
*
some words to the new integrated default configuration file "default.config"
- the configuration file "default.config" is located in the main directory of a theme.
current the following settings are possible for a user defined changing:
key_ProgressBar_Piece=|
key_ProgressBar_NoPiece=
key_ProgressBar_ReqPiece=:
key_ProgressBar_MaxPieces=300
key_UserConfig=user_lang_de.config
every setting have to be one line!
... to be continue
10. aug 2008
- refactoring package-tree
- refactoring class org.klomp.snarkxl.web.HtmlGenerator to org.i2p.i2psnarkxl.template.web.HtmlGenerator
- adding new class "TemplateConfig.class"
- adding configuration file for the themes "default.config"
- adding user specific keywords (unlimited) and user configuration files (unlimited)
With the "default.config" you could changing as example the strings that are used in the progressBars and
other stuff.
With the user keywords (made by your own) you could as example switching between languages or
replacing the code in the templates or a lot of unlimited[1] other things.
[1] limited by your imagination and/or experience
see: the faq What is a user keyword?
*
- refactoring package-tree
- refactoring class org.klomp.snarkxl.web.HtmlGenerator to org.i2p.i2psnarkxl.template.web.HtmlGenerator
- adding new class "TemplateConfig.class"
- adding configuration file for the themes "default.config"
- adding user specific keywords (unlimited) and user configuration files (unlimited)
With the "default.config" you could changing as example the strings that are used in the progressBars and
other stuff.
With the user keywords (made by your own) you could as example switching between languages or
replacing the code in the templates or a lot of unlimited[1] other things.
[1] limited by your imagination and/or experience
see: the faq What is a user keyword?
9. aug 2008
- updating the Keyword-List in faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080809a.zip
md5: 4fddf31e90f9ff292b6cd8a64a72970c
*
- updating the Keyword-List in faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080809a.zip
md5: 4fddf31e90f9ff292b6cd8a64a72970c
9. aug 2008
i experimenting a bit with the html-source for the text-based-progressBar-string to get
a better look'n feel. But i don't know how your browser will display it in the end.
so, here are the examples how it look at my side. if the display is different at your
side then please tell me!
this scrollsliders is shown up after pressing "ctrl" and "+" to increase the text-size.
*
i experimenting a bit with the html-source for the text-based-progressBar-string to get
a better look'n feel. But i don't know how your browser will display it in the end.
so, here are the examples how it look at my side. if the display is different at your
side then please tell me!
this scrollsliders is shown up after pressing "ctrl" and "+" to increase the text-size.
8. aug 2008
- adding new keywords {peer_total_progressbar_size}; {peers_total_pieces_available_string}
{peer_total_progressbar_size} is the integer value of {peers_total_pieces_available} in percent could be used
to strech some "width". I use it in the examples to strech the progressBar's.
{peers_total_pieces_available_string} is the text-based progressBar for available pieces
it included all pieces of the current peers.
*
- adding new keywords {peer_total_progressbar_size}; {peers_total_pieces_available_string}
{peer_total_progressbar_size} is the integer value of {peers_total_pieces_available} in percent could be used
to strech some "width". I use it in the examples to strech the progressBar's.
{peers_total_pieces_available_string} is the text-based progressBar for available pieces
it included all pieces of the current peers.
8. aug 2008
- updating the Keyword-List in faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080808a.zip
md5: 4bdfa74777c77bd5112b602737264725
*
- updating the Keyword-List in faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080808a.zip
md5: 4bdfa74777c77bd5112b602737264725
8. aug 2008
- adding new keyword {peers_total_pieces_available_percent}
this is the printout of {peers_total_pieces_available} in percent
PS: Don't be upset of the lenght of some keywords. After the testphase i'll integrate for every
keyword a shorten, abstract version too. At the moment i need just a human readable style to
find a redline in my doings and not to lossing myself in abstract spellings.
*
- adding new keyword {peers_total_pieces_available_percent}
this is the printout of {peers_total_pieces_available} in percent
PS: Don't be upset of the lenght of some keywords. After the testphase i'll integrate for every
keyword a shorten, abstract version too. At the moment i need just a human readable style to
find a redline in my doings and not to lossing myself in abstract spellings.
7. aug 2008
- adding the missing 'ps' to {torrent_ulrate} and {torrent_dlrate}
current they showing B or KB or MB or GB instead Bps or KBps or MBps or GBps.
- adding new keyword {peers_total_pieces_available}
this shown the current availabe pieces for a torrent by peers.
this could never been higher then the total size of pieces for a torrent-file
it count the different pieces of all peers for a torrent and not the sum of pieces by all peers.
that means if this count matches with the size of pieces of a torrent than the current peers could finishing
the torrent even if no seeder is online yet. The file is 100% availabe by the current peers.
at the moment this will only works if the text-based progressBar for pieces is shown.
in common versions this will be allways available.
The following example shown 3 peers with 40 + 40 + 26 pieces. The sum of shared pieces by peers is 106 and
the available different pieces by all peers is 65. So, everybody could still get something of the others.
Yet, it doesn't include our own pieces but in common versions this will be included too except we are seeding
because a seeder have allways all pieces and it is no advantage to count them. In common versions i will also
take out other seeders, so we see howmuch is available without seeders.
It's also a good indicator for the progress of a torrent.
*
- adding the missing 'ps' to {torrent_ulrate} and {torrent_dlrate}
current they showing B or KB or MB or GB instead Bps or KBps or MBps or GBps.
- adding new keyword {peers_total_pieces_available}
this shown the current availabe pieces for a torrent by peers.
this could never been higher then the total size of pieces for a torrent-file
it count the different pieces of all peers for a torrent and not the sum of pieces by all peers.
that means if this count matches with the size of pieces of a torrent than the current peers could finishing
the torrent even if no seeder is online yet. The file is 100% availabe by the current peers.
at the moment this will only works if the text-based progressBar for pieces is shown.
in common versions this will be allways available.
The following example shown 3 peers with 40 + 40 + 26 pieces. The sum of shared pieces by peers is 106 and
the available different pieces by all peers is 65. So, everybody could still get something of the others.
Yet, it doesn't include our own pieces but in common versions this will be included too except we are seeding
because a seeder have allways all pieces and it is no advantage to count them. In common versions i will also
take out other seeders, so we see howmuch is available without seeders.
It's also a good indicator for the progress of a torrent.
7. aug 2008
- updating the Keyword-List in faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080807a.zip
md5: d8239f40c60d397c34f5313e2a0157b0
*
- updating the Keyword-List in faq
- updating the examples
- preparing the zip-archiv
- update
i2psnarkxl-20080807a.zip
md5: d8239f40c60d397c34f5313e2a0157b0
7. aug 2008
- adding new keywords {peers_total_pieces_requested}; {peers_total_ulrate}; {peers_total_dlrate};
{peers_total_ultotal}; {peers_total_dltotal}
The new keywords represent the total sum of all peers for each torrent with which we are current connected.
"Current" because this could vary from sum of session totals (clients come and go in a session) and they
could vary from the aquivalent settings of the torrent. But we want the correct values of the peers like they
are displayed. I know thats sounds a little bit confused but trust me. It's all correct!
- adding new keywords {torrent_ulrate}; {torrent_dlrate}; {torrents_total_ulrate}; {torrents_total_dlrate};
{torrents_uploaded_total}; {torrents_downloaded_total}
This new keywords are the aquivalent of the keywords above, just for torrents.
*
- adding new keywords {peers_total_pieces_requested}; {peers_total_ulrate}; {peers_total_dlrate};
{peers_total_ultotal}; {peers_total_dltotal}
The new keywords represent the total sum of all peers for each torrent with which we are current connected.
"Current" because this could vary from sum of session totals (clients come and go in a session) and they
could vary from the aquivalent settings of the torrent. But we want the correct values of the peers like they
are displayed. I know thats sounds a little bit confused but trust me. It's all correct!
- adding new keywords {torrent_ulrate}; {torrent_dlrate}; {torrents_total_ulrate}; {torrents_total_dlrate};
{torrents_uploaded_total}; {torrents_downloaded_total}
This new keywords are the aquivalent of the keywords above, just for torrents.
6. aug 2008
Found postman on google cache:
http://209.85.135.104/search?q=cache:jh2JvITxevwJ:tracker.postman.i2p.to/
or
http://209.85.135.104/search?q=cache:tracker.postman.i2p.to:
'snapshot of the page as it appeared on 25 Jun 2008 14:16:40 GMT.'
but there have to be a newer google scan because google got infos about "i2psnarkxl"
thats dated end of jul
*
Found postman on google cache:
http://209.85.135.104/search?q=cache:jh2JvITxevwJ:tracker.postman.i2p.to/
or
http://209.85.135.104/search?q=cache:tracker.postman.i2p.to:
'snapshot of the page as it appeared on 25 Jun 2008 14:16:40 GMT.'
but there have to be a newer google scan because google got infos about "i2psnarkxl"
thats dated end of jul
6. aug 2008
- adding a function that allows to inserting comments in the templates.
all lines that starts with '##' are ignored by generating the html page.
you can use it for comments or just to take out some lines without to remove them
from the template. thought this could be very useful.
*
- adding a function that allows to inserting comments in the templates.
all lines that starts with '##' are ignored by generating the html page.
you can use it for comments or just to take out some lines without to remove them
from the template. thought this could be very useful.
6. aug 2008
Because i come more familary with the code of snark i could moving some methods for keywords on a
previous loop while running the templates. Torrents with status "NONE" print out more informations now.
Doing some stuffs to increase the performence on a browser refresh.
Except for {peer_pieces_string} [progressBar of pieces]. this i didn't touch yet.
(wanna keep this nice work for a lousy weekend)
- adding new keyword {torrent_pieces_completed}
- torrents with status "NONE" shown the total count of pieces and (new) the current completed count too
Did really some crazy stuff to stop, cut, slash, crash ... the i2p sessions without caring for
the running XL-Clients and ... good news! The workaround for lossing datas seems to work well!
The pid-file logic have done a good job. I didn't miss any data amount after restarting. But no reason
for a early happy hour! Murphy's Law find allways some new ways to keep coders at work. Day and nights.
btw: would be nice to see some screenshots of your work. Maybe we should make somewhere a gallery ...
uuuhh, before i forget this again. Please do not insert Javascript on your own templates! That really could
destroy your anonymity. Once you got happits to use XL-templates with Javascript ... other -external- loaded
templates could force and tread you with hidden stuff.
*
Because i come more familary with the code of snark i could moving some methods for keywords on a
previous loop while running the templates. Torrents with status "NONE" print out more informations now.
Doing some stuffs to increase the performence on a browser refresh.
Except for {peer_pieces_string} [progressBar of pieces]. this i didn't touch yet.
(wanna keep this nice work for a lousy weekend)
- adding new keyword {torrent_pieces_completed}
- torrents with status "NONE" shown the total count of pieces and (new) the current completed count too
Did really some crazy stuff to stop, cut, slash, crash ... the i2p sessions without caring for
the running XL-Clients and ... good news! The workaround for lossing datas seems to work well!
The pid-file logic have done a good job. I didn't miss any data amount after restarting. But no reason
for a early happy hour! Murphy's Law find allways some new ways to keep coders at work. Day and nights.
btw: would be nice to see some screenshots of your work. Maybe we should make somewhere a gallery ...
uuuhh, before i forget this again. Please do not insert Javascript on your own templates! That really could
destroy your anonymity. Once you got happits to use XL-templates with Javascript ... other -external- loaded
templates could force and tread you with hidden stuff.
5. aug 2008
i2psnarkxl-20080805a.zip
md5: a9a9120a8ae8e90035b3f0ed79f08471
*
Update
i2psnarkxl-20080805a.zip
md5: a9a9120a8ae8e90035b3f0ed79f08471
5. aug 2008
- enhancing the faq
- updating the examples
- preparing the zip-archiv for next update
- update
*
- enhancing the faq
- updating the examples
- preparing the zip-archiv for next update
- update
5. aug 2008
- starting a workaround about the lossing data problem while snark isn't closed valid at last i2p session
using the pid-file logic for each XL Client.
creating and removing a pidfile at the critical/uncritical times. if at next startup-procedur a pidfile from
the last session exists then the config-file will be cleaned up from the zmeta.datas before the torrents are
loaded to the client. let's see if this resolve the problem.
btw:
things you should not do: **
* naming the xl-clients as "i2p.war"; "router.war"; "routerjvm.war" they all creating pid-files too.
* naming the xl-clients as "dummyxl.war" or "unset.war". That all are logical keywords in the app while
the clients name is currently not indentified at startup.
* using same torrent folders for different XL-Clients.
* renaming the folder for the torrents as "unset". thats even a keyword in the app while the clients
name is currently not indentified at startup too.
**(just in case that "Murphy" is somewhere around on i2p)
*
- starting a workaround about the lossing data problem while snark isn't closed valid at last i2p session
using the pid-file logic for each XL Client.
creating and removing a pidfile at the critical/uncritical times. if at next startup-procedur a pidfile from
the last session exists then the config-file will be cleaned up from the zmeta.datas before the torrents are
loaded to the client. let's see if this resolve the problem.
btw:
things you should not do: **
* naming the xl-clients as "i2p.war"; "router.war"; "routerjvm.war" they all creating pid-files too.
* naming the xl-clients as "dummyxl.war" or "unset.war". That all are logical keywords in the app while
the clients name is currently not indentified at startup.
* using same torrent folders for different XL-Clients.
* renaming the folder for the torrents as "unset". thats even a keyword in the app while the clients
name is currently not indentified at startup too.
**(just in case that "Murphy" is somewhere around on i2p)
4. aug 2008
- enhancing faq Tips'nTricks
* "changing the refresh rates for the example themes"
* "some of the keywords you can use to toggle images"
- enhancing faq Installing I2PSnarkXL
- indexing the faq
- adding link "download this eepSite"
- adding new keyword {torrent_known_peer_count}
*
- enhancing faq Tips'nTricks
* "changing the refresh rates for the example themes"
* "some of the keywords you can use to toggle images"
- enhancing faq Installing I2PSnarkXL
- indexing the faq
- adding link "download this eepSite"
- adding new keyword {torrent_known_peer_count}
4. aug 2008
- fixing a bug that shown sometimes the wrong status of a torrent (Seeding <==> Leeching)
removed the 20080804-alpha torrent from tracker because the only once downloader was my second client
and this 20080804b version got some fixes more!
so nobody was hurt!
the current update is i2psnarkxl-20080804b.zip
md5: f51d96f981386d55c090963b870165fd
*
- fixing a bug that shown sometimes the wrong status of a torrent (Seeding <==> Leeching)
removed the 20080804-alpha torrent from tracker because the only once downloader was my second client
and this 20080804b version got some fixes more!
so nobody was hurt!
the current update is i2psnarkxl-20080804b.zip
md5: f51d96f981386d55c090963b870165fd
3. aug 2008
Update (removed)
i2psnarkxl-20080804.zip
md5: 0344c2308a447f8ba85f275cb0440e6f
edit:
REMOVED FROM TRACKER
*
Update (removed)
i2psnarkxl-20080804.zip
md5: 0344c2308a447f8ba85f275cb0440e6f
edit:
REMOVED FROM TRACKER
3. aug 2008
- fixing a little bug for themes that are without 'text-based' progressbar but still running the methode for it.
- adding a methode to toggle the peers in the themes
- keywordlist new: {link_ext_showpeers}; {torrent_status}; {torrent_percent}; {torrent_progressbar_size}
- updating the example templates
- including theme guru
- prepare the zip
- i2psnarkxl-20080804-md5-0344c2308a447f8ba85f275cb0440e6f-.zip
the 'close peers toogle' keeps the CPU usage low for the themes.
you do not need anymore to switch to the classic page to avoid from high browser access.
*
- fixing a little bug for themes that are without 'text-based' progressbar but still running the methode for it.
- adding a methode to toggle the peers in the themes
- keywordlist new: {link_ext_showpeers}; {torrent_status}; {torrent_percent}; {torrent_progressbar_size}
- updating the example templates
- including theme guru
- prepare the zip
- i2psnarkxl-20080804-md5-0344c2308a447f8ba85f275cb0440e6f-.zip
the 'close peers toogle' keeps the CPU usage low for the themes.
you do not need anymore to switch to the classic page to avoid from high browser access.
3, aug 2008
while downloading 2 torrents with more than 5000 pieces and a leecher count > 10 for each file
i see the problems with the 'text-based' progressbar for pieces. The CPU usage increases
enormously on every refresh intervall of the browser. shit happens!
thought this becomes a immediately point on the toDo list.
I know this string want bite me often but why so soon?!
following is the content of a 'text-based' progressbar string with > 5000 pieces.
For a better printout i replaced completed parts with 'x', incompleted parts with '-'.
'o' shown the parts we currently requesting from this clients.
*
while downloading 2 torrents with more than 5000 pieces and a leecher count > 10 for each file
i see the problems with the 'text-based' progressbar for pieces. The CPU usage increases
enormously on every refresh intervall of the browser. shit happens!
thought this becomes a immediately point on the toDo list.
I know this string want bite me often but why so soon?!
following is the content of a 'text-based' progressbar string with > 5000 pieces.
For a better printout i replaced completed parts with 'x', incompleted parts with '-'.
'o' shown the parts we currently requesting from this clients.
xoxxxx-xx--x-x-xx-xx--xxxxxxx-x---xx-xxxxxxx-xxxxxxx--x-x-xx-x-xxxxx--xxx--x
-xxx-xx--xxxxxxx-xxxxx-x-xx-x---xxx--xxxx--xx-xxx-x-x--x-x--x--x-xxxxxxx---x
-xxxxxxxxxx-x-xxx-xx-xxxx---x-x-xxxxxx-x--x-xx--xxxx--x-x-xxx-xx-xx--x-x-xxx
xxxxxxxx-x--xxx--x-xxxxx-xx-xxxxxx---xx---xx-x-xxxxx-xxxxx-xxx------x-xx-xx-
--xx----xxxx--xxxx-xx-----xxx-xxx--xxxxx-x-xxxxxx-x---x----xx-xxx-x-xxxx-xx-
xx--x--x--x--x-x--xxxxxx-x-xx-x-x-xxx--x---xx---x---xx-xxxx--xxxxx---xxx-xx-
xx-x-----xxxxx--xx-xxxxx----x-----xxxx-x--xxx-x-x-xxx-xx-xxxxx---x---xxxxx--
-----xxxxx--xxx---xxxxxx-xx-xx-x-xxxxxxx---xx-x-xxxx-xxx-x-xxxxxx-x---xxx---
x---x-xxx-x---xx-xxx-xxxxxx-xxxxx---x-xxxx-xx---xxxx-xx-x-xx--xxxxx-x---xxxx
xxxxxx-xx-xxx-xxx-xx--xx-xxxxxxx-xxxxxxxx---xx-----x--xxxx-xxxx-xxx-x--x-x-x
x-xxx-xxxx----x--xx-x-x-xxx--xxxxx---xxxxxx--xxxxxxx---xx-xxxx--xxxxx-xxxx-x
-x-xx----xx-xxxxx-xxxxxxxxx-x-xxxx-x-xxxx--xxxxxx--xx-x-xxx--xxxxx-xx-xxxx-x
--xxx---xxxxx-x-xxx--xxx-xx-----xx-xxx-xx-x-xxxx---xx-x-x-x--xx-x-xxxxxxxxxx
-x-x---xx-xxxxxx-xxxx-xxxxxxxxxx-xx--xxxxxxx--xx-x-xxxxxx-x--x-xxx----xx---x
x--x-xxxx-xxx-x-x---x-xx-xxxxxxxxxx-xxxxx-xxxxxx-xx-xx--x---xxx--xx-xxxxx-xx
xxx--xxx-x-x-xx----xxx---xxx-x--xx-xxxxxxx-x--xx-x-x---xx-x-xxx-xxxxxx-xx-x-
x-----x--xxx----x-x---xxxxx-xxx-xxx-x-xx-xx-x-x----xxx---xx-x--xxxxxxx---x-x
xx--xxxxx-x-x-xxxx--xxxxxxx-x-xx-xx-xx-x-x---x---x----x-xxx-xxx-xxxxx--xxxxx
xx-xxx-xx-xxx--x-xx-x-xx-xxx--xx-x---xxx----x-xxxxx-xxxx-xx-xxx-xx-x----xxx-
x-x---x-xxxxxxx-xxx---xxxxxxx-x-xxxx----x--x--xxxxxxx---x--xx--xxxxxxxxx-xx-
-x----xxxxxx-x-x-x----x-xx-xxxxx-xxxx-x--xxx--xx-xx-x-xx----x----x-----xxxx-
xxx-xxx-xxx---xxox-xx--xx-x--x---x-x-----x-xx-xxxxxxxx-xxxx----xxxx-xxxxxxx-
-xxxxx-xxx-x--xx---xx--x--xx--x-xx--x-x-xxxx-x-x---xxxxxxxxx-x--x-x-x-xxx-xx
x--xx-xxxxxx----x-xx----x--x---x-xxxxx---xx-x-xxxxx-xxxx-x-xxxx-xx--xx-xx--x
-x-xxx-xx-xxx-xxx----xxx-xxxxx-xx-xxxx--xxx-x-x-xx-xxx-xxxxxxxxx--xxx--x-x-x
-xx-xxx-xx--x-x---xxxxx-xxxxxx-x-xx----x-xxxx-x---x--xxxx--x-xxx--xxxx-xxx-x
-xx--xx-x--xxxx-xxx--x---xx-xx--xxxxx-x--xx---x--------xx---xxxxxxxx-x-x-xx-
x-xxxxxx-xxxx--xxxxxxxxx--x--xxxx-x--xxxxxxxxxx-xxx--xxx-x-xx-xxx-xx-x-xxxxx
-xxx--xxxx-xx---xx-xxxxx-x---x-x-xx-xxx-x-x-xx-x-xxx-xx-xxxxx-xx-x--xxxxxx-x
x---xxxx-xx---x---xx--xxx----xxxxx----x--xxxxx-x-xxx-x-xxxx-xx-x---xxxx-xxx-
-xxxx-x-x-x-x--xx--x--xxx-xx-xxxxxxx---xx-xxxxxxxxxx-xx-xx-x-x--xxxxxxxx--xx
--x---xx--x--xxx---xxxxxxx-x--x-xxxxx--xxxxx-x-xxx----xx-xx-xxxxxxxx-x-xx-x-
x--x--xxxxxxxxxxxx---x-xxxx--x---x-xxxxxxxx----xxxxxxxxxxx--x----x--x-x-xx-x
xx-xx-xxxxxxx-x-x-xxx--x-x-xx--xx-xxxxxxxx--xxxxxx---x-x-xxxxxx--xx-xxx-xxxx
xx-------xxxxx---x-xxxx-xxxxx-xx-x-x-x-x-xxxxx-xxxxxxxx--xxx-x-xxxx--xxx-xxx
x-xxx-xx-x-x-xxxxxxx-xx-xx-xxxxxxx-xxxxx-xx---x-xxxxxxxxx-xx-x-xxxxxxx--x-xx
-x---xxxxxx-xx--xxx-x---xxx-x--xxx-xxxxxx---xxxxxxxx--xx-xx-x-x---x--xxxxxx-
-xx---xxxxx--xx---xxx-xxxx-x-x----xx-xx--xx--x--x-x--x-x-xxx-x-xxxxxxx--xx-x
xxxx--x--xxx-x-xxxxxx--x----x----xxx--xxx--x-x---x--x-----xx-xx-x-x--xxxxxxx
x-xx--xxxx-xxx-xx-xxx-x-x-xxx--xxx-x-xx---xx-xxxxxxxx--xx--xxxxx-xxxx-xxx-xx
xx-xx-x-x--xx---x-xx-x-xx--xxxx-xxxx--x-xxxx-x-xxx-xxxxxx-xxx--xx--xx-x--xx-
xxxxxxxxxxx--x-xxx-xx-x-xxxxxxxxxx-xx--xxx-x--xxxx-x-x-xxxxxxxxxxxx-----x-xx
--x-xxxxxx-x-xxxxxxxx--xx-x-xxx--xxx-xxx-xxxx-xx--xx-xxx-xxxx-xxxxx-xxx-xx--
xxx----xx--x-xxx-xx-xxxxx-xx--xxxxx--xxxx---xxx-xxxx-xxxx-xxxxxxxx-xxx-xx-x-
--xxxxx--x-xx--xxxx-x--x--xxx-xx--xx-xx---xxx--x--xxx--x-xxxxx----xx-xx-xxxx
x--xx-x-xx-x-x------xx-xxxx--xx--xxx--x--xxxxxxx-x--xxx--x--x-x-xxxxxxx-xxxx
xxxxx-xxxx-x-xxxx--xxxx--xxxxxxxx-xx--xxx-xxxxxxxxx----xxx-xx-x--x---xxxx-xx
xxx-xxxxxxxx------x-xx-x-xx-xxxxx-x-xxxxx--x-xxxxx--xx-xx-xxx----xxx-x--x-x-
-xx-xxxx--xxxxxxxxx-x--x-xxx--xxxx-xxx-xxxx--xx--x-x-x-xx--xxxxx---x-x-x---x
-xxxxx-x-x-x--xxx-xxxxxxxx-xx-x--xxxx-xxx-xxxx-xx-------x--xxxxx----x-x-xxx-
xx-xx-xxxx-xxxx--xxx--xx--xxxxx-xxx-xxxxxxxxxxxxx-xx-x---xx--x-xx-xx---x-x-x
xx-x-x-xx-xxx--xx-xx--xxxxx--xx-xx-xx-xxxxxx-xxxxxx-xxxxxx-xx---x-xxxxxxxxx-
x-xxxxxxx-x-x-xxx-x-x-xxxxxx-xx-x-xx-xxx---xxxxxxxxx-xxx-xx---x-x---xx--x--x
-xx-x-xxxxx-xxxx-xx-xxx-x-xxxxxx-xxxxxxx-xxxx--xxxxx--xx-x-xxxxxxx-xx-xx-x--
xxx---xx-xxx-x-x--x-x-x-x-xx-x--xxx-xxxx-xxxxx-x-xxxxx-xx--xxx-x-x-xxxxxxx-x
xx---xxx-xxx--xx-xx--xxxx--xxxx-xxx--x--xxxxxx---x-xx-x-xx-xxxxxx-xx-x-x--xx
x-xxxxxxxxxxxxx-xxx-xxxx-xxxxxxx-xxxx-xxx--x-xxxx---xxxxxxxxx-xxx-xxxx-x-x-x
xxxxxxxx-xx-x------xxx-xx-xx--xxx-xxxxxxxxxxx--x-x---xxxx-----xxxxx---x-x-x-
xx-xx-xxx-x-xxx-x-x-xxxxxxxx-xxxxxx-x-xxxx-x-x-xx-xxx-xxxxx----xxxx-x-xxxxxx
xx-xxx---x-xx-xxx-xxx-x-xxxxxxx-xxxxx-x-x-xxx-x--x-------x--xx-x--x-xx-xxx-x
--xx----x--xx-x-------xxxxxx-xx-x---xxx--xx--xx-xx---xxx--x-x---xx--xxx-xxx-
--xx-x-xxx---xx-xxxxxxxx-x-x-xxxxx-xxxx-x-xx-xx-x--x--xxxx--xxxxxxx-xxx--x--
xx-xxx-x-x-x-xx--xxx-xx----xxxx-xxxxx-xx---xxx-----xx---x--xxxx--xx--xx-xxx-
xx--xxx-xx-x--xxxxx-xxx--x-xx-x-xx----x-x--xxx-xxxxx-x-x-x-x---x-x----x-xx--
xx-xxxxxxxxxx--x-x-xxx--xxxx-xxxx-----xxxxxxx-xxx-x-x-x--xxxx-xxx--xx-------
x-x----xxxx--x--x-xxxxxxxxx-xxxxx--x--xx-xx--xxxxxxxxxxx-xxxx---x--xxxx-x-x-
x---xxxx-x--xxxxx-xx-xxx--xxxxxxxxxxx-x-xxxxx-xx-xx-xxxxxxxxxxxxx---x---x-x-
--xxx-x--xxxx-xxxxxxxxxx-xxx--xx-x-xx-xxxx---xxxx--xxxxx-x----x-xx--x---xxxx
-xx-xxx-xxxx-xxx---xx------x-xxx--xx-xx-xxxxx-xxxx--xx-xxx-xx-x-x-xxxx-xx-xx
xxxxx-x-xxx-xx-x-xxx-x-x---xxxx-xx---xx--xxx--xxx--xxx-x-xxxxxxxx-xx-xxx-xx-
x-xxxx-x-xxx-xx-xxxxx-xxx--xxxxx-xxxxx--xxx--xxxxxxxxxxx--x-xxxx-x-xxxxx----
-x-x-x-x--xxxx---xx-xx--xxxx---xxx--xx-xxx-xxxx-xxxxx--xx-xxxx-x--xxx-x--xxx
xx----x-xxx-xxx----xxx--x-xxxxx-xxxxx-x------xx--xxx-xxxx--x--xxx--x-xxxx-xx
--xxx-x-x---x-x-xxxxx--x-xx--x-x----xx-x-xxxxx
3. aug 2008
made the new theme 'guru' to get a new look'n feel and to see what keywords are missed for next toDos.
*
made the new theme 'guru' to get a new look'n feel and to see what keywords are missed for next toDos.
2, aug 2008.
- inserting in Faq a HowTos 'How can i make my own themes?'
- extending the Faq 'Why should i use multiple bt-clients?' (thanks to stereotype)
*
- inserting in Faq a HowTos 'How can i make my own themes?'
- extending the Faq 'Why should i use multiple bt-clients?' (thanks to stereotype)
2, aug 2008.
Update latest source.
i2psnarkxl-20080802_md5-147be05c7cf8d87682cd67293dccf3b2-.zip ~ 289 KB
md5:
147be05c7cf8d87682cd67293dccf3b2
changes to previous zip-structure:
in the i2p/webapps folder is the file "[renameMe].war" instead the "i2psnarkxl.war"
rename it like you want for your installation and copy it to your "i2p/webapps" folder.
How to start the renamed war-file:
copy it to your "i2p/webapps" folder
restart i2p
client access:
http://127.0.0.1:7657/[renameMe]/
for the themes use:
http://127.0.0.1:7657/[renameMe]/?themes=jama
http://127.0.0.1:7657/[renameMe]/?themes=minimalist
in the link replace "[renameMe]" with the name of the war-file without ".war"
example:
rename "[renameMe].war" to "i2psnarkxl.war" then the link is
http://127.0.0.1:7657/i2psnarkxl/
for the themes use:
http://127.0.0.1:7657/i2psnarkxl/?themes=jama
http://127.0.0.1:7657/i2psnarkxl/?themes=minimalist
if you add the client with a new name to get a new multiple client then
you have to press once 'save configuration' after your first access to
http://127.0.0.1:7657/i2psnarkxl/
if you wanna use the themes then I2PSnarkXL expects that the following templates-path exists
i2p/templates/i2psnarkxl/jama/*
i2p/templates/i2psnarkxl/minimalist/*
and the jetty-server expects for resources in i2p/docs/themes/
i2p/docs/themes/i2psnarkxl/jama/*
i2p/docs/themes/i2psnarkxl/minimalist/*
all is included in the zip-archiv!
*
Update latest source.
i2psnarkxl-20080802_md5-147be05c7cf8d87682cd67293dccf3b2-.zip ~ 289 KB
md5:
147be05c7cf8d87682cd67293dccf3b2
changes to previous zip-structure:
in the i2p/webapps folder is the file "[renameMe].war" instead the "i2psnarkxl.war"
rename it like you want for your installation and copy it to your "i2p/webapps" folder.
How to start the renamed war-file:
copy it to your "i2p/webapps" folder
restart i2p
client access:
http://127.0.0.1:7657/[renameMe]/
for the themes use:
http://127.0.0.1:7657/[renameMe]/?themes=jama
http://127.0.0.1:7657/[renameMe]/?themes=minimalist
in the link replace "[renameMe]" with the name of the war-file without ".war"
example:
rename "[renameMe].war" to "i2psnarkxl.war" then the link is
http://127.0.0.1:7657/i2psnarkxl/
for the themes use:
http://127.0.0.1:7657/i2psnarkxl/?themes=jama
http://127.0.0.1:7657/i2psnarkxl/?themes=minimalist
if you add the client with a new name to get a new multiple client then
you have to press once 'save configuration' after your first access to
http://127.0.0.1:7657/i2psnarkxl/
if you wanna use the themes then I2PSnarkXL expects that the following templates-path exists
i2p/templates/i2psnarkxl/jama/*
i2p/templates/i2psnarkxl/minimalist/*
and the jetty-server expects for resources in i2p/docs/themes/
i2p/docs/themes/i2psnarkxl/jama/*
i2p/docs/themes/i2psnarkxl/minimalist/*
all is included in the zip-archiv!
2, aug 2008.
- extending the Faq
- adding a link for the latest source on the mainpage
*
- extending the Faq
- adding a link for the latest source on the mainpage
2, aug 2008.
vers. 0.6.2-9
The problem of lossing datas is still given in I2PSnark and I2PSnarkXL.
After a restart of I2P with cleaned up all I2PSnark*.config's brought back ~700mb in 3 current downloads.
*
vers. 0.6.2-9
The problem of lossing datas is still given in I2PSnark and I2PSnarkXL.
After a restart of I2P with cleaned up all I2PSnark*.config's brought back ~700mb in 3 current downloads.
1, aug 2008.
After i edited some lines to this webpage i've continuing the work on I2PSnarkXL.
I added some stuff to integrating a progressbar for pieces and it seems to work.
the only problem i got with the minmalist-theme because i like to have the
minmalist-theme as an example without any resources except pure Html-code.
So i include a keyword for a "text-based" progressbar for the torrent pieces.
but now i got a problem! ... has anybody an idea how to shorten a String for the
big-files with 1000 - 4000 pieces ... and to include it in a webpage of
1024 x 768 or 1200 x 1024 pixel ... and the overflow tag with scrolling doesn't
work like expected with different Browsers. thought that this problem will bite me
more often at the future
i'm not a great artist for webdesign so take the examples like they are .. just
as example and not as exhibit to winning a Oscar for art and design.
*
After i edited some lines to this webpage i've continuing the work on I2PSnarkXL.
I added some stuff to integrating a progressbar for pieces and it seems to work.
the only problem i got with the minmalist-theme because i like to have the
minmalist-theme as an example without any resources except pure Html-code.
So i include a keyword for a "text-based" progressbar for the torrent pieces.
but now i got a problem! ... has anybody an idea how to shorten a String for the
big-files with 1000 - 4000 pieces ... and to include it in a webpage of
1024 x 768 or 1200 x 1024 pixel ... and the overflow tag with scrolling doesn't
work like expected with different Browsers. thought that this problem will bite me
more often at the future
i'm not a great artist for webdesign so take the examples like they are .. just
as example and not as exhibit to winning a Oscar for art and design.
31, jul 2008.
Registering key on stats.i2p and starting the eepsite i2psnarkxl.i2p today.
After burst of enthusiasm, now i sitting here and starring on the empty screen without knowing how i
should start, what's to do at first ... crazy world.
... after a long while of starring at the still empty editor ...
stealing some sentences from complication.i2p for the faq.
***Registering key on stats.i2p and starting the eepsite i2psnarkxl.i2p today.
After burst of enthusiasm, now i sitting here and starring on the empty screen without knowing how i
should start, what's to do at first ... crazy world.
... after a long while of starring at the still empty editor ...
stealing some sentences from complication.i2p for the faq.