#saltr (irc2p) | I2P+ 2.5.2+ >> i2pplus.github.io | skank.i2p | git.skank.i2p | purokishi.i2p | vituperative.github.io/i2pchat | natter.i2p | notbob.i2p | ramble.i2p | shreddit.i2p | cake.i2p | /msg an op for voice

T3s|4 yep dr|z3d - on Win it looked like everything was running as expected, then seeing something like: Update available...attempting to d/l now. However, never saw the usual Contacting i2p+ server dialog/progress bar in the side panel. Perplexed, indeed :)

dr|z3d T3s|4: if you want to try something, you could rename your config dir with i2p stopped, then start it and see if a new profile fixes.

T3s|4_ alright, that'll be my next test when I'm back on Win

T3s|4_ dr|z3d: thanks good for everyone to know that Zuck remains as untrustworthy as ever ;p arstechnica.i2p/security/2023/07/how-threads-privacy-policy-compares-to-twitters-and-its-rivals/3

T3s|4 dr|z3d: stopping, renaming ProgramData\i2p, then restarting had no impact, other than seeing No update available after many attempts

Quaddle H T3s|4

Quaddle I can not visit i2p sites. Can you throw in a word, what to check ?

T3s|4 Quaddle what are your browser's proxy settings set to?

T3s|4 he ^left ;(

dr|z3d interesting, T3s|4. hmm.

dr|z3d any change in the location of the config dir as indicated on /info?

T3s|4 dr|z3d: too late to check that now, back on Arch. Will have a look next time

dr|z3d ok

dr|z3d not important given the no change in update checks/downloads

Invizzy hello everyone!

Invizzy So I've been struggling to understand this concept all day, but how exactly does DNS work within networks such as I2P? For an example, an internet connection must be available for these systems to communication, but in terms of DNS how would this work? It must pass through the ISP correct?

Invizzy Perhaps I am merely overthinking this as it must pass through the ISP to reach the outside, but how does it know where to go if the all data is encrypted and hidden from the ISP?

uop23ip Invizzy, geti2p.net/en/faq#addresses maybe this will help

Invizzy uop23ip: Thank you! I completely forgot about the FAQ smh

dr|z3d dns requests for .i2p hosts are processed in network, Invizzy. If they're reaching your dns provider, local or isp or otherwise, then you have a leak.

Invizzy dr|z3d: Thank you for the clarification! Fortunately, I don't believe that I've been experiencing any leaks.

Invizzy Also, is there any significance behind the reasoning for I2P+'s .i2p site name? lol

dr|z3d a skank is a Jamaican dance. other than that, not really :)

Invizzy Ah, because I sort of interpreted it as the insult lol

dr|z3d we have layers, encrypted layers :)

Invizzy Better to wrap it up in layers rather than none :)

dr|z3d en.wikipedia.org/wiki/Skank_(dance)

dr|z3d if you're running I2P+ Invizzy, you may want to consider using the /dev/ update path for in-console updates.

Invizzy I'm currently running I2P+ dr|z3d! I might give it a try. Would there be any potential de-anonymization's to running a router with a /dev/ build?

dr|z3d None. As far as your router is viewed on the network, it's just a standard release version.

dr|z3d Very occasionally there may be a feature that, to those that are looking hard enough, indicates your router's running a dev build, but it's fairly unusual, and for the most part I'll hold off incorporating the patch if it's a serious risk.

dr|z3d That being said, there are enough I2P+ routers on the network running dev builds, so the risk is pretty much non-existent.

dr|z3d the advantage to running dev builds, otoh, is that you tend to get fixes and enhancements sooner.

Invizzy Interesting. Are there any /dev/ patch notes to see the new patch features?

dr|z3d this will give you a breakdown of all the changes: gitlab.com/i2pplus/I2P.Plus/-/commits/master

dr|z3d another minor thing to note, as of 2.3.0, all dev builds are now supplied as pack200 update files, so they're ~50% smaller than a standard update, or about 33% smaller than a full release update.

dr|z3d not 33% smaller, sorry, 33% of the size or 66% smaller.

dr|z3d standard release update -> 15MB, standard dev update -> 11MB, dev update with pack200 -> 5MB.

dr|z3d sometimes dev builds are bigger, usually when a new geoip database is included.

Invizzy That seems pretty nice and should hopefully have a positive impact across the network with less bandwidth constraints.

dr|z3d how it used to be until Oracle retired pack200 with java 14. and then I pulled the pre-14 pack200 back into the console. :)

dr|z3d *it used to be that way as standard

Invizzy Odd. I don't have much experience with Oracle/Java but I was thinking of diving a little bit into Java. I've also never heard of pack200 either.

dr|z3d en.wikipedia.org/wiki/Pack200

Invizzy That seems pretty cool! Didn't know there was essentially compression methods for specifically for JAR files.

dr|z3d live and learn :)

dr|z3d as mentioned, it's now deprecated, but I2P+ brought it back to life :)

dr|z3d I figured a 50% saving for dev updates was worth the trouble.

Invizzy I would like to hopefully become certified in Java development. I'm still fairly new to programming though, but hopefully that'll give me a nice boost.

Invizzy If it's deprecated, would that mean that there's a possibility for vulnerabilities if it's not being maintained?

dr|z3d unlikely.

dr|z3d it was fully formed and road tested before it was deprecated. and there's no way to exploit it, anyways. it's just a packer/unpacker.

Invizzy Interesting. I wonder why the deprecation if it was fully functional and seemed to do great for its purpose.

dr|z3d powers that be at Oracle decided the benefits weren't worth the effort to maintain. and on fiber, they're probably right. but i2p usecase is a bit different.

dr|z3d oreilly.com/library/view/java-11-and/9781789133271/ae93e8f2-004e-4d6c-bcbe-8ce9c0b2247a.xhtml

dr|z3d "Introduced in Java 5, pack200 was a compression scheme for JAR files. It was used to decrease the disk space and bandwidth demand when Java programs were packaged, transmitted, or delivered. Developers used pack200 and unpack200 to compress and decompress the Java JAR files."

dr|z3d "However, these are becoming irrelevant in today's modern storage and transmission improvements. JEP 336 deprecates the pack200 and unpack200 tools, and also the corresponding pack200 API."

Invizzy Of course! It almost seems like a great revival story for something as simple as a compression tool being used for anonymity networks to push out updates.

dr|z3d Quaddle: proxy fixed?

Quaddle No, i am in targeting it with RN on salt

dr|z3d ok

Quaddle You can weigh in as you like mate