zzz
dr|z3d, StormyCloud, you really want the CSS to require a 346 KB font file with your little 2 KB checki2p.com page?
zzz
StormyCloud, how about supporting an RPC compatible with check.torproject.org/api/ip ?
StormyCloud
@zzz the font file is me, dr tried to convince me to use something smaller. Ill try to reduce it
zzz
I would just scrap it.
StormyCloud
Ill also checkout what it would require to implement RPC
zzz
the font is so important you're increasing the size of the page by 150x ?
zzz
StormyCloud, see also 2 emails
StormyCloud
Yes I just got your email's, ill respond once I have my morning fuel.
StormyCloud
I removed the font, it brings the loading time from 330ms to 208ms. Cant imagine anyone is noticing 100ms of loading speed tho
zzz
I've seen it take several seconds
zzz
the whole point is that it should be a tiny resource
StormyCloud
Well the whole website is now 12kb
zzz
:)
StormyCloud
Once I get fuel ill respond to your email and research implementing an RPC or API to check
zzz
I'd suggest you float it by eyedeekay to see if there's a possible user for an API in our easy-install bundle
zzz
or where else there may be some consumer for it
zzz
no use doing it unless you can find a user
not_bob
It's a good check to see if your outproxy is working.
not_bob
Short of going to an address thave gives you your visible IP and having to know which ones belong to i2p outproxies.
dr|z3d
zzz: nothing to do with me, the css. leave me out of it :)
zzz
as he said
dr|z3d
just be thankful you're not downloading a 3000x2000 bitmap logo..
zzz
apologies, didn't know, tagged you both
zzz
sorry to bother you
dr|z3d
is fine. and I've already had the conversation with StormyCloud about the font. waste of space I told him, but he didn't want to listen.
zzz
now he is
dr|z3d
apparently a second voice telling him the same thing made him see sense. so well done :)
zzz
sometimes the 2nd one in wins, yes
StormyCloud
Figured two people cant be wrong
dr|z3d
reading the backlog, the something smaller part of the font equation was "use OS-resident fonts".
dr|z3d
it's a good metric to consider, how big is the font in size relative to the total size of the content on the site.
dr|z3d
if it's a font that downloads once, stays cached, and is used on multiple pages, then it's maybe worth the size increase.
dr|z3d
of course, if you're only using a few glyphs from the font itself, you can always trim out the crud, the extended character set(s) etc. I use 2 fonts on skank, the total size of which is ~ 11K.
not_bob
There are some sites on I2P that use huge background images. It's strange.
eyedeekay
StormyCloud if such an API is available over HTTP(or S) then it can actually go right into the WebExtension I2PIPB, which would give it the broadest coverage
StormyCloud
Working on something now, should have a rough draft here shortly for testing
StormyCloud
Would it be preferred to have a separate link (checki2p.com/ip) or to just curl the checki2p.com with json headers?
StormyCloud
I have a working test for yall | curl -H "Accept: application/json" checki2p.com/index_test.php
eyedeekay
Another day, another gitlab security release...
eyedeekay
Thanks StormyCloud, works from here
eyedeekay
As soon as the API is in it's final location I can use that to report back in browser extension, browser profile, easy-install
StormyCloud
So I can integrate the function on the main site (checki2p.com) and if a user adds the json header it can report back in json or if they go via http it shows the website. Or we can just do something like checki2p.com/api and only provide json answer. Whatever the team thinks is best Im open to either option
eyedeekay
Personally I would vote for separate API and web endpoints
zzz
agreed
zzz
why not do it exactly the same, api/ip, complete with IsTor=true in the json
StormyCloud
Sure thing ill get this updated
zzz
but don't listen to me... it's between you two
zzz
maybe IsTor=true, IsI2P=true, IP="..."
StormyCloud
Alright completed please check and let me know if you think any changes are needed. checki2p.com/api/ip
eyedeekay
Thanks StormyCloud still tests fine from here, I'll add it to the extension this week