dr|z3d
new UI feature in 119+ for those on + dev builds. in-situ tunnel control in the tunnel manager.
dr|z3d
-120+ uploaded.
zzz
fixed my other bad sql bug from a month ago - reversed params
dr|z3d
making headway with sql, zzz?
zzz
dr|z3d, you were right, WAL mode was the magic, 100x speedup in sql writes
zzz
so yeah
dr|z3d
working on susidns addressbooks?
zzz
right now I'm just playing with it standalone
zzz
will take some more work to turn it into a plugin, import everything from blockfile, stop blockfile and start sql
zzz
but doable
dr|z3d
what's the projected benefit?
zzz
very little
zzz
not sure if faster.
zzz
should be more crash-resistant
dr|z3d
do we see many blockfile crashes? haven't see (m)any here.
zzz
never
dr|z3d
so maybe you're working on the wrong component.
zzz
we do have an elaborate fixup that's always run at startup, so not sure we'd ever know
zzz
learning experience only
zzz
may someday get ported to android but probably not by me
dr|z3d
conceivably susimail migt be a better fit.
dr|z3d
or blocklist management in the router.
dr|z3d
or snark metadata. anything where we're current using multiple flat files.
dr|z3d
netdb, even.
zzz
the problem with non-plugin, non-android, is that it requires native libs in a 13 MB jar, so that's a nonstarter
dr|z3d
this is nosql?
zzz
can't have the router not come up because the user is on some weird arch not supported
zzz
no this is native sqlite3 wrapped by github.com/xerial/sqlite-jdbc
dr|z3d
fallback to whatever we have now after testing for compatibility if fail, no?
zzz
thats not sql
dr|z3d
It's nosql.
zzz
there's also hsqldb that we used in syndie but I found that super glitchy
dr|z3d
you never answered my question about what you're using right now. nosql, sqlite, or something else?
zzz
the goal w/ sqlite3 was to prototype something that could be ported to android
zzz
sqlite3
dr|z3d
ok, sqlite.
dr|z3d
have you looked at this? github.com/xerial/sqlite-jdbc
zzz
that's the link I posted above
zzz
which is what I'm using
dr|z3d
ah, ok, good, never saw the link.
dr|z3d
should be able to bring that jar down in size some.
dr|z3d
ppc64 for Linux can go.
dr|z3d
maybe the native code which is the bulk of the jar can be removed, and then the router just grabs the relevant arch when on first run after install. size should then be acceptable, since most of the size is the arch-specific stuff.
not_bob
PPC is dead.
zzz
true
orignal
dr|z3d apepi said you can include shmoogle.i2p to I2P+
orignal
it's 24/7 now
not_bob
Nice!