~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%Liorar
%cumlord
+FreefallHeavens
+Xeha
+ardu
+bak83_
+hk
+poriori
+profetikla
+r00tobo_BNC
+uop23ip
+weko
Arch2
BubbRubb
Danny
DeltaOreo
Irc2PGuest33321
Irc2PGuest33419
Irc2PGuest46100
Irc2PGuest53192
Irc2PGuest59461
Leopold
Meow
Onn4l7h
Onn4|7h
SigSegv
acetone_
boonst
duck
kidsoldier
maylay
phobos_
pisslord
qend-irc2p_
radakayot_
shiver_
simprelay
solidx66
thetia
tr
u5657
woodwose
zer0bitz
zzz
thanks for testing and merging those 3 PRs. I added notes to the original PRs so reviewers know which ones you've tested
zzz
I'm currently sidequesting on EepPost...
dr|z3d
no problemo, no issues I've seen, all appear to work as intended.
dr|z3d
did postman send over his draft api?
zzz
da
dr|z3d
great
zzz
he's basically rejecting all my suggestions though
not_bob
:(
dr|z3d
like what?
zzz
we'll see
zzz
using various standards or examples as a starting point
zzz
that's fine, he's got a vision I guess
dr|z3d
sure, he's not attempting to set a global api standard, so if it works, it works :)
zzz
my point was it could make testing easier for him, and impl easier for us, but oh well
zzz
remains to be seen if access is best done from js or java. If js, no EepPost needed. Depends on the use case which isn't really clear yet
zzz
but sounds like no login will be required once you have your API key, so java-side is at least feasible
dr|z3d
java for the posts, js for the in UI updates.
zzz
maybe
cumlord
looks like can do search feature at very least and hash/ID conversion
cumlord
i will add to the bot in #torrents :)
dr|z3d
the idea is to be able to search by keyword, for example, and have results returned in snark.
cumlord
that's what i was hoping, it'd be a nice feature
zzz
yeah but I don't know if it's in the same search form as now, or a different one, where the results go, is it search-as-you-type or not, ...
dr|z3d
same search form, with a toggle for local/remote.
dr|z3d
search as you type, probably not.
zzz
you sound confident in all your answers... me, not so much
dr|z3d
well, you don't want to make the UI any more convoluted that it needs to be, so re-using existing elements is always a good idea.
dr|z3d
search results can be presented in the main view, with slight modifications to the column headers and action button column.
cumlord
upload through snark could also be a neat feature but ig that would require EepPost
dr|z3d
that's what zzz's planning, supported post requests in eepget.
dr|z3d
*supporting
RN
*** giggles at "<dr|z3d> well, you don't want to make the UI any more convoluted that it needs to be..." ***
cumlord
ohhh
cumlord
i wouldn't know what to do for upload with ui, lot of inputs
dr|z3d
*** applies a controlnet filter to RN and turns her into a strawberry/potato hybrid. ***
dr|z3d
upload will require a new form and presentation. no way around it.
zzz
what can the #torrents bot do now?
RN
*** potatoeberries ***
cumlord
it gives rss feed from tracker2/simp, search and metadata retrieval from simp only, and scrapes known trackers for a given infohash
cumlord
also provides online tracker list
zzz
is simp going to support the postman API?
RN
<3 the rss feature
T3s|4
lols at the Dan Qualye ^potato spelling ;p
cumlord
yes going to do it the same way
RN
*** nods at T3s|4 ***
cumlord
although, it will be missing some fields and i'll likely need to rework some things
zzz
side quest complete, I have a working CLI EepPost, in 3 modes (formdata, mutlipart, and plain text)
dr|z3d
very excellent.
zzz
for snark, would need a I2PSocketEepPost variant
dr|z3d
can it encode binary to base64?
dr|z3d
maybe it doesn't need to? maybe that's handled elsewhere?
zzz
no, I chased that rabbit hole, but unlike for email, binary is the standard for http post
dr|z3d
yeah, but json.
zzz
same thing.
zzz
if you wnat binary in your json, you'd encode it before giving it to EepPost
zzz
or else its not valid json
dr|z3d
ok, so we handle encoding outside of eepget.
dr|z3d
I think I linked postman to this, re binary in json: itoolkit.co/blog/2023/06/how-do-you-send-binary-data-in-json
zzz
right, eeppost knows nothing about json
dr|z3d
roger that.
zzz
well, the transmission-remote API is one way, but that was one of the rejection suggestions...
dr|z3d
that looks like it would involve re-encoding the torrent. I think postman just wants to take the torrent file as-is.
dr|z3d
if we use bas64, what we add to the filesize with the encoding we can mostly claw back with gzip.
zzz
there's no choice but to b64 it to be valid json
zzz
there's no gzip support in EepPost, not sure if worth it
dr|z3d
effort vs reward. it shouldn't be too much effort to add gzip support, should it?
dr|z3d
as for reward, other than for postman, not sure where gzip'ing post requests would win us much, but who knows? maybe someone uses it as part of an uploader/fileshare feature where gzip might be handy.
zzz
no? my median .torrent file is about 20KB
dr|z3d
yeah, most are fairly small, though postman's mentioned 2MB torrents.
zzz
and torrent files generally are not compressible since they're mostly hashes, but you would get back the b64 penalty, as you say
zzz
most torrents I see these days seem to have 1024 or 1025 pieces, with a non-power-of-2 piece size. That keeps the size right at 20KB
zzz
don't know when that changed but back in the day everything was power-of-2, and snark still does that