Blog on I2P - The Invisible Internet Project

I2P 2.11.0 Release

Mon, 09 Feb 2026 00:00:00 +0000

As of this release, I2P now requires Java 17 or later. Please consult your operating system’s documentation for how to update Java. I2P now also uses Jetty 12. Please check your router logs for migration issues.

Work in this release continues to improve support for post-quantum cryptography. Post-Quantum crypto is now enabled at the ratchet layer by default.

We have implemented the first round of mitigations to the ongoing spam attacks. Additional mitigations are being developed.

Stormy Weather

Wed, 04 Feb 2026 00:00:00 +0000

The I2P network is currently experiencing instability due to ongoing Denial-of-Service and resource exhaustion attacks. These attacks are impacting the performance and reliability of I2P services and hidden sites. The I2P Development Team is actively investigating and implementing mitigations to counter these attacks.

Introducing the New I2P Website

Tue, 06 Jan 2026 00:00:00 +0000

Launching the Redesigned I2P Website

We are pleased to announce the launch of the redesigned I2P website. This update is the result of a focused effort to make I2P easier to discover, easier to understand, and easier to contribute to—without compromising the values the project is built on.

This work is primarily aimed at the I2P community: long-time users, contributors, developers, researchers, and those discovering I2P for the first time and trying to understand how it fits together.

StormyCloud Joins the I2P Family

Sat, 01 Nov 2025 00:00:00 +0000

We’re excited to share important news: StormyCloud is officially joining forces with I2P in a significant way.

For years, StormyCloud has been a critical part of I2P’s infrastructure, providing hosting and support that keeps the network running smoothly. Now we’re formalizing that partnership and expanding what we can do together.

We’re particularly glad to announce that Lance James and idk are joining StormyCloud’s Board of Directors. Lance founded the Invisible Internet Project, which evolved into what we now know as I2P, and his experience building privacy-focused networks goes back decades. idk has been extensively involved in I2P development for years — if you use I2P, you’ve benefited from his work.

New I2P Routers

Thu, 16 Oct 2025 00:00:00 +0000

It’s an exciting time for I2P development, our community is growing and there are now multiple new, fully-functioning I2P router prototypes emerging on the scene! We’re very excited about this development and about sharing the news with you.

How does this help the network?

Writing I2P routers helps us prove that our specification documents can be used to produce new I2P routers, opens up the code to new analysis tools, and generally improves the security and interoperability of the network. Multiple I2P routers means that potential bugs are not uniform, an attack on one router may not work on a different router, avoiding a monoculture problem. Perhaps the most exciting prospect in the long-term, however, is embedding.

I2P 2.10.0 Release

Mon, 08 Sep 2025 00:00:00 +0000

Work continues on the implementation and deployment of post-quantum cryptography in I2P. In this release post-quantum cryptography is available but not turned on by default for new tunnels. Those of you interested in testing post-quantum support should enable it via the “Hidden Service Manager” under “Encryption Types.” Be sure to get in touch on #i2p-dev in IRC2P for help and to report any issues you encounter.

I2PSnark now supports UDP trackers. This should help the network overall by reducing the load of torrent trackers.

I2P 2.9.0 Release

Mon, 02 Jun 2025 00:00:00 +0000

I2P 2.9.0 is a maintenance release that includes bug fixes and work on new features.

What’s New

Thread usage has been improved to improve the performance of the i2ptunnel system. NTCP2 has been improved to resist probing attacks. The notification system has been integrated into more applications to provide better feedback to users from I2PSnark and the other applications. Automatic floodfill enrollment has been fixed. Users may observe increased resource usage when acting as floodfill. If this is not desired, floodfill mode can be disabled on the /config page.

I2P 2.8.2 Release

Sat, 29 Mar 2025 00:00:00 +0000

2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release. The bug primarily affects high-bandwidth routers.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

Release Details

Bug Fixes

Fix SHA256 double-free from Noise
Clear i2ptunnel bubble count when clearing status messages

Other Improvements

Reduce memory usage in BanlistRenderer
Use torrent name instead of torrent file name in notifications
Translation updates

SHA256 Checksums

7658f9ba7e28ab29ffeb3ec1909bf04f5ae391ee159980145ea01bd793c46f80 i2pinstall_2.8.2_windows.exe
cd606827a9bca363bd6b3c89664772ec211d276cce3148f207643cc5e5949b8a i2pinstall_2.8.2.jar
039b59fedd4a64aaeb6b74ab974310abdc9c08cb47ef1b8568c718965b50a485 i2psource_2.8.2.tar.bz2
71cef41d7184516e42c15dc5105e52ab19960affd571b636e767e8bf8c227075 i2pupdate_2.8.2.zip
15d886a9015dcf27ccc25e31b703ef6538b8b777176adf643dfe8ee0ba4984e0 i2pupdate.su3

2.8.1 Release

Mon, 17 Mar 2025 00:00:00 +0000

2.8.1 fixes accesses to local sites that were broken in 2.8.0. We have added notification bubbles to several applications in the console to highlight application messages. We fixed a tunnel test bug that may have been affecting tunnel reliability. The addressbook now has a new “latest” tab that displays the newest hostnames added from your subscriptions. There are several dark theme fixes and improvements.

We fixed the installer that previously failed on Java 21 or higher. We also fixed installing to directory paths that contain spaces on Linux. For those of you that use Docker, we updated outdated Docker container and container libraries.

I2P 2.8.0 Released

Tue, 04 Feb 2025 00:00:00 +0000

This release improves I2P by fixing bugs, removing unused code, and improving network stability.

We have improved handling of congested routers in the network. Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting. We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload. Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.

I2P 2.7.0 Released

Wed, 09 Oct 2024 00:00:00 +0000

This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.

Access to information from the console and applications has been improved. Issues have been fixed in I2PSnark and SusiMail search. The netDB search embedded into the router console now operates in a more intuitive and useful way. Minor improvements have been made to diagnostic displays in advanced mode.

Bugs have also been fixed to improve compatibility within the network. An issue with publishing leaseSets was solved which improves reliability major hidden services. I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent. This prevents torrents from being unnecessarily disrupted by these changes. We welcomed this contribution from a new contributor. A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.

2.6.1 Release

Tue, 06 Aug 2024 00:00:00 +0000

I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application. This bug caused scrolling to be disabled, rendering some configuration inaccessible.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

Release Details

Changes

Graphs: render graphs in svg
Translations: generate internal translation leaderboard

Bug Fixes

i2ptunnel: Fix bug causing truncation configuration UI

Other

Translation updates

Full list of fixed bugs

I2P 2.6.0 Release

Fri, 19 Jul 2024 00:00:00 +0000

This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network’s reliability.

Newer routers will be favored when selecting floodfill routers. I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes. Legacy transport protocols are being removed, simplifying the code in the UDP transports. Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability. Additional tweaks were made to peer selection strategies.

2.5.2 Release

Wed, 15 May 2024 00:00:00 +0000

I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

Release Details

Changes

Console: Update rrd4j to 3.9.1-preview
Router: Publish G cap if symmetric natted

Bug Fixes

i2ptunnel: Fix bug causing truncation of some HTTP content
i2ptunnel: Fix custom option form width (light theme)
Tunnels: Fix selection of peers with expired RIs

Other

Translation updates

Full list of fixed bugs

New Release I2P 2.5.1

Mon, 06 May 2024 00:00:00 +0000

I2P 2.5.1 is being released to address Denial-of-Service Attacks affecting the I2P network and services. With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack. This should help the network return to normal operation. Those of you who have disabled the Sybil attack detection tool may safely re-enable it. Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.

Stormy Weather

Thu, 25 Apr 2024 00:00:00 +0000

The I2P network is currently under a Denial-of-Service attack. This attack affects I2P and i2pd but in different ways and is having a serious effect on network health. Reachability of I2P sites is badly degraded.

If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability. Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.

New Release I2P 2.5.0

Mon, 08 Apr 2024 00:00:00 +0000

This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.

New features have been added to I2PSnark like the ability to search through torrents. Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent. We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support. New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails. Tunnels created with the Hidden Services manager now support “Keepalive” which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.

Many Masks, One Mind: Securing the NetDB

Fri, 29 Mar 2024 00:00:00 +0000

Author’s note: the attacks referred to in this article are not possible against current versions of I2P.

As a self-organizing peer-to-peer network, I2P relies on the routers participating in the network to have a way to share information about what is on the network and how to reach it. I2P routers achieve this information sharing using the NetDB, a DHT based on Kademlia but modified to work for I2P. The NetDB needs to share two main kinds of entries, “RouterInfos” which peers will use to communicate with other routers directly, and “LeaseSets” which other peers will use to communicate with I2P clients through anonymous tunnels. Routers are frequently commmunicating NetDB entries with eachother, either by sending the information to a router or client, or requesting information from a router or client. This means that the entries can arrive directly or indirectly, anonymously or non-anonymously, depending on the needs of the network and the capabilities of the client. However, as an anonymizing network, it is also important that it remain impossible for information sent anonymously to be requested back non-anonymously. It is also important and for information sent non-anonymously to be impossible to request back anonymously. If it becomes possible for either of those situations to occur, then a linking attack may be carried out which allows an attacker to determine if a clients and routers are sharing a common view of the NetDB. If it can be reliably determined that the 2 targets share a common view of the NetDB, then there’s a very good chance they are on the same router, weakening the target’s anonymity drastically. Because there are so few anonymizing networks, and I2P is the only one where the routing table is shared via the operation of a DHT, this class of attack is all but unique to I2P and its resolution is important to I2P’s success.

I2P 2.4.0 Release with Congestion and NetDB Security improvements

Mon, 18 Dec 2023 00:00:00 +0000

Update details

This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network. It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.

The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them. This will help the network limit the effect of tunnel spam. It will also help the network heal during and after DDoS attacks.

Easy-Install for Windows 2.3.0 Released

Mon, 10 Jul 2023 00:00:00 +0000

The I2P Easy-Install bundle for Windows version 2.3.0 has now been released. As usual, this release includes an updated version of the I2P router. This extends to security issues which affect people hosting services on the network.

This will be the last release of the Easy-Install bundle which will be incompatible with the I2P Desktop GUI. It has been updated to include new versions of all included webextensions. A longstanding bug in I2P in Private Browsing which makes it incompatible with custom themes has been fixed. Users are still advised to not install custom themes. Snark tabs are not automatically pinned to the top of the tab order in Firefox. Except for using alternate cookieStores, Snark tabs now behave as normal browser tabs.

I2P Release 2.3.0

Sun, 25 Jun 2023 00:00:00 +0000

This release contains fixes for CVE-2023-36325. CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter. An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client. The message, after passing through the bloom filter, is not allowed to be re-used in a second message. The attacker then sends the same message directly to the router. The router passes the message to the bloom filter, and is dropped. This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client. This has been fixed by separting the bloom filter’s functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly. Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives. Users of Java I2P are recommended to update immediately to avoid the attack.

I2P Release 2.2.1

Wed, 12 Apr 2023 00:00:00 +0000

After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages. This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package. Docker packages were not reading arguments correctly, resulting in inaccessible configuration files. This issue has also been resolved. The docker container is now also compatible with Podman.

I2P Release 2.2.0

Mon, 13 Mar 2023 00:00:00 +0000

We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023. This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks. The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.

About the recent Denial of Service attacks

Thu, 09 Feb 2023 00:00:00 +0000

The I2P network is currently being affected by a Denial of Service attack. The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping. Participants in the network have experienced difficulties connecting to I2P sites and using I2P services. Mitigation strategies are being investigated and implemented gradually.

While the attack has degraded performance, the network remains intact and usable. Java I2P routers appear to be handling the issues better than i2pd routers for now. Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.

I2P Dev Meeting - February 07, 2023

Tue, 07 Feb 2023 00:00:00 +0000

Quick recap

Present: eyedeekay, zzz, not_bob, echelonMAC, obscuratus

Meeting Log

(08:01:07 PM) eyedeekay: Hi everybody, sorry I'm late, got disconnected right before the meeting (08:01:59 PM) eyedeekay: 1. Hi (08:01:59 PM) eyedeekay: 2. 2.1.0 Status Report (08:01:59 PM) eyedeekay: 3. 2.2.0 Development Status (08:01:59 PM) eyedeekay: 4. Congestion Throttling (08:01:59 PM) eyedeekay: 5. Hypothetical Traffic Management ( Flood of Tor Users) (08:01:59 PM) eyedeekay: 6. Stickers for translators (08:01:59 PM) eyedeekay: zzz where do you want to do your report about the DOS? 2 or own topic? (08:02:45 PM) zzz: let's call it 3b) (08:02:46 PM) zzz: or 2b) (08:02:59 PM) eyedeekay: OK 2b then (08:03:00 PM) zzz: your choice (08:03:53 PM) eyedeekay: 1. Hi who all is here today besides me and zzz? (08:03:58 PM) zzz: hi (08:04:09 PM) not_bob: Here (08:04:18 PM) echelonMAC: here (08:04:18 PM) obscuratus: Hi (08:04:29 PM) eyedeekay: Great turnout, thanks everybody (08:04:30 PM) echelonMAC: on replacement system. (08:05:06 PM) eyedeekay: 2. 2.1.0 Status Report (08:05:15 PM) zzz: irc is laggier than usual so please allow a little extra time for responses (08:05:38 PM) eyedeekay: Thanks zzz I will keep that in mind (08:09:02 PM) eyedeekay: Where to even start... my focus has been on Android UX issues in particular fixing up things I was doing wrong when initializing the app (08:09:04 PM) eyedeekay: Android will get a point release on that account (08:10:00 PM) eyedeekay: The topic I'm sure is on everybody's mind right now is the network being under attack which has shifted everybody's attention (08:10:05 PM) eyedeekay: And that is topic 2b (08:10:59 PM) eyedeekay: Shoot I mixed up the topics, scratch that, that was supposed to go to 3. sorry, long week, lot going on (08:12:03 PM) eyedeekay: zzz would you do me a favor to take 2? I think I am ill-equipped to present on everything which is going on (08:12:28 PM) zzz: sure (08:12:29 PM) zzz: but before I do (08:12:56 PM) zzz: do you and echelonMAC have a 2.1.0 mac easy-install bundle progress report? (08:13:17 PM) eyedeekay: Oh yes I can do that (08:14:38 PM) eyedeekay: So, we've been closing in on issues, and right now echelonMAC and have different hypothesis on what's going on which we're both pursuing (08:14:38 PM) eyedeekay: My hypothesis is that this all stems from a stale workaround for a bug in Java 14 (08:15:08 PM) eyedeekay: Where jpackage is supposed to sign the dylib files that are packed into a disk image(dmg) but which are in fact left unsigned (08:15:33 PM) echelonMAC: in short: eyedeekaym did redo the signing script, I can buiodl and sign, but still wrong signing for apple (08:15:55 PM) eyedeekay: zab worked around this by creating the .app directory and signing the stuff inside it then using jpackage only for the final packaging step (08:16:35 PM) eyedeekay: so when we upgraded Java's we started signing everything twice, and we no longer needed to do that signing step manually (08:16:47 PM) eyedeekay: echelonMAC correct me if I'm wrong but you think you have the wrong sort of keys? (08:17:10 PM) echelonMAC: maybe, maybe not, unsure about that (08:17:18 PM) echelonMAC: at least the logs showing this error (08:17:53 PM) zzz: my question was higher level, what's the ETA, is 2.1.0 still a target or has that been abandoned and you're hoping for 2.2.0, or what? (08:18:15 PM) echelonMAC: 2.1.0 is still the target, but currently no ETA (08:18:39 PM) echelonMAC: I can build nearly instant, but digging deeper is currently out of time... (08:18:48 PM) eyedeekay: I still want to cut a release of 2.1.0 as soon as we know we can pass notarization, IMO once we can pass it once we should be able to do it predictably (08:18:59 PM) zzz: eyedeekay more or less committed to early april 2.2.0 in his blog post, you're not endorsing that ETA echelonMAC ? (08:19:49 PM) echelonMAC: I am completely helpless and cant predict a ETA, as I do not full yunderstand signing and building yet. (08:20:12 PM) echelonMAC: more or less, I do follow scripts blindly, if idk can fix the signage, the notarization is a 5 min job. (08:20:24 PM) echelonMAC: IF the sign does work as appple expect it (08:20:26 PM) zzz: ok then I recommend an edit of the blog post eyedeekay, let's not promise things we can't deliver on (08:20:33 PM) eyedeekay: Will do (08:21:19 PM) zzz: ok thanks you ready for my part of 2) ? (08:21:41 PM) eyedeekay: Yes please (08:21:48 PM) zzz: great (08:22:00 PM) zzz: last meeting was one week after the release, now we're 4 weeks out (08:22:15 PM) zzz: my hope was that expl. build success would climb steadily (08:22:35 PM) zzz: from the low-20% to low-30%, and then "pop" out of congestion, back to low 40s (08:22:45 PM) zzz: only the first part happened (08:25:20 PM) zzz: and then we swung back and forth between low 20s and low 30s (08:26:56 PM) zzz: so, we have some theories, see 2b) (08:26:56 PM) zzz: but I'm happy with the performance of 2.1.0 otherwise (08:26:56 PM) zzz: not too many bug reports (08:26:56 PM) zzz: I'll give an overview of what we are fixing in 2b) and 3) (08:26:56 PM) zzz: about 50% of the network has updated to 2.1.0 or the i2pd equivalent (08:26:56 PM) zzz: everybody please update if you haven't (08:26:56 PM) zzz: that's all I have for 2a), but I'll pause for a minute for questions / comments before starting 2b) (08:28:33 PM) zzz: ok, 2b) current network conditions (08:28:33 PM) zzz: over the weekend started an unambiguous attack (08:28:33 PM) zzz: lots of floodfill routers (08:28:33 PM) zzz: for the most part, the network overall, and java routers, are handling it ok (08:28:33 PM) zzz: I do have one report of routers crashing with OOM (out of memory) (08:28:54 PM) zzz: I understand that i2pd routers are really struggling with very low tunnel build success rates (08:29:06 PM) not_bob: My fleet is up to date. (08:29:15 PM) zzz: the attack is starting / stopping / changing several times a day (08:29:37 PM) zzz: so we're only about 60 hours in to understanding it and discussing countermeasures (08:30:15 PM) zzz: remember the tunnel build problem (now much more likely to be classified as a different attack) started Dec. 19 and took us several weeks to understand and address (08:30:27 PM) zzz: so it's early days (08:30:36 PM) not_bob: I have one I2P+ router and it's done well to weather this. But, my i2pd routers not so much. I've seen as low as 3% tunnel build success. I'm currently sitting around 10% on those routers. (08:31:17 PM) zzz: but this is a straightforward sybil / DHT attack, new to us but familiar to anybody doing peer-to-peer / DHT applications (08:31:53 PM) zzz: far too early to say if it will require a release ahead of schedule (for java i2p) or if so when (08:32:23 PM) zzz: EOT, I'll wait a couple minutes for discussion / comments / questions (08:33:24 PM) eyedeekay: Should people who wind up OOM increase the RAM available to their router? (08:36:18 PM) zzz: yeah, that's a straightforward mitigation (08:36:18 PM) zzz: stop your router, edit wrapper.config, restart (08:36:18 PM) zzz: I expect I'll have mitigations in dev builds in a few days (08:36:18 PM) dr|z3d: ideally you want your min heap at around 256M and your max ram at 2-3 times that. (08:36:18 PM) not_bob: I do not currently have any stock I2P routers running. (08:36:18 PM) zzz: I want to repeat what I said above that the attacks are evolving rapidly, and we want to take our time to address the overall issues (08:36:18 PM) zzz: not to focus too narrowly on the specifics (08:37:36 PM) zzz: back to you eyedeekay if there's nothing else on 2b) (08:38:06 PM) eyedeekay: thanks very much zzz. 3) 2.2.0 Development Status (08:39:51 PM) eyedeekay: As I mistakenly stated before, my focus has been on Android UX issues in particular fixing up things I was doing wrong when initializing the app, pretty basic stuff all things considered but all of which was due for improvement (08:39:57 PM) eyedeekay: or outright fixing (08:40:49 PM) eyedeekay: Examples being fixes for subscriptions and custom ports when building tunnels which got in several user's way after a large increase in users with 2.10 (08:41:07 PM) dr|z3d: as an aside, and to shine some light on the size of the attack, we've got a user reporting ~30K banned routers. so it's non-trivial :) (08:41:07 PM) dr|z3d: (that'll be shiver, who's here) (08:42:36 PM) mark22k: I got 56005 banned peers. (08:42:58 PM) eyedeekay: Holy moley. I have 11027 and I thought that was a lot (08:43:08 PM) moristo: Is this the work of a nation state--the banned routers or any other noticable patten? (08:43:50 PM) moristo: Spectrum internet was off yesetrday in FL and Italy the day before. (08:43:54 PM) moristo: *yesterday. (08:43:55 PM) zzz: let's get back to 3) please and table further attack discussion until after the meeting (08:44:05 PM) echelonMAC: Banned Peers (57053) (08:44:22 PM) moristo: oh, is there a meeting in progress? My bad. (08:46:50 PM) zzz: eyedeekay, you still with us? (08:47:11 PM) eyedeekay: yeah I'm here (08:47:37 PM) zzz: you have more on 3) or is it my turn? (08:47:37 PM) eyedeekay: started a long one: (08:47:37 PM) eyedeekay: i2p.firefox(Easy-Install for Windows is also getting worked on, more of the work is being done by removal there, updates are getting simplified now that the old admin-style installs are all migrated to user-style installs (08:47:37 PM) eyedeekay: portable USB install support is on the horizon for 2.2.0 (08:47:43 PM) eyedeekay: With updates (08:48:21 PM) eyedeekay: Other issues and user-complaints I'm addressing or deciding how to address are on that issue tracker (08:48:28 PM) eyedeekay: EOT for me (08:48:47 PM) zzz: ok you saw the NPE issue in i2p.i2p right? (08:49:10 PM) eyedeekay: Yes I did, hot on the trail (08:49:21 PM) zzz: ok holler if you need help ofc (08:49:24 PM) zzz: 3) for me: (08:49:47 PM) zzz: I finished the peer selection refactor I've been working on since september, finally (08:50:31 PM) zzz: I think I fixed the erroneous symmetric nat indications that were in 2.1.0, but need somebody with that problem to test and report (08:50:59 PM) zzz: got a cool new i2psnark search box (08:51:19 PM) zzz: almost done with "congestion caps" (proposal 162) (08:51:31 PM) echelonMAC: :-) (08:51:49 PM) zzz: and some more tweaks to refine our handling of tunnel build congestion (08:52:18 PM) zzz: late last week, I thought I was pretty much done with 2.2.0 and could relax for two months until the release (08:52:31 PM) zzz: so, unfortunately, now we have a lot more to do (08:52:48 PM) zzz: that's the way it goes sometimes (08:53:24 PM) not_bob: Thank you for that, a major quality of life improvement. (08:53:24 PM) zzz: EOT, I'll wait a minute for discussion, then back to you eyedeekay (08:53:37 PM) zzz: haha not_bob you're welcome (08:55:00 PM) eyedeekay: Last call for 3? (08:55:20 PM) eyedeekay: 4. Congestion Throttling - I think this was a tunnel_king topic, is tunnel_king here? (08:55:42 PM) zzz: back to you eyedeekay (08:57:39 PM) eyedeekay: 4. Congestion Throttling, 5. Hypothetical Traffic Management ( Flood of Tor Users) - both introduced by tunnel_king, last call for tunnel_king (08:59:01 PM) eyedeekay: OK last one, 6. Stickers for translators (08:59:01 PM) eyedeekay: Specifically rules for people receiving stickers outside of the Americas (08:59:58 PM) zzz: this was my topic, only because unresolved since last meeting (09:00:28 PM) zzz: echelonMAC you have an answer? (09:00:41 PM) echelonMAC: not en detail, but who wnats should receive a bunch of stickers if they sent their address (09:01:04 PM) echelonMAC: aka sned a announcement in transifex and send out after receive of address (09:01:19 PM) echelonMAC: but currently no new stickers arrivced here (09:01:35 PM) eyedeekay: Tracking says the 10th (09:01:55 PM) zzz: I'm awaiting echelonMAC to post the instructions on my forum, then I will copy/paste to transifex (09:02:17 PM) echelonMAC: ok (09:02:28 PM) zzz: that's where we've been for a month (09:02:42 PM) zzz: thanks (09:03:33 PM) eyedeekay: Anything else for 6 or for the meeting? (09:03:36 PM) zzz: EOT on 6) for me, back to you eyedeekay (09:04:32 PM) zzz: one closing word for the meeting: zzz.i2p the best place for news and weather, I'll post there when I know more than I do now (09:04:32 PM) zzz: thanks (09:04:55 PM) eyedeekay: Thanks very much for that zzz, and thanks everybody for coming to the meeting (09:05:44 PM) eyedeekay: See you around IRC and same time next month (09:08:55 PM) zzz: thanks eyedeekay (09:08:55 PM) zzz: got thru it without disconnects

Update on Mac Easy Install Notarization

Tue, 31 Jan 2023 00:00:00 +0000

The I2P Easy-Install Bundle for Mac has been experiencing stalled updates for the past 2 releases due to the departure of its maintainer. It is recommended that users of the Easy-Install bundle for Mac switch to the classic java-style installer which was recently restored to the download page. 1.9.0 has known security issues and is not suitable for hosting services or any long-term use. Users are advised to migrate away as soon as possible. Advanced users of the Easy-Install bundle may work around this by compiling the bundle from source and self-signing the software.

Windows Easy-Install 2.1.0 Release

Fri, 13 Jan 2023 00:00:00 +0000

Update details

The I2P Easy-Install bundle for Windows version 2.1.0 has been released. As usual, this release includes an updated version of the I2P Router. This release of I2P provides improved strategies for dealing with network congestion. These should improve performance, connectivity, and secure the long-term health of the I2P network.

Present: echelon, eyedeekay, zzz

Meeting Log

(03:00:31 PM) eyedeekay: Hi everyone, welcome to the November 8 meeting (03:00:31 PM) eyedeekay: 1. Hi (03:00:31 PM) eyedeekay: 2. 2.0.0 development status (03:00:31 PM) eyedeekay: 3. Publish source tarballs for bundle releases (03:00:31 PM) eyedeekay: 4. Free Stickers for Translators (03:00:31 PM) eyedeekay: Anything else for the agenda? (03:00:39 PM) mode (-m ) by zzz (03:01:19 PM) zzz: hi (03:01:58 PM) eyedeekay: hi zzz (03:02:03 PM) eyedeekay: Anybody else here today? (03:02:08 PM) eche|on: hi (03:02:18 PM) eyedeekay: Hi eche|on (03:02:39 PM) eyedeekay: 2. 2.0.0 development status (03:02:58 PM) eyedeekay: We're 2 weeks from release with a tag freeze tomorrow, IIRC (03:03:49 PM) eyedeekay: Yes that's exactly when (03:04:38 PM) eyedeekay: zzz and orignal have been hard at work getting ssu2 ready, the plan is still to enable it (03:05:08 PM) eyedeekay: I'll be doing an unsigned release of the I2P Easy-Install for Windows (03:05:50 PM) eyedeekay: I don't know the Mac release status, though, are Mac users stuck on 1.9.0 until we can find a new Mac maintainer/signer? (03:06:25 PM) zzz: yes. There's a pretty good summary of the release at `http://zzz.i2p/topics/3377` (03:07:02 PM) zzz: the SSU2 testing in the last 3 months with 2% enabled has been a tremendous success (03:07:17 PM) zzz: haven't found any major issues, but we've fixed countless minor ones (03:08:19 PM) eche|on: go ahead with SSU2 (03:08:35 PM) eche|on: about mac: I got a dev account and a MAC, but no idea howto currently (03:08:39 PM) eche|on: and less time (03:09:03 PM) zzz: interesting (03:09:31 PM) zzz: do you think you _could_ do it at some point? If so, when? (03:09:39 PM) eche|on: I do have the git repo of the mac inclusions, but currently not yet looked into (03:09:54 PM) eche|on: IF I find out howto, rather soon (tm) (03:10:05 PM) zzz: even if it's a month or two late, that would be fantastic (03:10:08 PM) eche|on: but the howto may fail in shorter terms (03:10:41 PM) eche|on: also no idea about whats apple going to do, but those are parts to find out (03:11:10 PM) eyedeekay: I'll see if I can help you, building the mac jpackages is pretty straightforward, I've never signed them but it's all in the scripts zab wrote (03:11:25 PM) zzz: when I do the 2.0.0 news.xml, I'll also put a news entry in the mac feed saying it will be delayed (03:11:42 PM) zzz: eyedeekay, do you have a mac? (03:11:57 PM) eyedeekay: I have an Intel Mac but no dev account (03:12:04 PM) eche|on: sadie has a mac, but neither idk nor sadie do want to go public with their names (03:12:25 PM) eche|on: getting a dev account is rather simple : give out your name and pay 100$ a year (03:12:28 PM) eyedeekay: I can make a dmg but it gets signed with local keys that aren't allowed on other Macs (03:12:32 PM) zzz: I understand. The idea is you could walk thru everything but the notarization (03:12:32 PM) eche|on: more or like thats it (03:13:12 PM) eche|on: bb 2min (03:13:25 PM) zzz: afaik it's the notarization that's the real pita. Hopefully the howto is clear... (03:14:14 PM) eyedeekay: I think the only pitfall really is getting the Java dev environments set up, there's a tool you install through brew that switches version that makes it very easy though (03:14:25 PM) zzz: eyedeekay, let's put this on the agenda for next month (03:14:36 PM) eyedeekay: Can do (03:15:19 PM) zzz: in the mean time, please run thru the howto as it currently exists as far as you can w/o notarization, just to test the howto and see if it needs any fixes for ech (03:16:10 PM) zzz: esp. to check if the arm64 side is documented (03:16:45 PM) eyedeekay: I will do everything I can, although I won't be able to run through the arm64 process because I do not have an arm64 Mac (03:16:53 PM) eche|on: I will check howto get the certs with notarization, (03:16:55 PM) eyedeekay: I'll do everything up to that though (03:17:18 PM) eche|on: eyedeekay: just order a arm64 mac. refund as usual (03:17:28 PM) eche|on: no need to stop at that (03:17:30 PM) zzz: do you need an ARM mac to build ARM? (03:17:41 PM) zzz: probably... (03:17:59 PM) eyedeekay: I'm not quite sure on the subtleties of it all re: cross-compilation (03:18:02 PM) zzz: there's also a possible workflow where idk builds and ech notarizes (03:18:23 PM) zzz: but we don't need to work it all out here (03:18:44 PM) eyedeekay: But jpackage is pretty picky about architecture/OS combinations (03:19:28 PM) SoniEx2: raspberry pi? (03:19:39 PM) zzz: let's move on to next topic (03:19:40 PM) eyedeekay: ELF not Mach-O (03:19:42 PM) eyedeekay: But yes (03:19:45 PM) eyedeekay: 3. Publish source tarballs for bundle releases (03:20:24 PM) eyedeekay: Since it's just me now and I wanted to publish source tarballs the whole time, 2.0.0 Windows getting source tarballs (03:20:36 PM) eyedeekay: One for the bundle itself and one for the profile manager component (03:21:17 PM) eyedeekay: As part of going through the scripts from the Mac bundle I'll add source tarball generation as part of the process (03:21:18 PM) zzz: ok, and since the mac objector has left, let's add one to the mac page also (03:21:28 PM) eyedeekay: Will do (03:21:41 PM) zzz: great, I'm happy (03:22:38 PM) eyedeekay: 4. Free Stickers for Translators (03:23:27 PM) eche|on: yeah (03:23:49 PM) eyedeekay: eche|on and I talked about this briefly after last month's meeting by email (03:23:49 PM) eyedeekay: I think we were each in favor of doing it? I don't have my mail open (03:24:23 PM) eche|on: sure we can do this, one for each part of the wolrd (03:24:28 PM) zzz: it was my proposal, but it requires a) stickers and b) somebody to mail them (03:24:30 PM) eche|on: but my sticker ressources are limited (03:24:47 PM) zzz: as I understand we're essentially out of stickers (03:24:59 PM) eche|on: sadie/idk still do have several (03:25:05 PM) eche|on: I got around 400 or alike only (03:25:23 PM) eche|on: should be enough for 1year+, but plan ahead (03:25:26 PM) eyedeekay: Oh I ran myself down to like, 8 at All Things Open last week (03:25:30 PM) eyedeekay: I'll need to order more (03:25:53 PM) eche|on: ah, ok (03:26:10 PM) zzz: can you two coordinate on who is ordering, what the design is, and make sure each of you gets half? (03:26:16 PM) eyedeekay: Yes we can (03:26:34 PM) zzz: super (03:27:05 PM) zzz: when you have them in hand, holler and I'll announce on TX (03:27:11 PM) eche|on: good (03:27:22 PM) zzz: thanks guys (03:27:46 PM) eyedeekay: No problem (03:27:56 PM) eyedeekay: Anything else on 4 or for the meeting? (03:28:25 PM) eche|on: nope (03:29:14 PM) eyedeekay: All right thanks everybody for coming, I'll post the meeting in a few minutes

SSU2 Transport

Tue, 11 Oct 2022 00:00:00 +0000

Overview

I2P has used a censorship-resistant UDP transport protocol “SSU” since 2005. We’ve had few, if any, reports of SSU being blocked in 17 years. However, by today’s standards of security, blocking resistance, and performance, we can do better. Much better.

That’s why, together with the i2pd project , we have created and implemented “SSU2”, a modern UDP protocol designed to the highest standards of security and blocking resistance. This protocol will replace SSU.

I2P Dev Meeting - October 04, 2022

Tue, 04 Oct 2022 00:00:00 +0000

Quick recap

Present: eyedeekay, zzz, zlatinb

Meeting Log

(04:00:08 PM) eyedeekay: Hi everyone, welcome to the October 4 2022 meeting (04:00:08 PM) eyedeekay: 1. Hi (04:00:18 PM) zlatinb: hi (04:00:28 PM) zzz: hi (04:00:51 PM) eyedeekay: 1. Hi (04:00:51 PM) eyedeekay: 2. 1.10.0 development status (04:00:51 PM) eyedeekay: 3. next release 2.0.0? (04:00:51 PM) eyedeekay: 4. Publish source tarballs for bundle releases (04:00:51 PM) eyedeekay: 5. Free stickers for translators (04:00:51 PM) eyedeekay: 6. Windows Easy-Install Update/Out-of-Beta (04:01:05 PM) eyedeekay: 2. 1.10.0 development status (04:01:15 PM) eyedeekay: About 7 weeks to go (04:01:24 PM) eyedeekay: My big priority this month has been to get the Windows Easy-Install bundle ready to go out of beta (04:01:31 PM) eyedeekay: Lots of stuff on the forum about that, targeting stable updates, compatibility with existing/unbundled routers, and a more stable and flexible way to manage and launch browser profiles, more on all that in item 6 (04:01:38 PM) eyedeekay: Also working on a "Split Tunneling" or "Per-App VPN" tool in Android(on the roadmap). (04:01:47 PM) eyedeekay: The utility is that it allow users to configure their browsers more easily, in a way which prevents WebRTC escapes by putting them onto an interface which corresponds to an I2P connection and not to their network provider (04:02:05 PM) eyedeekay: zzz, zlatinb what would you like to add that you're working on (04:02:30 PM) zzz: not a lot to report... SSU2 testing continues to go well... (04:02:53 PM) zzz: put up proposal 161 about compressible padding, we'll be discussing it in #ls2 meetings... (04:03:06 PM) zlatinb: Nothing specific I'm working on, just want to let everyone know that I'll be afk from 22nd Nov to 10th Dec so if the next release gets tagged on the 21st I may be able to build the mac bundles but will most likely not be able to seed the torrents (04:03:29 PM) eyedeekay: If you send me the files I'll seed them for you (04:03:32 PM) zzz: I have some peer selection efficiency improvements I'm going to try to get in soon, may or may not make it (04:03:43 PM) zzz: EOT (04:04:21 PM) eyedeekay: Thanks zzz, zlatinb, I don't want to rush anybody but we do have a long agenda today, anything else to add on 2? (04:04:59 PM) eyedeekay: 3. next release 2.0.0? (04:04:59 PM) eyedeekay: My vote is yes to 2.0.0 (04:05:19 PM) zzz: yeah I put it up for comments on my forum and got I think 1 yes and no no's (04:05:36 PM) eyedeekay: I was a yes at the last meeting too I think (04:05:46 PM) zzz: I'd like to decide today because I have a SSU2 blog post ready to go and it would be helpful to refer to the next release by number (04:06:22 PM) zzz: yeah I didn't hear any strong opinions one way or the other last meeting which is why we pushed it a month (04:06:34 PM) zzz: I think it's a good idea (04:06:51 PM) zzz: so if there's no objections, let's call it 2.0.0! (04:07:30 PM) eyedeekay: Timeout 1m for objections (04:07:47 PM) zzz: make it 30 seconds :) (04:07:54 PM) eyedeekay: Yeah I already burned 30 (04:08:04 PM) eyedeekay: OK there it is (04:08:06 PM) eyedeekay: 2.0.0 (04:08:17 PM) eyedeekay: 4. Publish source tarballs for bundle releases (04:08:31 PM) zzz: yeah this was my item (04:08:53 PM) zzz: standard open source practice is to post source tarballs, even if we can point to a git tag (04:09:06 PM) zzz: I understand that the Mac source doesn't change release to release? (04:09:10 PM) zzz: but the windows source does? (04:09:46 PM) zlatinb: well the mac bundle has evolved to enable arm64 but in general it doesn't change (04:10:02 PM) eyedeekay: What we both do is clone a copy of the repo and check out a specific release tag, ant distclean, generate our jars, and copy them into the bundle trees (04:10:15 PM) zzz: anyway, my recommendation is that we generate source tarballs as part of the build process and link to them on the respective download pages (04:10:36 PM) zzz: if they don't change, then I guess they can be unversioned (04:10:50 PM) zzz: so the windows source doesn't change release-to-release either? (04:11:01 PM) zlatinb: I would rather just tag and then fetch the tarball from github. I expect at least for a while the only thing changing in the mac bundle will be the changelog file (04:11:50 PM) zzz: you all can work out the details, but the goal is to have source and instructions so anybody can build it themselves (04:12:00 PM) eyedeekay: The i2p jars that get included don't change except to get updated, but the Windows source has changed in the launcher quite a lot since it started (04:12:12 PM) zzz: are you two willing to do that and add it to your release processes? (04:12:21 PM) eyedeekay: Yes absolutely (04:12:31 PM) eyedeekay: My release scripts and daily scripts now include tarball every time (04:12:36 PM) zzz: you don't need to include dependencies such as i2p, and probably shouldn't (04:12:37 PM) eyedeekay: zab's too IIRC (04:12:54 PM) zlatinb: the question is where to put the tarballs, should they be available on the site, etc. (04:13:25 PM) zzz: somewhere on the download server with everything else, with links on the bundle pages. You two can work out the details to be consistent (04:13:59 PM) zlatinb: well that's the thing, if we can just point to a gitlab tag then there's no need for any extraneous links (04:14:31 PM) zzz: disagree, I think it's good open source practice to publish source tarballs (04:14:55 PM) zlatinb: github and maybe gitlab allow tarball download off of a tag (04:14:57 PM) eyedeekay: It's not much more effort, I'm not against it, I tag in the same script I generate tarballs in (04:15:05 PM) zzz: here's the binary, here's the source, here's the gpg sigs, here's the build instructions (04:15:29 PM) zzz: it's also consistent with our mainline release to have tarballs (04:16:15 PM) zzz: sounds like zlatinb is not in agreement? should we push this off to next month? (04:16:38 PM) zlatinb: yeah I think it's unnecessary (04:16:57 PM) zlatinb: but don't mind doing it if that's what the decision is (04:17:11 PM) zzz: if it never changes, you only have to do it once and you're done (04:17:47 PM) zlatinb: it has changed very rarely historically (04:18:03 PM) eyedeekay: Kicking it down the road for now is fine with me, zlatinb and I can work out what we're going to do or not do in the meantime (04:18:33 PM) eyedeekay: This might be a situation where we have to be a little different because my bundle has been a little more rapidly-changing than his (04:19:27 PM) zzz: if we don't want to decide today I'll start a forum thread to solicit more opinions (04:20:44 PM) zlatinb: ok (04:20:44 PM) zzz: ok = you're oppposed for now? (04:21:02 PM) eyedeekay: Probably a good idea, and I'm pro tarballs (04:21:31 PM) zlatinb: yeah (04:21:31 PM) zzz: no problem, eyedeekay put it on the list for next month (04:21:37 PM) eyedeekay: OK can do (04:21:52 PM) eyedeekay: Anything else for 4? (04:22:38 PM) eyedeekay: 5. Free stickers for translators (04:22:55 PM) eyedeekay: zzz this one was also yours, take it away whenever you're ready (04:23:16 PM) zzz: yeah, credit sarah jamie lewis on twitter (04:23:32 PM) zzz: for her project which I've forgotten the name... cwtch? (04:24:02 PM) eyedeekay: That's the one (04:24:02 PM) zzz: anyway, thought it was a good idea, but we'd need a) stickers and b) people to mail them (04:24:17 PM) zzz: both of which we used to have but are now out of both people and stickers? (04:24:40 PM) zzz: so, do we want to do it, and should we order stickers (even if we don't) (04:24:45 PM) zzz: EOT (04:25:26 PM) zzz: sadie and eche|on used to be the sticker people I think (04:25:38 PM) eyedeekay: I went through and counted mine up, I've got maybe 35 of the old ones(Toopie) and 91 left of the run I ordered in the spring, but I'd be fine with ordering more (04:25:41 PM) zzz: anyway, comments please... yes/no/maybe? (04:26:00 PM) eyedeekay: I can mail them within the US and Canada but the EU isn't great for me (04:26:21 PM) zzz: we have hundreds of translators registered. only a few are probably active (04:26:41 PM) zzz: who is the sticker-orderer-person? (04:27:54 PM) eyedeekay: The last person to order stickers was probably me, but I did them on my own time/out of pocket so I would have them for conventions (04:28:19 PM) zzz: who's in charge of PR? (04:28:48 PM) zzz: who has an opinion about stickers for translators? (04:28:48 PM) zzz: well, you could have / should have gotten reimbursed... echelon used to be the sticker guy (04:29:54 PM) zzz: we're going to need his buyin both for the cost, and to make him the EU mail person, and to send half to you and half to him (04:30:15 PM) zzz: since he's not around, put this on the list for next month, I'll try to get his attention (04:30:22 PM) eyedeekay: I think that if translators request stickers we should be able to get them some stickers, but that it should be contingent on request (04:30:59 PM) zzz: sure, we don't have anybody's address, they have to ask. but we would have to tell them to ask (04:31:17 PM) uis is now known as Irc2PGuest33729 (04:31:48 PM) zzz: if anybody's going to CCC then you need to hop on more stickers, independent of translators (04:32:42 PM) zzz: EOT, push it to next month, no answers today (04:32:47 PM) eyedeekay: Ack, I do plan to go so I'll make sure I have some stickers (04:32:47 PM) eyedeekay: So next step is start an email chain with Ech about it (04:33:09 PM) eyedeekay: EOT from me, anything else on 5? (04:33:50 PM) eyedeekay: 6. Windows Easy-Install Update/Out-of-Beta (04:33:58 PM) eyedeekay: This one's mine obviously (04:34:26 PM) eyedeekay: So 1.9.5 point release happened technically because of the reseed application context timer obviously (04:34:45 PM) eyedeekay: But it was a convenient time to also keep an eye on how the updates performed (04:35:54 PM) zlatinb: and how did it behave? (04:35:55 PM) eyedeekay: It wasn't without complications, people who were using fell into 3 groups (04:36:56 PM) eyedeekay: 1. People for whom it worked perfectly (04:36:56 PM) eyedeekay: 2. People for whom it resulted in corrupted router.config files for un-bundled routers (04:36:56 PM) eyedeekay: 3. People for whom it it did not update because the router.config files were from un-bundled routers (04:37:22 PM) eyedeekay: 2 and 3 were problems, I followed up with the fix in a forum post on zzz.i2p (04:37:43 PM) eyedeekay: I believe they are fixed now and cannot recur in the future (04:37:57 PM) eyedeekay: Therefore I think the update process will be ready by what is now 2.0.0 (04:38:08 PM) eyedeekay: I actually think it's ready now but 7 weeks to test (04:38:53 PM) eyedeekay: So I would like to move it out of beta in November (04:39:09 PM) zzz: we don't have documented criteria for out-of-beta, really (04:39:17 PM) zzz: but for me it's that the release processes are solid, things aren't getting missed (04:39:27 PM) zzz: we're not doing point releases a week later to fix stuff (04:39:45 PM) zzz: but you may wish to list your own feature goals (04:40:21 PM) zzz: for example, are you two solid on reviewing the java updates every three months and jointly deciding to release or not? (04:40:40 PM) zzz: I didn't see any on-IRC discussion. did it happen off-IRC perhaps? (04:41:31 PM) zlatinb: the last discussion happened here, there has been no off-IRC discussion regarding jre point releases since (04:42:21 PM) eyedeekay: Didn't we talk about it on Whereby a little after that? (04:42:36 PM) eyedeekay: IIRC we only release in the Java cycle if there's a CVE which affects the last release? (04:42:46 PM) zzz: just to take an example, 18.0.2.1 August 18 2022 fixes a JIT bug that crashes the JRE. Are you two both on that, or did you jointly decide it wasn't necessary? (04:43:33 PM) zlatinb: I'm not on that I don't think (04:43:43 PM) zlatinb: and don't remember discussing that bug; I usually look only at the CVEs (04:44:08 PM) zlatinb: 21:43:29 zlatinb: I'm not on that I don't think (04:44:08 PM) zlatinb: 21:43:42 zlatinb: and don't remember discussing that bug; I usually look only at the CVEs (04:44:12 PM) zzz: back (04:45:12 PM) eyedeekay: I am on 18.0.2.1 but because I pushed back my release to try and make sure I addressed some stability issues and by that time Java had updated (04:45:24 PM) eyedeekay: Also my point release was built with an updated JDK (04:45:35 PM) eyedeekay: So that's got us out-of-sync again I think (04:45:54 PM) zzz: that's what I'm getting at about processes. If the build and release processes aren't yet stable and being reliably followed, these procucts aren't ready to graduate (04:46:01 PM) zzz: so when you updated, to 18.0.2.1, did you tell zlatinb you were doing it and suggest he do the same? (04:47:04 PM) eyedeekay: No I didn't, I simply let it auto-update and built with the latest version (04:48:13 PM) eyedeekay: So... there's another process to revise on my side (04:49:31 PM) zzz: I'd suggest you work on a solid bug-free release in november (together with whatever feature goals you have) and if that goes well put yourself on the agenda for december (04:50:00 PM) eyedeekay: OK can do (04:50:56 PM) zzz: or january because the release is likely to be late nov., may not have enough info by 1st week in dec. (04:52:02 PM) eyedeekay: If there's not enough to go on by then I'll move it (04:52:15 PM) eyedeekay: Anything else for 6? (04:52:27 PM) zzz: a brief 6a) (04:52:30 PM) eyedeekay: Sure (04:52:52 PM) zzz: zlatinb, reported that the mac arm update went well, so as far as I'm concerned it's out of beta as discussed on my forum (04:53:28 PM) zzz: zlatinb, you need to update your page to remove the beta label (04:53:28 PM) zzz: eot (04:53:28 PM) zlatinb: ok (04:53:29 PM) zlatinb: will do soon (04:54:24 PM) eyedeekay: All right that puts us at just shy of an hour, anything else for the meeting? (04:54:26 PM) eyedeekay: timeout 1m (04:54:41 PM) zlatinb: yes (04:54:57 PM) zlatinb: if StormyCloud reads the logs, I encourage them to address the concerns raised on reddit (04:56:15 PM) zlatinb: the longer that question stays unanswered the worse it looks (04:56:18 PM) eyedeekay: agreed, they do sometimes come to reddit and it would be good to hear from them (04:56:36 PM) zlatinb: eot (04:56:43 PM) eyedeekay: Thanks zlatinb (04:57:37 PM) eyedeekay: Anything else for the meeting(again)? timeout 30s this time (04:58:21 PM) eyedeekay: Thanks everyone for coming, I'll post the logs tonight, see you around IRC and same time next month

A Reminder to be Safe as I2P Grows

Mon, 26 Sep 2022 00:00:00 +0000

A Reminder to be Safe as I2P Grows

It is an an exciting time for The Invisible Internet Project (I2P). We are completing our migration to modern cryptography across all of our transports, ( Java and C++), and we have recently gained a high-capacity and professional outproxy service, and there are more applications integrating I2P based functionality than ever. The network is poised to grow, so now is a good time to remind everyone to be smart and be safe when obtaining I2P and I2P-related software. We welcome new applications, implementations, and forks with new ideas, and the power of the network comes from its openness to participation by all I2P users. In fact, we don’t like to call you users, we like to use the word “Participants” because each of you helps the network, in your own way by contributing content, developing applications, or simply routing traffic and helping other participants find peers.

Meet your Maintainer: DivaExchange

Mon, 26 Sep 2022 00:00:00 +0000

In this second installment of Meet Your Maintainer, I reached out to Konrad from DIVA.EXCHANGE to talk about DIVA’s research and services. DIVA.EXCHANGE is developing software with the goal of providing free banking technology for everyone. It is secure without a central infrastructure, and based on blockchain and I2P technology.

What got you interested in I2P?

About 10 years ago I had a presentation for “Technologieforum Zug” - a very local technology network for business guys. I was introducing I2P and Tor as overlay networks to them - to show them that other interesting things exist out there.

Meet Your Maintainer: StormyCloud

Wed, 07 Sep 2022 00:00:00 +0000

A conversation with StormyCloud Inc.

With the most recent I2P Java release , the existing outproxy, false.i2p was replaced with the new StormyCloud outproxy for new I2P installs. For people who are updating their router, changing over to the Stormycloud service can be done quickly.

In your Hidden Services Manager, change both Outproxies and SSL Outproxies to exit.stormycloud.i2p and click on the save button at the bottom of the page.

Who is StormyCloud Inc?

Mission of StormyCloud Inc.

Windows Easy-Install Bundle 1.9.5 Release

Wed, 07 Sep 2022 00:00:00 +0000

Bug Fixing release for Windows 11 users

This point release includes a bug fix in the included I2P router, which resolves a highly obscure bug where the context clock is out of sync with the clock in use by the File System, resulting in a router which is unable to read the current state of it’s own NetDB. Although this bug has only been observed on Windows 11 so far, it is highly recommended that all users update to the new build.

I2P Dev Meeting - September 06, 2022

Tue, 06 Sep 2022 00:00:00 +0000

Quick recap

Present: eyedeekay, zzz, zlatinb, not_bob, RightNow, RN

Meeting Log

(04:01:46 PM) eyedeekay: Hi everybody (04:01:50 PM) eyedeekay: welcome to the Tuesday September 6 meeting (04:02:02 PM) zzz: hi (04:02:07 PM) mode (-m ) by zzz (04:02:13 PM) zlatinb: hi (04:02:26 PM) eyedeekay: 1. Hi (04:02:26 PM) eyedeekay: 2. 1.9.0 release status (04:02:26 PM) eyedeekay: 3. 1.10.0 development status (04:02:26 PM) eyedeekay: 4. next release 2.0.0? (04:02:26 PM) eyedeekay: 5. Mac arm64 bundle out of beta if 1.9.0 update was successful? (followup from last meeting) (04:02:51 PM) eyedeekay: Anything else to add before we get started? (04:03:19 PM) eyedeekay: hi zzz, hi zlatinb (04:03:46 PM) eyedeekay: 2. 1.9.0 release status (04:05:11 PM) eyedeekay: We released about 2 weeks ago, there was a slight delay getting Android and the Easy-Install bundle out now (04:05:11 PM) eyedeekay: F-Droid builds are now fixed as well so people who wish to can install from F-Droid main if they choose to and the app will work (04:05:37 PM) not_bob: Thank you for that. (04:05:43 PM) eyedeekay: No problem (04:06:41 PM) eyedeekay: I'm going to be doing a point release for the Windows Easy-Install bundle, zlatinb found a very hard-to-spot bug which sees to affect easy-install bundle on Windows 11 slightly more than other places (04:07:17 PM) eyedeekay: zzz do you want to talk Debian or anything else? (04:07:51 PM) zzz: sure (04:07:53 PM) zzz: about 40% of net is updated which is typical for 2 weeks in (04:08:10 PM) zzz: we have a few hundred SSU2-enabled routers now, as desired/expected (04:08:41 PM) zzz: no major issues so far (04:09:06 PM) zzz: although zlatinb's bug is maybe medium-major :) (04:09:07 PM) zzz: EOT (04:10:01 PM) eyedeekay: Yeah and what I don't understand is how it went without happening much for so long, and then it hits the easy bundle twice in quick succession (04:10:17 PM) zlatinb: well its kind of by accident that I have to use a windows 11 laptop for a few days, it discovered a lot of issues (04:11:08 PM) zlatinb: I guess the reseed problem either caused people to try again or give up on i2p off the bat (04:11:09 PM) zzz: that's usually the way it goes... dev gets new setup... all hell breaks loose (04:11:59 PM) zlatinb: there is still an unresolved forking issue with firefox on first launch (04:12:48 PM) zlatinb: so ideally we should try and do something about it (04:13:30 PM) eyedeekay: Indeed, it only happens the very first time the browser launcher is run, every subsequent time it works fine (04:13:36 PM) zlatinb: maybe launch headless or play with the launch options, idk (04:14:10 PM) eyedeekay: Yeah I could launch it headless on the first run, let it fork and close, then subsequently run with the window open (04:14:58 PM) eyedeekay: That's a good idea thanks zlatinb (04:15:15 PM) eyedeekay: Anything else on 2? (04:16:03 PM) goingpostal is now known as Irc2PGuest14444 (04:16:29 PM) eyedeekay: 3. 1.10.0 development status (04:18:30 PM) eyedeekay: Sorry I'm a little less prepared than usual, stuck in somebody else's office all day, bear with me (04:21:00 PM) eyedeekay: 2 weeks in, I've been working on a number of improvements to the Windows bundle to make it more stable and intuitive to use and to help track down this clock-skew bug (04:21:37 PM) eyedeekay: I've also been porting the profile and launcher parts of it(less the jpackaged router) to non-Windows platforms to hopefully provide automatic browser configuration there (04:22:06 PM) eyedeekay: zzz has been working on SSU2, fixing bugs with the help of orignal, would you like to update us on that zzz (04:22:16 PM) zzz: yes, thanks. early days, but a summary of changes and fixes so far is at `http://zzz.i2p/topics/3377` (04:22:32 PM) zzz: SSU2 - added the ack-immediate flag and connection migration (04:22:47 PM) zzz: which are the last two things we wanted to get in before enabling for all (04:24:07 PM) eyedeekay: Cool so you're right on track then? (04:24:30 PM) zzz: the larger user base has us finding corner cases and more rare bugs, nothing too serious, fixing as we go (04:24:30 PM) zzz: the plans for months has been for us to enable SSU2 for everybody in the November release and we are still on track (04:24:30 PM) zzz: EOT (04:24:42 PM) zzz: yes (04:24:51 PM) eyedeekay: Awesome thanks for the update (04:25:09 PM) eyedeekay: Anything else for 3? (04:25:41 PM) eyedeekay: 4) next release 2.0.0? (04:25:52 PM) eyedeekay: zzz you added this topic, would you like to get us started? (04:26:12 PM) zzz: this was a suggestion from dr|z3d so if he's around I'll ask him to make his pitch (04:26:50 PM) zzz: but if he's not, I'll say it's not a bad idea (04:27:05 PM) zzz: linux is about to go from 5.19 to 6.0 (04:27:25 PM) zzz: tor's arti just went to 1.0.0 (04:27:26 PM) zzz: ssu2 as good an excuse as any (04:27:45 PM) RightNow: and I2P is going from SSU to SSU2 (04:27:47 PM) zzz: EOT - thoughts everyone? and we don't need to decide today, we have 11 more weeks (04:28:30 PM) not_bob: I have no issue with it so long it works. (04:29:18 PM) zzz: anybody hate it? anybody love it? (04:29:21 PM) eyedeekay: Sure, I think it makes sense, both transports will have been modernized, it's a big milestone (04:29:43 PM) zlatinb: I kind of wish we had something bigger of a bang to go to 2.0 (04:29:48 PM) RightNow is now known as RN (04:30:34 PM) eyedeekay: Use it for 3.0.0 maybe? (04:30:38 PM) zzz: there's nothing bigger on the roadmap. frankly, I hope we don't ever do anything bigger, I'm tired... (04:30:56 PM) zlatinb: also I have to leave now sorry, on the last topic yes I think the mac arm bundle is ready to go out of beta. I will have the windows laptop for another day or two for testing. Gotta bolt now, sorry (04:30:59 PM) zlatinb: ttyl (04:31:05 PM) RN: zzz, you are also thanked. (04:32:26 PM) eyedeekay: Yes zzz, your dedication and hard work are appreciated (04:32:34 PM) zzz: tell you what eyedeekay let me post in the 1.10 thread on my forum and will come back next month with a report, stick it on the agenda for next month (04:32:44 PM) eyedeekay: Will do zzz (04:33:18 PM) zzz: wasn't trying to elicit thanks, just pointing out this was the last - and hardest - of the crypto migration we've been on for about a decade (04:33:36 PM) eyedeekay: Didn't need to elicit it, you deserve it :) (04:33:52 PM) eyedeekay: But point taken, it's a huge effort (04:33:58 PM) RN: it is a milestone worth celebration, and yeah, you deserve it! (04:34:14 PM) zzz: if we'd tried to do SSU2 first it would have killed us all. we only managed due to the experience of all the rest of it (04:34:26 PM) zzz: shared credit to the i2pd project of course (04:35:01 PM) eyedeekay: Indeed. Back on track though, anything else on 4? (04:35:15 PM) RN: but you led the charge. (04:35:21 PM) zzz: if we want to do post-quantum that can be 3.0.0 :) (04:35:43 PM) eyedeekay: Good idea, that will be exciting (04:35:53 PM) zzz: nope, nothing else (04:36:05 PM) eyedeekay: Well 5) was: Mac arm64 bundle out of beta if 1.9.0 update was successful? (followup from last meeting) (04:36:43 PM) eyedeekay: Which zlatinb gave us a status update for on his way out the door, with the update being successful I see no reason against it (04:37:38 PM) eyedeekay: Anybody else have anything to add to this topic? (04:38:06 PM) zzz: I assume zlatinb meant the update worked; if so, he can remove the beta label on the web page (04:38:32 PM) zzz: that was the only reservation I had at the last meeting (04:38:33 PM) zzz: eot (04:39:45 PM) eyedeekay: OK. One of us should ping us when we see him online (04:39:52 PM) eyedeekay: Anything else for the meeting? (04:40:04 PM) eyedeekay: ping *him (04:41:14 PM) eyedeekay: Well I guess without his git creds I may as well remove the label (04:41:27 PM) eyedeekay: So I'll do it (04:41:43 PM) zzz: do you have confirmation the update worked? (04:42:11 PM) zzz: because he didn't say that above (04:42:53 PM) eyedeekay: I don't think I do (04:43:01 PM) eyedeekay: Nope (04:43:14 PM) eyedeekay: No I've not strictly speaking heard anyone say those exact words yet (04:43:21 PM) eyedeekay: So I'll wait (04:43:26 PM) eyedeekay: And ask him (04:43:32 PM) zzz: ok (04:44:19 PM) eyedeekay: Anything else for the meeting timeout 1m? (04:45:44 PM) eyedeekay: All right thanks everyone for coming

Windows Easy-Install Bundle 1.9.0 Release

Sun, 28 Aug 2022 00:00:00 +0000

This update includes the new 1.9.0 router and major quality-of-life improvements for bundle users

This release includes the new I2P 1.9.0 router and is based on Java 18.02.1.

The old batch scripts have been phased out in favor of a more flexible and stable solution in the jpackage itself. This should fix all bugs related to path-finding and path-quoting which were present in the batch scripts. After you upgrade, the batch scripts can be safely deleted. They will be removed by the installer in the next update.

1.9.0 Release

Mon, 22 Aug 2022 00:00:00 +0000

Update details

We have spent the last three months working on our new UDP transport protocol “SSU2” with a small number of volunteer testers. This release completes the implementation, including relay and peer testing. We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random. This will allow us to do much more testing in the next three months, finish the connection migration feature, and fix any remaining issues. We plan to enable it for everyone in the next release scheduled for November. No manual configuration is necessary. Of course, there’s the usual collection of bug fixes in this release as well. We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.

How to Switch to the StormyCloud Outproxy Service

Thu, 04 Aug 2022 00:00:00 +0000

How to Switch to the StormyCloud Outproxy Service

A New, Professional Outproxy

For years, I2P has been served by a single default outproxy, false.i2p whose reliability has been degrading. Although several competitors have emerged to take up some of the slack, they are mostly unable to volunteer to serve the clients of an entire I2P implementation by default. However, StormyCloud, a professional, non-profit organization which runs Tor exit nodes, has started a new, professional outproxy service which has been tested by members of the I2P community and which will become the new default outproxy in the upcoming release.

Apple Silicon Easy Install

Wed, 03 Aug 2022 00:00:00 +0000

We are pleased to offer an Easy Install BETA bundle for Mac OS running on Apple Silicon hardware. You can download it here:

I2P Mac OS Easy Install bundles

Speed

In our internal benchmarks the cryptographic operations are between 2 and 2.5 times faster than when running the Intel bundle under Rosetta.

Known Issues

Quitting I2P by right-clicking on the dock icon causes I2P to freeze and a “Force Quit” is necessary. This issue will be fixed for the 1.9 release.
If you already had an Intel bundle installed on your Mac, you need to modify some settings to prevent in-network updates from reverting you to an Intel bundle. Please see the instructions on the download page.

I2P Dev Meeting - May 03, 2022

Tue, 03 May 2022 00:00:00 +0000

Quick recap

Present: eyedeekay, zzz, zlatinb

Meeting Log

(03:48:58 PM) eyedeekay: It would seem not, I'll have a look at gitlab's bugtracker and see if I can find an explanation (04:00:03 PM) eyedeekay: Hi everyone, welcome to the development meeting (04:00:03 PM) eyedeekay: 1. Hi (04:00:03 PM) eyedeekay: 2. Release Date (04:00:03 PM) eyedeekay: 3. Development Status (1.8.0 / 0.9.54) (04:00:05 PM) eyedeekay: hi (04:00:13 PM) zlatinb: hi (04:00:17 PM) zzz: hello (04:00:45 PM) eyedeekay: 2. Release date (04:01:16 PM) eyedeekay: We need to decide on one, tentatively it's been the 23rd for a while, that works for me if it works for everybody else? (04:01:43 PM) zzz: that would be 13 weeks, fine with me (04:02:01 PM) zzz: need approval from eche|off eche|on if he's here (04:03:04 PM) eyedeekay: looks like not but I can email him after the meeting (04:04:00 PM) eyedeekay: looking like the 23rd pending email to ech (04:04:09 PM) eyedeekay: Anything else for 2? (04:04:58 PM) eyedeekay: 3. Development Status (1.8.0 / 0.9.54) (04:07:41 PM) eyedeekay: We're definitely less than a month from releasing 1.8.0/0.9.54 in any case, with lots of it being preparation/implementation for SSU2 by zzz (04:08:42 PM) eyedeekay: Big changes should be done soon, and tag freeze is on the 11th so translations must be in by then (04:09:28 PM) eyedeekay: /translations/strings (04:09:58 PM) eyedeekay: zzz, zlatinb anything to add on this topic? (04:10:44 PM) zzz: not much, I'm pretty much done, will be chasing a few minor things on my list in the next couple weeks (04:11:02 PM) zlatinb: nothing from me (04:11:03 PM) zzz: any new ssu2 stuff I'll probably either hold off or stick in a branch (04:11:11 PM) zzz: eot (04:12:05 PM) eyedeekay: thanks guys (04:12:49 PM) eyedeekay: Anything else for the meeting? Last-minute topics? timeout 1m (04:14:13 PM) eyedeekay: All right, quick meeting today (04:14:33 PM) eyedeekay: Thanks everyone for coming, I'll email echelon then post the logs

Jpackage Update for Java CVE-2022-21449

Thu, 21 Apr 2022 00:00:00 +0000

Update details

New I2P Easy-Install bundles have been generated using the latest release of the Java Virtual Machine which contains a fix for CVE-2022-21449 “Psychic Signatures.” It is recommended that users of the easy-install bundles update as soon as possible. Current OSX users will recieve updates automatically, Windows users should download the installer from our downloads page and run the installer normally.

Sat, 01 Jan 2022 00:00:00 +0000

Update details

Development Highlights

The 0.9.49 release began the migration to the new, faster ECIES-X25519 encryption for routers. It took many years of work on the specifications and protocols for new encryption, and this release, new installs and a very small percentage of existing installs (randomly selected at restart) began using the new encryption. This is the first time that the default encryption type has ever been changed, so the full migration would take place over several releases in order to minimize any issues.

I2P is not affected by the log4j vulnerability

Sat, 11 Dec 2021 00:00:00 +0000

I2P is not affected by the log4j 0-Day vulnerability which was published yesterday, CVE-2021-44228. I2P doesn’t use log4j for logging, however we also needed to review our dependencies for log4j usage, especially jetty. This review has not revealed any vulnerabilities.

It was also important to check all of our plugins. Plugins may bring in their own logging systems, including log4j. We found that most plugins also do not use log4j, and those that do did not use a vulnerable version of log4j.

I2P Dev Meeting - December 07, 2021

Tue, 07 Dec 2021 00:00:00 +0000

Quick recap

Present: eyedeekay, zzz, zlatinb

Meeting Log

(03:00:21 PM) eyedeekay: Hi everybody, welcome to the December 7 meeting (03:00:28 PM) eyedeekay: 1) Hi (03:00:28 PM) eyedeekay: 2) 1.6.1 Release Status (03:00:28 PM) eyedeekay: 3) jpackage Update Status (03:00:28 PM) eyedeekay: 4) Monero Integrations (03:00:28 PM) eyedeekay: 5) New SAM Library (03:00:37 PM) zzz: hi (03:00:41 PM) zlatinb: hi (03:01:05 PM) eyedeekay: Hi zzz, hi zlatinb (03:01:12 PM) eyedeekay: Anybody else here today? (03:01:16 PM) mode (-m ) by zzz (03:01:31 PM) eyedeekay: 2) 1.6.1 release status (03:02:32 PM) eyedeekay: Release 1.6.1 is available, the torrent is live, as are Debian/Ubuntu/Launchpad, Maven, GPlay, and our F-Droid (03:03:10 PM) eyedeekay: F-Droid's repository is still out of date, one of my tasks this week is to get our app working with their auto-build system again (03:04:01 PM) eyedeekay: Debian's repositories, as far as we know, aren't going to recieve our updates at this time, people who are using Debian packages should switch to deb.i2p2.de or deb.i2p2.no (03:05:18 PM) eyedeekay: The DMG bundle built by zlatinb has also been updated to 1.6.1 and is available on the mirrors and as an update (03:06:01 PM) eyedeekay: The exe bundle built by me is going to be up today, I had planned to do it yesterday but got bogged down in Windows updates so I'll do it this evening. (03:06:40 PM) eyedeekay: According to stats.i2p about 20% of the network has updated (03:06:47 PM) eyedeekay: Anything to add zzz, zlatinb? (03:09:13 PM) eyedeekay: Hello? (03:11:26 PM) eyedeekay: OK I'm back (03:11:40 PM) eyedeekay: (03:06:40 PM) eyedeekay: According to stats.i2p about 20% of the network has updated (03:11:40 PM) eyedeekay: (03:06:47 PM) eyedeekay: Anything to add zzz, zlatinb? (03:11:50 PM) zzz: yes (03:12:05 PM) zzz: no sign of a biglybt update yet, hopefully that will come soon (03:12:10 PM) zzz: no user complaints yet (03:12:26 PM) zzz: echelon had trouble with a 1.6.1-2 dev build but we don't know why (03:13:03 PM) zzz: also, users of any i2p package version (current or older) may have a problem due to changing jetty9 dependencies (03:13:24 PM) zzz: if so, sudo apt install libservlet3.1-java manually (03:14:44 PM) zlatinb: re biglybt I heard from Parg earlier today regarding an unrelated matter so he is ok. (03:15:52 PM) zzz: may also affect bleeding-edge ubuntu jammy, not sure (03:15:52 PM) zzz: eot (03:16:12 PM) zlatinb: eot (03:16:22 PM) zzz: I mean debian/ubuntu package (03:16:22 PM) zzz: eot2 (03:16:22 PM) zzz: this is on debian sid and maybe jammy only (03:16:22 PM) zzz: eot3 (03:16:22 PM) zzz: will give him a few more days and then bug him (03:16:31 PM) eyedeekay: Thanks zzz, the package/dependency thing will probably bubble up on Reddit if it's a problem (03:16:58 PM) eyedeekay: I run sid on the day-to-day basis and haven't hit this one so far (03:17:01 PM) zzz: ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997213 (03:18:40 PM) eyedeekay: 3) jpackage Update Status (03:19:36 PM) eyedeekay: Partly covered this one already, zlatinb's dmg packages are up on the mirrors and listed on the site (03:20:29 PM) eyedeekay: I had some updates I needed to do to my Windows laptop so didn't get the exe builds done last night, got it out for after the meeting (03:21:08 PM) eyedeekay: I've flipped my news server over to publish zlatinb's new packages (03:21:59 PM) eyedeekay: I haven't heard from any users so far (03:22:27 PM) zlatinb: The dmg jpackage is at this point well-streamlined. We did an end-to-end test of the in-network update with 1.5.0->1.5.1 and that worked (but from the second try) (03:23:02 PM) zlatinb: 1 person has downloaded the torrent according to snark (03:23:27 PM) zlatinb: not much else to report on the mac jpackage, it basically works (03:23:28 PM) zlatinb: eot (03:24:04 PM) eyedeekay: Thanks zlatinb (03:24:41 PM) eyedeekay: 4) Monero Integrations (03:25:55 PM) eyedeekay: There was some renewed interest in getting Monero-over-I2P working automatically in the GUI wallets(like Feather in particular) over the thanksgiving holiday (03:26:38 PM) eyedeekay: We're doing some design mockups and analysis of the tradeoffs of different configurations over here: (03:26:39 PM) eyedeekay: https://github.com/monero-project/monero-gui/issues/2274 (03:27:15 PM) eyedeekay: They're interested in adopting several things from us, including eventually our model for distributing software updates in-network (03:27:53 PM) eyedeekay: If anybody wants to participate in that discussion we're having it there mostly, and also on the Monero Matrix channel (03:28:06 PM) eyedeekay: Monero-Community (03:28:20 PM) eyedeekay: EOT (03:29:05 PM) eyedeekay: 5) New SAM library (03:29:14 PM) zzz: cool, I assume they've already looked at what bitcoin did for the low-level address protocols (03:29:17 PM) zzz: eot (03:30:31 PM) eyedeekay: Yes they have (03:31:24 PM) eyedeekay: The other cool thing that happened last week is the folks at diva.exchange have created a new SAM library for node.js/javascript in general (03:32:02 PM) eyedeekay: It's much more thoroughly and recently documented than the old one which is now unmaintained (03:32:07 PM) eyedeekay: Source is here: https://codeberg.org/diva.exchange/i2p-sam (03:32:23 PM) eyedeekay: NPM package is here https://www.npmjs.com/package/@diva.exchange/i2p-sam (03:33:00 PM) eyedeekay: Given how popular node is I'm giving it a bit of a signal boost, seems like everybody writes their webapps in node these days (03:33:15 PM) eyedeekay: eot (03:34:21 PM) eyedeekay: Anything else for the meeting? (03:35:13 PM) zlatinb: not from me (03:36:01 PM) eyedeekay: timeout 1, (03:36:04 PM) eyedeekay: 1m (03:37:03 PM) eyedeekay: OK then thanks zzz, zlatinb, next meeting will be Jan 4, 2022 (03:37:03 PM) eyedeekay: I will post the logs shortly

1.6.1 Release

Mon, 29 Nov 2021 00:00:00 +0000

Update details

Note: 1.6.1 is the current release. 1.6.0 was tagged but not released.

This release completes the rollout of two major protocol updates developed in 2021. The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year. Short tunnel build messages are enabled for a significant bandwidth reduction.

We added a theme selection panel to the new install wizard. We’ve improved SSU performance and fixed an issue with SSU peer test messages. The tunnel build Bloom filter was adjusted to reduce memory usage. We have enhanced support for non-Java plugins.

I2P Dev Meeting - November 02, 2021

Tue, 02 Nov 2021 00:00:00 +0000

Quick recap

Present: eyedeekay, zzz, zlatinb, Ryemantis_

Meeting Log

(04:00:16 PM) eyedeekay: Hi everybody, welcome to the November 2 Community Meeting (04:00:16 PM) eyedeekay: 1) Hi (04:00:16 PM) eyedeekay: 2) 1.6.0 Development Status / Upcoming Release (04:00:16 PM) eyedeekay: 3) mac/win jpackage beta status, user test reports, in-net 17.0.2 update status, plans for 1.6.0 update ? (04:00:35 PM) zzz: hi (04:00:38 PM) zlatinb: hi (04:00:55 PM) eyedeekay: Hi zzz, zlatinb (04:01:25 PM) eyedeekay: 2) 1.6.0 Development Status / Upcoming Release (04:02:25 PM) eyedeekay: Release thread is here: `http://zzz.i2p/topics/3170-1-6-0-release-summary` and we still haven't picked a date, I should have replied on that thread, do we want to do that here? (04:02:43 PM) zzz: yes please (04:03:18 PM) zzz: 3 weeks from now would be 13 weeks. +/- 1 week ok with me also (04:03:19 PM) eyedeekay: OK then in my case I am in favor of the week of the 29th, after US Thanksgiving (04:04:12 PM) zlatinb: I'm afk from my main workstation until early Dec, so can't build or sign jpackage installers. But I can still give an OTP for the signtool as that's on my phone. (04:05:34 PM) zzz: ok, so tentatively the week of the 28th then? eche|off eche|on any objections? (04:07:30 PM) eyedeekay: Week of the 28th sounds good to me for now. (04:08:34 PM) eyedeekay: Anything else for topic 2)? (04:08:45 PM) zzz: yeah, quick status (04:09:02 PM) zzz: looking like a fairly modest release as measured by amount of changes (04:09:27 PM) zzz: some SSU speedups are perhaps the headline (04:09:48 PM) zzz: zlatinb, if you have time to squeeze in the unit test deprecation fixes that would be good (04:09:52 PM) zzz: EOT (04:10:02 PM) eyedeekay: Thanks zzz (04:10:28 PM) zlatinb: yeah, no promises on the unit test :) (04:10:42 PM) eyedeekay: 3) mac/win jpackage beta status, user test reports, in-net 17.0.2 update status, plans for 1.6.0 update? (04:12:18 PM) zlatinb: I assume that is jdk 17.0.1, there's no 17.0.2 out yet afaik (04:12:21 PM) zzz: yeah I added that item just to give you two a chance to give the community an update (04:12:32 PM) eyedeekay: zlatinb and I discussed it a few days ago and evaluated the prospect of doing an OpenJDK 17 update for the jpackage installs (04:12:43 PM) zzz: ignore any typos :) (04:13:36 PM) Ryemantis__ is now known as Ryemantis_ (04:14:08 PM) eyedeekay: Right now we're prepared to do in-network updates of the jpackage installs but we are going to wait for the main release to do our jpackage releases which will update to either 17.0.1 or 17.0.2 (04:14:55 PM) zlatinb: 17.0.2 isn't due until mid-january, so we should definitely have a 1.6.0 jpackage release (04:15:32 PM) zlatinb: my view is that I would really like to do a dry-run of the in-network update process to shake out any insects, but that needs to happen in the next 7 days cause I'm afk afterwards (04:16:03 PM) zlatinb: to summarize, the following needs to happen: (04:16:12 PM) zzz: eyedeekay, that wasn't very clear... you're 'prepared' but you're not going to do it, you're going to wait? (04:16:28 PM) zlatinb: 1. update of the i2p.newsxml repo to produce entries.html per platform (04:16:50 PM) zlatinb: 2. Make sure idk and ech's news http servers can serve the new news.su3 files (04:17:17 PM) zlatinb: 3. branch i2p.i2p from the i2p-1.5.0 tag, bump CoreVersion/RouterVersion, tag i2p-1.5.1 (04:17:27 PM) zlatinb: 4. build jpackage installers, sign/notarize as necessary (04:17:47 PM) zlatinb: 5. build new entries.html with new release.json (04:17:50 PM) zlatinb: 6. deploy (04:17:51 PM) zlatinb: eot (04:18:03 PM) zlatinb: so I don't know if that can happen in 7 days, but it would be very nice if it could (04:19:10 PM) eyedeekay: By prepared I mean the i2p.newsxml changes produce valid feeds that can be used to distribute in network updates and they work on my lighttpd news setup (04:20:00 PM) eyedeekay: I need to add platform-specific entries.html support, right now everybody gets all the news but a different torrent (04:20:38 PM) zzz: even bigger picture, since it's beta, is it going well, are you getting downloads and/or complaints? (04:21:16 PM) zlatinb: downloads - ~25/day for mac, ~100/day for windows according to matomo (04:21:44 PM) eyedeekay: No major complaints, there was an issue with detecting the path to the installed package depending on architecture and whether windows was installed which affects some fraction of the Windows users but *only* when the launcher is run from the installer (04:22:03 PM) eyedeekay: So after the installer is run the bug goes away, and it's fixed in the new version (04:22:11 PM) eyedeekay: Well, will be (04:22:15 PM) zzz: great (04:22:21 PM) eyedeekay: That's the thing zab reported last month (04:22:40 PM) eyedeekay: *installed or updated from an earlier edition (04:24:34 PM) Ryemantis_: Hi everyone. Just wanted to also quickly check in and apologize for being quite the last few weeks. October was a very busy month for me and also had a hardware failure mixed in. After this week I should have some time to get my workstation back together and continue work on Android I2P. Currently working on LiveData, Remote-starting I2P, and UPnP fix. Will also update on the forums once I am back at (04:24:35 PM) Ryemantis_: it. Please let me know too if anything else needs more immediate attention. (04:25:04 PM) eyedeekay: Excellent to hear from you Ryemantis_ and welcome to the meeting (04:25:28 PM) eyedeekay: Thanks for the update on what you're working on, hardware failures and life happen to all of us (04:27:01 PM) eyedeekay: So back to 3) for a moment, for right now it's incumbent on me to add support for entries.html in data/platform/branch/entries.html instead of only in data/entries.html so we can have platform-specific newsfeeds (04:27:13 PM) Ryemantis_: Definitely appreciate the understanding and thank you all for you hard work (04:28:23 PM) eyedeekay: As opposed to one feed where everybody gets everybody's news (04:29:00 PM) eyedeekay: After that, we can start at step 3. in zlatinb's description (04:29:37 PM) eyedeekay: Anything for 3)? (04:30:20 PM) zlatinb: no I think that captures everything (04:30:46 PM) eyedeekay: Cool anything else for the meeting zzz zlatinb Ryemantis_ ? (04:31:04 PM) zzz: nope (04:31:30 PM) Ryemantis_: nope (04:31:49 PM) zlatinb: yeah quick one - next meeting is it on the 1st? (04:31:54 PM) ***zlatinb checks calendar (04:32:12 PM) eyedeekay: I think the 7th zlatinb (04:32:20 PM) zlatinb: ok nvm then (04:32:33 PM) eyedeekay: The first is a Wednesday by my calendar (04:33:28 PM) eyedeekay: Oh right that reminds me, DST. I've always scheduled the meetings on UTC, but does anyone want to adjust the time of the meeting for DST? (04:33:36 PM) zzz has changed the topic to: 1.5.0-4 | Tag freeze Wed. Nov. 17 (04:35:30 PM) eyedeekay: I'll take that as a no then. Unless someone brings it up in a forum thread, meetings will continue to be scheduled at the same time UTC (04:36:05 PM) eyedeekay: Thanks everybody for coming to the meeting, I'll post the logs in a few minutes.

I2P Jpackages get their First Update

Tue, 02 Nov 2021 00:00:00 +0000

A few months ago we released new packages which we hoped would help with onboarding new people to the I2P network by making the installation and configuration of I2P easier for more people. We removed dozens of steps from the installation process by switching from an external JVM to a Jpackage, built standard packages for target operating systems, and signed them in a way the operating system would recognize to keep the user secure. Since then, the jpackage routers have reached a new milestone, they are about to recieve their first incremental updates. These updates will replace the JDK 16 jpackage with an updated JDK 17 jpackage and provide fixes for some small bugs which we caught after the release.

I2P Dev Meeting - October 05, 2021

Tue, 05 Oct 2021 00:00:00 +0000

Quick recap

Present: eyedeekay, zzz, zlatinb, T3s|4

Meeting Log

(04:00:04 PM) eyedeekay: Hi everyone welcome to the community meeting (04:00:04 PM) eyedeekay: 1) Hi (04:00:04 PM) eyedeekay: 2) Remaining 0.9.50/1.5.0 items (04:00:04 PM) eyedeekay: 3) Jpackage Distributions (04:00:04 PM) eyedeekay: 4) 1.6.0 Development Status (04:00:15 PM) mode (-m ) by zzz (04:00:16 PM) eyedeekay: 1) Hi who is here today? (04:00:24 PM) zlatinb: hi (04:00:24 PM) zzz: here (04:00:48 PM) eyedeekay: Hi zzz, hi zlatinb (04:01:30 PM) eyedeekay: 2) Remaining 0.9.50/1.5.0 items (04:02:21 PM) eyedeekay: It's the same story here as last meeting, we currently cannot reach mhatta, and our debian main packages are therefore not updated (04:02:55 PM) eyedeekay: The official recommendation for installing I2P on Debian and Ubuntu will be changing in the next release to use our own .deb repository/PPA (04:03:26 PM) eyedeekay: We're also updating the instructions to reflect some recommendations which will make usage of our repository more secure (04:03:52 PM) eyedeekay: In the new setup, our .deb package signing keys will only be valid for our packages, instead of across all packages (04:04:04 PM) eyedeekay: Current deb/ubuntu users will not need to change anything (04:05:04 PM) eyedeekay: That's all I have for 2) anything from anyone else? (04:05:23 PM) T3s|4: eyedeekay: ^all noted, and I am also present (04:06:21 PM) eyedeekay: Thanks T3s|4 (04:06:21 PM) eyedeekay: Timeout 1m for 2) (04:07:36 PM) eyedeekay: OK 3) Jpackage Distributions (04:08:02 PM) zlatinb: I have two items for this topic, both not good (04:08:18 PM) eyedeekay: OK maybe you should start us off then (04:08:42 PM) zlatinb: 3.1 - the Mac DMG was not deployed properly to the sigterm.no mirror and I discovered it two weeks after release (04:09:11 PM) zlatinb: which is a major fail, we need to understand why it happened and how can we prevent it in future (04:09:30 PM) zlatinb: 3.2 - I just tried the windows AIO on a fresh windows 10 VM with just Firefox installed, and the .bat couldn't launch the I2P.exe (04:09:50 PM) zlatinb: launching I2P.exe manually worked fine, but something in the connection between the two failed (04:09:50 PM) zzz: what is AIO? (04:09:55 PM) eyedeekay: Easy-Install (04:09:56 PM) zlatinb: All-In-One (04:10:17 PM) zlatinb: EOT (04:11:42 PM) eyedeekay: The sigterm.no fail was partly my fault, I've resolved the issue there which had to do with the way I used to do mirror-syncing. (04:12:13 PM) eyedeekay: Re the Windows bundle, that should definitely not be the case, not good. I'll follow up with it on i2p.firefox as soon as the meeting is over, thanks for bringing it to my attention. (04:12:50 PM) zlatinb: ok, happy to help debug in any way (04:14:54 PM) eyedeekay: OK on my side I'm testing the changes to i2p.newsxml for us to do updates with, should be ready to review this week, there are some minor changes to the instructions for running the news server I'll need to go over with ech but we're already in communication about that (04:16:03 PM) zzz: 3.3 re: bundles for OSX, I recommend we advertise that they are untested on ARM Macs, that performance is unknown, and we should solicit testers (04:16:17 PM) eyedeekay: Yes agreed, I can make that change to the web site tonight (04:16:19 PM) zzz: and from that, decide when to start making ARM builds (04:17:17 PM) eyedeekay: Will do (04:17:20 PM) zzz: note that Java 17 in theory supports OSX ARm native, but I don't know if any of the openjdk-type sites have the JRE builds yet (04:18:26 PM) zzz: EOT, thx (04:18:38 PM) zlatinb: building for Mac aarch64 needs to happen on Mac aarch64 because jpackage (04:18:55 PM) zlatinb: so that means I need to get an ARM Mac at some point (04:19:12 PM) zlatinb: or someone else needs to get an Apple dev account (04:19:31 PM) zlatinb: eot (04:20:35 PM) eyedeekay: My Mac is also x86_64 unfortunately or I'd offer to do it (04:21:17 PM) eyedeekay: Anything else for 3)? (04:22:19 PM) eyedeekay: OK then 4) is 1.6.0 Development Status (04:25:17 PM) eyedeekay: zzz's been keeping us up to date with his developments and status here: `http://zzz.i2p/topics/3170-1-6-0-release-summary` (04:25:20 PM) eyedeekay: 6 weeks in, approx. 7 weeks to go (04:25:40 PM) eyedeekay: One of my two big planned changes for the router console isn't likely to go in, X-I2P-Locations in the HTTP proxy (04:26:10 PM) eyedeekay: The other, managing fork-and-forget plugins are going to be ready this week (04:27:10 PM) eyedeekay: Work on SSU2 continues in #LS2 (04:27:10 PM) eyedeekay: zlatinb and zzz have also been identifying and debugging performance issues in SSU1 (04:27:26 PM) eyedeekay: Anything to add zzz, zlatinb (04:27:28 PM) eyedeekay: ? (04:28:07 PM) zzz: so far there's not a lot of big things in this release (04:28:21 PM) zzz: very small diff as of now (04:28:50 PM) zzz: let's get any other big changes in soon (04:29:36 PM) eyedeekay: I'm not letting anything big or drastic go past this weekend for me. If I can't get it done by Monday I'll stick to small stuff. (04:29:40 PM) zzz: should be on track for a late Nov. release (04:30:43 PM) zzz: eot (04:30:45 PM) zzz: oh, also awaiting a post-EOL Jetty 9.3.30 release with some CVE backports. They've tagged it but not posted the builds yet, that's typical for them (04:31:43 PM) eyedeekay: If they wait to long to post the builds would it require delaying the release? (04:32:37 PM) zzz: should only be a week or so. if for some reason they don't do it, we can just take their patches (04:33:02 PM) eyedeekay: OK, thanks for clarifying (04:33:35 PM) eyedeekay: Is there anything else for 4) and if not, is there anything anyone else would like to discuss while we're here? (04:35:03 PM) eyedeekay: Timeout 1m (04:35:04 PM) zzz: if anybody with a registered nick wants voice, let me know before I click the 'm' button. sorry for the inconvenience (04:37:10 PM) eyedeekay: OK everybody thanks for coming to the meeting (04:37:10 PM) eyedeekay: See you around IRC and at the meeting next month (04:37:20 PM) eyedeekay: I've got some website updates to make (04:37:59 PM) eyedeekay: Please note zzz's ^ statement about voice on the IRC server (04:40:00 PM) eyedeekay: Oh one other thing, I'm going to be out-of-town Thursday and Friday, I'll be working offline those days. Message idk_afk if I'm not online and I will see it by the evening

Bitcoin Core adds support for I2P!

Sat, 18 Sep 2021 00:00:00 +0000

An event months in the making, Bitcoin Core has added official support for I2P! Bitcoin-over-I2P nodes can interact fully with the rest of the Bitcoin nodes, using the help of nodes that operate within both I2P and the clearnet, making them first-class participants in the Bitcoin network. It’s exciting to see large communities like Bitcoin taking notice of the advantages I2P can bring to them providing privacy and reachability to people all over the world.

Improving I2P Adoption and Onboarding using Jpackage, I2P-Zero

Wed, 15 Sep 2021 00:00:00 +0000

For the majority of I2P’s existence, it’s been an application that runs with the help of a Java Virtual Machine that is already installed on the platform. This has always been the normal way to distribute Java applications, but it leads to a complicated installation procedure for many people. To make things even more complicated, the “right answer” to making I2P easy to install on any given platform might not be the same as any other platform. For example, I2P is quite simple to install with standard tools on Debian and Ubuntu based operating systems, because we can simply list the required Java components as “Required” by our package, however on Windows or OSX, there is no such system allowing us to make sure that a compatible Java is installed.

I2P Dev Meeting - September 07, 2021

Tue, 07 Sep 2021 00:00:00 +0000

Quick recap

Present: eyedeekay, zzz, zlatinb

Meeting Log

(04:02:11 PM) eyedeekay: Hi everyone, sorry for the short notice, welcome to the September 7th meeting (04:02:11 PM) eyedeekay: 1) Hi (04:02:11 PM) eyedeekay: 2) Remaining 0.9.50/1.5.0 items (04:02:11 PM) eyedeekay: 3) Debian Repository Changes (04:02:11 PM) eyedeekay: 4) Jpackage Distributions (04:02:11 PM) eyedeekay: 5) 1.6.0 plans (04:03:12 PM) zlatinb: hi (04:03:21 PM) eyedeekay: Hi zlatinb (04:04:21 PM) eyedeekay: OK we can just get started, if anybody else joins us mid meeting please chime in and let us know you're here (04:04:49 PM) zzz: hi (04:04:54 PM) eyedeekay: Hi zzz (04:05:03 PM) eyedeekay: I'll take 2) remaining 0.9.50 items and 1.5.0 items (04:05:41 PM) serempa: hi (04:05:55 PM) eyedeekay: Hi serempa, welcome to the community meeting (04:06:19 PM) serempa: oh lucky me :) (04:06:20 PM) eyedeekay: It's the usual story, our Debian upstream package maintained by mhatta is not up to date, at this point we recommend that you use the project debian repository, newly under my administration at http(s)://deb.i2p2.de (04:06:54 PM) eyedeekay: First Tuesday of every month, 8PM UTC, tell your friends :) (04:07:19 PM) serempa: hmm actually I'm using i2pd (04:07:28 PM) zzz: looks like our f-droid and official f-droid still todo eyedeekay ? (04:07:41 PM) eyedeekay: Yes I was just coming to that (04:09:26 PM) eyedeekay: I am still getting the F-Droid repository updated, I have no control over when official F-Droid gets updated so the recommendation will be similar, our F-Droid will be updated before the official F-Droid repository is (04:10:23 PM) eyedeekay: So for up-to-date packages our self-hosted F-Droid is likely required (04:10:48 PM) zzz: I don't see anything else that's missing (04:11:42 PM) eyedeekay: Those are the only two release products remaining (04:12:35 PM) serempa: sorry to ask but any arm packages maintained by someone? (04:13:16 PM) zzz: we work on any platform that has java (04:13:20 PM) serempa: in rpi repos its 0.9.38-3.1 (04:13:47 PM) eyedeekay: That's raspbian without adding deb.i2p2.de to the sources.list? (04:14:01 PM) eyedeekay: Just to be clear serempa? (04:14:05 PM) zzz: you can follow the instructions on geti2p.net/debian to use our repo serempa (04:14:21 PM) serempa: ooh gotcha sorry (04:14:23 PM) eyedeekay: Yes it should have up-to-date pi packages (04:14:37 PM) eyedeekay: Which brings us to 3) Debian repository changes (04:14:37 PM) eyedeekay: We had a DNS issue with the old http://deb.i2p2.no repository (04:15:43 PM) eyedeekay: The server we used to use for it is no longer being used for anything, it's been retired. From now on, deb.i2p2.de and deb.i2p2.no are available using both HTTP and HTTPS (04:16:40 PM) eyedeekay: Please let us know if you run into any issues using the new setup, which should have fewer issues overall (04:17:22 PM) eyedeekay: Anything to add on 3)? (04:18:07 PM) eyedeekay: 4) Jpackage Distributions (04:19:29 PM) eyedeekay: Zab had a successful jpackage release so far, at least, some people are using it (04:20:29 PM) eyedeekay: We've got a better idea of how to adapt the news server now so that the jpackages can retrieve news and updates for their distributions (04:20:45 PM) eyedeekay: I'm delaying my release until I am able to release a new version of I2P In Private Browsing which includes a few bugfixes and which will set the home page a and search engine (04:21:31 PM) eyedeekay: That should be about another week (04:21:49 PM) eyedeekay: Anything else on 4) zlatinb? zzz? (04:22:06 PM) zlatinb: oops wait (04:22:06 PM) zlatinb: lag lag (04:22:37 PM) eyedeekay: Not a problem, go ahead zlatinb (04:22:39 PM) zlatinb: yes, the mac dmg is getting ~25 downloads/day on average (04:22:44 PM) eyedeekay: Nice! (04:23:10 PM) zlatinb: the /en/download/mac page gets good traffic too. A lot of people visit it after trying to download the .jar (04:23:50 PM) zzz: back sorry, computer issues (04:24:12 PM) eyedeekay: (04:22:39 PM) zlatinb: yes, the mac dmg is getting ~25 downloads/day on average (04:24:12 PM) eyedeekay: (04:22:44 PM) eyedeekay: Nice! (04:24:12 PM) eyedeekay: (04:23:10 PM) zlatinb: the /en/download/mac page gets good traffic too. A lot of people visit it after trying to download the .jar (04:24:24 PM) eyedeekay: In case you need it^ (04:25:09 PM) zzz: have you three resolved the news server URL issues yet? (04:25:39 PM) zlatinb: which doesn't work at all on recent Mac OS versions because notarization (04:25:39 PM) zlatinb: eot (04:25:39 PM) zlatinb_ is now known as zlatinb (04:25:47 PM) zlatinb: bad lag, sorry (04:27:00 PM) eyedeekay: Not yet, zlatinb when would be a good time for us to meet and talk about the remaining news URL issues? I have one or two questions for you about requirements for that, if we could meet this week that would be enough (04:27:42 PM) zlatinb: yes, I'm happy to do the python changes once we agree on how to handle things (04:27:56 PM) zlatinb: the big question is do we want separate news feeds for the different products or just different metadata (04:28:05 PM) zlatinb: we need to decide on that (04:29:45 PM) eyedeekay: Then I'd like to do a quick voice meeting for that sometime this week, we can schedule later, I'm not sure which pros and cons I care about yet (04:30:01 PM) zlatinb: sure (04:30:08 PM) eyedeekay: Sounds good (04:30:21 PM) eyedeekay: Anything else for 4)? (04:30:30 PM) zzz: you'll need a different feed the first time you do an in-between update, e.g. for java (04:31:17 PM) zzz: be sure to include echelon as he may have his own issues (04:32:19 PM) eyedeekay: In-between like from non-jpackage to jpackage? On my side that's "disabled" the NSIS installer won't over-write an IzPack installer if it finds one (04:33:01 PM) zzz: couldn't think of the right word. I mean an intermediate release, between the upstream releases, e.g. 1.5.1 (04:33:10 PM) eyedeekay: Oh I see (04:33:20 PM) eyedeekay: That makes sense, thanks for pointing that out (04:33:50 PM) eyedeekay: I'll send out a group email so we're all looped in (04:34:12 PM) eyedeekay: And we'll definitely need those because of OpenJDK releases (04:34:34 PM) eyedeekay: So we definitely care (04:35:13 PM) eyedeekay: OK anything else for 4)? (04:36:21 PM) eyedeekay: That brings us to 5) 1.6.0 plans (04:37:45 PM) eyedeekay: We should probably just take a moment to write out our plans down, timeout 3min (04:38:23 PM) zzz: I've updated the roadmap on the website for 1.5.0 and 1.6.0 - eyedeekay please review and fixup your items (04:38:45 PM) zlatinb: I'm going to see if there is a quick fix for the SSU slowness that I've observed in the testnet. If it's something simple like a delayed ack taking too long I think we can put it in 1.6.0 (04:39:04 PM) zlatinb: if it turns out to be more complicated then it's not really worth it as we're working on replacement (04:39:40 PM) zzz: I don't have a lot on my list for 1.6.0... at this point my main priority is SSU2, which is very early days, I don't expect it to be completed before mid next year (04:39:52 PM) eyedeekay: Ack, zzz, I will do this evening (04:39:52 PM) eyedeekay: I brought copypasta, this is the list taped to my bookshelf: (04:39:52 PM) eyedeekay: Code/Packaging: (04:39:52 PM) eyedeekay: 1) Eliminate the class of "Unmanaged" plugins, make Fork-and-Exec plugins manageable. (04:39:52 PM) eyedeekay: 2) Add support for Client-Side of X-I2P-Location to HTTP Proxy (04:39:52 PM) eyedeekay: 3) Debianize the I2P Browser Profile (04:39:52 PM) eyedeekay: 4) Pluginize the I2P Browser Profile (04:39:52 PM) eyedeekay: 5) Move goSam and sam3 to i2pgit.org instead of Github (04:39:52 PM) eyedeekay: 6) Clean up sam-forwarder UDP tunnels and move to go-i2p namespace (04:39:52 PM) eyedeekay: 7) Finally fix and merge go-i2p changes upstream (04:39:52 PM) eyedeekay: Web/Documentation: (04:39:52 PM) eyedeekay: 1) Document "How to Use" I2P for Android Browsing, Mail, Bittorrent (04:39:52 PM) eyedeekay: 2) Split download page into managable chunks, redirect to page by OS (04:39:52 PM) eyedeekay: 3) Document Jpackage install processes on Web Site (04:39:52 PM) eyedeekay: Misc: (04:39:52 PM) eyedeekay: 1) Migrate i2p.keyring.i2p to i2pgit.org (04:39:52 PM) eyedeekay: 2) Pluginize my other apps(BRB, Railroad, reseed-tools) (04:39:52 PM) eyedeekay: 3) Go rewrite of News Server(newsxml-tools) (04:39:52 PM) eyedeekay: 4) Generic Go SU3 Signing tool (04:40:33 PM) zzz: eyedeekay, I need misc #1 this week please (04:40:47 PM) eyedeekay: Absolutely (04:40:54 PM) zzz: super, thx (04:41:10 PM) eyedeekay: No problem (04:42:03 PM) eyedeekay: Anything else on 5)? (04:43:21 PM) eyedeekay: Anything else for the meeting? Timeout 2m in case of lag (04:43:53 PM) zlatinb: hmm yes has anyone noticed terrible lag today? I'm also having to try up to 10 times to push something to git.idk.i2p (04:46:39 PM) eyedeekay: I have noticed some inconsistent difficulties pushing to git.idk.i2p in the past week (04:48:07 PM) eyedeekay: Usually gone in a few minutes but requiring multiple retries (04:49:37 PM) eyedeekay: I have it configured for 6 tunnels and 2 backup tunnels using one hop right now (04:54:59 PM) eyedeekay: It isn't multihomed but I could make it so (04:55:08 PM) eyedeekay: If there's anything else for the meeting? timeout 1m (04:57:26 PM) eyedeekay: All right thanks for coming everyone, same time next month, I'll post the meeting minutes to the site shortly

Level up your I2P Skills with Encrypted LeaseSets

Tue, 07 Sep 2021 00:00:00 +0000

Level up your I2P Skills with Encrypted LeaseSets

It has been said in the past that I2P emphasizes support for Hidden Services, which is true in many ways. However, what this means to users, developers, and hidden service administrators isn’t always the same. Encrypted LeaseSets and their use-cases provide a unique, practical window into how I2P makes hidden services more versatile, easier to administer, and how I2P extends on the Hidden Service concept to provide security benefits for potentially interesting use-cases.

20 Years of Privacy: A Brief History of I2P

Sat, 28 Aug 2021 00:00:00 +0000

Invisibility is the best defense: building an internet within an internet

“I believe most people want this technology so they can express themselves freely. It’s a comfortable feeling when you know you can do that. At the same time we can conquer some of the problems seen within the Internet by changing the way security and privacy is viewed, as well as the extent to what it is valued.”

In October 2001, 0x90 (Lance James) had a dream. It started as a “desire for instant communication with other Freenet users to talk about Freenet issues, and exchange Freenet keys while still maintaining anonymity, privacy and security.” It was called IIP — the Invisible IRC Project.

I2P Celebrates its 20th Year

Thu, 26 Aug 2021 00:00:00 +0000

20 Years of I2P

It’s hard to believe, but I2P has been around for nearly 20 years! From its beginning as a C project which provided anonymous access to IRC, we’ve had hundreds of contributors, accepted checkins from dozens of coders, used 2 main languages, 3 version control systems, experienced a migration of its crypography, and multiple soft-forks. There have been around 500 registered sites on the Invisible Web, and countless unregistered I2P sites that were only accessible via their cryptographic hostnames.

1.5.0 Release

Mon, 23 Aug 2021 00:00:00 +0000

Update details

Thu, 10 Dec 2020 00:00:00 +0000

Hello Git, Goodbye Monotone

Most new I2P routers join the network by bootstrapping with the help of a reseed service. However, reseed services are centralized and comparatively easy to block, considering the emphasis on de-centralized and un-blockable connections in the rest of the I2P network. If a new I2P router finds itself unable to bootstrap, it may be a possible to use an existing I2P router to generate a working “Reseed bundle” and bootstrap without the need of a reseed service.

0.9.46 Release

Mon, 25 May 2020 00:00:00 +0000

Update details

0.9.46 contains significant performance improvements in the streaming library. We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.

Windows users only: This release fixes a local privilege escalation vulnerability which could be exploited by a local user that has the ability to run programs. Please apply the update as soon as possible. Thanks to Blaze Infosec for their responsible disclosure of the issue.

I2P Dev Meeting - May 05, 2020

Tue, 05 May 2020 00:00:00 +0000

Quick recap

Present: echelon, eyedeekay, zlatinb, zzz

Meeting Log

22:00:09 <eyedeekay> Hi everybody, welcome to the meeting for the first Tuesday of the month, and the final meeting before the 0.9.46 release. Who else is in attendance? 22:00:27 <zzz> hi 22:00:28 <zlatinb> hi 22:01:02 <eyedeekay> 0) Hi 22:01:02 <eyedeekay> 1) 0.9.46 status/release 22:01:03 <eyedeekay> 2) git migration status 22:01:03 <eyedeekay> 3) reseeds 22:01:03 <eyedeekay> 4) misc 22:03:07 <eyedeekay> This is the last IRC meeting before the release of 0.9.46, tag freeze is in about a week so translated strings must be finished by then. Any remaining changes must be submitted by the final deadline on the 22nd of this month. 22:03:58 <eyedeekay> We are on track to do this release on time as far as I know. 22:04:15 <eyedeekay> For my part, In the 0.9.46 cycle, I've continued on organizational, cosmetic, and UI changes to the applications, focusing on i2ptunnel mostly. I have also been working on a tunnel rotation setting for i2ptunnel, which I will be ready to check in soon. I doubt that I will finish dynamic tunnel allocation for i2ptunnel in time for 0.9.46. 22:04:21 <eyedeekay> Anyone have anything to add? 22:04:38 <zzz> yes 22:04:52 <zzz> the two headline items, streaming improvements and finishing ratchet, are done 22:05:01 <eyedeekay> Excellent! 22:05:03 <zzz> testing of ratchet with i2pd is going well 22:05:08 <zzz> good early reports on streaming 22:05:17 <zzz> tweaks will continue right up to the release 22:05:28 <zzz> I'm now focusing mostly on bug fixes, all over 22:05:55 <zzz> should be on track for a release early the week of the 25th 22:05:57 <zzz> eot 22:06:05 <eyedeekay> Very good. For people following along on #ls2, this has been very exciting to watch. 22:06:22 <eyedeekay> zlatinb, anything on your end? 22:07:29 <zlatinb> just lots of streaming work, to either continue or be applied to ssu in 47 22:07:52 <eyedeekay> Cool then. Moving on to 2) 22:08:14 <eyedeekay> 2) git migration status 22:08:14 <eyedeekay> Git has been prepared for general use, it has been moved into a datacenter, faster hardware, and a faster connection. Settings for a new git i2ptunnel have largely been decided upon, but not checked in. New gitlab signups will be presented with a basic terms-of-service. If they cannot comply with those TOS, the option of self-hosting git services is clearly outlined. It has backups, and it has both HTTPS and .oni 22:08:14 <eyedeekay> o support gittorrent is still ongoing, as is the trac ticket migration. As long as we continue to use trac for issues for the time being, I believe Git is ready for full-time use if we transition after this release. 22:10:16 <eyedeekay> mtn history remains a sticking point for some interesting repositories 22:15:23 <eyedeekay> So sorry, pidgin crashed on me. 22:15:23 <eyedeekay> Where were we? 22:15:38 <zzz> "mtn history remains..." 22:20:14 <eyedeekay> Thank you zzz. 22:21:03 <eyedeekay> I don't think I have much else to say about git from my end. If no one else has any comments, we can move on to reseeds 22:21:03 <eyedeekay> timeout 1min 22:21:03 <eyedeekay> Oh right I didn't mention the HTTPS url. Our git is visible at i2pgit.org 22:21:05 <eyedeekay> Moving on, topic 3) reseeds 22:21:05 <eyedeekay> zzz you have the floor 22:21:18 <zzz> wait 22:21:25 <eyedeekay> OK 22:21:31 <zzz> may I have an opportunity to add some thoughts on 2) ? 22:21:37 <eyedeekay> Sure 22:21:51 <zzz> thank you 22:22:11 <zzz> first of all, I'm getting better at git and gitlab, and I submitted 3 MRs to muwire this weekend 22:22:21 <zzz> two went well, one not as much, but we're learning 22:22:30 <zzz> feeling much more comfortable 22:22:52 <zzz> second: as mentioned I think last meeting, we would greatly benefit from a plan and a schedule on the migration 22:23:00 <zzz> I don't think one is posted anywhere 22:23:23 <zzz> in particular what branches when, and so on 22:23:23 <zzz> eot 22:27:42 <eyedeekay> Oh shoot that did not make it to the thread. We did discuss a schedule which included shifting things that were not i2p.i2p to git before i2p.i2p itself. That needs to be made available before we finish the transition. I will post it tonight. Thank you zzz for the reminder and for giving git a chance. 22:27:42 <eyedeekay> Anything else on 2) from anybody? 22:28:58 <eyedeekay> OK then 3) reseeds 22:29:04 <zzz> thank you 22:29:16 <zzz> I want to put out an urgent call for more reseeds 22:29:33 <zzz> meeh runs 3 of our 10, and all 3 were down for about two weeks. One came back. 22:29:43 <zzz> and the other two are still down, for different reasons 22:29:52 <zzz> he is unresponsive 22:30:12 <zzz> it's not a good situation. If they're still down in 2 weeks I'll remove them before the release 22:30:16 <zzz> and we'll be down to 7 or 8 22:30:39 <zzz> reseeds that are down result in a terrible new-user experience, it's unacceptable 22:31:12 <zzz> anybody that wants to run one please contact me 22:31:24 <fug> make running reseeds easier, then people will run them 22:31:26 <zzz> it would be nice to have one from biglybt or other i2p-adjacent organizations 22:31:45 <zzz> sure, could always be better 22:32:08 <zzz> unfortunately the person managing our reseeds and the software vanished last year, so that's unstaffed also 22:32:11 <eyedeekay> fug what qualifies as easier? That would be a job for me, I'm the Go guy, I'd be happy to dockerize it or make it checkinstallable or go get-able or whatever. 22:32:16 <zzz> EOT 22:32:44 <zzz> reseed plugin he also left half-done 22:32:47 <fug> eyedeekay: docker image would be good 22:33:03 <eyedeekay> Cool, I'll post it here in a day or two. 22:33:29 <fug> but something like a simple, single application that would do the reseeding with little to no required setup would be even better 22:35:50 <eyedeekay> That's pretty close to what the Go reseed is, although I'll admit there are some rough edges. I'll start with Docker. 22:36:01 <eyedeekay> Anything else on 3)? 22:36:23 <zzz> no. thanks for adding it to the agenda 22:36:48 <eyedeekay> You're welcome, no problem. 4) misc 22:39:29 <eyedeekay> I want to thank dr|zed for contributing the improved CSS for my personal web sites, I really appreciate the thought that was put into it. I also managed to get a little design advice on my WebExtension. Anybody doing something cool or exciting? 22:40:53 <eyedeekay> (That hasn't been mentioned elsewhere?) 22:42:04 <eyedeekay> timeout 1m 22:43:47 <eyedeekay> If no one else has anything to add, I'm going to go ahead and close the meeting. 22:44:49 <eyedeekay> All right *bafs*. Thanks everybody for coming and contributing to the meeting, see you around IRC

I2P Dev Meeting - April 07, 2020

Tue, 07 Apr 2020 00:00:00 +0000

Quick recap

Present: echelon, eyedeekay, zlatinb, zzz

Meeting Log

22:04:29 <eyedeekay> Hi everybody, who all is here? 22:04:40 <eche|on> peep :-=) 22:04:46 <zlatinb> hi 22:04:48 <zzz> present 22:06:18 <eyedeekay> All right, first topic, 0.9.46, zzz take it away 22:06:52 <zzz> wrapping up about two months of work on ratchet (proposal 144) 22:07:16 <zzz> I'm about at completion of "phase 2" where it's feature-complete 22:07:32 <zzz> and will be moving into more bug fixing and testing 22:07:51 <zzz> so 46 will be where more people can test it, and perhaps we enable it by default in 47 22:08:23 <zzz> going forward I'll be turning attention to other bug fixes and topics, such as streaming (working with zlatinb) 22:08:56 <zzz> EOT from me, so perhaps others would like to say what they're working on for 46 22:09:01 <eche|on> I just did upgrade to -5 2 days ago, still works fine, the tunnel patch round robin is included, currently no big change noted 22:09:56 <zlatinb> Ive been re-re-reading the TCP RFCs and noticing many discrepancies in our streaming and ssu implementations. So I rewrote them. Tickets are on trac 22:10:24 <eche|on> very very detailed reading and checking, zlatinb 22:11:34 <eyedeekay> I've started working on revisions to the i2ptunnel UI to reduce the amount of unnecessary information we present to new users and on the periodic key rotation mechanism for i2ptunnels 22:12:19 <eyedeekay> Lots of out-of-tree stuff for me too, I want to replace the Firefox profile bundle with something that works on non-Windows platforms as well, that is shaping up quite nicely. 22:12:32 <eyedeekay> Is that all for everyone? 22:12:46 <eche|on> looks like 22:12:49 <eyedeekay> Also, does anyone have any questions? 22:13:47 <eyedeekay> So far so good. Next is misc 22:14:37 <eyedeekay> Re: git migration, the decision has been made to migrate i2p.i2p *after* the next release and not before. Other repositories may be migrated sooner on a case-by-case basis. 22:15:06 <eche|on> good 22:15:20 <eyedeekay> Registration on git.idk.i2p is open, but it requires manual approval from an admin. We are timely about it, but feel free to ping me if you're in a hurry. 22:16:46 <eyedeekay> The preferred approach is to use git with SSH at this time, except for the initial clone, which you can perform by downloading the git bundle with snark. 22:16:50 <eyedeekay> EOT 22:17:18 <eyedeekay> Any questions for me re: git migration? 22:17:31 <eche|on> any progress on trac ticket inclusion? 22:17:49 <eyedeekay> I haven't had time to work on tracboat, so no not yet. 22:17:58 <eche|on> ok 22:18:41 <zlatinb> I have 2 questions regarding the migration: 22:18:41 <zlatinb> 1. Is there a way to change the network read timeout in ssh during the git clone. If yes, increasing it to something like 5 minutes will improve the chances of success 22:18:41 <zlatinb> 2. As trac hasnt been very reliable, is it ok to start opening or mirroring tickets to GitLab. Will they be looked at? 22:19:15 <eyedeekay> 1: I have been investigating this, it does not appear so but I cannot answer conclusively yet. 22:19:20 <zzz> re: 2) not by me, if you mean i2p.i2p 22:19:25 <eche|on> for 2: tracboat would be the script solution including all trac tickets into git 22:19:54 <zzz> related q: what's the plan to improve the consistently poor uptime of public-facing services run by meeh? 22:20:02 <eche|on> oh, sorry, for copy/migrating existnat tickets, new ones maybe a issue 22:20:18 <zlatinb> will ticket numbers be preserved? If so, what happens to the tickets already opened on GL, do they need to be deleted? 22:21:21 <eyedeekay> Ticket numbers should be preserved if I can get the migration to work, duplicate tickets will need to be deleted manually when one or the other ticket is closed. 22:22:08 <zlatinb> and if for whatever reason the migration cant work, whats the backup plan? 22:23:12 <zzz> we haven't yet agreed to trac migration at all; I assume any of this is just experiments. I propose that trac migration be deferred until after all mtn branches (including those not on GH at all yet) are migrated to git 22:23:33 <zzz> perhaps sept. earliest 22:23:42 <eche|on> the answer to this will correlate with zzz question, currently there is no fixed plan. My idea would be keeping trac running with older tickets 22:24:02 <eyedeekay> I don't have a way to fix trac, migrating tickets off of it is the only thing I personally can do. If I can't migrate them with tracboat, I have to do it myself. I know the gitlab side of it, I will just have to learn the trac side of it. I know gitlab seems like an obvious and appealing replacement for trac, but this is a substantial blocker. 22:24:03 <zlatinb> ok, and until a migration has been attempted are we to continue using trac? 22:24:41 <eyedeekay> Yes 22:24:51 <eche|on> ticket wise: please use trac as long until ticket migration has been done 22:24:53 <zzz> so who is in charge of fixing meeh's services? or have we given up and are now working to replace everything he runs? If that's what we're doing, let's be explicit about it 22:25:56 <eche|on> meeh is in charge for his services. trac should be replaced by git. 22:26:31 <zzz> which doesn't fix the systemic issues with other services such as deb repo and outproxy 22:26:31 <eche|on> the debian repository is a open point currently, I did a mirror of it, but currently need more time to look into setting it up as expected 22:27:32 <eche|on> outproxy I will not touch at all 22:27:50 <eyedeekay> I am happy to help replace meeh's deb repo, but I can't do anything for outproxy. 22:29:19 <eche|on> meeh often told us the issue is mostly the old system on old IPs he is using, with welterde changing the DNS that did change today 22:29:33 <zzz> I assume ticket migration for a particular branch X would occur only after we have moved from mtn to git for X 22:29:35 <eche|on> but currently no idea 22:30:55 <eyedeekay> zzz Yes 22:31:08 <eyedeekay> Re: ticket migration 22:31:27 <eyedeekay> That way we would not confuse people about where issues are being discussed. 22:32:21 <eyedeekay> Anything else? 22:34:22 <eyedeekay> timeout: 60s 22:36:22 <eyedeekay> **Bafs** OK thanks for coming everyone

Using a git bundle to fetch the I2P source code

Wed, 18 Mar 2020 00:00:00 +0000

Cloning large software repositories over I2P can be difficult, and using git can sometimes make this harder. Fortunately, it can also sometimes make it easier. Git has a git bundle command which can be used to turn a git repository into a file which git can then clone, fetch, or import from a location on your local disk. By combining this capability with bittorrent downloads, we can solve our remaining problems with git clone.

Gitlab over I2P Setup

Mon, 16 Mar 2020 00:00:00 +0000

This is the setup process I use for configuring Gitlab and I2P, with Docker in place to manage the service itself. Gitlab is very easy to host on I2P in this fashion, it can be administered by one person without much difficulty. These instructions should work on any Debian-based system and should easily translate to any system where Docker and an I2P router are available.

Dependencies and Docker

Because Gitlab runs in a container, we only need to install the dependencies required for the container on our main system. Conveniently, you can install everything you need with:

Git over I2P for Users

Fri, 06 Mar 2020 00:00:00 +0000

Tutorial for setting up git access through an I2P Tunnel. This tunnel will act as your access point to a single git service on I2P. It is part of the overall effort to transition I2P from monotone to Git.

Before anything else: Know the capabilities the service offers to the public

Depending on how the git service is configured, it may or may not offer all services on the same address. In the case of git.idk.i2p, there is a public HTTP URL, and an SSH URL to configure for your Git SSH client. Either can be used to push or pull, but SSH is recommended.

I2P Dev Meeting - March 03, 2020

Tue, 03 Mar 2020 00:00:00 +0000

Quick recap

Present: echelon, eyedeekay, sadie, mikalv, zzz

Meeting Log

20:59:49 <eyedeekay> Hi everybody, about a minute until meeting time, who all is here? 20:00:33 <eche|on> Ok, it is time. Welcome to the IRC dev meeting 3rd march 2020. 20:00:40 <eche|on> Agenda: 20:00:40 <eche|on> 0) Hi 20:00:40 <eche|on> 1) 0.9.45 release status 20:00:40 <eche|on> 2) 0.9.46 plans 20:00:40 <eche|on> 3) I2P Android state/future 20:00:40 <eche|on> 4) MTN => Git plans 20:00:40 <eche|on> 5) misc - UX plans for 2020; donation page 20:01:28 <eche|on> so, as the old baffer is nearly unuseable for me, and I do not have a new one yet, lets start 20:01:31 <eche|on> 0) hi 20:01:33 <nextloop> hi! 20:01:38 <eche|on> I am here, eyedeekay is here, nextloop is here 20:01:40 <zzz> hi 20:02:21 <eche|on> ok, lets go on to 1) 20:02:36 <eche|on> 0.9.45 was released some days ago and it looks fine so far 20:02:42 <eche|on> any comments? 20:03:03 <zzz> all went smoothly on my side 20:03:11 <nextloop> what's the status of android? 20:03:16 <zzz> in-net, PPA, deb repo. No major reports so far 20:03:31 <eche|on> android still not done, see point 3 20:03:34 <zzz> I leave it to you to report maven/fdroid/android/mac, I have no insights on that 20:03:47 <eche|on> mac was built and put online 20:04:09 <eche|on> from my side it went well enough 20:04:13 <eche|on> hi sadie_ 20:04:45 <eche|on> ok, and now go on to 2, the 0.9.46 plans 20:04:55 <eche|on> zzz: any plans for 0.9.46 on your roadmap? 20:05:17 <sadie_> hi 20:05:51 <zzz> rrd4j is in replacing jrobin 20:05:56 <zzz> about 30 checkins so far in a week 20:06:10 <zzz> orignal and I hope to finish up ratchet (prop. 144) 20:06:28 <eche|on> good pace, will slow down for sure. Will ratchet be in .46 or a maybe? 20:06:41 <zzz> jogger SSU fixes... maybe... maybe not... 20:07:23 <zzz> ratchet is in 45, it works, but a lot of the details aren't finished, hopefully will be for 46 20:07:36 <eche|on> ok, good. 20:08:15 <zzz> ratchet todo list `http://zzz.i2p/topics/2639` 20:08:49 <eche|on> whats the estimated timeframe for a 0.9.46 release? may? 20:08:50 <zzz> what's everybody else's plans? 20:09:15 <eche|on> eyedeekay, sadie, plan for 0.9.46 ? 20:09:18 <eyedeekay> My top priority is the readme located in the router console at this time, currently I am slightly blocked on a chat recommendation still but will resolve that soon. I'll be building on this to progressively work on our in-console help. 20:09:24 <zzz> late may is my proposal, subject to other's agreement 20:10:07 <eche|on> ok, late may looks good, will verify with others the next days. 20:10:20 <eyedeekay> I am happy with late May 20:10:32 <mikalv_> same 20:10:43 <eche|on> ok, any other notes on 0.9.46 plans? 20:10:51 <eche|on> comments, questions? 20:11:24 <mikalv_> no but we should land the android architecture support question now that we got everyone here 20:11:32 <eche|on> thats point 3 :-) 20:11:44 <mikalv_> basically google says: support x64 or drop the platform (if only provided 32bit) 20:11:47 <eche|on> wo which we come now after no one stood up for another question on point 2 20:11:56 <mikalv_> great 20:11:59 <eche|on> mikalv_: whats the state of android 0.9.45 ? 20:12:31 <mikalv_> I've built it, got google's complaint, and awaited this meeting for a administrative decision to what we should do 20:12:48 <mikalv_> if we should drop mips and such, or try produce the 64bit binaries for it 20:13:04 <zzz> whats your recommendation? 20:13:34 <mikalv_> once that's landed, we should be ready to release at any time if we remove it, and not sure if we need to produce the 64bit binaries as I've not tried that before 20:13:42 <eche|on> IMHO not much MIPS and x86 android devices available, so drop them for 0.9.45, but keep it on mind 20:13:57 <sadie_> For me ,Information architecture review of console and website , then Identity and values workshop with Ura and Simply Secure. Post install work, infrastructure and policy review 20:14:06 <mikalv_> I tried to get google play to somehow tell me how much they where used (the different architectures) but I couldn't find any metrics for it 20:14:10 <zzz> you have user stats mikal? 20:14:22 <eche|on> ok, sadie, point 2 addition, noted :-) 20:14:23 <mikalv_> the closest we get is a list of devices 20:14:27 <nextloop> the architecture is just relevant for the NDK jbigi lib right? 20:14:35 <mikalv_> but then, we need to know what arch all the different devices is 20:14:38 <zzz> sounds like an easy decision to me 20:14:40 <eche|on> yes, nextloop, mostly yes 20:14:44 <mikalv_> yes nextloop 20:14:48 <nextloop> because it gets built from source every f-droid release 20:15:17 <nextloop> i never veryfied if it really gets used or uses the java fallback 20:15:25 <eche|on> ok 20:15:25 <mikalv_> but is that for the 64bit versions so the f-droid has binaries that don't exists in the gplay version? 20:16:24 <nextloop> it just runs the shell script i believe. whatever is built there gets built 20:16:50 <eche|on> mikalv_: please check the shell script/f-droid version, if 64 bit available, use it, else drop that architecture 20:17:24 <mikalv_> okay I'll do so then unless any objections 20:17:35 <eyedeekay> No objections from me. 20:17:40 <mikalv_> (?) 20:17:43 <mikalv_> great 20:17:46 <eche|on> now to the more interesting point: future of android I2P version. As bote is nearly dead and not in use, and no dev available, the use case for android I2P is gone 20:17:57 <eche|on> do we want a future android I2P release? 20:18:09 <eche|on> even without bote and nearly null use case? 20:18:16 <eche|on> eyedeekay: opinion? zzz? 20:18:28 <zzz> your premise is that the sole use case for the android router app is bote? 20:18:47 <eche|on> as the browser has other issues (as mikalv_ told me), what is left? 20:18:59 <eyedeekay> People are using Java I2P on Android for non-Bote things. There's a dude hosting Yacy on top of termux or some crazy nonsense like that. I don't want to stifle people. 20:19:03 <eche|on> beside being a simple router on small devices 20:19:18 <zzz> it's simply not true that browsing is broken 20:19:34 <mikalv_> its basically no "non technical" way to use the android version of today 20:19:39 <eche|on> ok, good, so your both vote for future of android 20:19:41 <zzz> right idk? 20:19:48 <mikalv_> you can tweak firefox in about:config which mozilla warns you to not do 20:20:06 <eyedeekay> Yes I think Android can have a future. 20:20:06 <mikalv_> but beyond that, it need some kind of life purpose in my point of view 20:20:45 <eche|on> but as I have seen also, android will change owner to eyedeekay, is that correct? 20:20:46 <zzz> what's behind this? does the team not want to support it? 20:20:51 <eyedeekay> Yes 20:21:00 <eche|on> O 20:21:01 <eche|on> ok 20:21:12 <eche|on> zzz: I try to figure opinions and ideas 20:21:26 <eche|on> and as it looks, eyedeekay will support androif for 0.9.46 and further on 20:21:35 <eyedeekay> I will continue to at least maintain Android builds, I will take ownership of it. I do wish to keep supporting it. Just to clarify 20:21:45 <zzz> I think android is important. Right now we're providing terrible support. We aren't fixing _any_ bugs and there's no new development 20:21:48 <eche|on> and as users seem to use it, it will be supported 20:22:12 <zzz> if we can't increase our support with the current team than we should hire somebody new to do it 20:22:33 <eche|on> ok 20:22:48 <sadie_> I have applied for support that I would suggest going to Android. No answer yet. 20:23:12 <sadie_> I think that Android is important 20:23:38 <eche|on> so android i2p will live on and we try to get better support for it, at least better than just supllying new releases 20:23:59 <eche|on> and if funding is available, get a dev on funds to support android dev 20:24:25 <eche|on> any questions, comments, hints on point 3 android? 20:25:43 <eche|on> ok, going on to topic 4) the forthcoming monotone to Git translation 20:26:20 <eche|on> we decided to drop monotone and use git instead, a translation plan is still in work to maintain best useability and features which are needed for I2P development 20:26:40 <eche|on> currently eyedeekay did setup a git server on `http://git.idk.i2p` and made a howto on https://github.com/eyedeekay/git-over-i2p/blob/master/GIT.md 20:27:02 <eche|on> we do work on getting trac into the git instance and migrate all the tickets into git 20:27:26 <eche|on> after that migration is done securly and verified, we decide on a date to switch 20:27:46 <eche|on> currently we do look out for testers of the guide and the git server inside of I2P 20:28:03 <eche|on> and for sure: for more hints, tips, ideas, feature requests on this topic 20:28:07 <eche|on> so, please 20:28:12 <eche|on> eyedeekay: more comments on this? 20:28:39 <eyedeekay> I've also been working on adding SOCKS support to webtorrent, which will hopefully make it possible for us to use gittorrent as well in the near future. 20:29:19 <eche|on> nextloop: comments? as you do work the sync script currently? 20:29:49 <zzz> is muwire code set up and bridged to GH as we planned? 20:30:18 <eyedeekay> While my testing over the past few weeks has been successful, I would like it very much if people could review my guide and make comments where it could be clarified or simplified. 20:30:37 <nextloop> the topic of breaking connections during initial cloneing is solved by doing shallow clone and iterative unshallowing, am I right? 20:30:46 <eche|on> zzz: no idea yet, not yet worked on my side 20:30:55 <eyedeekay> Yes that works right now. 20:30:56 <zzz> idk? 20:31:13 <eche|on> yes, nextloop, that does help a bit, but even the depth of 1 version is still ~100 MB to fetch 20:31:37 <eche|on> with unshallowing it grows slightly bigger (4-5 times in my experiment) 20:31:49 <zzz> I have a question about user names on git.idk - do we need to pick a username unused on GH, or do we need to defensively register it on GH, to make it all work right? 20:32:12 <nextloop> zzz: github identifies the committers based on e-mail addresses. 20:32:17 <zzz> there was a report on zzz.i2p a while back that there are several fake zzz-i2p accounts on GH. is that a problem? 20:32:42 <nextloop> so if you add your email you use for i2p git to github the commit will be linked to your account 20:33:16 <nextloop> eyedeekay: is the regular torrent archive already in place? if i remember correctly you were working on that 20:33:48 <eyedeekay> Well it's generatable, but there's nothing scheduling it yet 20:34:32 <zzz> so I need to register on git.idk with a valid clearnet email address if I want to (before or after) register on GH? or that's a local setup thing? 20:34:55 <zzz> anyway, we're in the weeds here, sorry, I'll work with idk to figure it out 20:35:17 <eyedeekay> You don't need to pick an unused GH username AFAIK, you could work entirely from the gitlab instance and we wouldn't need github at all 20:35:17 <eche|on> clearnet email should be in this case the i2pmail.org address IMHO 20:35:46 <nextloop> zzz: yes for github you need to verify the email. use i2p-mail.org perhaps? 20:35:54 <eche|on> currently the plan is to use the gitlab (idk in i2p net git instance) for our work and sync to github 20:36:23 <eche|on> the trac tickets would be on in-net gitlab server 20:36:25 <nextloop> eyedeekay: i would be motivated to setup such an automatic archiving 20:36:27 <zzz> I just want to make sure it's not linked to some fake zzz account when it gets bridged to GH 20:36:47 <eche|on> (sorry for the hassle, gitlab and github are both servers with lots of features around git, both do nearly the same tasks) 20:37:18 <eche|on> valid point, zzz 20:37:47 <eche|on> ok, before going into much deeper details, any more comments? 20:39:06 <eche|on> going on to topic 5 - misc topics. currently 2 from my side: a) donation page and b) UX plans for 2020 20:39:40 <eche|on> 5a) a new donation page is setup by mikalv_ on https://donate.i2p.io/ and those accounts are all benefits to the I2P company mikalv_ is running with torkel in norway 20:40:07 <eche|on> it is live and do collect donations from now on, soon (tm) it will be advertised on webpage and twitter 20:40:24 <eche|on> any comments on this? issues, problems? 20:41:29 <eche|on> 5)b) UX plans for 2020 - sadie is working with elio on a UX project, in whic elio has been granted funds to work on I2P UX 20:41:42 <eche|on> sadie, any more information, plans, ideas, comments? 20:42:05 <sadie_> Information architecture review of console and website , then Identity and values workshop with Ura and Simply Secure will be the work for this month 20:42:41 <sadie_> We have received very good feedback on the set up wizard! 20:43:31 <eyedeekay> From me, the Browser project has been officially placed on hiatus. We pretty much couldn't have picked a worse time to attempt such a thing, as Mozilla's codebase has been changing drastically as we tried to work with it. The project will be revisited when we have less of a moving target. I will be making improvements to I2P and web browsing in less time-dominating projects. 20:43:36 <sadie_> So research, synthesis and documentation phase for now. 20:44:03 <zzz> eyedeekay, status of beta 8, promised in 'a couple days' at the meeting a month ago? 20:44:24 <eyedeekay> It is cancelled. There was no use in creating it, as it will only be viable for a very short time. 20:44:35 <eche|on> thank you sadie, whats the timeframe for the whole project? end date 20:44:56 <eche|on> eyedeekay: please announce that on webpage 20:45:21 <eyedeekay> Will do 20:45:22 <sadie_> End date projection for study is mid June 20:45:49 <zzz> if beta 8 would not have been viable for long, I assume beta 7 on our website is long since obsolete and should be removed, for sure 20:45:53 <eche|on> ok, and is there a rough idea at which timepoint UX enhancements will get into I2P code? 20:46:59 <eche|on> sadie? 20:47:28 <eche|on> zzz: that should be done with the announcement of the final end of the browser project 20:47:33 <sadie_> It will not be until after June. We need to go through the process first. If there are improvements we can execute on easily as they are suggested and approved we will. 20:47:35 <zzz> sadie_, is the funding organization for Ura public? and if so who? 20:47:46 <mikalv_> yes the browser project was unluckly started at the wrong time as mozilla rewrote basically everything in their codebase the same year 20:48:05 <anonymousmaybe> i2pbrowser currently has many security vulnerabilities didnt fixed since ages because it didnt catch up with TB/FF patched releases 20:48:09 <mikalv_> so each release had quite some different code than the previous one and so on 20:48:23 <eche|on> sadie_: ok, looks like early 0.9.47, maybe 0.9.48 will be first i2p version whcih will get changes of this project 20:48:25 <sadie_> The funding for this study is provided through usability lab. 20:48:39 <zzz> which is OTF? 20:48:40 <sadie_> correct ech 20:48:47 <mikalv_> tbb had 10 people rewrite all their patches like three or four times in 2019 20:49:34 <eche|on> https://www.opentech.fund/labs/usability-lab/ 20:49:45 <sadie_> OTF Resource Labs 20:49:58 <zzz> would be good to get some thanks-tweets and a blog post out there if it's public, this is big news that we should be telling people about! 20:50:37 <fug> you should also tell people how you gutted the UI and removed docs 20:51:09 <eche|on> On a minor down side, the InternetFreedomFestival in Valencia, spain, was canclled due to high risk on the corona-virus. 20:51:18 <eche|on> so new I2P participation in there 20:51:38 <eche|on> zzz: noted and will happen 20:52:15 <sadie_> zzz, yes I have announced it on forum last week. PR rollout has been planned 20:52:26 <eche|on> any more comments, topics under topic 5) misc? 20:52:51 <eche|on> `http://i2pforum.i2p/viewtopic.php?f=27&t=925` 20:53:00 <eche|on> is the forum entry with news entries 20:53:10 <fug> zzz: github does detection based on the email specified in commits, said email needs to be registered with a github account, and registration requires sending a confirmation link to the email 20:53:33 <fug> zzz: so in case of your commits with .i2p mail, you won't be able to confirm them 20:53:55 <anonymousmaybe> any road map for i2prouter isolation? https://trac.i2p2.de/ticket/2132 20:54:47 <eche|on> i2p debian package split up is IMHO on hold currently 20:54:51 <eyedeekay> No road map on that yet. 20:55:02 <anonymousmaybe> ah sad.. 20:55:22 <eche|on> AFAIK some discussion with the deb maintainer were made, with no productive outcome yet 20:56:02 <anonymousmaybe> ticket already there but no work done for it 20:56:17 <zzz> no 45 for sid yet either, no news from mhatta 20:56:38 <anonymousmaybe> mikalv_ fixed trac filtering Tor/I2P users? 20:56:42 <fug> there's https://github.com/tracboat/tracboat for trac->gitlab migration, has it been evaluated? 20:57:25 <eche|on> IMHO eyedeekay does trying tracboat for the migration, at least the name was mentioned 20:57:28 <fug> where is some information page that describes status of migration to git? 20:57:46 <eche|on> currently no page except for the howto and git server mentioned above 20:57:56 <eche|on> as we are still in early phase 20:58:17 <fug> you still should have a page for that info 20:58:21 <eche|on> noted to create a info page 20:58:22 <mikalv_> I hope it's fixed, has anyone had issues with it the past days? 20:58:38 <eyedeekay> trac? Not lately 20:58:49 <eche|on> yes, mikalv_, there was a user in here trying to push a ticket and got spam blocked 20:58:59 <eche|on> but ok, any other comment for dev meeting? 20:59:09 <zzz> outproxy is still a pile of crap but trac working well for me 20:59:20 <mikalv_> and now we're talking about trac's own system, and not the i2ptunnel right? 20:59:26 <eche|on> yes 20:59:43 <eche|on> uhh, the 60 min limit is here... 20:59:55 <eche|on> any further comments? 21:00:05 <fug> yes, info about developing i2p 21:00:16 <fug> should mention usage of new git instance instead of mtn that no one uses 21:00:45 <eche|on> will be done, if it is valid and verified to be done 100% 21:01:24 <eche|on> If no other comment gets in, the timeframe of this IRC meeting getting nearly a 60 min, which is a soft border, I would like to close this meeting. Due to a missing appropriate buffer, I'll make a "plopp" sound. 21:01:45 <eche|on> so, ears up: "plopp" 21:01:56 <sadie_> mic drop 21:02:02 <eche|on> dev meeting over. thank you all for your time, ideas and comments 21:02:14 <eche|on> a log will be posted soon 21:02:14 <sadie_> thanks ech

0.9.45 Release

Tue, 25 Feb 2020 00:00:00 +0000

Update details

0.9.45 contains important fixes for hidden mode and the bandwidth tester. There’s an update to the console dark theme. We continue work on improving performance and the development of new end-to-end encryption (proposal 144).

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

RELEASE DETAILS

Changes

Dark theme improvements
Console icon changes
Move some translations from console to router and core for embedded uses
Jetty 9.2.29
Tomcat 8.5.50
i2psnark HTML5 preview player for partial files

Bug Fixes

I2P Dev Meeting - February 04, 2020

Tue, 04 Feb 2020 00:00:00 +0000

Quick recap

Present: echelon, eyedeekay, sadie, zlatinb, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) I2P Browser project status (sadie, meeh, idk) 20:00:00 <zzz> 2) Outproxy use cases / status (sadie) 20:00:00 <zzz> 3) 0.9.45 development status (zzz) 20:00:00 <zzz> 4) Status scrum (zlatinb) 20:00:04 <zzz> 0) Hi 20:00:06 <zzz> hi 20:00:19 <zlatinb> hi 20:00:29 <zzz> 1) I2P Browser project status (sadie, meeh, idk) 20:00:51 <zzz> sadie, what's the latest on the browser project? 20:01:22 <zzz> or, as she's not here, anybody else? 20:02:09 <eyedeekay> Hi 20:02:55 <zzz> eyedeekay, you have a status update on the browser project? 20:03:22 <eyedeekay> We're about to put out the last release of the browser for six months before it goes on hiatus. We've decided we need to be much smarter about how we encapsulate configuration and build the browser for the project to become sustainable, right now it is a massive drain on resources. A more complete statement will be issued on the website at the time of the browser release. 20:04:11 <zzz> this release will be beta 8? iirc at our last meeting two months ago, it was projected to be out within 3 days 20:04:58 <eyedeekay> Yes, that is the reason it's going on hiatus. It's simply not sustainable to go about it the way we have been, other options need to be explored that require us to do less work to merely keep up with Firefox release. 20:05:27 <zzz> ok. welcome sadie_, you have anything to add? 20:05:44 <sadie_> no 20:06:05 <zzz> anybody have any comments or questions on 1) browser ? 20:06:52 <zzz> anything else on 1) ? 20:07:29 <zzz> 2) Outproxy use cases / status (sadie) 20:07:32 <eyedeekay> We will be providing recommendations for replacement procedures to configure browsers. 20:07:47 <zzz> ok 20:08:04 <zzz> sadie_, please give us an update on the outproxy research 20:08:51 <sadie_> outproxy research has been postponed over the past months. 20:09:42 <zzz> ok, any outlook on when it may restart? 20:11:53 <zzz> any comments or questions on 2) outproxy ? 20:12:20 <sadie_> it is not a high priority in the immediate future, as per roadmap. 20:12:40 <eyedeekay> Meeh has actually improved outproxy performance noticably of late for the general-use, default outproxy at false.i2p 20:13:11 <zzz> anything else on 2) ? 20:14:04 <zzz> 3) 0.9.45 development status (zzz) 20:14:15 <zzz> development is going well 20:14:32 <zzz> we have 17K lines of diff so far, including a big update to the dark themes 20:14:38 <zzz> some fixes for hidden mode 20:14:47 <eche|on> hope that will help 20:15:16 <zzz> some icon changes, new tomcat, new jetty, HTML5 preview player for partial files in i2psnark 20:15:52 <zzz> dates are in the /topic above. tag freeze in a week, checkin deadline in 2 1/2 weeks, release in 3 weeks 20:16:34 <zzz> Not strictly in .45, but I can announce that we've had good interoperability test progress with i2pd on proposal 144 (new encryption) 20:16:59 <zzz> and we're continuing to work through bugs and issues on both sides, and in the proposal itself 20:17:27 <zzz> anybody else wish to highlight anything that's gone in for .45, or anything that will be? 20:19:01 <zzz> anything else on 3) ? questions or comments? 20:19:22 <eche|on> nope 20:20:02 <zzz> 4) Status scrum (zlatinb) 20:20:08 <zzz> go ahead zlatinb 20:20:15 <zlatinb> Hi. Briefly: 1) what youve done since last meeting 2) what you plan to do next month 3) any blockers or help needed. Say EOT when done 20:20:46 <zlatinb> me: 1) MW plugin 2) More work on MW plugin, jogger rewrite of SSU 3) no blockers EOT 20:21:16 <zzz> 1) bug fixes, proposal 144, review jogger patches and proposal; 2) more of the same, plus .45 release; 3) no blockers EOT 20:21:54 <eche|on> nothing special, server support, `http://wiki.i2p-projekt.i2p` runs and is being filled, all fine 20:23:26 <sadie_> working on post install docs improvements with idk, secured more Usability Testing research , community outreach / PR strategy / testing idk's webextensions/ discovery process - resilient infra, rebranding research - more of the same next month 20:23:57 <zlatinb> anyone else? T-1 minute till scrum end 20:24:01 <eyedeekay> 1) Biggest part of my work was a substantial revision to the default dark theme to improve readability and make it look more modern and consistent. I also added features and fixed bugs in my webextension for Firefox, it now has the ability to talk to i2pcontrol and snark-rpc. I also set up my personal eepSite and a common git resource(a gitlab instance at git.idk.i2p) for the project. 2) I will be working inside 20:24:01 <eyedeekay> the git migration. 3) no blockers. 20:24:41 <zlatinb> thanks, scrum.end 20:24:48 <zzz> ok thanks zlatinb 20:25:07 <zzz> anybody have any questions, comments, or additional topics for the meeting? 20:26:13 * zzz grabs the baffer 20:27:01 * zzz *bafs* the meeting closed

I2P Dev Meeting - December 03, 2019

Tue, 03 Dec 2019 00:00:00 +0000

Quick recap

Present: eyedeekay, meeh, sadie, zlatinb, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) I2P Browser project status (sadie, meeh, idk) 20:00:00 <zzz> 2) Outproxy use cases / status (sadie) 20:00:00 <zzz> 3) 0.9.44 release status (zzz) 20:00:00 <zzz> 4) Status scrum (zlatinb) 20:00:10 <sadie__> hi 20:00:20 <zzz> 0) Hi 20:00:22 <zzz> hi 20:00:47 <zzz> 1) I2P Browser project status (sadie, meeh, idk) 20:00:49 <zlatinb> hi 20:01:00 <meeh> hi 20:01:23 <zzz> sadie, what's the latest on the I2P Browser project? and feel free to delegate any parts of your answer to idk and meeh 20:01:32 <eyedeekay> Hi 20:03:02 <meeh> The biggest news is probably that our next release is now is based upon ESR 68 and not 60, and our extensions is in the progress to be ported into the source since mozilla removes some of our current used api in later versions 20:03:27 <zzz> and when is that release scheduled? 20:03:47 <meeh> It's also the first release which should be signed by our new EV code signing certificate so no more scary warnings 20:03:54 <meeh> in two three days 20:04:06 <meeh> let's say 6th 20:04:15 <zzz> ok so this will be beta 8 I think? 20:04:26 <meeh> yea that's correct 20:04:27 <eyedeekay> Yes beta 8 20:04:43 <zzz> super. anything else to add sadie__ eyedeekay ? 20:05:08 <eyedeekay> Besides that we now also enable the suite of I2P applications, snark, susimail, etc. 20:05:19 <sadie__> yes - we will have an updated MVP and roadmap available as well 20:05:54 <zzz> when will those be posted? 20:05:56 <meeh> and we will in time, release replacements with modern standards for at least susimail and addressbook to start with 20:06:14 <meeh> that was not for this release doh, but in later releases 20:06:47 <sadie__> those should be on the site middle of next week, along with the updated project name and branding direction 20:07:15 <meeh> one news not directly linked to the browser is that we now also have a Rack "runner" which directly talks to I2PSocket and don't require the user to port it via some local tcp port 20:07:25 <zzz> nice. care to leak the new name or you going to hold off until it's up on the site? 20:07:34 <meeh> so it makes it possible to run for example Ruby on Rails directly towards I2PSocket 20:07:57 <sadie__> We are holding off until the site is updated =) 20:08:12 <zzz> nice meeh, always better to avoid going out-and-back via a standard socket 20:08:51 <zzz> sounds like great progress 20:09:01 <zzz> anything else on 1) ? anybody have any questions? 20:10:31 <zzz> 2) Outproxy use cases / status (sadie) 20:10:41 <zzz> sadie__, whats the latest on this research effort? 20:10:44 <sadie__> The outproxy turnkey solution has been put on hold until I can acquire the resources needed for proper information gathering to complete the MVP. This research will not resume until next year. General use outproxy discussion will resume in the coming weeks. At this point the priority for the our proxy should be investigating and improving performance issues. 20:11:45 <zzz> ok, re: the project's outproxy, what's the status on investigation and improvement? 20:12:10 <zzz> meeh you have any info on that? 20:12:17 <sadie__> meeh can comment of that effort better than I 20:12:28 <meeh> Also since the topic is outproxy, the jruby gem I made also have a simple single threaded outproxy that can run as a i2p plugin for that matter 20:12:33 <meeh> found here https://github.com/mikalv/ji2p-jruby/blob/master/bin/simple_outproxy 20:13:08 <zzz> but what about the current outproxy? 20:13:09 <meeh> also I've started splitting the gem up, so you don't need to bundle cluster support and such for a simple i2p plugin not having anything to do with such 20:13:13 <meeh> because it's gotten quite big 20:13:41 <meeh> yea, I've had some cable and switch upgrades which was a bottleneck for the public outproxy 20:13:52 <zzz> I've started keeping track of every outproxy fetch, success or failure, on a postit. Today's success rate is only 75% 20:14:26 <zzz> sadie says it's a priority, so what do you plan to do next? 20:14:39 <meeh> the next browser release beta 8, sorry I forgot to mention before, will have many more destinations pointing to the same service as we believe the destinations in themself are the next bottleneck 20:14:56 <meeh> so not only false.i2p and my tor bridge, but more like in the count of 20 20:15:30 <meeh> I will also switch the proxy software with a custom made elixir/erlang software for that, which I wrote back some months ago 20:15:45 <meeh> also found here https://github.com/mikalv/i2p-outproxy-elixir 20:16:00 <zzz> have you considered switching from i2pd to java? I think there's some major issues with running it on i2pd 20:16:14 <meeh> I got some uncommited changes I'll push before I do the switch, and anyone can use this to run their own. I'll make better docs for that as well 20:16:25 <meeh> I use both currently 20:16:29 <meeh> both java and i2pd 20:16:39 <zzz> ok 20:16:40 <meeh> it should be four routers all having the two dest 20:16:51 <meeh> pointing to the same http proxy endpoint 20:17:05 <zzz> do you have a conclusion yet on which provides better service? 20:17:17 <meeh> the i2pd's are setup with like 100 tunnels compared to java's 16 tunnel limit 20:17:49 <meeh> no sorry not yet, but that's something I've put in my todo list of things I should do in near future 20:18:21 <zzz> ok, I encourage the team to use a measurement-based approach to making improvements. don't just shotgun it and change everything 20:18:51 <meeh> yea, I've done that before and learned from it - so no worry, measurement-based it is 20:18:55 <zzz> anything else on 2) sadie__ ? 20:19:09 <sadie__> no 20:19:22 <zzz> anybody have any questions on 2) ? 20:20:19 <zzz> 3) 0.9.44 release status 20:20:29 <zzz> ok we got the 0.9.44 release out on Sunday 20:21:00 <zzz> it fixes a nasty issue in the way new encryption types are handled. Everybody should upgrade as soon as they can 20:21:12 <meeh> for android it's published on google play, fdroid and on our download page where the latter includes gpg signature and website updated 20:21:33 <zzz> great. how about mavencentral? 20:22:03 <meeh> yea, it's a required dependency of the above, so when I've done the above I must already have done mavencentral 20:22:07 <zzz> it's available for in-net updates now. About 10% of the network has upgraded already 20:22:38 <zzz> I also did the PPA and deb repo on sunday 20:22:58 <zzz> so I think that's most of it 20:23:05 <zzz> no complaints so far 20:23:24 <zzz> unfortunately, the bandwidth tester is pretty much completely broken 20:23:51 <zzz> something changed in the test pool lately, and the way we were doing the handshake stopped working 20:24:10 <zzz> I spent the last day and a half working on it, and I got it going again 20:24:40 <zzz> if anybody sees stuff like this is broken, please file a ticket. It's a shame we didn't realize it was busted before the release 20:25:29 <meeh> we got a new (standalone) donation page just around the corner also, which would enable more ways to donate, also recurring paypal etc 20:25:39 <zzz> so that's about all I have on .44. We're just getting started on .45 and putting the plan together, but I expect the 45 release will be in February 20:25:44 <meeh> and it looks **nice** 20:25:48 <meeh> with capital letters 20:25:56 <zzz> ok meeh, great 20:26:02 <zzz> anything else on 3) ? 20:27:02 <zzz> 4) status scrum 20:27:06 <zzz> go ahead zlatinb 20:27:31 <zlatinb> hi, very briefly: 1) what youve been doing last month 2) what you plan to do next month 3) any blockers or do you need help 4) EOT 20:28:31 <zlatinb> me: 1) fixed the scriptable filter writing to disk every 10 seconds, investigated servlet 3.0 support (broken for inner classes) 2) packaging MW as a router plugin 3) no blockers 20:28:35 <zlatinb> EOT 20:28:49 <zzz> 1) .44 release, bug fixes, prop. 144 (ratchet) coding and testing; fixed a bad tunnel bug causing slow startup, got a new version of zzzot out with drzed's help 20:29:28 <zzz> 1 (cont) lots of work testing reseeds and working with reseeders to get things un-broken; tested and removed open trackers also 20:30:09 <meeh> done: jruby gem for interacting and/or controlling the router embedded or standalone, initial kubernetes support for either HA destinations or cluster testing of i2p, many many firefox patches either written by scratch or ported from tor browser, outproxy improvements, and a new mail application with the attent to replace susimail one day 20:30:19 <meeh> initial work on the last one* 20:30:23 <zzz> 2) bug fixes, prop. 144 testing, more work on improving performance, 36C3 20:30:46 <sadie__> Last month has been working on css light theme changes that are in the latest release, responding to Usability Lab for UX Study funding for router console, and driving product decisions for the future of the browser. Next month, will be post install guide, and more css work, browser management and developemnt 20:30:56 <zzz> 3) no blockers; 4) EOT 20:31:10 <sadie__> no blockers, EOT 20:31:15 <eyedeekay> 1) I have been working on opening up the I2P Browser experience to more of I2P's overall capabilities and adjusting the organization/look-and-feel of the router console and home pages. 2) Next month I'll be working on more browser feature improvements, more SAM tutorials, and more router console UI improvements. 3) no blockers EOT. 20:31:48 <zlatinb> thanks, thats everyone I think </scrum> 20:32:08 <zzz> super, anything else on 4) ? anybody have any questions? 20:32:24 <zzz> or any other topics for the meeting? 20:32:28 <meeh> next month: release beta 8 of the browser, figure out how we can use the osslsigncode software to sign windows binaries on unix systems, switch outproxy software, continue the work of the new mail app, and finish the changes for the jruby gem 20:33:16 <zzz> EOT meeh? 20:33:32 <meeh> yea, EOT. 20:34:16 <zzz> ok. A reminder there will be no meeting next month as we'll be recovering from 36C3. If anybody would like to join our meetings at 36C3, come find our table 20:34:32 <zzz> I'm sure I will tweet out the approximate location 20:34:48 <sadie__> and we will have a new banner for the table! 20:34:48 <meeh> we can probably publish some public notes from the meeting as well? 20:34:58 <meeh> that's from ccc 20:34:59 <zzz> any other topics for the meeting, while I look for the baffer? 20:35:28 <zzz> you volunteering meeh? 20:35:41 <meeh> I can try do that yea 20:35:59 <sadie__> I will do a report for ccc 20:36:35 <zzz> ok, I found the *baffer* so I guess that's about it for today 20:36:46 <zzz> see you all in person in 4 weeks 20:37:10 <zzz> whups, 3 1/2 weeks 20:37:24 * zzz *bafs* the meeting closed

0.9.44 Release

Sun, 01 Dec 2019 00:00:00 +0000

Update details

0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types. All users should update as soon as possible.

The release includes initial support for new end-to-end encryption (proposal 144). Work continues on this project, and it is not yet ready for use. There are changes to the console home page, and new embedded HTML5 media players in i2psnark. Additional fixes for firewalled IPv6 networks are included. Tunnel build fixes should result in faster startup for some users.

I2P Dev Meeting - November 05, 2019

Tue, 05 Nov 2019 00:00:00 +0000

Quick recap

Present: echelon, eyedeekay, lbt, sadie, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 0.9.43 release status (zzz) 20:00:00 <zzz> 2) I2P Browser project status (sadie, meeh) 20:00:00 <zzz> 3) Outproxy use cases / status (sadie) 20:00:00 <zzz> 4) 0.9.44 development status (zzz) 20:00:00 <zzz> 5) Proposals status (zzz) 20:00:00 <zzz> 6) Status scrum (zlatinb) 20:00:04 <zzz> 0) Hi 20:00:06 <zzz> hi 20:00:10 <sadie_> hi 20:00:25 <zzz> 1) 0.9.43 release status (zzz) 20:00:38 <zzz> 43 has been out a couple weeks, no serious issues so far 20:01:02 <zzz> the remaining items are the official f-droid (nextloop) and official debian (mhatta) 20:01:08 <eyedeekay> hi 20:01:37 <zzz> any other outstanding issues with the 43 release? 20:03:01 <zzz> 2) I2P Browser project status (sadie, meeh) 20:03:16 <zzz> meeh, sadie, what's the latest info on the browser? 20:04:49 <sadie_> Beta 7 has been released 20:05:10 <eyedeekay> I2P Browser was Beta 7 was released yesterday, along with an updated road-map. This is the second-to-last release which will be based on firefox 60. We fixed some bugs and implemented continuous integration, as well as developed a revised and updated plan for the future of the browser as a product. 20:05:11 <sadie_> the notes can be found on the project website. 20:05:35 <zzz> the release date is wrong on the site FYI 20:05:51 <eyedeekay> Oh shoot, sorry I missed that. Will change it immediately. 20:06:03 <sadie_> We have also been working on the roadmap, which can also be found on the project website 20:06:29 <zzz> what can you tell us about upcoming beta 8? what's in it, when will it be out? 20:07:40 <sadie_> beta 8 will be out at the end of November. 20:08:19 <zzz> anybody have any questions about the browser? meeh you have anything to add? 20:08:27 <eyedeekay> Beta 8 will be released at the end of November, it will be the final version based on Firefox 60. We're preparing for some architectural changes which will make applications more visible, you'll start to see the beginnings of that in Beta 8, as well as more feedback in the browser about the readiness of the bundled router. 20:08:53 <sadie_> we are working on a better landing page, an HTTP proxy readiness indicator , and dynamic themes 20:09:20 <zzz> sounds great, I hope everybody gives beta 7 a try 20:09:45 <zzz> anything else on 2) ? 20:11:00 <zzz> 3) Outproxy use cases / status (sadie) 20:11:17 <zzz> sadie_, what's the latest on this topic? 20:11:32 <sadie_> We have brought the requirements document along as far as I feel we can without now doing more user research. 20:11:38 <sadie_> Mid month I will reconnect with the person who inspired the turnkey outproxy solution. We can evaluate the requirements document that has been created, and begin to address the user research questions more thoroughly. The requirements for this solution are part of the deliverables for the next release.We have brought the requirements document along as far as I feel we can without now doing more user 20:11:38 <sadie_> research. 20:12:41 <zzz> ok, to be clear we're only working on requirements during the 44 timeframe. Any implementation would be in 45 or later, right? 20:12:53 <sadie_> correct 20:13:32 <zzz> ok, anything else you want to add? Anybody have any questions about the outproxy research? 20:14:01 <zzz> anything else on 3) ? 20:15:01 <zzz> 4) 0.9.44 development status (zzz) 20:15:23 <zzz> we're two weeks in to the .44 cycle, with lots of new code checked in 20:15:52 <zzz> almost all is the implementation of proposal 144, new encryption for destinations 20:16:07 <zzz> I expect to start interoperability testing with chisana_ soon 20:16:35 <zzz> and should be ready for brave testers in a couple weeks 20:16:57 <zzz> but it will be quite a while before we're using it by default, perhaps 6-12 months 20:17:23 <zzz> lots of testing and other changes needed to make it solid 20:17:59 <zzz> the other major thing I have queued up for .44 is some SSU performance improvements, spurred on by our prolific trac ticker 'jogger' 20:18:17 <zzz> sadie_, eyedeekay, meeh, anything you'd like to add on what you're working on for .44 ? 20:19:34 <zzz> anything else on 4) ? 20:19:35 <sadie_> router console /home changes, website long term strategy 20:20:45 <zzz> 5) Proposals status (zzz) 20:21:05 <zzz> not much else to say here, 99% of the focus is on 144. 20:21:30 <zzz> next up is probably 152, 153, or maybe even a new SSU 2 proposal 20:21:47 <zzz> I don't expect much progress on any of that until the new year 20:21:58 <zzz> any questions on proposals? 20:22:06 <zzz> anything else on 5) ? 20:23:01 <zzz> 6) Status scrum (zlatinb) 20:23:12 <zzz> I think zlatinb said he couldn't make it today 20:23:32 <eche|on> new server with new hardware and new IPs, migrating services from one server to another with time. no blockers 20:23:41 <zzz> so everybody you know the drill, please say 1) what you did last month 2) what you're doing next month; 3) any blockers 20:23:52 <zzz> and end with EOT 20:24:49 <zzz> me: 1) got the .44 release out, lots of work on new encryptoin; 2) more work on new encryption, SSU performance improvements, bug fixes; 3) no blockers; EOT 20:25:11 <zzz> sadie_, meeh, eyedeekay, please go in parallel 20:25:48 <sadie_> Last month and the upcoming month I will continue to work on I2P browser, keep refining the router console light theme, and develop a long term strategy for website with IDK. Outproxy product management and requirements gathering will continue. Proposals for research and development: proposals to improve UX and usability studies have been submitted or are otherwise being written. Presentation and wo 20:25:48 <sadie_> rkshops for conferences have started for 2020. 20:27:01 <zzz> last call eyedeekay meeh zlatinb 20:27:11 <eyedeekay> 1) I have been working on things that go into the browser or which are intended to help the browser. 2) Going to work on improving the organization of some of the router console home pages as well as implement some of the browser design improvements. 3 No blockers EOT 20:27:53 <zzz> ok, presuming EOTs from eche|on and sadie_ ... anything else on 6) ? 20:28:02 <sadie_> yes 20:28:34 <zzz> any other topics or questions for the meeting? 20:28:59 <eche|on> what abouit bote? 20:29:04 <eche|on> any sign from str4d? 20:29:28 <zzz> I've seen an occasional RT on twitter, so he's alive 20:29:59 <zzz> thats all I know 20:30:26 <zzz> other than what's in the tickets 20:30:27 <eche|on> ok 20:30:38 <zzz> anything else about bote? 20:31:01 <zzz> anything else for the meeting? 20:31:22 <lbt> A "thank you" to all of you :) 20:31:48 <zzz> you're welcome lbt, thanks for joining the meeting 20:31:54 <eyedeekay> You're welcome friend :) 20:33:00 * zzz *bafs* the meeting closed

Highlighting Research

Fri, 25 Oct 2019 00:00:00 +0000

Highlighting Research - An Empirical Study of the I2P Anonymity Network and its Censorship Resistance

The following blog post is authored by Information Controls Fellow Hoàng Nguyên Phong. As an ICFP fellow, Phong’s research focused on analyzing different aspects of the I2P network, a privacy-enhancing Internet tool that can be used to access online content over an anonymity-enhancing network helpful in circumventing state-imposed censorship. Working with his host organization, the University of Massachusetts Amherst, Phong studied the I2P network’s censorship resilience, including identifying what blocking methods a state censor might use to inhibit access to I2P and investigating potential solutions to make I2P more resistant to such blockage.

0.9.43 Release

Tue, 22 Oct 2019 00:00:00 +0000

Update details

In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements. Our implementation of the new leaseset specification (LS2) is now complete. We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release. Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

Our Networks Trip Report- idk

Sat, 05 Oct 2019 00:00:00 +0000

Our Networks Trip Report

The weekend of September 20th I traveled to Toronto to meet with Sadie to take part in the Our Networks conference. The Our Networks conference encompasses a wide variety of topic including many peer-to-peer technologies with an eye toward their potential to make the world a better place.

The conference was fascinating, full of very smart people working on everything from physical mesh networks to the distributed web to, of course, anonymity. We got to talk to some great people from Tor, Protocol Labs, Parity Labs, the Dat Project, as well as a variety of artists and social scientists. Lots of fun too, and a great environment. Dat in particular presents some pretty cool opportunities for future co-operation I think.

I2P Dev Meeting - October 01, 2019

Tue, 01 Oct 2019 00:00:00 +0000

Quick recap

Present: chisana, echelon, eyedeekay, meeh, nextloop, sadie, zlatinb, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 0.9.42 release status (zzz) 20:00:00 <zzz> 2) I2P Browser "labs" project status (sadie, meeh) 20:00:00 <zzz> 3) Outproxy use cases / status (sadie) 20:00:00 <zzz> 4) 0.9.43 development status (zzz) 20:00:00 <zzz> 5) Proposals status (zzz) 20:00:00 <zzz> 6) Status scrum (zlatinb) 20:00:05 <meeh> hi 20:00:05 <zzz> 0) Hi 20:00:08 <zzz> hi 20:00:16 <zlatinb> hi 20:00:18 <nextloop> Hi 20:00:23 <sadie__> hi 20:00:49 <zzz> 1) 0.9.42 release status (zzz) 20:01:12 <zzz> 42 release was 5 weeks ago, I believe the only remaining items as of a month ago were the client lib and a new bote android release, and the deb/ubuntu official 20:01:19 <zzz> those are all done 20:01:41 <zzz> not much else to say about .42, which seems to be running well 20:01:46 <zzz> anything else on 1) ? 20:02:29 <zzz> 2) I2P Browser "labs" project status (sadie, meeh) 20:02:37 <eyedeekay> Hi everybody 20:02:45 <meeh> we're in route on all the tasks, I've also started the initial patching of ESR68 which would be our new beta by 31 dec. 20:02:46 <zzz> sadie, meeh, what can you tell us about this new project and product, what's the status? 20:03:01 <chisana_> hi 20:03:02 <sadie__> Beta 7 will be released October 23 or immediately after 0.9.43 is tagged. As of today, we are on track with the roadmap items for the upcoming release. A tentative roadmap for future releases has been created, taking us up until June 2020 20:03:04 <zzz> what is the next task, or next release meeh? 20:03:07 * chisana_ lurks 20:03:13 <meeh> oct 23 20:03:33 <meeh> or as soon as 0.9.43 is out on that date or after 20:03:36 <meeh> depends on us 20:03:50 <zzz> can you two please tell us where the roadmap is, and what's going to be in beta 7? 20:04:39 <sadie__> The items on the Roadmap are on track as of taday 20:05:00 <zzz> is the roadmap posted anywhere where people can look at it? 20:06:27 <meeh> the next release would for the most contain bugfixes, stability patches, better initial dialog window "backend" 20:06:35 <eyedeekay> These are the items that are also on the project roadmap for 9.43. 20:07:17 <meeh> if mozilla has any patches we should include by that time, those will be added as well 20:07:18 <zzz> ok, so the roadmap for beta 7 is on the i2p roadmap on our website, people can look at it there 20:07:29 <sadie__> yes 20:07:36 <zzz> is the roadmap through June 2020 posted anywhere for people to look at it? 20:07:56 <sadie__> not yet 20:07:57 <eyedeekay> Not yet, can be soon. 20:08:17 <zzz> ok. anybody have any questions for the browser team? 20:09:03 <zzz> anything else on 2)? anything else the team wants to say about the browser? 20:09:26 <sadie__> please test, join the mailing list! 20:09:44 <zzz> want to plug how to subscribe to the mailing list sadie? 20:10:02 <meeh> available at `http://lists.i2p` or https://lists.i2p.email 20:10:17 <zzz> great 20:10:20 <sadie__> sure - everything you need can be found on the site https://geti2p.net/en/browser/develop 20:10:25 <zzz> anything else on 2)? 20:11:01 <zzz> 3) Outproxy use cases / status (sadie) 20:11:13 <zzz> sadie, tell us about the outproxy project status please 20:11:16 <sadie__> Open Outproxy MVP has been made, we are almost there with the Friends and Family MVP, but still need to gather more information around admin, logging and reporting requirements. Meetings will resume week of October 21. 20:12:06 <sadie__> I have some new ideas / thoughts about how to handle admin, and more research to do ahead of the next meeting 20:12:15 <zzz> by "made" you don't mean that we've finished development I hope... and could you define MVP for everybody please? 20:12:40 <sadie__> Minimal Viable Product 20:13:03 <sadie__> no - we are still working on requirements in a few areas 20:13:16 <zzz> so by 'made' you mean a list of requirements, right? 20:13:32 <sadie__> correct! 20:14:10 <zzz> where can people see that list, and what's the best way for people to get feedback to you about it? 20:15:05 <sadie__> I will update trac, and invite people to join in the conversation there 20:15:40 <zzz> please tell everybody where on trac they will be able to see it? 20:16:07 <sadie__> one moment 20:17:04 <zzz> while you're looking, I'll comment that the target for this is next year... not for .43 or .44 20:17:14 <zzz> for the implementation, that is 20:17:46 <zzz> any questions or comments about the outproxy project, while she's looking? 20:19:00 <sadie__> #2472 was where we began the discussion 20:19:00 <zzz> anything else on 3) ? 20:19:59 <zzz> ok, so you'll put the requirements list up on ticket 2472 and that's where you would like feedback, right? 20:20:17 <sadie__> correct 20:20:27 <zzz> super 20:20:56 <zzz> 4) 0.9.43 development status (zzz) 20:21:19 <zzz> the website has the roadmap for .43, including the browser items for beta 7, as previously mentioned 20:21:46 <zzz> we're 5 weeks in on the development for .43, with a release expected about 3 weeks from today 20:22:12 <zzz> things are going well, with some IPv6 fixes, and more work on making encrypted ls2 easier to use 20:22:52 <zzz> anybody else want to tell us what you're working on for .43, besides the browser beta 7? 20:23:36 <zzz> tag freeze will be a week from tomorrow, and I'll update transifex at that time and let everybody know to start translating 20:23:42 <zlatinb> hopefully Ill get around to testing servlet 3.0 annotation scanning 20:24:12 <zzz> ok, yeah, I'd like to finish that if you need it, or can it if you don't :) 20:24:18 <meeh> improving the jlinked build of ours, which is related to browser stuff doh, but still on the java codebase 20:24:42 <sadie__> IDK and I are working on a new set up wizard and new website menu navigation has been done. I will make more cosmetic changes to console css 20:24:47 <meeh> I'll guess we look into more on that topic as well as the addressbook is broken when using jlink 20:25:13 <zlatinb> yeah and plugins too - but those are probably going to stay broken for a while 20:25:19 <zzz> oh, and we'll be working on android fixes for 43 next week 20:26:38 <zzz> I don't think you want to bother enabling router plugins for the browser, but maybe others are pushing you for it? worth investigating further 20:27:04 <zzz> anything else on 4) ? 20:28:21 <zzz> 5) Proposals status (zzz) 20:28:45 <zzz> the sole focus of the #ls2 proposals team in the last month has been prop. 144 - new encryption 20:29:02 <zzz> we're getting close to a complete and consistent spec, and we've started writing some test code 20:30:01 <zzz> I expect some of that code to get into the java .44 release - not .43 - but it's going to be early next year before it's really finished up in the live net 20:30:20 <zzz> and then perhaps another few releases to shake out the bugs 20:30:45 <zzz> but it's exciting as we are close to replacing one of the original and very slow crypto algorithms, ElGamal 20:31:28 <zzz> I expect we'll then turn to another part of the ElGamal replacement, with proposal 152, for how we do tunnel builds 20:31:46 <zzz> but we could decide to work on "SSU2" as well... we haven't talked about it 20:31:56 <zzz> those would be for mid-to-late next year I'd guess 20:32:33 <zzz> the team is working well together and we've been working on 144 for almost a year, so we'll all be very happy to be done with it in the coming months 20:32:43 <zzz> any questions on these or any other proposals? 20:33:19 <zzz> anything else on 5) ? 20:34:00 <zzz> 6) status scrum (zlatinb) 20:34:04 <zzz> take it away zab 20:34:29 <zlatinb> Hi, briefly describe 1) what youve been doing last month 2) what you plan to do next month 3) any blockers or help needed? Say EOT when finished 20:34:59 <meeh> Its been quite much initial work on the browser project, both due to the integration of the router and the learning experience of the whole Firefox codebase, build system and architecture to get to a level that we can say we got things under control. Were about to have nightly builds and CI ready for both the esr60 and esr68 branches as well as pull requests that we might receive. 20:35:01 <meeh> The artifact builds are also a goal to archive, which would enable people with weaker hardware to download parts of the Firefox build to reducing the heaviest compile operations, and the development less of a hassle. Also been looking into unit and regression testing for the browser to avoid stupid bugs and to make the product more stable and reliable. 20:35:01 <meeh> Were also closing in to having our customized build scripts thats not based upon tors perl build script base, both to support remote builds and the fact that were not many knowing perl. Beyond this Ive also done some reading and research in the legal system here for running our organization. Initial work on the logging policy of project servers. 20:35:05 <meeh> EOT 20:35:18 <zlatinb> me: 1) testnet-ing jogger patches, some jlink work 2) more testnet, servlet 3.0 3) no blockers EOT 20:35:20 <sadie__> Attended Our Networks last weekend in Toronto, drew up new set up wizard to be implemented in the release by IDK, getting more cosmetic css changes decided on for the next release, moving outproxy and browser consensus along, community outreach and more UX funding has been applied for. Next month, will be focusing on funding options , new PR strategies, 36c3 outreach, getting an intro to I2P slide 20:35:20 <sadie__> deck finished for future talks that we can all use, susi mail improvements, and continuing to work on browser and outproxy. EOT 20:35:32 <zzz> 1) bug fixes, IPv6, ls2 encryption, proposal 144 20:36:06 <eche|on> server running, the same, no blockers 20:36:25 <zzz> 2) bug fixes, IPv6, ls2 encryption, proposal 144 spec and test code, prep and release 0.9.43, more outproxy meetings and definition 20:36:48 <zzz> 3) no blockers, EOT 20:37:11 <zlatinb> scrum.setTimeout(60*1000); 20:37:25 <zzz> eyedeekay? 20:37:35 <eyedeekay> just a moment 20:37:55 <eyedeekay> I've been working on upgrading the bandwidth wizard to make it work better with the I2P browser and in general appear more modern and less confusing. I've also been working on organizing, de-duplicating, and improving SAM libraries and making small changes to the browser. Next month I'll be helping with the browser mostly, but I have a few things I may propose in i2ptunnel as well. No blockers. 20:38:41 <zzz> sadie__, or eyedeekay, have a link to an Our Networks trip report for people to read? 20:38:48 <meeh> no blockers, most of mentioned tasks are continuing (I'll keep on working on them in the future) 20:39:16 <sadie__> not - we need to get that done. It will be on the site blog 20:39:29 <eyedeekay> I'll put mine up on the blog this week. 20:39:47 <zlatinb> thanks, I think thats everyone, scrum end 20:40:03 <zzz> that's it for 6) 20:40:21 <zzz> anybody else have any questions or comments or something to add? There's definitely a lot going on! 20:41:11 <zzz> anything else for the meeting? 20:41:21 * zzz looks for the baffer 20:42:05 <zzz> there it is... 20:42:15 * zzz *bafs* the meeting closed

I2P Dev Meeting - September 03, 2019

Tue, 03 Sep 2019 00:00:00 +0000

Quick recap

Present: eyedeekay, sadie, zlatinb, zzz

Meeting Log

Note: sadie's lines did not come through in the meeting, pasted in below.

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 0.9.42 release status (zzz) 20:00:00 <zzz> 2) I2P Browser “labs” project status (sadie, meeh) 20:00:00 <zzz> 3) Outproxy use cases / status (sadie) 20:00:00 <zzz> 4) 0.9.43 development status (zzz) 20:00:00 <zzz> 5) Proposals status (zzz) 20:00:00 <zzz> 6) Status scrum (zlatinb) 20:00:04 <zzz> 0) Hi 20:00:06 <zzz> hi 20:00:17 <zlatinb> hi 20:00:30 <zzz> 1) 0.9.42 release status (zzz) 20:00:48 <zzz> the release went pretty smoothly last week 20:00:56 <zzz> there’s only a few things outstanding 20:01:27 <zzz> getting the github bridge back working (nextloop), the debian sid package (mhatta), and the android client lib that we forgot for 41 (meeh) 20:01:37 <zzz> nextloop, meeh, you have ETAs for those items? 20:03:06 <zzz> anything else on 1) ? 20:04:02 <zzz> 2) I2P Browser “labs” project status (sadie, meeh) 20:04:25 <zzz> sadie, meeh, what’s the status, and what’s the next milestone? <sadie> Beta 5 was supposed to be out on Friday, but there were some issues. It looks like some are ready https://i2bbparts.meeh.no/i2p-browser/ but I really needed to hear from meeh about the next deadline for this <sadie> The Lab Page will be live by the end of this week. The next Browser milestone will be discussing the beta 6 release console requirements 20:05:51 <zzz> anything else on 2) ? 20:06:43 <zzz> 3) Outproxy use cases / status (sadie) 20:06:57 <zzz> sadie, what’s the status, and what’s the next milestone? <sadie> Anyone can follow our meeting notes on ticket 2472. We have decided on use case statuses and have a list of requirements. Next milestone will be user requirements for a Friends and Family use case as well as development requirements for Friends and Familiy and General use case to see where they may ovelap 20:08:05 <zzz> anything else on 3) ? 20:08:19 <eyedeekay> Sorry I’m late 20:09:01 <zzz> 4) 0.9.43 development status (zzz) 20:09:21 <zzz> we’re just getting started on the 43 cycle that we have planned to release in about 7 weeks 20:09:40 <zzz> we’ve updated the roadmap on the website but will be adding some more items 20:10:06 <zzz> I’ve been fixing some IPv6 bugs, and speeding up tunnel AES processing 20:10:30 <zzz> soon I will be turning my attention to the new blinding info I2CP message 20:10:59 <zzz> eyedeekay, zlatinb, you have anything to add about .43? 20:11:46 <eyedeekay> No I don’t think so 20:12:02 <zlatinb> probably more testnet stuff 20:12:32 <zzz> yeah, we do have a few more jogger tickets to look at, w.r.t. SSU 20:12:48 <zzz> anything else on 4) ? 20:14:00 <zzz> 5) Proposals status (zzz) 20:14:20 <zzz> our primary focus is on the very complex new encryption proposal 144 20:14:48 <zzz> we’ve made some good progress in recent weeks and have made some major updates to the proposal itself 20:15:35 <zzz> there’s a few cleanups and holes to fill in, but I’m hopeful it’s in good enough shape that we could start to code some unit test implementations soon, maybe by the end of the month 20:16:17 <zzz> also, the blinding info message for proposal 123 (encrypted LS2) will get another look after I start to code it in the next week 20:16:52 <zzz> also, we’re expecting an update on proposal 152 (tunnel build messages) from chisana soon 20:17:27 <zzz> we finished up proposal 147 (cross-network prevention) last month and both i2p and i2pd have that coded and in the .42 release 20:18:23 <zzz> so things are moving forward, even if 144 seems slow and daunting, even it is making good progress 20:18:27 <zzz> anything else on 5) ? 20:20:00 <zzz> 6) Status scrum (zlatinb) 20:20:05 <zzz> take it away zlatinb 20:20:42 <zlatinb> Hi, please say in a few words : 1) what youve been doing since last scrum 2) what you plan to do next month 3) do you have any blockers or need help. Say EOT when done 20:21:23 <zlatinb> me: 1) Various experiments on the testnet to speed up bulk transfers 2) more testnet work on a hopefully bigger server/network 3) no blockers EOT 20:22:15 <zzz> 1) bug fixes, the configuration split change, .42 release, proposals, DEFCON workshops (see my trip report on i2pforum and our website) 20:23:56 <zzz> 2) bug fixes, proposal 144, blinding info message, speedups, helping out with the outproxy research, fix the SSL wizard broken by conf. split 20:24:20 <zzz> more IPv6 fixes 20:24:38 <zzz> 3) no blockers EOT 20:24:50 <eyedeekay> 1) Since last scrum I’ve been working on bugfixes, the web site, working on the outproxy proposal, and things to do with i2ptunnels. 2) Continue re-organizing and improving the presentation of the web site. Work on advancing the outproxy proposal 3) no blockers EOT <sadie> 1) Attended FOCI, researched funding options, met with potential funders, had a meeting with Tails ( including Mhatta ), worked on I2P Browser branding, website updates with IDK, made small changes to console for the last release <sadie> 2) my next month I am working on grants, console and website improvements, set up wizard, attending Our Networks in Toronto, moving I2P Browser and OutProxy research along <sadie> 3) no blockers EOT 20:25:29 <zlatinb> scrum.setTimeout( 60 * 1000 ); 20:27:04 <zzz> ok, timing out 20:27:10 <zlatinb> ScrumTimeoutException 20:27:41 <zzz> last call for sadie meeh nextloop to circle back to 1)-3) 20:27:52 <zzz> any other topics for the meeting? 20:28:47 * zzz grabs the baffer 20:30:00 * zzz bafs the meeting closed

Def Con Trip Report- idk

Fri, 30 Aug 2019 00:00:00 +0000

Def Con Trip Report

I went to Def Con 27 last weekend to give a workshop on I2P application development, and to meet zzz, mhatta, and Alex in person.

My workshop went well, we even had a few application developers attend! In particular I had a pretty lengthy conversation with a person named Mary about how I2P could be used to eliminate centralization and enhance privacy in a “Magic Wormhole” type of application. While I wasn’t totally familiar with Magic Wormhole at the time, I think most of my advice was usable. I think Mary had some very interesting and workable ideas about sharing information in more human-centric ways that could be interesting in I2P applications, and am looking forward to experimenting with some of those.

Def Con Trip Report- zzz

Fri, 30 Aug 2019 00:00:00 +0000

Def Con Trip Report

idk and I attended DEFCON 27 and presented two workshops on I2P for application developers, with support from mhatta and Alex. I gave the workshop at Monero Village and idk gave the one at Crypto/Privacy Village. Here, I will summarize the Monero Village workshop, and a Tor talk by Roger Dingledine. idk will post a trip report covering his workshop.

We had about 8 attendees for the Monero Village workshop, entitled “I2P for Cryptocurrency Developers”. We planned to discuss the particular networking needs for each application and work through the various i2ptunnel and SAM options available. However, all attendees were relatively unfamiliar with I2P, so we pivoted and gave an overview of I2P. As none of the attendees had a laptop with them, we helped several of them install I2P on their Android phone and walked through some of the features of the app. For all users, the app appeared to reseed and build tunnels fairly quickly.

Internet Freedom Festival Trip Report

Fri, 30 Aug 2019 00:00:00 +0000

Internet Freedom Festival Trip Report

This was my first time attending IFF, and what a great experience for I2P this was! I met with human rights defenders, people who work on censorship metrics, and of course UX and security professionals.

My goal was to connect with people to further support I2P’s UX overhaul, keeping in mind security and UX considerations for frontline workers. As it was pointed out to me, people see I2P as a very important and powerful resource to circumvent censorship and support safe communication, however the interface suffers from some usability concerns. People were happy with our initial steps to make first time users have a better experience, such as our set up wizard and bandwidth detection tool. I also received positive reviews on our changes to the website and /home icons. It was very encouraging to hear directly from the community that small changes we have made are in the right direction.

RightsCon Trip Report

Fri, 30 Aug 2019 00:00:00 +0000

RightsCon Trip Report

The messages from activists in Syria during the Access No! session on the first day were deeply moving and really drove home why I work in digital rights. We listened to the experiences of activists who are unable to travel due to lack of status, documentation and active conflict. For these people “the internet is the only passport (they) carry.” Human rights defenders spoke of the importance of digital training to keep people protected when they are communicating with family inside of the country, as well as with family and friends who have left. They had created digital clinics to show people how to use services securely, for instance, how to use features like Signal’s disappearing messages so that those messages could not be used against them when devices are searched at security check points. Continuing to pursue education was also very important, the internet being relied on to access resources.

USENIX FOCI Trip Report

Fri, 30 Aug 2019 00:00:00 +0000

USENIX FOCI Trip Report

Over the past year I have had the good fortune to participate in the research Nguyen Phong Hoang from Stony Brook University has been doing regarding I2P censorship. The infrastructure used for this research provided numerous and geographically diverse vantage points, and also the ability to conduct in-depth measurements across all levels of the network stack. I2P services which were measured for availability included official homepage, mirror site, reseed servers and active relays.

0.9.42 Release

Tue, 27 Aug 2019 00:00:00 +0000

Update details

0.9.42 continues the work to make I2P faster and more reliable. It includes several changes to speed up our UDP transport. We have split up the configuration files to enable future work for more modular packaging. We continue work to implement new proposals for faster and more secure encryption. There are, of course, a lot of bug fixes also.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

I2P Dev Meeting - August 06, 2019

Tue, 06 Aug 2019 00:00:00 +0000

Quick recap

Present: mikalv, zlatinb, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 0.9.41 release status remaining items (mhatta, nextloop) 20:00:00 <zzz> 2) 0.9.42 development status (zzz) 20:00:00 <zzz> 3) LS2 status (zzz) 20:00:00 <zzz> 4) I2P Browser "labs" project status (meeh) 20:00:00 <zzz> 5) Status scrum (zlatinb) 20:00:04 <zzz> 0) Hi 20:00:07 <zzz> hi! 20:00:19 <zzz> 1) 0.9.41 release status remaining items (mhatta, nextloop) 20:00:46 <zzz> within the last couple weeks, I see that mhatta did get 41 into sid, which is great 20:01:04 <zzz> I talked to nextloop also, he didn't get 41 into fdroid, but somebody else did. 20:01:27 <zzz> and nextloop promised to get back to doing f-droid going forward. super! 20:01:31 <zzz> anything else on 1) ? 20:01:50 <zzz> anybody else here? please say hi 20:01:58 <zlatinb> hi 20:02:37 <zzz> ok, one other. Hopefully everybody else shows up soon 20:02:50 <zzz> 2) .42 dev status 20:03:02 <zzz> we're 5 weeks in, 3 weeks to go, 1 week to tag freeze 20:03:20 <zzz> we landed the configuration splitting code I worked on with idk 20:03:58 <zzz> lots of bug fixes; GMP 6.1.2; updated the debian files to work for buster 20:04:17 <zzz> some ls2 fixes also 20:04:39 <zzz> zlatinb, you want to mention what you're doing with your test net, and what it's yielded so far? 20:05:11 <zlatinb> yes, so basically I set up a testnet with LXC containers 20:05:32 <zlatinb> so far it has discovered one major bug around bloom filter usage and one minor ssu bug 20:05:58 <zlatinb> been doing fine-tuning of different constants lately, but will put it to work to verify joggers patches/ideas 20:06:06 <zlatinb> eot 20:06:23 <zzz> that's really great, thanks 20:07:04 <zzz> if we can get some minimal latency added in that would be even better, but it's been fun to find and fix some bottlenecks 20:07:15 <zzz> anything else on 1) ? 20:07:30 <zzz> woops, anything else on 2) ? 20:08:27 <zzz> 3) ls2 status 20:08:38 <zzz> lots of progress in the last month 20:09:05 <zzz> we've agreed to a small proposal, 147, to prevent test networks from cross-contaminating with the main network 20:09:12 <zzz> that code will be in .42 20:09:45 <zzz> chisana has two proposals out, 152 and 153, to make tunnel building and tunnel encryption (respectively) more secure by using more modern encryption 20:10:14 <zzz> we've talked about them a little, but haven't formally reviewed them yet 20:10:47 <zzz> proposal 123 (LS2) continues to get some minor tweaks as we finish implementation and testing in the live network, but everything seems to be working well 20:11:26 <zzz> the big one is proposal 144, new encryption. We're making slow but steady progress. We've been at it for maybe 9 months now? 20:11:58 <zzz> there are still some major techincal issues to resolve before we can start test implementations 20:12:20 <zzz> the biggest problem right now is finding enough of people's time to work things through 20:12:46 <zzz> any questions on 3) ls2 and other proposals ? 20:13:47 <zzz> ok, on to 4) I2P Browser labs project status 20:13:54 <zzz> mikalv, what's the latest? 20:14:16 <mikalv> we're moving towards a integration with the i2p router itself, jlinked 20:14:38 <mikalv> on the i2pbutton side of this, we're more or less done, a few things left to fix 20:15:15 <mikalv> on the build scripts, we have to write it, since the devs has used a mocked extract of i2p jlinked where the browser starts it, for testing 20:15:48 <zzz> what's the current beta version, and when will we see the next beta version? 20:15:52 <mikalv> beyond that we try to have at least two meetings a week to make it a real product and with clear goals 20:16:24 <mikalv> the current is still beta4, and I'm hoping to get beta5 out by the end of this week - if so, with the router embedded 20:17:27 <zzz> I understand you've started a mailing list for it? would you like to announce it here or is it not ready yet? 20:18:09 <zzz> sadie, zlatinb, anything you want to add about the browser 20:18:20 <zzz> ? 20:19:36 <zzz> anybody have any questions on 4) the browser? 20:20:21 <zzz> anything else on 4) ? 20:21:10 <zzz> 5) scrum - take it away zlatinb 20:22:02 <zlatinb> lets do the scrum in parallel; in a few words - 1) what have you been working since last scrum 2) what you plan to work on next month 3) do you have any blockers or do you need help. Say EOT when done 20:22:34 <zlatinb> me: 1) building a testnet, chasing bottlenecks 2) more testnet, will also take a look at joggers tickets 3) none really EOT 20:23:34 <zzz> 1) 41 release, config splitting code, bug fixes, proposals, planning for new encryption types, ls2 fixes 20:24:10 <zzz> 2) 42 release, bug fixes, proposals (especially research on new encryption issues), DEFCON 20:24:16 <zzz> 3) no blockers; EOT 20:25:18 <mikalv> I've been working mainly on the browser (including i2pbutton which now launches a router if found), I've also done huge improvements in my end for the outproxy, I've also started prototyping a solution for private outproxies which has so good speed I can actually use it for clearnet browsing on daily basis 20:25:53 <mikalv> and I've also put up mailinglists yes, which over I2P is found at `https://lists.i2p/postorius/lists/` but also available from clearnet at https://lists.i2p.email/postorius/lists/ 20:26:20 <mikalv> anyone with constructive ideas, contribution, discussions and such are of course welcome 20:26:57 <mikalv> beyond that I've done some research into how we can accept creditcard donations, and how we also can sell shirs and such at the same time 20:27:10 <mikalv> EOT 20:27:12 <mikalv> noblock 20:28:14 <zzz> guess that's it? zlatinb we'll leave it to you to flog the no-shows? 20:28:17 <zlatinb> anyone else? if not scrum ends in 1 minute :) 20:28:27 <zlatinb> ok 20:28:33 <zlatinb> ScrumTimeoutException 20:28:41 <mikalv> lol 20:28:42 <zzz> while we're in the 'grace period' - DEFCON! idk and I will be there this weekend! 20:29:04 <zzz> Monero Village Friday afternoon, and Crypto/Privacy Village Saturday afternoon 20:29:22 <zzz> workshop, q&a, and stickers both days. come say hello 20:29:57 <zzz> re: outproxies, I'm going to put that on the agenda for next month, for sadie to give us a readout on what we're trying to do 20:30:06 <zzz> anything else for the meeting? 20:30:52 <zzz> oh, and Sadie will be presenting a paper at FOCI in San Jose next week! be sure to find her if you're there 20:30:59 <mikalv> nah, but I expect we got more for the browser/outproxy cases by next meeting 20:31:39 <zzz> yeah, we don't have a good plan yet for either browser or outproxy. We have ideas and proofs of concept, but no plan 20:31:53 <zzz> so will be good to see that come together 20:32:02 * zzz warms up the baffer 20:32:44 <zzz> last baf of the summer, see you in september... 20:32:55 * zzz ****bafs**** the meeting closed

Conference Schedule August 2019

Mon, 29 Jul 2019 00:00:00 +0000

Conference Schedule August 2019

Hi Everyone,

Next month will be busy! Meet up with I2P developers at two workshops at Defcon 27, and connect with researchers who have been observing I2P censorship at FOCI ‘19.

I2P for Cryptocurrency Developers

zzz

Monero Village
August 9, 3:15pm
Monero Village will be on the 26th floor of Bally’s map

This workshop will assist developers in designing applications to communicate over I2P for anonymity and security. We will discuss common requirements for cryptocurrency applications, and review each application’s architecture and specific needs.Then, we will cover tunnel communications, router and library selection, and packaging choices, and answer all questions related to integrating I2P.

Speeding up your I2P network

Sat, 27 Jul 2019 00:00:00 +0000

This post is adapted directly from material originally created for mhatta’s medium blog . He deserves the credit for the OP. It has been updated in certain places where it refers to old versions of I2P as current and has undergone some light editing. -idk

Right after it starts up, I2P is often seen as a little bit slow. It’s true, and we all know why, by nature, garlic routing adds overhead to the familiar experience of using the internet so that you can have privacy, but this means that for many or most I2P services, your data will need to go through 12 hops by default.

0.9.41 Release

Tue, 02 Jul 2019 00:00:00 +0000

Update details

0.9.41 includes performance improvements, streaming library enhancements, and important bug fixes. We continue development work on new leasesets (LS2) and encrypted leasesets. The release contains the usual assortment of bug fixes and translation updates.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

I2P Dev Meeting - July 02, 2019

Tue, 02 Jul 2019 00:00:00 +0000

Quick recap

Present: eyedeekay, meeh, sadie, zlatinb, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 0.9.40 release status remaining items (mhatta, nextloop) 20:00:00 <zzz> 2) 0.9.41 release status (zzz) 20:00:00 <zzz> 3) LS2 status (zzz) 20:00:00 <zzz> 4) I2P Browser "labs" project status (meeh) 20:00:00 <zzz> 5) muwire.i2p console home page request (zlatinb) 20:00:00 <zzz> 6) Status scrum (zlatinb) 20:00:03 <zzz> 0) Hi 20:00:05 <zzz> hi 20:00:12 <zlatinb> hi 20:00:31 <zzz> 1) 0.9.40 release status remaining items (mhatta, nextloop) 20:00:42 <zzz> still no word from mhatta or nextloop, sadly 20:00:59 <zzz> I've made repeated attempts to find a new deb maintainer, no luck so far 20:01:09 <zzz> anything else on 1) ? 20:01:35 <zzz> 2) 0.9.41 release status (zzz) 20:01:46 <sadie__> hi 20:01:54 <eyedeekay> Hi 20:02:09 <zzz> we're wrapping up the review period. I expect to have in-net updates tomorrow morning, with other things to follow 20:02:44 <zzz> and then we'll do it all again for 42 20:03:06 <zzz> anything else on 2) ? 20:03:48 <zzz> 3) LS2 status (zzz) 20:04:01 <zzz> we're making slow but steady progress 20:04:11 <zzz> .41 has support for per-client auth 20:04:22 <zzz> garlic farm is also progressing, slowly 20:04:46 <zzz> we plan one new I2CP message for .42 to pass blinding info from the client to the router 20:05:12 <zzz> we're continuing to make headway on proposal 144 for new encryption, but it's really difficult 20:05:42 <zzz> I hope to have a good spec for 144 in a couple of months, maybe have some test code out there late this year 20:05:55 <zzz> as always our meetings are mondays 6:30 PM UTC in #ls2, all welcome 20:06:07 <zzz> anything else on 3) ? 20:06:37 <zzz> 4) I2P Browser "labs" project status (meeh) 20:06:45 <zzz> meeh what's the latest on the browser? 20:07:38 <zzz> ok I guess he's not here 20:07:51 <zzz> 5) muwire.i2p console home page request (zlatinb) 20:08:01 <zlatinb> hi 20:08:07 <zzz> `http://zzz.i2p/topics/2722` 20:08:11 <zzz> tell us about your site please 20:09:30 <zlatinb> MuWire is a general purpose file-sharing application which works on top of i2p. The site contains download links, screenshots and general information about the application. 20:10:05 <zlatinb> I believe MW is of general interest and usefulness to the i2p community; it has been growing quickly and drawing lots of interest. 20:10:22 <zzz> anybody have any comments about this request? for it? against it? 20:10:41 <zzz> or any questions? 20:11:39 <zzz> I support the request, I think it's a cool application that is only useful if it has lots of users, and we can help that by putting it on the console 20:11:55 <zzz> sadie__, ? eyedeekay ? 20:12:23 <sadie__> I support the request 20:12:30 <eyedeekay> I also support it. 20:12:49 <zzz> super. hearing no objections, we'll stick it in for .42 20:12:54 <zzz> anything else on 5) ? 20:13:41 <zzz> 6) Status scrum (zlatinb) 20:13:45 <zzz> take it away zab 20:14:15 <zlatinb> Hi, lets do the scrum in parallel. Please say in a few words : 1) what have you been doing since the last scrum 2) what you plan to do next month 3) if you have any blockers or need help. When done, say EOT 20:15:38 <zzz> 1) bug fixes, per-client authentication, garlic farm, new encryption, more bug fixes, getting ready for the release, early work on new things for .42 20:15:39 <zlatinb> me: 1) just a small tweak to the RouterContext api to allow custom log manager 2) Have more Router/RouterContext changes Id like to do to make things better for embedding the router. May also work on garlic farm if that opens up. 3) No blockers really, just would be nice to have Maven streamlined 20:15:41 <zlatinb> EOT 20:16:41 <zzz> 1a) lots of android bug fixes and cleanups 2) .41 release, config split for .42, new i2cp message for .42, prop 144 new encryption work 20:17:20 <sadie__> I continued to work on the console - updated logo added to both themes. Traveled to Tunis for RightsCon and made more connections in the community. Community outreach, testing, going through tickets and getting used to tx. 20:17:37 <zzz> 2a) getting ready for defcon, more garlic farm work, working with #ls2 team on tunnel building for routers with new encryption 20:17:45 <sadie__> next month Threat model update, user research and persona creation, funding outreach 20:17:45 <eyedeekay> I have been working on split tunnel configuration, recently it's been testing on multiple platforms. I made a webextension to improve how browsing works on Android by automatically configuring the browser, wrote/mirrored a bunch of blog posts, and worked on the web site. 2) Finish testing split tunnels and get them into the router for .42. Work with meeh on the browser. 3) no blockers EOT 20:17:46 <sadie__> EOT 20:18:01 <zzz> 3) no blockers, EOT 20:18:15 <zlatinb> thanks, thats I believe everyone </scrum> 20:18:22 <meeh> I'm writing 20:18:24 <meeh> moment 20:18:37 <zzz> ok 20:21:29 <meeh> I've been working mainly on the browser, also looked into the maven dependencies issue, documentation and also looked into how much of a hassle it would be to build the browser for android so we can deprecate the internal one in our app. 20:22:29 <zzz> meeh was that 1) ? please give 2) and 3) followed by EOT 20:25:34 <meeh> 1) yea, above 2) browser: get user documentation ready, make current features stable, finish the rebranding specially in terms of icons and graphics. osx launcher: finish the torrent snark share feature. android: finish the evaluation of how much hassle a port of the browser would be - tor does the same now, and given we're using much of the same and build scripts it's maybe doable. and lastly, for the donations 20:26:39 <meeh> 3) no blockers, and no help needed beyond always happy to accept PRs for browser stuff and specially android stuff which I'm not really skilled at 20:27:03 <zzz> EOT? 20:27:07 <meeh> EOT 20:27:14 <zzz> ok thanks meeh 20:27:22 <zzz> so that's it for 6) scrum 20:27:34 <zzz> let's circle back to 4) I2P Browser (meeh) 20:28:06 <zzz> could you please give us a status if there's anything more to add than what was in your scrum? 20:28:56 <zzz> last release, next release, stability, features, ... ? 20:30:21 <meeh> I think we have coverd most of the icon graphics in the browser project, however we also got some images (I specially recall the onboarding wizard now) needs to be repaced with something, same goes for text. Also the last week showed that it takes roughly 1-2days (up to 48hrs) for us to react on a security issue (that was, from when I had time until it was built) 20:34:05 <meeh> developer documentation shoud be enough for a while, the user documentation is soon done, trying to not rip off too much from places like mozilla and such in the attempt. Our approach to modifications to the fork is to place most of our logic and features into i2pbutton - and only do what's really needed in the firefox source, and which so far seem to work well.This also includes translations since firefox 20:34:05 <meeh> provide their own so the only left out to translate are i2p spesific strings 20:35:01 <zzz> ok thanks for the update. ANything else on 4) ? 20:35:07 <zzz> any questions about the browser? 20:35:16 <meeh> thoughts about moving to a new ESR release is ... bob-bob positive, meaning, I'm quite unsure if it can be done automatic, however the few places that need a patch or two is starting to get really well known for me 20:35:56 <meeh> next release should not be that long, it depends a bit on how much the team wish to fuel the fire in the coming weeks 20:36:35 <zzz> yeah we have to weigh the priorities. I think we're learning more about how much effort it would be to do this for real 20:36:46 <zzz> anything else on 4) ? 20:36:50 <meeh> I really don't have a schedule on that beyond when some new/current feature is done or more done, and/or any security patches are released for android 20:36:53 <meeh> ffirefox** 20:38:10 <zzz> anything else on 4) ? 20:39:05 <zzz> anything else for the meeting? 20:39:54 <zzz> thanks everybody 20:40:01 * zzz *bafs* the meeting closed

So You Want To Write A SAM Library

Sun, 23 Jun 2019 00:00:00 +0000

Or, talking to i2p for people who aren’t really used to reading specs

One of the best features of I2P, in my opinion, is it’s SAM API, which can be used to build a bridge between I2P and your application or language of choice. Currently, dozens of SAM libraries exist for a variety of languages, including:

If you’re using any of these languages, you may be able to port your application to I2P already, using an existing library. That’s not what this tutorial is about, though. This tutorial is about what to do if you want to create a SAM library in a new language. In this tutorial, I will implement a new SAM library in Java. I chose Java because there isn’t a Java library that connects you to SAM yet, because of Java’s use in Android, and because it’s a language almost everybody has at least a little experience with, so hopefully you can translate it into a language of your choice.

How to set up an ssh server behind I2P for personal access

Sat, 15 Jun 2019 00:00:00 +0000

How to set up an ssh server behind I2P for personal access

This is a tutorial on how to set up and tweak an I2P tunnel in order to use it to access an SSH server remotely, using either I2P or i2pd. For now, it assumes you will install your SSH server from a package manager and that it’s running as a service.

Considerations: In this guide, I’m assuming a few things. They will need to be adjusted depending on the complications that arise in your particular setup, especially if you use VM’s or containers for isolation. This assumes that the I2P router and the ssh server are running on the same localhost. You should be using newly-generated SSH host keys, either by using a freshly installed sshd, or by deleting old keys and forcing their re-generation. For example:

I2P Dev Meeting - June 04, 2019

Tue, 04 Jun 2019 00:00:00 +0000

Quick recap

Present: echelon, eyedeekay, zlatinb, zzz

Meeting Log

20:00:14 <zzz> 0) Hi 20:00:16 <zzz> hi 20:00:43 <zzz> 1) 0.9.40 release status remaining items (meeh, mhatta, nextloop, str4d) 20:00:43 <zzz> 2) Fixed i2pbote-android release status (meeh) 20:00:43 <zzz> 3) 0.9.41 dev status (zzz) 20:00:43 <zzz> 4) LS2 status (zzz) 20:00:43 <zzz> 5) I2P Browser "labs" project status (meeh) 20:00:43 <zzz> 6) Status scrum (zlatinb) 20:01:03 <zzz> 1) 0.9.40 release status remaining items (meeh, mhatta, nextloop, str4d) 20:01:28 <zzz> I believe that Debian/Ubuntu and official f-droid remain? 20:01:41 <zzz> I did hear back from mhatta, but he didn't make any promises 20:02:04 <zzz> I have reached out to other Debian people to see if anybody else could do it, nothing yet 20:02:10 <zzz> nextloop you have an update for us? 20:02:53 <eche|on> i build test build for debian buster and stretch on echelon.i2p/update/ 20:02:57 <zzz> anything else on 1) ? 20:03:29 <zzz> 2) Fixed i2pbote-android release status (meeh) 20:03:40 <zzz> mikalv, you have an update for us on bote? 20:04:52 <zzz> I believe we got the bote release out and it's working for people 20:04:58 <zzz> anything else on 2) ? 20:05:16 <eyedeekay> Nothing from me 20:05:30 <zzz> 3) 0.9.41 dev status (zzz) 20:05:45 <zzz> ok, we're a little bit more than halfway through the .41 dev cycle and it's going well 20:06:06 <zzz> big feature is the per-client authentication stuff for encrypted LS2 20:06:19 <zzz> we've also fixed a bug in large message handling that I think will help bote work better 20:06:55 <eche|on> we will see, test build available 20:06:56 <zzz> idk and I are working on splitting up the clients.config and i2ptunnel.config files, but it's looking like it will have to wait until .42 20:07:38 <zzz> for bote to see a difference it will probably have to get out to most of the network, as the bug could be hit by any router along the way 20:08:03 <eche|on> yeah 20:08:12 <zzz> the release is scheduled for the first week of July 20:08:33 <zzz> anything else on 3) ? 20:09:28 <zzz> 4) LS2 status (zzz) 20:09:58 <zzz> still going strong. We've had 42 weekly meetings so far and no end in sight, although we're spending more time on the new encryption (proposal 144) lately 20:10:19 <zzz> I already mentioned the per-client auth code that will be in 41. 20:10:54 <zzz> Garlic farm development for meta ls2 has been on hold for maybe 3 weeks, in favor of the client auth code, but we will be returning to it shortly 20:11:27 <zzz> I'm continuing to migrate specs from the proposals to the main specs part of our website 20:11:38 <zzz> as we get things implemented and tested 20:11:52 <zzz> our meetings are still 6:30 PM UTC on mondays in #ls2 20:12:11 <zzz> anything else on 4) ? 20:13:04 <zzz> 5) I2P Browser "labs" project status (mikalv) 20:13:15 <zzz> mikalv, how is the i2p browser going? 20:14:08 <zzz> I know a new beta release went out and it's getting some testing, but it doesn't work at all for some people? 20:15:04 <zzz> there's also a request for more documentation on our lab download page, and he said he would be getting to that soon, so keep an eye out 20:15:17 <zzz> ok, I guess mikalv isn't around, anything else on 5) ? 20:16:08 <zzz> 6) Status scrum (zlatinb) 20:16:13 <zzz> take it away zlatinb 20:16:42 <zlatinb> Hi lets do the usual - say 1) what youve been doing since last scrum 2) what you plan to do next month 3) if you have any blockers or need help 20:16:46 <zlatinb> end with EOT when done 20:17:08 <zlatinb> me: 1) some garlic farm, not much else 2) hopefully more garlic farm 3) no blockers 20:17:09 <zlatinb> EOT 20:17:17 <eche|on> doing the same as always, keepeing server alive, going on the same, no blocker, eot 20:17:30 <zzz> 1) garlic farm, ls2, and per-client auth; bug fixes 20:18:10 <zzz> 2) garlic farm, bug fixes, GMP 6.1.2, config file splitting, getting ready for 0.9.41 release 20:18:18 <eyedeekay> Split i2ptunnel configs and writing documentation/blogs, 2) more of that 3) no blockers eot 20:18:32 <zzz> 3) no blockers, EOT 20:18:44 <zlatinb> ok I think this is everyone, thanks 20:19:04 <zzz> ok, that was pretty quick, we're getting more efficient! 20:19:18 <zzz> anything else for the meeting today? 20:20:15 <zzz> oh, and congrats to eyedeekay who has signed a dev agreement and been granted mtn checkin privileges! while he's done quite a lot for us in the last few months, now he can do damage a lot faster! 20:20:37 <eyedeekay> :-D 20:20:38 <zzz> looking forward to having eyedeekay directly on the code base 20:21:07 * zzz looks for the baffer to swing at you 20:22:01 * zzz *bafs* the meeting closed

Basic I2P Tunnels Tutorial with Pictures

Sun, 02 Jun 2019 00:00:00 +0000

Although the Java I2P router comes pre-configured with a static web server, jetty, to provide the user’s first eepSite, many require more sophisticated functionality from their web server and would rather create an eepSite with a different server. This is of course possible, and actually is really easy once you’ve done it one time.

Although it is easy to do, there are a few things you should consider before doing it. You will want to remove identifying characteristics from your web server, like potentially identifying headers and default error pages that report the server/distro type. More information about threats to anonymity posed by improperly configured applications see: Riseup here , Whonix Here , This blog article for some opsec fails , and the I2P applications page here . Although much of this information is expressed for Tor Onion Services, the same procedures and principles apply to hosting applications over I2P.

How to offer your existing Web Site as an I2P eepSite

Sun, 02 Jun 2019 00:00:00 +0000

This blog post is intended as a general guide to running a mirror of a clear-net service as an eepSite. It elaborates on the previous blog post about basic I2PTunnel tunnels.

Unfortunately, it’s probably impossible to completely cover all possible cases of making an existing web site available as an eepSite, there’s simply too diverse an array of server-side software, not to mention the in-practice peculiarities of any particular deployment of software. Instead, I’m going to try and convey, as specifically as possible, the general process preparing a service for deployment to the eepWeb or other hidden services.

How to volunteer by helping I2P-Bote bootstrap

Mon, 20 May 2019 00:00:00 +0000

An easy way to help people message each other privately is to run an I2P-Bote peer which can be used by new bote users to bootstrap their own I2P-Bote peers. Unfortunately, until now, the process of setting up an I2P-Bote bootstrap peer has been much more obscure than it should be. It’s actually extremely simple!

What is I2P-bote?

I2P-bote is a private messaging system built on i2p, which has additional features to make it even more difficult to discern information about the messages that are transmitted. Because of this, it can be used to transmit private messages securely while tolerating high latency and not relying on a centralized relay to send messages when the sender goes offline. This is in contrast to almost every other popular private messaging system, which either require both parties to be online or rely on a semi-trusted service which transmits messages on behalf of senders who go offline.

0.9.40 Release

Tue, 07 May 2019 00:00:00 +0000

Update details

0.9.40 disables the old NTCP1 transport and removes support for SSU introductions over IPv6. Now that NTCP2 has been enabled by default for over 6 months, it’s time to disable the old NTCP1 transport and save bandwidth and memory. We continue development work on LS2 and encrypted leasesets. Several bugs have been fixed.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

I2P Dev Meeting - May 07, 2019

Tue, 07 May 2019 00:00:00 +0000

Quick recap

Present: chisana, eyedeekay, meeh, sadie, zlatinb, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 0.9.39 release status remaining items (meeh, mhatta, nextloop, str4d) 20:00:00 <zzz> 2) Fixed i2pbote-android release status (meeh) 20:00:00 <zzz> 3) 0.9.40 dev status (zzz) 20:00:00 <zzz> 4) LS2 status (zzz) 20:00:00 <zzz> 5) Status scrum (zlatinb) 20:00:04 <zzz> 0) Hi 20:00:06 <zzz> hi 20:00:10 <meeh> hi 20:00:17 <zlatinb> hi 20:00:51 <zzz> 1) 0.9.39 release status remaining items (meeh, mhatta, nextloop, str4d) 20:00:55 <eyedeekay> hi 20:01:07 <zzz> this agenda item was from the meeting last month... 20:01:29 <zzz> where we were still missing debian, f-droid, and mavencentral 20:01:40 <zzz> meeh you have an update for us on any of those items? 20:02:33 <meeh> me and str4d will pair this release, meaning he walks over all the steps with me, which includes maven/f-droid. I'm contacting him today about this since we last discussed this a week or two ago. 20:02:43 <zzz> and has anybody heard from mhatta re: debian? 20:02:51 <meeh> that should cover fdroid, maven and googleplay 20:03:15 <zzz> meeh this is about .39 - have f-droid and mavencentral releases for .39 been posted? 20:03:33 <sadie_> hi 20:03:34 <meeh> osx launcher will ofc be updated as well 20:03:52 <meeh> no, but when I pair with str4d I learn how I can fix that 20:03:59 <meeh> so then both 39 and 40 should be fixed 20:03:59 <zzz> we're talking .39 items from 7 weeks ago that were not complete at the last meeting 5 weeks ago 20:04:17 <meeh> `https://search.maven.org/search?q=g:net.i2p` 20:04:19 <meeh> maven is latest bt 20:04:24 <meeh> w 20:04:24 <meeh> .39 20:04:48 <zzz> ok. so what's the ETA for "pairing" (don't let him infect you with zcash-speak) 20:05:38 <R4SAS> :D 20:05:39 <zzz> and I thought our f-droid problem was server dependency issues, not the know-how. Were those resolved? 20:05:57 <meeh> my answer on that is when str4d have time for me for a quick walkthrough - which I took as he would find time for really quick when I spoke with him last. I'll update you on what he says today 20:06:41 <zzz> for mavencentral, you have everything you need including the howto, right? you have all the permissions you need? 20:06:58 <meeh> no howto 20:07:19 <zzz> I'm asking because 'when str4d has time' means nothing unfortunately :( 20:07:28 <meeh> we have some maven gradle script files in our repo, which I could *guess* how work and try, which I prefer not to mess up 20:07:46 <meeh> I have hope in him this time 20:08:09 <meeh> time to get rid of nagging, to free more time, - sounds something everyone would accept 20:08:42 <zzz> sure, it's the long plan to remove str4d from all dependencies, we're almost there, keep pushing until it's done 20:09:36 <zzz> ok back to mhatta - anybody heard from him? is it time to start calling him or where do we go from here? 20:09:46 <zzz> zlatinb, any ideas? 20:10:04 <zzz> and anybody heard from nextloop? 20:10:15 <zlatinb> calling him last time didnt work, although he confirmed I had the right number 20:10:27 <zlatinb> no ideas unfortunately 20:10:39 <zzz> meeh, as I understand it you can also just put in some request to get into the real f-droid, we don't really need nextloop. Do you know how to do that? 20:10:40 <sadie_> can anyone take on mhatta's tasks? 20:11:15 <zzz> anyone who's an official Debian Developer... know any others with time? 20:11:38 <meeh> I'm sorry to say I'm even less known with frdroid than android - I've only (at least in my memory) been the hoster of our private repo 20:11:53 <sadie_> no - but we should start looking 20:11:57 <meeh> but I can ask str4d while I talk to him, he should know 20:12:20 <zzz> ok meeh remember there's two fdroids, ours and the official fdroid.org, so please get the howto for both. Please try finding nextloop 20:12:27 <zzz> twitter, email, etc 20:13:13 <meeh> yea, our own is moved, and should in theory be working when I try those python commands to push it, - I'll test that out after speaking with str4d 20:13:19 <zzz> anything else on 1) ? We didn'd do a great job on .39 20:13:40 <zzz> so let's fix it quick for .40 20:13:57 <zzz> releases is what we do, when we can't get the releases out, we've failed 20:14:16 <zzz> anything else on 1) ? 20:15:18 <zzz> 2) Fixed i2pbote-android release status (meeh) 20:15:35 <zzz> meeh what's the status on the long-awaited bote android release? 20:15:42 <meeh> currently it still hangs on "connecting" 20:16:14 <zzz> but eyedeekay reports it works? 20:16:36 <zzz> did you try it non-firewalled meeh? 20:16:41 <eyedeekay> it works only if you use the built-in router. This is on a tablet 20:16:44 <meeh> ok, I feel we have talked many times now about the release. please don't take me as rude, mean, or anything besides just "trying to be as clear as possible" - I do not release a broken product. Unless I can send a message from my bote-android to my desktop-android - I'm not releasing 20:17:20 <zzz> this is a status meeting for everybody. Pretend you havent talked to me in a month, and tell everybody where we're at please. Youre not talking to me, you're reporting to the world 20:17:41 <meeh> because uless that, what we release is per definition broken - and it would reflect badly back at us 20:18:00 <meeh> ok sorry - but there it is ^ :) 20:18:27 <zzz> so, what's the outlook or ETA or guess for getting it fixed and released? 20:18:41 <meeh> but yea, I strongly feel that pushing a broken release would reflect badly at i2p - does anyone disagree on that statement? 20:19:11 <zzz> I'm not pushing you to release. I'm asking when it will be released. 20:19:26 <zzz> that's the purpose of this meeting, to report status 20:19:34 <meeh> how long time would you think it would take to make bote connect via tcp socket instead of unix domain? 20:19:46 <zzz> I dont know 20:20:06 <meeh> because at best, which I hope, it's that we need to do.. if not, no clue at all :( 20:20:32 <meeh> because if peers aren't the issue, and we still strugles to connect 20:20:38 <meeh> and based upon my debug sessions 20:20:48 <meeh> I suspect it's the IPC between the apps which make nonce 20:20:56 <meeh> and destroy the com 20:21:06 <zzz> ok. perhaps we can get some more testers from asking here in this channel... maybe cisiey 20:21:15 <meeh> cause the tunnel and leases seems ok in my view 20:21:39 <meeh> which my logical next place to look then is between router <-> bote 20:21:46 <zzz> ok. but if it's trying to build a tunnel for bote, then it's not a problem with the i2cp socket 20:21:57 <meeh> maybe the control socket work, but the data transfer stops 20:22:07 <zzz> you're either talking to the router or you aren't. it's all over the same socket 20:22:17 <zzz> (control and data) 20:22:32 <meeh> maybe google do something we don't know - wouldn't be the first time 20:22:50 <zzz> the good news is you're making progress, we've been stuck plenty of times before and always figured it out 20:22:54 <zzz> thanks for the update 20:22:57 <zzz> anything else on 2) ? 20:23:07 <meeh> so i2cp works like tls, it configures and then goes to pure data transfer? 20:23:34 <zzz> it's muxed control and data, all the time. it doesn't ever 'go to' pure data 20:23:54 <meeh> okay, ascii encoded binary data then or? 20:24:15 <zzz> I can walk you through how i2cp works after the meeting if you'd like 20:24:21 <meeh> anyway - we can take impl. details later 20:24:22 <meeh> yea 20:24:27 <zzz> anything else on 2) ? 20:25:02 <zzz> 3) 0.9.40 dev status (zzz) 20:25:16 <zzz> 0.9.40 dev status is DONE! 20:25:30 <zzz> we went for a short 6 1/2 week cycle and we released today 20:25:32 <chisana> congrats! 20:25:54 <zzz> in-net update is alive. Not sure if the English news has been updated though. The swarm seems a little small? 20:26:05 <zzz> eche|off, have you investigated? 20:26:25 <zzz> it's at least partially updating 20:26:47 <zzz> we're going to watch this one closely because we disabled NTCP 1, which shouldn't have any ill effects, but we'll see 20:27:19 <zzz> so, let's talk release items ETA. The in-net update is out, the website is updated. I'll do our PPA and deb repo tomorrow. 20:27:45 <zzz> meeh what's the eta for the android router release? 20:28:01 <meeh> again, I'll do this time with str4d 20:28:23 <meeh> the whole "str4d part" of the release in one pack 20:28:24 <meeh> :) 20:28:28 <zzz> even for android router? you did it by yourself last time. 20:28:42 <zzz> I'd just like to depend on him for as little as possible 20:28:42 <meeh> Yes, by hacking around maven 20:28:50 <meeh> but the correct order is to deploy maven first 20:29:05 <meeh> Yes, but the goal is that this is the last time we do that, <ever> 20:29:24 <zzz> ok. we'll see if that comes true, hopefully so 20:30:07 <meeh> for the record, I've already contacted him on DM @ twitter 20:30:25 <zzz> ok let us know when you have an ETA 20:30:26 <meeh> which is where I've been talking with him the past times 20:31:02 <zzz> zlatinb, I guess you and I should send out to all 10 of mhatta's emails to try and get his attention? It's been two months since we've heard from him 20:31:25 <zzz> would hate to have some old release in buster 20:31:27 <zlatinb> sure, give me the emails and Ill blast something out 20:31:38 <zzz> ok 20:31:59 <zzz> eche|off, eche|on you here? 20:32:39 <zzz> ok I guess that's it for 3) ? 20:33:18 <zzz> 4) LS2 status (zzz) 20:33:42 <zzz> I'll give a quick status on the 3 main proposals: 123, 144, and 150 20:34:13 <zzz> 123 is the ls2 proposal. It's mostly done and we got a lot of the encrypted ls2 code into .40 where we can do more testing 20:34:34 <zzz> the proposal itself hasn't changed much at all in the last month which is good 20:35:05 <zzz> 144 is the new encryption proposal. It's seen zero activity in the last month while higher-priority things happened 20:35:26 <zzz> but I've received a lot of comments on it. expect an updated draft in a week or two 20:35:48 <zzz> I'd like to see some implementations of 144 in 4-6 months but we have a lot of work to do to get there 20:36:05 <zzz> 150 is the new 'garlic farm' proposal based on raft, to manage massive multihoming. 20:36:30 <zzz> it's a new proposal but it's gotten pretty good feedback, less complaints by far than 144! 20:37:04 <zzz> zlatinb, when you think we might have an experimental plugin implementing 150? a couple of months? 20:37:24 <zzz> I guess we need to talk about what we can squeeze into .41 to support it 20:37:38 <zlatinb> depends on how we scope it; many of the listed features are really just nice-to-haves 20:37:59 <zzz> yeah in my revision yesterday I marked a lot of it as not-first-release 20:38:07 <zlatinb> if we cut everything to the absolute bare minimum maybe less than a few months 20:38:47 <zzz> yeah we haven't had our roadmap meeting for .41 yet, so I'm not sure what's where priority-wise 20:38:49 <zlatinb> its a medium-sized project I think 20:39:18 <zzz> agreed 20:39:37 <zzz> anybody have any questions on 4), ls2, or related proposals? 20:39:52 <zzz> as usual, all are welcome at our meetings, Mondays 6:30 PM UTC in IRC #ls2 20:40:27 <chisana> if i can get a "working/MVP" ECIES together, will that help with 144 completion? 20:40:54 <zzz> of course 20:41:37 <zzz> somebody has to be first. we've done integration testing with several other proposals, going back a year to NTCP 2. 20:42:03 <zzz> somebody is done first, then somebody else, then you try to get them to talk, then you try to figure out who's right and who's wrong 20:42:33 <zzz> it's hard and slow work but it's the only way to do it 20:43:15 <chisana> for sure, 144 is where I'll be spending most of my time, so will be sure to come with frequent updates/questions 20:43:25 <zzz> we've learned we're almost never done until we have two impls. that's the only way to 'test' the spec 20:43:41 <zzz> great 20:43:49 <zzz> anybody have any questions on 4), ls2, or related proposals? 20:44:30 <zzz> 5) status scrum (zlatinb) 20:44:36 <zzz> you have the floor zlatinb 20:45:15 <zlatinb> Hi. The usual scum in parallel. Please describe in a few words 1) what you have been doing since the last scrum 2) what you plan on doing next month 3) if you have any blockers or need help. Say EOT when done 20:45:49 <zlatinb> Me: 1) finishing touches on the advanced filter, work on garlic farm, outproxy tuning with arctic, some jogger tix 2) hopefully just garlic farm 3) no blockers EOT 20:47:03 <zzz> 1) bug fixes; signed windows installer; switch to izpack 5; susidns import feature; implementation of encrypted ls2; .40 review and release; working on android I2CP issues 20:47:38 <meeh> 1) I've been redesigning the osx launcher and upgraded swift code to 4.2 soon 5, cleaned up in the code, migrated more from objc. I've also been doing some improvements for the services I host for i2p inc. outproxy. and some android development and learning 20:47:55 <zzz> 1 cont.) wrote garlic farm proposal, lots of garlic farm architecture stuff; ls2 meetings and discussions; work with sadie on icons etc. 20:48:09 <sadie_> working on updating iconography for .40, will continue this for .41 and also updating logo with the logo created by Ura for console, site. Improvements to set up wizard, preparing for trip to RightsCon and outreach with TX, IFF EOT 20:48:55 <zzz> 2) .40 PPA release; .41 roadmap; config splitting work with eyedeekay, garlic farm; ls2 meetings; bug fixes; maybe automate sybil detection -> blacklisting? 20:49:03 <meeh> 2) for the next month I plan to give our browser some love again, updating version to equal upstream, some i2p integration improvements if it's doable, make the osx native context menu -> snark-share usable, and also look into more the issues with mattermost/irc/our-communication 20:49:06 <eyedeekay> 1) Bote, bug fixes, writing guides 2) hopefully split configuration, bote, and bugfixes 3) no blockers EOR 20:49:10 <eyedeekay> *EOT 20:49:38 <meeh> 3) no hopefully not, only would now be awaiting str4d to suggest a time where we can pair and do the release 20:49:48 <sadie_> outproxy docs /testing 20:49:50 <meeh> EOT 20:49:56 <zzz> 3) blockers: mhatta for debian/tails stuff 20:50:06 <eyedeekay> Oh also I'd like to spend some time with meeh on the browser as well in the next month. 20:50:17 <zzz> EOT 20:50:51 <zlatinb> Thanks, that completes the scrum. 20:50:59 <zzz> ok thanks zlatinb 20:51:12 <zzz> a couple quick questions before we wrap up the meeting 20:51:27 <zzz> does a 8 week cycle and a July 2 release date for .41 work? meeh? 20:52:12 <meeh> no imidiate things saying it shouldn't work, I think it's ok 20:52:26 <zzz> ok, that's what we'll pencil in until we hear from eche|off 20:52:57 <zzz> next, meeh, did you get the osx .40 build out? it's on the d/l page because it's triggered from the version number, but I didn't ask you if you'd done it yet 20:53:16 <zzz> so that's a bug in our process 20:53:24 <meeh> no I was thinking of starting that process now after the meeting 20:53:37 <meeh> didn't get time in front 20:54:06 <zzz> ok thanks. I'll fix our checklist so I don't bump the build on the d/l page until you're done, for next time 20:54:33 <zzz> last question for meeh, do you plan to do a browser release to fix the firefox cert thing? or do you even need to? 20:55:19 <meeh> could you eleberate the "firefox cert thing" please? :p 20:55:21 <zzz> as you said, time for some love for the browser. At some point we should talk about whether the 'lab' project should graduate to something more, or be killed? 20:55:48 <zzz> where the plugins like noscript broke. I'll fill you in later or look on twitter or ars technica 20:55:48 <meeh> yes, why don't we take that as a topic on our next meeting then? 20:55:54 <meeh> regarding RC or death 20:55:58 <zzz> ok, will do 20:56:09 <zzz> anybody have anything else for the meeting? 20:56:27 <meeh> I'm gonna start the osx build now if it's not anything more 20:56:44 * zzz looks for the baffer 20:57:00 <meeh> next osx upgrade would auto-update (woho!) 20:57:18 * zzz *bafffs* the meeting closed

I2P Dev Meeting - April 02, 2019

0.9.38 Release

Tue, 22 Jan 2019 00:00:00 +0000

Update details

0.9.38 enables NTCP2 by default for all users. NTCP2 provides effective resistance against DPI censorship and results in reduced CPU load because of the faster, modern cryptography used. The release also includes important bug fixes and performance improvements.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

I2P Dev Meeting - December 06, 2018

Thu, 06 Dec 2018 00:00:00 +0000

Quick recap

Present: alex, zlatinb, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 0.9.38 dev status (zzz) 20:00:00 <zzz> 2) LS2 status (zzz) 20:00:00 <zzz> 3) 35c3 state (echelon) 20:00:00 <zzz> 4) Status scrum (zlatinb) 20:00:03 <zzz> 0) Hi 20:00:05 <zzz> hi 20:00:08 <zlatinb> hi 20:00:13 <zzz> 1) 0.9.38 dev status (zzz) 20:00:32 <zzz> 38 is shaping up to be a very big release, we already have over 30k lines of diff 20:01:03 <zzz> checked in so far are the basics for the new wizard, the new geoip implementation, and initial LS2 support 20:01:26 <zzz> 37 is running very smoothly with 75% or more of the network running it, no NTCP2 problems reported 20:01:55 <zzz> the icons and CSS changes should start to show up next week 20:02:21 <zzz> our plans are for a late-january release. With a couple weeks off for the holidays, there's still a lot to do between now and then 20:02:26 <zzz> but it's all going smoothly so far 20:02:50 <zzz> I encourage all of you to test a dev build from bobthebuilder.i2p, or build it yourself 20:03:08 <zzz> we need testers as there's a lot of changes, we need to catch the issues now, not after the release 20:03:15 <zzz> anything else on 1) ? 20:04:16 <zzz> 2) LS2 status (zzz) 20:04:47 <zzz> we had our 19th weekly meeting yesterday. The basic LS2 part is done and I'm working on implementing it for 38 20:05:28 <zzz> right now we're doing two things in parallel - working on the encrypted LS2 spec, and starting work on proposal 144, which defines a new crypto and end-to-end protocol that relies on LS2 20:05:43 <zzz> encrypted LS2 should be wrapped up shortly. 20:06:24 <zzz> proposal 144, which we call ECIES-X25519-AEAD-ratchet, is quite complex and I think will take a month or two to shake out 20:06:41 <zzz> meetings are mondays 7:30 UTC in #ls2, all are welcome 20:06:55 <zzz> anything else on 2) ? 20:08:00 <zzz> 3) 35c3 state (echelon) 20:08:17 <zzz> I believe echelon can't make it here today 20:08:46 <zzz> I do know he's working on a tabletop banner solution, and sweets to give away, and he bought all our tickets 20:08:56 <zzz> so I think we're in good shape, see you all there in 3 weeks 20:09:01 <zzz> anything else on 3) ? 20:09:51 <zzz> oh, and a reminder, we will not have a meeting here on January 1, our meetings will be at CCC. The next meeting here will be Feb. 5 20:10:11 <zzz> 4) Status scrum (zlatinb) 20:10:15 <zzz> take it away zlatinb 20:10:28 <zlatinb> Hi. Were going to do the scrum in parallel as its easy to follow on IRC anyway. Just start typing 1) what have you been up to the last month 2) what you plan to do next month 3) any blockers or help needed. Finish your report with EOT 20:10:56 <zzz> ok lets see how this goes... 20:11:10 <alex_the_designerr> alex i really love hexagons here : icon work is progressing as zzz mentioned in 1) 20:11:30 <alex_the_designerr> last month i did website updates and some logo work 20:11:48 <zlatinb> 1) Work on onboarding, mainly wizard, and windows firefox installer with IDK. Got a signing certificate so our windows installers can be signed. Small experimental hacks on snark 20:12:09 <alex_the_designerr> next month i will finalize the initial drop of the new website, land icons, and *hopefully* get a blessing on a new logo 20:12:21 <zlatinb> 2) Wrap up the windows firefox profile insttaller and the wizard work for 0.9.38 20:12:32 <alex_the_designerr> stretch goals of personas and patterns 20:13:01 <alex_the_designerr> no blockers, just hustle EOT 20:13:06 <zlatinb> 3) No blockers, but will need to work closely with zzz to get things in monotone in a meaningful way, also with meeh if were to reuse the firefox profiile in OSX 20:13:07 <zlatinb> EOT 20:13:09 <zzz> me: 1) wizard, geoip, ls2, prop. 144, bug fixes; 2) ls2, prop. 144, integrating changes from design team, bug fixes, prep for 35C3, 35C3, set up signing machine; 3) no blockers EOT 20:13:57 <zlatinb> anyone else from the team here? 20:14:30 <zlatinb> doesnt look like it. Thats all from me on 4) 20:14:47 <zzz> ok, anybody have anything else for the meeting? 20:15:49 * zzz finds the baffer 20:16:06 * zzz *bafs* the meeting closed

I2P Dev Meeting - November 06, 2018

Tue, 06 Nov 2018 00:00:00 +0000

Quick recap

Present: echelon, str4d, meeh, zlatinb

Meeting Log

<eche|on> 0) Hi <eche|on> 1) 0.9.38 dev status (echelon) <eche|on> 2) LS2 status (echelon) <eche|on> 3) Status scrum (zlatinb) <eche|on> no other topic was added on thread in i2p before. <eche|on> 0) <eche|on> hi! <eche|on> welcome! <zlatinb> hi <eche|on> any addition to agenda? <eche|on> seems not to be <eche|on> 1) 0.9.38 dev status <eche|on> 0.9.38 will be a console update mostly, sadie and the UX, UI team is working hard on it, as seen on friday live steam made by alex <eche|on> the specs are hard to find but are making good progress <eche|on> we do figure out whats possible to change in console and we will include first parts in 0.9.38 <eche|on> plans are a few month until all changes are in, not all will be in 0.9.38 <str4d> hi <eche|on> currently plan for release of 0.9.38 is december, shortly ahead of 35c3 <eche|on> any more on 1) ? <zlatinb> I thought 0,9.38 was going to be January, but fine <eche|on> yeah, if it is to much work, we postpone to jan, after 35c3 <zlatinb> nothing more from me on 1) <eche|on> ok <eche|on> 2) LS2 status update <eche|on> nothing important to update here, dev meetings goind on, topics are discussed, but no code has been released yet <eche|on> hard, tough work, lots of topics, takes more time, guessed are not before .40 <eche|on> any more on 2) <eche|on> ? <str4d> Anyone interested in giving feedback should look at https://geti2p.net/spec/proposals/123-new-netdb-entries (which is where most changes are currently centered on) <eche|on> yeah, please interact and give feedback <eche|on> so handing over to zlatinb for 3) scrum status <zlatinb> hi. Only eche|on and meeh are in the channel right now, so why dont you guys go ahead and give us the 1-2-3 (in parallel) <eche|on> 1) working on fundings, server, preparing 35c3, bought tickets <eche|on> 2) going with this work <eche|on> 3) no blockers <eche|on> <meeh> 1) OSX Launcher cleanup & firefox profile <meeh> 2) Server migration <meeh> 3) Testnet development <meeh> 4) No blockers <zlatinb> Here are mine: 1) last month I worked on UX with Sadie and Alex, Testnet definition (post is on zzz.i2p forum) and custom Firefox I2P profile (post is on i2pforum) 2) more UX, code signing certificate 3) no blockers <str4d> ERR_OUT_OF_BOUNDS_WRITE <zlatinb> lol <eche|on> right, please test the Firefox I2P profile, zlatinb please hand out the link <zlatinb> `https://github.com/eyedeekay/firefox.profile.i2p/releases` <eche|on> thank you <meeh> nice, thanks <eche|on> about 35c3: the core team will meet in Leipzig <eche|on> if anyone else want to come, we are happy to meet you and spend some time to discuss I2P topics, or just have a coffee/beer/sweets <eche|on> Ok, thats all from the agenda, any add ons? <str4d> Have fun! I won't be at 35c3 this year, but I will be at RWC in January. <eche|on> *me warms up the sidekick baffer* <eche|on> great, alex plans to attend, beside sadie, to <eche|on> *baffer swings* <str4d> Aesome <str4d> s/Ae/Awe/ <eche|on> *baff* the meeting is closed. Thank you for your attending. Lets see again for next meeting in december, 4th 8pm UTC

Developing privacy-aware applications with Python and I2P

Tue, 23 Oct 2018 00:00:00 +0000

Invisible Internet Project (I2P) provides a framework for developing privacy-aware applications. It is a virtual network working on top of the regular Internet, in which hosts can exchange data without disclosing their “real” IP addresses. Connections inside I2P network are established between virtual addresses called I2P destinations. It’s possible to have as many of destinations as one needs, even use a new destination for each connection, they don’t disclose any information about the real IP address to the other side.

0.9.37 Release

Thu, 04 Oct 2018 00:00:00 +0000

Update details

0.9.37 continues work on our new transport NTCP2, which was introduced in the previous release. A new SSU IPv6 peer testing protocol is now supported. The release contains numerous bug fixes and performance improvements.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

I2P Dev Meeting - October 02, 2018

Tue, 02 Oct 2018 00:00:00 +0000

Quick recap

Present: alex, anonymousmaybe, DogeDollars, echelon, villain, zlatinb, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 0.9.37 dev status (zzz) 20:00:00 <zzz> 2) LS2 status (zzz) 20:00:00 <zzz> 3) Status scrum (zlatinb) 20:00:03 <zzz> 0) Hi 20:00:05 <zzz> Hi 20:00:11 <zlatinb> hi 20:00:17 <zzz> 1) 0.9.37 dev status (zzz) 20:00:41 <zzz> as most of you know, we pulled in the 37 release a couple weeks. Checkin deadline was yesterday, release will be thursday 20:00:57 <zzz> there's very little in it other than enabling NTCP2 by default 20:01:28 <zzz> OSX launcher won't be ready for the release, but we're seeing really good progress on it 20:01:54 <zzz> if all goes well, this will be our last release of the year. We have the holidays and CCC, and expect 38 in january 20:01:59 <zzz> anything else on 1) ? 20:02:30 <villain> hi guys 20:02:43 <zzz> 2) LS2 status (zzz) 20:02:59 <zzz> we've had 12 meetings over the last 3 months and we're making slow but steady progress 20:03:39 <zzz> we have a good understanding on what's needed for new crypto, and have agreed to most of the generic issues on how to add new crypto and get new LSes in and out of the netdb 20:03:40 <eche|on> hi 20:04:16 <eche|on> sounds great so far 20:04:17 <zzz> we'll continue to work on related issues such as encrypted leasesets and massive multihoming, as well as start to discuss specifics for particular new crypto choices 20:04:51 <zzz> I expect the LS2 meetings will continue for some time, so if you're interested please join in the discussions 20:05:02 <zzz> anything else on 2) ? 20:05:14 <eche|on> good to see some progress 20:06:14 <zzz> 3) Status scrum (zlatinb) 20:06:18 <zzz> all yours zab 20:06:44 <zlatinb> alright lets do the scrum, the usual 1) what youve been doing last month 2) what youre going to do next month 3) any blockers? 20:07:02 <zlatinb> villain: this would be your first real scrum I think, so you go first :) 20:08:23 <zlatinb> villain? 20:08:26 <villain> ok, 1) released asyncio SAM library https://github.com/l-n-s/i2plib and it's documentation, made a GUI filesharing application with it https://github.com/l-n-s/QuickShare, learned how JSP works in RouterConsole, made a first release of rpm package for CentOS and Fedora and set up a COPR repo for rpm packages https://copr.fedorainfracloud.org/coprs/supervillain/I2P/ 20:08:56 <zlatinb> ok well get back to you. zzz how about you go first instead 20:08:59 <eche|on> 1) server maintenance, cover the server outakes, managing finances 2) going on this work, getting new stickers, 3) no blockers so far :-) 20:09:04 <villain> 2) making Fedora package use system libraries, work on a better Router Console design after the release, publishing an article about I2P application development via SAM API 20:09:09 <zlatinb> oops sorry 20:09:12 <eche|on> uups 20:09:29 <villain> 3) need to do something with Jetty dependency in Fedora, since we only support v9.2 and Fedora has v9.4 20:09:39 <DogeDollars> lol 20:10:03 <zzz> yay parallel scrum 20:10:11 <zzz> for me: 20:10:12 <villain> :D 20:10:39 <eche|on> villain: about jetty, needs more work, afaik they changed some apis in between 20:10:44 <zzz> 1) lots of minor NTCP2 bug fixes that appeared since the 36 release, thanks to all the testers 20:11:11 <zzz> getting ready for the 37 release, testing OSX installer, other bug fixes and research, LS2 research 20:11:42 <zzz> 2) 37 release, starting serious work on migrating to new geoip database format, more LS2, more bug fixes, working with the PR/UI teams on console ideas 20:12:23 <zzz> 3) no blockers... also note, due to some personal obligations, I'm only working about half time last month and next 20:12:24 <zzz> EOT 20:12:52 <zlatinb> alright, eche|on ? 20:12:59 <eche|on> 1) server maintenance, cover the server outakes, managing finances 2) going on this work, getting new stickers, 3) no blockers so far :-) 20:13:22 <zlatinb> great thanks 20:13:33 <zlatinb> alex_the_designer: since you just joined, its our monthly scrum 20:13:46 <alex_the_designer> howdy! 20:13:55 <zlatinb> wanna tell us 1) what youve been up to last month 2) what youre going to do next month 3) do you have any blockers 20:15:04 <alex_the_designer> 1 . i've been streaming on fridays. during that time i've been making incremental progress on the website update. i also created a survey to help us with branding & design. 20:16:15 <alex_the_designer> 2. i'll continue streaming, but i am going to try to wrap up web dev outside of the stream. i'm also a bit overdue on the revamped whitepaper. i want to land at least an outline and rough draft by end-of-month 20:17:22 <alex_the_designer> 3. the only blocker atm is a bit of lack of knowledge on how the current web framework generates paths. not earth shattering, just requires more doc reading and fumbling 20:18:28 <zlatinb> ok, Ill talk about the survey a bit more after the scrum. Thank you 20:18:32 <zlatinb> meeh: are you here? 20:20:10 <zlatinb> meeh? 20:21:00 <zlatinb> feel free to give your 1-2-3s whenever you come around 20:21:20 <zlatinb> thats EOT for the scrum, but Id like to talk a bit about Alexs survey 20:21:27 <zzz> go ahead 20:22:17 <zlatinb> to everyone in the channel, please give this survey some thought and fill it out. It is hosted on google forms, but (unless you do something stupid) it isnt possible to correlate your google id with your I2P persona 20:22:46 <zlatinb> here is the link: https://docs.google.com/forms/d/e/1FAIpQLSdVCHXXBnHOrPpR6RH2DkCf3Q4W1kPBpg0QWToxfday0xqNAg/viewform 20:23:14 <zlatinb> alex_the_designer: please say a few words about how this survey will help you with the creative process 20:23:21 <alex_the_designer> certainly! 20:24:14 <alex_the_designer> so from the basics, it's important to understand the differences between how we, as internal maintainers perceive the utility of the system and our presentation as a brand versus how the users perceive the utility of the system and their identity as humans 20:24:41 <alex_the_designer> that's pretty deep, but there are some really straightforward things we can use 20:25:22 <villain> oh that makes sense 20:25:25 <alex_the_designer> for example, if we find that a lot of people have an aggressive stance, we can use basic color theory to know that fiery colors (reds, yellows, oranges) make sense 20:25:34 <anonymousmaybe> seriously? "what things should i2p consider to decide who i2p is for?" 20:25:55 <alex_the_designer> all of the questions are serious anon :D 20:26:19 <villain> i just didn't understand, are those questions personal or related to the project vision 20:26:48 <villain> will fill it soon 20:27:02 <alex_the_designer> it's important to talk a bit about yourself and your values and your ideals for the project 20:27:31 <anonymousmaybe> alex_the_designer yeah that one kinda bad , because I2P for everyone no question about it 20:27:46 <alex_the_designer> there is an implicit assumption there that who we are and what we do are not compartmentalized, but rather feed off one another :D 20:28:36 <anonymousmaybe> i like compartmentalization , thats why i use Qubes :p 20:28:42 <alex_the_designer> anon to say it is for everyone is not wholly correct is it? 20:28:57 <alex_the_designer> surveillance states for ex :D 20:29:48 <zzz> anything else re: the survey? 20:29:52 <alex_the_designer> universality can be an outcome though, so if you feel strongly about it, please do write about it :D 20:30:10 <zlatinb> not from me (re: survey) 20:30:25 <zzz> anything else for the meeting? 20:30:51 <anonymousmaybe> zzz any consideration for sandboxing i2p? 20:30:54 <alex_the_designer> i would just say that your efforts in the survey are deeply appreciated. i know it is rather long 20:31:16 <zzz> thanks for doing this alex 20:31:30 <anonymousmaybe> alex_the_designer yeah will do the fill up 20:31:46 <zzz> anonymousmaybe, not that I know of, and I'm the wrong guy to ask, but you could bring it up in this channel after the meeting 20:31:50 <zzz> anything else for the meeting? 20:32:16 * zzz grabs the baffer 20:33:00 * zzz *baffffs* the meeting closed

I2P Dev Meeting - September 05, 2018

Wed, 05 Sep 2018 00:00:00 +0000

Quick recap

Present: alex, echelon, mikalv, R4SAS, villain, zzz

Meeting Log

20:07:48 <zzz> 0) Hi 20:07:48 <zzz> 1) 0.9.36 release status (zzz) 20:07:48 <zzz> 2) 0.9.37 dev status (zzz) 20:07:48 <zzz> 3) LS2 status (zzz) 20:07:48 <zzz> 4) CCC planning (zzz/echelon/mikalv) 20:07:48 <zzz> 5) Status scrum (zlatinb) 20:07:55 <zzz> 0) Hi 20:07:58 <zzz> Hi 20:08:00 <eche|on> hi 20:08:16 <villain> hi :) 20:08:22 <zzz> apologies for being late 20:08:29 <zzz> 1) 0.9.36 release status (zzz) 20:08:47 <zzz> I believe we're done with everything, with the possible exception of f-droid 20:08:53 <R4SAS> hi 20:09:04 <zzz> nextloop, any f-droid status? 20:09:44 <zzz> ntcp2 testing is going well 20:09:56 <zzz> anything else on 1) ? 20:10:09 <R4SAS> I got one 20:10:33 <R4SAS> where can I see packages for debian as listing? 20:10:54 <zzz> I think it's packages.debian.org - there's a search box 20:11:12 <R4SAS> I'm thinkig about adding i2p packages in my repo 20:11:32 <zzz> there's also one packages.ubuntu.com 20:11:44 <zzz> and our repo is deb.i2p2.de 20:12:00 <zzz> anything else on 1) ? 20:12:03 <R4SAS> for ubuntu I will use launchpad packages 20:12:36 <zzz> 2) 0.9.37 dev status (zzz) 20:13:03 <zzz> it's early in the .37 cycle. We've set a 9 week cycle with a release the week of Oct. 22 20:13:21 <eche|on> ok 20:13:39 <zzz> meeh is working on getting the osx installer done for 37. I'm working on migrating to the new maxmind geoip format 20:13:56 <zzz> everybody is looking at UI stuff 20:14:13 <zzz> we should have the usability test results soon 20:14:40 <zzz> we're going to hopefully move the console help page to transifex 20:15:07 <zzz> so translators save some time for mid october to translate it! 20:15:11 <zzz> anything else on 2) ? 20:15:28 <eche|on> nothing yet, ntcp2 default? 20:15:32 <eche|on> in .37 ? 20:15:37 <meeh> yes I'm working on the osx wrapper - now ported to xcode, that and how,if,what i2p-browser :) 20:15:38 <zzz> yeah that too :) 20:16:32 <zzz> yes, ntcp2 by default in 37. Everybody please test dev builds where it is the default, or enable it in .36-0 release 20:16:38 <zzz> anything else on 2) ? 20:17:34 <zzz> 3) LS2 status 20:17:42 <zzz> we've had about 8 meetings over two months 20:18:06 <zzz> we still are in the discussion phase, but I think we are close to making some decisions and moving forward 20:18:29 <eche|on> at least sth 20:18:30 <zzz> there are a lot of related issues, such as new crypto, that are complicating things 20:18:47 <zzz> it's a lot of things that have been on the table for 5 years or more that we are finally addressing 20:19:05 <eche|on> good job ! 20:19:17 <zzz> what is clear is that we won't do everything at once 20:19:35 <zzz> we're going to make some initial changes, that will allow for optional things, and more changes to follow 20:19:53 <zzz> we have started updating the proposal document 20:20:17 <zzz> I hope to have some decisions documented soon... that will allow us to start some coding and experiments 20:21:09 <zzz> we took a week off for labor day but our next meeting is next monday the 12th at 5 PM UTC in #ls2 20:21:44 <zzz> all are welcome, it's complex and hard to follow even for us that have our heads in it, but it's fun to see things come together 20:21:48 <zzz> anything else on 3) ? 20:22:34 <zzz> 4) CCC planning 20:22:57 <eche|on> ok, ccc will be leipzig 20:23:01 <zzz> We made preliminary decisions last december but we traditionally finalize the rules around this time every year 20:23:13 <zzz> absolutely for sure leipzig, right? 20:23:29 <eche|on> yes, officially announced from CCC already 20:23:36 <zzz> great, I didn't see that 20:24:19 <zzz> we pay for congress tickets, we reimburse up to 1500 euro for plane/train, and new for this year we agreed to up to 400 euro hotel expenses 20:24:27 <eche|on> yes 20:24:56 <zzz> over 1500 or paid in advance only for 'special circumstances', i.e. you are broke :) 20:25:13 <eche|on> look all good so far 20:25:25 <zzz> and that's for paid program members only, unless approval from echelon. 20:25:28 <eche|on> tickets will be managed central, if possible 20:25:38 <zzz> we will buy the congress tickets centrally, correct. 20:25:48 <zzz> so we need to know who is coming... soon... 20:26:12 <zzz> so, any objections or changes to the rules as I've listed them here? 20:26:12 <eche|on> I assume we need to by end of oct 20:26:20 <eche|on> no need to change 20:26:31 <meeh> nope, all fine 20:26:49 <zzz> the idea is, if you want to be there, the project will help you get there 20:27:35 <zzz> stickers and power strips and banners and tables and other logistics like that, we will work out as we go, no need to discuss here in the meeting 20:27:58 <eche|on> ok, yes 20:28:31 <zzz> if you haven't gotten your plane tickets yet, do it NOW, there aren't a lot of flights into LEJ. If you're riding your bike or taking the train, you have more time 20:28:54 <zzz> those who haven't been before, ask those who have about hotels and anything else you want to know 20:29:09 <zzz> anything else on 4) ? 20:30:19 <zzz> 5) scrum 20:30:28 <zzz> zab is out, so I'll run it 20:31:05 <zzz> when I call on you, please say 1) what you did last month 2) what you're going to do next month 3) any blockers; end with EOT or 'thats it' or something 20:31:13 <zzz> villain, you go first 20:33:00 <zzz> eche|on, you're next 20:33:35 <eche|on> I did do all financial stuff, server work, testing, helping with release (news), going to do same for next month, no blockers. Ill be afk tomorrow til wednesday 12th 20:33:58 <zzz> thanks. meeh your turn 20:34:27 <meeh> okay, I got time for three points 20:34:28 <meeh> * worked with porting osx launcher finished to xcode - revert was hard, since my monotone skills say I shouldn't play with fire (this was freeze time) 20:34:28 <meeh> * one of the DCs I got servers at had a power failure where everything went off - so I've mostly making sure things run and arguing with servers today. 20:34:28 <meeh> * looked into both firefox/chromium for solving self-signed certificate issues as well as a privacy browser, did a 24hrs monkey coding on a qt plugin which is based upon chromium but gave awesome results. 20:35:23 <zzz> and for next month? blockers? 20:35:49 <meeh> osx launcher is fully moved to xcode now, icon is showing again, some odd behavior with action handler but should be fixed anytime soon 20:36:31 <villain> Ok, learned things about monotone and java. fixed https://trac.i2p2.de/ticket/1244, added a ntcp2 article translation. made a press-release for the 0.9.36 in russian. Last week, developing that async python library, now finishing documentation for it. https://github.com/l-n-s/i2plib 20:36:47 <meeh> for next month I'll look more into the browser case if you rest approve when I'll give you an review next meeting, if not it's probably android and osx which is highest on the lsit 20:37:35 <zzz> villain, for next month? blockers? 20:38:57 <zzz> for me, last month I fixed a lot of NTCP2 and other bugs, and got the 36 release out. 20:39:30 <zzz> next month will be the new geoip code, continuing to work on LS2, fix more bugs, get the help page ready for translation 20:39:53 <zzz> I will be mostly afk for the next week, however 20:39:56 <zzz> no blockers 20:40:28 <zzz> anybody else here to report? sl or alex_the_designer ? 20:40:32 <eche|on> :-) 20:40:39 <alex_the_designer2> hi 20:40:59 <zzz> hi alex_the_designer2 please give us your 1/2/3 last month/next month/blockers 20:41:06 <alex_the_designer2> last month : was blocked on onboarding. major thanks to eche|on and meeh for getting me unblocked 20:41:23 <villain> the next month as zzz mentioned, will get more practice with monotone, fixing the website tickets, finish a redhat package. would like to hear feedback on my python lib from str4d , and add it to i2p organisation on github, if it's fine 20:41:37 <villain> no blockers except that 20:41:43 <villain> EOT 20:42:10 <zzz> thanks villain 20:42:15 <alex_the_designer2> this month : looking at trac issue 1996 (pretty sure that was the one you wanted input for), also starting writeup on whitepaper. got some headway on www update during friday streams but will also do during weekdays. 20:42:46 <alex_the_designer2> no blockers. will be afk-ish 17-21 as i'll be in SF. EOT or 'that it' or something :D 20:43:06 <zzz> alex_the_designer2, also perhaps since this is your first meeting, could you give us a quick overview of your friday night twitch sessions, what might come out of it, how we can participate? 20:43:20 <alex_the_designer2> sure thing! 20:44:14 <alex_the_designer2> so fridays from 9:30pm CST to about 11pm CST i stream on twitch.tv/alex_the_designer . when i started back in january the overall theme was 'FOSS Design' but it has been more aimed toward i2p 20:45:00 <alex_the_designer2> i have been doing basic tutorials and whatnot to help first timers understand how to set up i2p and host a site as i believe content is the primary blocker for wide adoption 20:45:36 <alex_the_designer2> what would be helpful is for folks to show up and socialize if they wish. also promoting the show via whatever social media channels you prefer is super helpful 20:46:26 <alex_the_designer2> i also have some raw recordings which i wish to post online from prior shows, but i need to edit those (mainly to redact my home IP) 20:46:48 <zzz> are you getting feedback from the viewers that will give us insight on priorities and UI choices? How can you funnel what you're learning back to the rest of us, either in posts or tickets or writeups? Have any plans? 20:47:08 <alex_the_designer2> the_tin_hat has been showing up on the regular and has provided a lot of comic relief and feedback 20:47:42 <alex_the_designer2> when it comes to UI choices, i haven't had enough feedback from users to truly justify any choices 20:47:52 <eche|on> ok, in 6h my alarmclock goes on, I head into bed, cya later 20:48:03 <alex_the_designer2> so it's by gut & trial and error 20:48:04 <zzz> night echelon 20:48:15 <alex_the_designer2> cya echelon! 20:48:35 <zzz> ok so perhaps we need to expand the audience first 20:49:04 <zzz> so let's get out the word more, maybe on our forums, or blog post... not just twitter 20:49:33 <zzz> thanks alex for the overview, you're doing good work, hopefully it results in more users and content and a better product 20:49:38 <alex_the_designer2> every channel is super helpful as the audience is all over :D 20:49:45 <zzz> right 20:49:48 <alex_the_designer2> thanks for the vote of support! 20:50:07 <zzz> anybody else I missed for the scrum? sadie sl 20:50:18 <zzz> anything else for the meeting? 20:50:52 * zzz grabs the baffer 20:51:13 <villain> alex_the_designer2: can make reddit /r/i2p announcements for your streams 20:51:31 <zzz> good idea 20:51:36 <alex_the_designer2> much obliged villain 20:51:42 <zzz> sorry again for the late meeting start 20:51:49 * zzz *bafs* the meeting closed

0.9.36 Release

Thu, 23 Aug 2018 00:00:00 +0000

Update details

0.9.36 introduces NTCP2, our new secure transport protocol. NTCP2 provides effective resistance against DPI censorship and results in reduced CPU load. It makes I2P more likely to run on low-end devices such as smartphones and home routers. The protocol is disabled by default in this release for testing.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

NTCP2 Implementation Details

Mon, 20 Aug 2018 00:00:00 +0000

I2P’s transport protocols were originally developed around 15 years ago. Back then, the main goal was to hide the transferred data, not to hide the fact that one was using the protocol itself. Nobody thought seriously about protecting against DPI (deep packets inspection) and protocols censorship. Times change, and even though original transport protocols are still providing strong security, there was a demand for a new transport protocol. NTCP2 is designed to resist current censorship threats. Mainly, DPI analysis of packets length. Plus, the new protocol uses the most modern cryptography developments. NTCP2 is based on the Noise Protocol Framework , with SHA256 as a hash function and x25519 as an elliptic curve Diffie-Hellman (DH) key exchange.

I2P Dev Meeting - August 07, 2018

Tue, 07 Aug 2018 00:00:00 +0000

Quick recap

Present: echelon, mikalv, villain, zlatinb, zzz

Meeting Log

20:00:05 <zzz> 0) Hi 20:00:05 <zzz> 1) 0.9.36 status (zzz) 20:00:05 <zzz> 2) LS2 status (zzz) 20:00:05 <zzz> 3) Applications for bobthebuilder.i2p and paste.crypthost.i2p at `http://zzz.i2p/posts/13897` 20:00:05 <zzz> 4) Status scrum (zlatinb) 20:00:05 <zzz> 5) Reschedule Sept. 4 meeting (zzz) 20:00:10 <zzz> 0) Hi 20:00:12 <zzz> hi 20:00:21 <zzz> 1) 0.9.36 status (zzz) 20:00:27 <zlatinb> hi 20:00:29 <villain> hi all 20:00:34 <zzz> 6 weeks into the 36 cycle, 2 weeks to go 20:00:52 <mikalv> hi 20:00:53 <zzz> tag freeze is tomorrow; checkin deadline a week from friday; release week of aug. 20 20:01:18 <zzz> everybody please test. I'll mark the next version as -rc 20:01:31 <zzz> anything else on 1) ? 20:02:24 <zzz> 2) LS2 status (zzz) 20:02:30 <zzz> we had our 5th meeting yesterday 20:02:47 <zzz> going well, but going very slowly. The issues are complex and interrelated 20:03:11 <zzz> I updated the proposal (123) today, but it's still very rough 20:03:41 <zzz> we haven't even agreed on goals and priorities yet, so it's going to be a while, but I'm happy with the process 20:03:58 <zzz> all are welcome, next meeting is next monday, 6 PM UTC in #ls2 20:04:27 <zzz> anything else on 2) ? 20:05:13 <zzz> 3) Applications for bobthebuilder.i2p and paste.crypthost.i2p at `http://zzz.i2p/posts/13897` 20:05:25 <zzz> these are console home page requests 20:05:33 <zzz> is the applicant sl here? 20:06:07 <zlatinb> usually not as its late in $HOME 20:06:27 <zzz> anybody have any comments pro or con on adding these to the console home page? 20:07:06 <zlatinb> Im +1 on adding bob the builder, neutral on the new paste 20:07:13 <zzz> any objections? 20:07:31 <mikalv> I'm +1 for online services on the console 20:07:55 <zzz> doesn't hurt to have a second paste, especially since the one we have now has been offline for weeks at a time 20:08:15 <zzz> although it's been fairly reliable lately 20:08:40 <zzz> hearing no objections, I will add them to the console for 36 20:08:46 <villain> if there are dead links to remove, can add those links instead 20:08:50 <zzz> anything else on 3) ? 20:09:04 <eche|on> nope 20:09:11 <zzz> zerobin isn't dead, it just hasn't had the best uptime in the past 20:09:46 <zzz> 4) Status scrum (zlatinb) 20:09:49 <zzz> go zlatinb 20:10:31 <zlatinb> ok, were going to go around the room and when your name is called describe briefly 1) what youve been up to last month 2) what you plan to do next month 3) if youre blocked by anyone or need help 20:10:57 <zlatinb> were going to start with The New Kid - villain. Since this is your first scrum, skip 1) and just go with 2) and 3) 20:11:09 <zlatinb> go villain 20:12:24 <zlatinb> villain you there? 20:12:34 <villain> learning java and monotone, plans to fix few more website tickets before 36 release, as zzz discussed with zzz. and learn more :) 20:13:00 <villain> no blockings at the moment 20:13:41 <zlatinb> great. Usually we say EOT at the end of the report :) 20:13:48 <villain> now doing research on https://trac.i2p2.de/ticket/1583 20:13:57 <villain> EOT 20:13:59 <villain> heh 20:14:17 <zlatinb> thank you. zzz youre next 20:14:37 <zzz> ok. last month was mostly polishing and testing ntcp2, with orignal's help 20:14:46 <zzz> starting up the LS2 research and meetings 20:14:59 <zzz> lots and lots of bug fixes of course 20:15:33 <zzz> next month will be getting the .36 release out, and continuing on LS2, bug fixes, etc 20:15:41 <zzz> also doing some code refactoring along the way 20:16:06 <zzz> hope to get to SSL wizard for non-jetty for 37. Sadly didnt' get to it for 36, it was too hard 20:16:13 <zzz> no blockers; EOT 20:17:14 <eche|on> ok, I did lots of forum admin work, some code testing, donations and account managing, going with this the next month, no blockers currently 20:17:20 <eche|on> uupos 20:17:40 <zlatinb> ok eche|on might as well go with you next :) 20:17:51 <eche|on> thats more or less all^^ 20:18:04 <zlatinb> ok cool 20:18:10 <zlatinb> mikalv: what about you? 20:18:14 <mikalv> Yea, well for me; Current; OSX Launcher beta for 0.9.36 Gonna; 1. Continue on the OSX launcher (making it pretty, some more features and work on stablility). 2. Hopefully help zzz with the LS2 research and impl. 3. Push out an test-MVP/alpha of a browser bundle. 20:18:23 <mikalv> 4. Continue my campain for no-single-person-of-failure where the core members which hosts core services give access to other core members as backup/fallback if someone goes missing so the project dont suffer more of such events. 20:18:28 <mikalv> Blocker; Hoping we could get the DNS control of i2p2.de from welt. 20:18:56 <mikalv> either me or eche|on, at least someone more active 20:19:09 <zlatinb> wow that was well-prepared, well done 20:19:25 <zlatinb> sadie mentioned she *might* be able to make it paging sadie 20:19:49 <zlatinb> str4d: any chance youre around? 20:19:53 <eche|on> Welt contacted me, I replied, no more answer from him 20:19:58 <mikalv> zlatinb: remember I've done this for two years each day before i2p now :p 20:20:41 <mikalv> I wish to get control of the DNS domain, so I can more freely change trac ip, and later on download 20:20:59 <zlatinb> Alex W. was around but just left so I guess thats everyone for the scrum 20:21:16 <mikalv> cause of situation, the old deperecated server reverse-proxy to the new trac :( 20:22:04 <zzz> 5) Reschedule Sept. 4 meeting (zzz) 20:22:08 <zlatinb> EOT 20:22:19 <mikalv> yea sorrry EOT 20:22:26 <zzz> ok I can't make Sept. 4 and I think some others can't either 20:22:46 <zzz> we could do Wed. Sept. 5 or Tues. Sept. 11? 20:23:01 <zzz> if the 11th, there would be only 3 weeks between that and the october 2 meeting 20:23:27 <zlatinb> Ill be on the road most of september so cant promise either the 5th or the 11th 20:23:27 <zzz> I want to put CCC on the agenda for the Sept. meeting, even though we made most of the decisions last december for funding 20:23:44 <mikalv> I think I can both, so for me it's ok 20:23:53 <zzz> eche|on, what about you? 20:24:12 <eche|on> 11th is not OK 20:24:30 <zzz> wed. 5th ok? 20:24:41 <eche|on> 5th seems to be ok 20:24:52 <zzz> ok, let's pencil it in for wed. the 5th 20:24:55 <mikalv> ok 20:25:02 <zzz> anything else on 5) ? 20:25:06 <zzz> anything else for the meeting? 20:25:51 * zzz grabs the baffer 20:26:40 * zzz *bafs* the meeting closed

I2P Dev Meeting - July 03, 2018

Tue, 03 Jul 2018 00:00:00 +0000

Tue, 10 Apr 2018 00:00:00 +0000

Update details

0.9.34 includes important bug fixes for hidden services, streaming, and SAM. The release continues work on preparation for Ed25519 as the default signature type and NTCP2 as a new transport. Performance improvements and the usual assortment of bug fixes are included.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

I2P Dev Meeting - April 03, 2018

Tue, 03 Apr 2018 00:00:00 +0000

Quick recap

Present: manas, meeh, str4d, zlatinb, zzz

Meeting Log

20:00:01 <zzz> 0) Hi 20:00:01 <zzz> 1) 0.9.34 update (zzz) 20:00:01 <zzz> 2) 0.9.34 blocker tickets (str4d) 20:00:01 <zzz> 3) 0.9.34 Android/Maven build and release roles and schedule (str4d/meeh) 20:00:01 <zzz> 4) Proposed removal of open4you.i2p and git.repo.i2p from console home page (anonymousmaybe) 20:00:01 <zzz> 5) 0.9.35 plan (zzz) 20:00:01 <zzz> 6) NTCP2 plan (zzz) 20:00:01 <zzz> 7) Status scrum (zab) 20:00:05 <zzz> 0) Hi 20:00:07 <zzz> Hi 20:00:30 <zzz> welcome to meeting 269, spanning almost 16 years 20:00:33 <manas> Hey 20:00:43 <zlatinb> hi 20:00:44 <zzz> 1) 0.9.34 update (zzz) 20:00:55 <zzz> ok, translation and checkin deadline is in 3 days 20:01:20 <zzz> not much for recent bug reports 20:01:36 <zzz> so we are looking good, pending item 2) 20:01:56 <zzz> I've been working on .35 and beyond the last couple of weeks 20:02:04 <zzz> anything else on 1) ? 20:03:00 <zzz> 2) 0.9.34 blocker tickets (str4d) 20:03:25 <i2pr> [Slack/str4d] Hi :B 20:03:32 <zzz> str4d has several blocker tickets dating back several months, and have been pushed past a couple of releases already 20:03:38 <manas> hey there str4d 20:03:38 <zzz> str4d, what's your plan for these? 20:04:10 <i2pr> [Slack/str4d] I see two blocker tickets. 20:04:19 <i2pr> [Slack/str4d] One is reseeding on older Androids 20:04:39 <zzz> ok good, 2 is better than 'several' 20:04:45 <i2pr> [Slack/str4d] For that one, we narrowed down the problem window, but could not at the time identify a fix (the one we tried didn't work) 20:05:07 <i2pr> [Slack/str4d] I do not have time at the moment to work on it, and the older versions are slowly becoming less-used 20:05:24 <i2pr> [Slack/str4d] So I'm thinking that we should just deprecate the older Android versions 20:05:59 <i2pr> [Slack/str4d] Note that Google Play Store has put in requirements that new app uploads start conforming to newer APIs, so we may in that sense have our hand forced if we want to continue to push through GPlay 20:07:02 <zzz> and the other one? 20:07:16 <i2pr> [Slack/str4d] Dropping support for older APIs should be relatively simple to do as part of the next update, if we agree on it. 20:08:03 <i2pr> [Slack/str4d] The other is translated string fixes from 0.9.31 (in OP says "minor, but classing as a blocker") 20:09:19 <i2pr> [Slack/str4d] Some of this I have fixed locally, but have not had time to extract and push out. 20:09:41 <zzz> I guess the question is whether you intend to do any UI bug fixes at all. Last fix we saw from you was 5 months ago. I highlighted about 10 tickets a month ago I wanted to see fixed for .34. Do you intend to do any UI work going forward or should we find a replacement? 20:09:58 <i2pr> [Slack/str4d] Realistically, if left to me, it will keep slipping, as my priorities are elsewhere at present. 20:10:39 <i2pr> [Slack/str4d] I do plan to push more of the UI patches, but I do not have time to make it a sufficiently-short timescale. 20:11:05 <zzz> ok so we shouldn't expect any UI work, including even simple fixes, at all from you, either for .34 or later? 20:11:31 <i2pr> [Slack/str4d] The problem is that the word "simple" is doing a lot of heavy lifting there :stuck_out_tongue: 20:12:11 <i2pr> [Slack/str4d] For .34, correct, don't expect any UI work from me. 20:12:15 <zzz> ok. I wish we knew this months ago. We've lost an awful lot of time. We'll start reassigning the work and looking for replacements. 20:12:22 <zzz> anything else for 2) ? 20:13:01 <i2pr> [Slack/str4d] I am happy to pass patchsets to others for extracting the "simple" fixes - maybe they will have better luck than I wrangling monotone+git 20:13:23 <zzz> 3) 0.9.34 Android/Maven build and release roles and schedule (str4d/meeh) 20:14:03 <zzz> I'd like to know if str4d and meeh have figured out who is doing what for the .34 maven/fdroid/android releases, so I know who to hold to account and when it's going to happen 20:15:37 <i2pr> [Slack/str4d] Meeh has the signing keys for Android and FDroid 20:15:51 <meeh> We can figure it out now. What do you think str4d , do you got time for it, or should I? 20:16:16 <i2pr> [Slack/str4d] I'd be happy for you to do it with me in your ear :slightly_smiling_face: 20:16:31 <i2pr> [Slack/str4d] (because I want to build out our release capabilities) 20:16:47 <zzz> meeh that ok with you? 20:17:00 <i2pr> [Slack/str4d] We can set up a time to pair on it. 20:17:16 <meeh> Yea, we can do that. That's the best option so far, so you can get me up to date on how, and what to do 20:17:29 <zzz> what about maven central? 20:17:45 <i2pr> [Slack/str4d] I'm currently the only one with credentials for it. 20:18:08 <meeh> Yea, I don't have maven access 20:18:22 <i2pr> [Slack/str4d] There's a few hoops that need to be jumped through with Sonatype to change that 20:18:29 <zzz> so are you doing it or giving meeh the privs? I need to know who is responsible and when it's going to happen 20:18:39 <i2pr> [Slack/str4d] (vaguely recalling what I had to do in order to set it up in the first place) 20:18:52 <i2pr> [Slack/str4d] I will do that for .34 20:19:21 <i2pr> [Slack/str4d] (probably in the same pairing with meeh) 20:19:57 <zzz> ok can I hold you two to a two-week deadline to get it all released? If I get mine cut by April 10, that would be April 24. ok? 20:20:41 <i2pr> [Slack/str4d] Okay. 20:20:51 <zzz> ok meeh? 20:20:56 <i2pr> [Slack/str4d] I'm in Denver week of 9th, then back in UK following week 20:21:09 <i2pr> [Slack/str4d] So whichever week works better timezone-wise for meeh 20:21:11 <meeh> Yepp 20:21:39 <zzz> ok. meeh you also owe me an ack that you checked the gplay crash report 20:21:45 <zzz> anything else on 3) ? 20:21:49 <meeh> I should be able to adjust to something that fits for str4d in that timeline 20:22:27 <zzz> 4) Proposed removal of open4you.i2p and git.repo.i2p from console home page (anonymousmaybe) 20:22:48 <zzz> ok anonymousmaybe reports that those two sites have been down for weeks or months and recommends that they be removed from the router console 20:22:55 <zzz> any objections? 20:23:28 <i2pr> [Slack/str4d] git.repo.i2p has been down for a while primarily because I have not had time to go in and get it running again. 20:23:53 <zzz> so I don't hear you objecting :) 20:23:55 <i2pr> [Slack/str4d] If it is desired that it be running again, I can make time to do that. But I would also not object to it being removed. 20:24:06 <zzz> if not, I'll remove them both for .34 20:24:31 <i2pr> [Slack/str4d] No objections from me on open4you.i2p 20:24:33 <zzz> you may apply for reinclusion following our normal processes once it's up and stable 20:25:00 <zzz> it's a terrible user experience to have dead links on our console home page, and we owe it to our users to keep them up or remove them 20:25:06 <i2pr> [Slack/str4d] ACK (I followed that process the first time IIRC :D) 20:25:15 <zzz> ok anything else on 4) ? 20:25:54 <zzz> 5) 0.9.35 plan (zzz) 20:26:11 <zzz> ok we had a roadmap meeting a week or two ago, and the roadmap on our website reflects the results 20:26:22 <zzz> everything else has been pushed to 36/37 20:26:35 <zzz> we've been hard at work on 35 features for a couple of weeks already 20:26:55 <zzz> this is the way I want to work for every release, where the work is done in advance and then merged in early in the cycle 20:27:13 <i2pr> [Slack/str4d] +1 20:27:13 <zzz> the schedule is for a .35 release in mid-late June, standard 10-week cycle 20:27:34 <manas> There will be a meeting similar to the last one prior to the .35 release? 20:27:57 <zzz> yeah, I'd like to do a roadmap meeting for the next one a few weeks before each release 20:28:06 <manas> ok sounds good 20:28:20 <zzz> all the anything else on 5) ? 20:28:35 <zzz> s/all the// 20:29:08 <i2pr> [Slack/str4d] .35 roadmap looks reasonable to me 20:29:24 <i2pr> [Slack/str4d] +1 on private testnet setup improvements :smile: 20:30:01 <zzz> 6) NTCP2 plan (zzz) 20:30:09 <manas> I had posted on the forums a little late but would like to have a meeting (or discuss at next meeting) to discuss specifics about the private test net 20:30:30 <zzz> ok we've convened a team with reps from all 3 projects. We've had two meetings so far and have a new version of the proposal posted 20:30:39 <meeh> manas I'll contact you in a day or so, done some work on the topic as well 20:30:43 <zzz> we plan to meet once a week and put out a new draft after each meeting 20:30:49 <manas> meeh: alright :) 20:31:02 <zzz> the goal is to be done by the end of april and have test implementations by the end of may. 20:31:19 <zzz> the next meeting is in #ntcp2 April 9, 4 PM UTC, all welcome. 20:31:20 <i2pr> [Slack/str4d] Which proposal is being furthered? 20:31:36 <zzz> the version that we posted yesterday. 20:31:52 <zlatinb> its available on clearnet forum str4d 20:32:16 <zzz> actually, it's on the website. proposal 111. 20:32:56 <i2pr> [Slack/str4d] Okay, so it's the update I proposed 20:33:06 <zzz> comments may be made on i2pforum.i2p, i2pforum.i2p, the trac ticket, the zzz.i2p thread, in #ntcp2, here, you can email me, anyway anybody wants to do it. Clearnet or not. We welcome participation from all. 20:33:11 <i2pr> [Slack/str4d] I need to check whether what was pushed to the website matches what I've been working on locally 20:33:46 <zzz> as I emailed you a week ago, we do not require a separate proposal from you. 20:34:12 <zzz> 111 will be the proposal and we will update it each week after our meeting.\ 20:34:33 <i2pr> [Slack/str4d] I'll ping you after meeting. 20:34:40 <zzz> anything else on 6) ? 20:36:00 <zzz> 7) Status scrum (zab) 20:36:04 <zzz> over to you zlatinb 20:36:30 <zlatinb> Hi. Before we start the scrum, everyone who wants to get paid please fill out the timesheet/request form that zzz posted on his forum 20:36:55 <zlatinb> and email the form to me 20:36:58 <zlatinb> now off to scrum 20:37:01 <zzz> ok I suggest we wait until at least the last week of the month, so people know how much they worked up until then? 20:37:42 <i2pr> [Slack/str4d] I agree. My understanding was the quarter started in Feb 20:37:43 <zlatinb> sure, but I would need a few days after I receive the form 20:38:09 <manas> I believe the post said not before APR 23 20:38:29 <zzz> On the post I said earliest to email is April 23 and latest is April 30. But you make the rules and I'll update it. 20:38:49 <zlatinb> those dates are fine 20:39:07 * zlatinb got caught for not having read the post ;-) 20:39:17 <zlatinb> anyway :) 20:39:50 <zlatinb> so scrum - well go around the room, when your name is called pls post a short description of 20:39:56 <zlatinb> 1) what youve been doing since last scrum 20:40:02 <zlatinb> 2) what you plan to do next month 20:40:21 <zlatinb> 3) are you blocked by anyone or do you need help on anything 20:40:40 <zlatinb> pls do so even if youve been updating on the video chat, this is for posterity 20:41:02 <zlatinb> so, zzz you go first 20:41:35 <zzz> thanks zlatinb. In the last month I've done a lot of work on the .34 release, including lots of bug fixes and new features. 20:42:13 <zzz> More recently, I have transitioned to 35 features and research, including susimail folders, and the new NTCP2 protocol 20:42:53 <zzz> in the next month I plan to review the paper we received a month ago, continue work on NTCP2, get the 34 release out, 20:43:05 <zzz> and fix bugs. 3) no blockers. EOT. 20:43:18 <zlatinb> thanks 20:43:26 <zlatinb> eche|off: are you here by any chance? 20:43:39 <zzz> i think not 20:43:40 <zlatinb> I know he said he wouldnt be but just in case... 20:44:03 <zlatinb> alright. Next full-timer- meeh, go 20:44:22 <meeh> Highlights 20:44:22 <meeh> I've soon done with an MVP for a new OSX launcher, improved outproxy service and tuning it for better performance. I've done some few scala tests, more to come. And I've setup test systems I need for both Android and OSX dev/test. Also used some time to get known with the codebases again. Also somewhat read me up on proposals. 20:44:40 <meeh> Misc: Much I can't really recall at the moment. 20:45:23 <meeh> For next round: Have the MVP for OSX ready. Mindblow you with a nice browser bundle. Focus more on scalatests, android and contribution documentation 20:45:51 <meeh> Blockers; mja.. being more secure on dns changes as discussed on last video 20:46:12 <zlatinb> yes indeed, Ill have to get more serious chasing welt 20:46:34 <zlatinb> anything else meeh ? 20:46:51 <meeh> Cause once we can be sure of changes and when, I can deprecate some old services with fresh servers and software (cleanup, and such) 20:46:59 <meeh> Improve my services for i2p 20:47:04 <meeh> Done now :) 20:47:19 <zlatinb> cool 20:47:35 <zlatinb> manas: it must be very late where you are, good to see you, Your update pls? 20:47:56 <manas> hey, everyone. good to see all again 20:47:57 <manas> to summarize: I have studied up to chapter 4, which is on java syntax, of the book which I am using to study Java. will be continuing with chapter 5 this month, objects in java. have written some java code which was reviewed by zzz (thank you, zzz). will be continuing to study crypto as well. reading up on ant and gradle. thinking about the test net, planning on acquiring some hardware for 20:47:58 <manas> this. continuing to maintain services which I run and staying on top of security disclosures. reading/responding to trac and forum posts regularly. 20:48:19 <manas> meeh, if you have any writeups/documentation to share about running an outproxy I would be interested in reading it :) 20:48:21 <manas> eot 20:48:57 <zlatinb> good stuff - I want to talk about the outproxy business in light of OTF soon 20:49:08 <meeh> Sure, we can talk about that later. Mainly it's a tunnel without anything in the domain field 20:49:09 <zlatinb> but now back to scrum - str4d your tunr 20:49:11 <zlatinb> turn 20:49:18 <i2pr> [Slack/str4d] In the last month I worked on our current crypto specs, started the process for migrating proposals to the new forum, attended the Tor developer meeting in Rome (for Zcash, but had various I2P-relevant discussions), worked with Elio/Ura on website mockups, worked on Ire in preparation for NTCP2 draft implementation, and generally thought 20:49:19 <i2pr> about NTCP2 crypto primitives. 20:50:20 <i2pr> [Slack/str4d] In the next month I plan to check my email XD, pair w/ meeh on .34 Android/Maven, schedule into my calendar these meetings I seem to be missing, review the paper, start a draft implementation of NTCP2 in order to figure out some of the Noise library issues, and work on specifying the Elligator-esque ephemeral key blinding. 20:50:50 <i2pr> [Slack/str4d] Only blocker is email-related, will ping people after about it. 20:50:57 <i2pr> [Slack/str4d] EOT 20:51:38 <zlatinb> i2pr: str4d ping ping 20:52:35 <zlatinb> thanks 20:52:46 <zlatinb> is sadie around on slack? 20:53:40 <zlatinb> if not I think this is everyone / everything for 7) 20:54:03 <zzz> ok, thanks zlatinb, anybody have anything else for the meeting? 20:54:38 <i2pr> [Slack/str4d] I don't think she's here 20:54:55 <meeh> no, just announcement that I will setup more resources for outproxy and improve it 20:55:03 * zzz grabs the baffer 20:56:00 * zzz *baffs* the meeting closed

I2P Dev Meeting - March 06, 2018

Tue, 06 Mar 2018 00:00:00 +0000

Quick recap

Present: echelon, meeh, psi, str4d, zlatinb, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 0.9.33 remaining release items (f-droid.org, official Debian) (nextloop, mhatta) 20:00:00 <zzz> 2) 0.9.34 update (zzz) 20:00:00 <zzz> 3) Status scrum (zab) 20:00:04 <zzz> 0) Hi 20:00:06 <zzz> hi 20:00:17 <zlatinb> hi 20:00:20 <zzz> welcome to meeting 268 of this great 15-year-old project! 20:00:44 <zzz> 1) 0.9.33 remaining release items (f-droid.org, official Debian) (nextloop, mhatta) 20:01:03 <zzz> ok, nextloop did a PR for f-droid, it hasn't appeared yet, but hopefully will soon 20:01:30 <zzz> for Debian, we still haven't heard from mhatta, and we've missed the Bionic deadline 20:01:51 <zzz> anything else on 1) ? 20:03:01 <zzz> 2) 0.9.34 update (zzz) 20:03:37 <zzz> we're halfway through the scheduled 10-week cycle. I've set the checkin deadline for 4 1/2 weeks from now. Tag freeze in 3 weeks, release in 5 weeks 20:04:03 <zzz> we're at 16K lines of diff. The most notable change is part 2 of the susimail rework. The rest is fixes all over 20:04:28 <zzz> I encourage everyone in the team to fix a few tickets for the release, if at all possible 20:05:01 <zzz> we're past the 'big changes' deadline, but still hoping for various fixes to come in from everybody 20:05:21 <zzz> and of course, testing the dev builds is also everyone's job, please help out 20:05:31 <zzz> anything else on 2) ? 20:07:01 <zzz> 3) Status scrum (zab) all yours 20:07:04 <eche|on> not really 20:07:11 <zlatinb> Hi. Were going to go all around the room and when your name is called please give a brief description of: 20:07:21 <zlatinb> 1) what have you been doing since the last scrum 20:07:29 <zlatinb> 2) what you plan to do the next month 20:07:44 <zlatinb> 3) are you blocked by anything or do you need help from someone 20:08:11 <zlatinb> Please wait until the scrum is finished if you feel you need to address a question or have a comment 20:08:21 <zlatinb> lets go - zzz kick it off 20:09:10 <zzz> ok. in addition to what I already said... I've been working on improving ssl support in the console and eepsites; upnp improvements; ipv6 fixes; and misc. refactoring 20:09:40 <zzz> I expect to continue on ssl and ipv6 in the coming month, as well as wrapping up other fixes for the release, which will be in early april 20:10:06 <zzz> I'm blocked on working on proposals, waiting to work with str4d 20:10:07 <zzz> EOT 20:10:41 <zlatinb> eche|on: please go ahead 20:11:07 <eche|on> ok, Ive been working on trac, forum and blog 20:11:28 <eche|on> next month this will go on, a bit more pr, update finances,... 20:11:39 <eche|on> currenly all ok, next week I am on travel 20:12:12 <zlatinb> great. meeh are you here? Can you give us an update? 20:12:38 <meeh> Yes, moment 20:13:45 <meeh> I've been working on the OSX launcher part cause it bugs the crap out of me since I'm on OSX, also - the last 1,5 day I've used on migrating the horrible sqlite db of ours (trac) to something that scales 20:13:53 <meeh> Trying to avoid that null byte issue 20:14:31 <meeh> Seem like I will get it working now once I've manually defined all tables up front in pgsql before I try to import (without tables then) 20:15:37 <meeh> And yea, I also might have something regarding git->monotone export 20:15:45 <meeh> That's all for me 20:16:22 <zlatinb> ok, not blocked on anything I take it? 20:16:46 <meeh> nope 20:16:50 <meeh> All fine :) 20:17:16 <zlatinb> excellent. psi you wanna join the fun? 20:17:22 <psi> sure 20:17:28 <psi> let's see 20:17:47 <psi> 1) this is my first scrum for i2p 20:18:18 <psi> 2) this month i'll make libsam super shiny and awesome 20:18:32 <psi> possibly adding epoll/kqueue variant 20:18:57 <psi> 3) currently waiting for review on the PR i made on github for libsam 20:19:00 <psi> EOT 20:19:20 <zlatinb> good stuff 20:19:24 <zlatinb> str4d: are you here? 20:19:51 <zlatinb> sadie maybe you are? 20:20:09 <zzz> sadie told me she'd probably miss it 20:20:41 <zlatinb> and str4d seems away 20:20:55 <zlatinb> so that concludes the scrum I believe - manas is exempt and mhatta awol 20:21:20 <zzz> ok, anything else for 3)? anything else for the meeting? 20:21:34 <zlatinb> now, does anyone have any questions or comments on anything that was brought up during the scrum? 20:21:41 <meeh> I got a question regarding oracle, license, and us whenever it's q/a time 20:21:54 <zlatinb> (this is the blocker/blockee part) 20:22:05 <zlatinb> meeh: ok we can chat after the meeting 20:22:43 <zzz> I'll just add that I'm blocked on all the possible packaging changes and improvements by mhatta 20:23:12 <zzz> and on the Tails startup notification feature, ditto 20:24:22 <zlatinb> ok. That concludes 3) I think 20:24:33 <zzz> ok, anything else for the meeting? 20:25:02 * zzz grabs the baffer 20:25:27 <i2pr> [Slack/str4d] Here 20:25:38 * zzz puts down the baffer 20:25:38 <zlatinb> ohai 20:25:39 <i2pr> [Slack/str4d] Sorry for delay, internet issues again 20:26:13 <zlatinb> so yeah, briefly 1) what you did 2) going to do 3) blocked / need help? 20:27:58 <i2pr> [Slack/str4d] 1) bug fixing, release work, router console UI patchset, Android work & signing key delegation, ticket triage, XRDS article 20:29:14 <i2pr> [Slack/str4d] Oh, and collaboration with Ura 20:29:24 <i2pr> [Slack/str4d] (plus usual meetings etc.) 20:31:40 <i2pr> [Slack/str4d] 2) Migrate all proposals to new forum, finish up NTCP Noise draft as a new proposal, Tor Dev meeting, sync w/ Ura, sync w/ dawuud on SPHINCS, possibly paper review, revisions on XRDS article, ticket triage 20:34:49 <zlatinb> are you blocked on anything or need help from someone? 20:34:50 <i2pr> [Slack/str4d] 3) Nothing right now, but outreach to people interested in reviewing things 20:35:07 <i2pr> [Slack/str4d] Oh, mailing list 20:35:20 <zzz> ok, anything else for 3)? anything else for the meeting? 20:36:03 * zzz grabs the baffer again 20:36:23 <zzz> zab I like the 1-2-3, that worked well 20:37:01 * zzz **bafs** the meeting closed

I2P at BSidesNYC

Mon, 12 Feb 2018 00:00:00 +0000

Sadie and str4d attended BSidesNYC on Saturday January 20th. Thank you to the BSides Team for setting such a great conference!

Aside from a few talks, we mostly worked on several goals that we had set for the day during the afternoon in the common area at John Jay College.

Our most pressing task was writing the high-level roadmap for 2018, following the discussions at 34C3. This has now been posted - go check it out! We also picked up some communication threads that were put aside over the holiday period around our nascent Vulnerability Response Process, and getting it into “production use”.

High-level Roadmap for 2018

Sun, 11 Feb 2018 00:00:00 +0000

Wed, 03 May 2017 00:00:00 +0000

Update details

0.9.29 Release

Mon, 27 Feb 2017 00:00:00 +0000

Update details

0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages. We now support NTP over IPv6. We’ve added preliminary Docker support. We now have translated man pages. We now pass same-origin Referer headers through the HTTP proxy. There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

I2P Dev Meeting - February 07, 2017

Tue, 07 Feb 2017 00:00:00 +0000

Quick recap

Present: echelon, EinMbyte, manas, psi, str4d, zzz

Meeting Log

20:00:00 <zzz> 0) Hi 20:00:00 <zzz> 1) 33C3 follow-up 20:00:00 <zzz> 2) 0.9.29 update (zzz) 20:00:00 <zzz> 3) Tails maintainer (zzz) `http://zzz.i2p/topics/2108` 20:00:00 <zzz> 4) NTCP2 draft (Manas) 20:00:00 <zzz> 5) Reseed documentation patch (Manas) 20:00:04 <zzz> 0) Hi 20:00:05 <zzz> hi 20:00:21 <zzz> 1) 33C3 follow-up 20:00:32 <eche|off> hi 20:00:50 <zzz> anybody have anything they'd like to say about 33c3? I'd say the traffic to our table was less than previous years 20:01:07 <zzz> thanks to manas for doing some writeups over on zzz.i2p 20:01:09 <psi> ohay 20:01:15 <eche|off> yeah, was less, but still ok 20:01:21 <zzz> we'll cover tails in 3) 20:01:32 <zzz> let's hope for a new city this year 20:01:54 <zzz> anything else on 1) ? 20:02:25 <i2pr> [Slack/str4d] Hi 20:02:26 <i2pr> [Slack/str4d] I can't comment on that, but I really enjoyed it! 20:02:28 <manas> Hey! 20:02:38 <zzz> ok, moving on 20:02:43 <zzz> 2) 0.9.29 update (zzz) 20:02:51 <i2pr> [Slack/str4d] I had a good time with Yolgie in Linz and Vienna; should be a good connection moving forward 20:03:17 <zzz> I've set the checkin deadline for 2 1/2 weeks from now, friday 2/24, release about 2/27 20:03:21 <zzz> mostly bug fixes 20:03:30 <eche|off> uh, time to get something done, ok 20:03:40 <zzz> I'm also (still) planning to enforce sigs over at stats.i2p registration very soon 20:04:04 <manas> Enforce sigs? 20:04:12 <zzz> str4ds console rework was pushed to .30, so that would be a mid-Feb prop deadline 20:04:17 <zzz> *mid-march 20:04:32 <manas> So more verification steps when registering a host name? 20:04:42 <zzz> manas, basically proofs that you control the domain you're registering 20:05:10 <manas> Hm ok 20:05:15 <zzz> I fixed a bunch of bugs over the weekend, knocking out trac tickets, going to try for a few more in next week or two 20:05:38 <zzz> so the tag freeze and tx push will be in about 8 days 20:06:07 <zzz> i figured out how to do man page translations, so everybody go do your thing over on transifex for that 20:06:13 <zzz> anything else on 2) ? 20:06:16 <i2pr> [Slack/str4d] Woo 20:06:19 <i2pr> [Slack/str4d] If there's anything useful for me to work on for .29, let me know. Otherwise I'll continue on the .ui branch. 20:06:20 <eche|off> done that already^^ 20:06:37 <eche|off> I will do the cert on my reseed... 20:06:45 <manas> I'm continuing to work on the Hindi translations :) 20:07:04 <zzz> yeah str4d there's definitely some things that need work before you prop or the pitchforks will come out 20:07:14 <zzz> ok great 20:07:29 <zzz> 3) Tails maintainer (zzz) `http://zzz.i2p/topics/2108` 20:07:40 <i2pr> [Slack/str4d] I've got a bunch of changes locally that I'm tidying up before pushing 20:08:07 <zzz> we met a guy 'yolgie' at ccc who said he'd do it. pinged him in early jan, he said he'd start in feb. pinged him a few days ago,no response yet 20:08:26 <zzz> we're about to get evicted from tails, so anybody that can help would be great 20:08:45 <psi> i am ready to go with tails whenever, i have finally got building tails down 20:08:51 <i2pr> [Slack/str4d] What's the timescale on that? 20:08:57 <manas> psi: nice! 20:09:50 <zzz> see the zzz.i2p thread for a link to a tails ticket that has the schedule for our evition 20:09:55 <zzz> *eviction 20:11:15 <zzz> theres a bunch of old tickets and a bunch of haters and so it's all just about over 20:11:20 <zzz> anything else on 3) ? 20:11:44 <eche|off> I hope it will be fine 20:11:55 <zzz> 4) NTCP2 draft (Manas) 20:12:00 <zzz> manas what do you have for us? 20:12:24 <manas> Draft has been prepared, it's posted up on zzz.i2p 20:12:40 <manas> I haven't heard any comments as of today 20:12:51 <zzz> so it's a consolidation of the old proposal and EinMByte's complete rewrite? 20:13:07 <manas> I think I included the important bits, but I would need someone who knows this topic better to review. 20:13:14 <eche|off> some folks asking when it is done, but nothing more.. 20:13:30 <manas> zzz: Yes 20:13:47 * psi starts reading ntcp proposal 20:13:53 <zzz> this is progress, albeit small. I still consider the whole thing completely stalled, won't happen until people start participating 20:14:00 <manas> zzz: I did not include the parts from the old proposal which were outdated 20:14:22 <zzz> ok I'll give it a couple more days, if there are no comments in the zzz.i2p thread I'll just check it into the website? 20:14:59 <manas> zzz: There are a few minor edits I can make (style) at the very end 20:15:09 <zzz> ok great. anything else on 4) ? 20:15:16 <manas> From tuna's recent post 20:15:38 <manas> But that's all 20:15:41 <zzz> 5) Reseed documentation patch (Manas) 20:15:46 <zzz> manas what do you have for us? 20:16:04 <manas> Heard from backup 20:16:08 <manas> His comments are here: `http://zzz.i2p/topics/2210-reseed-webpage-updates` 20:16:27 <manas> Will be making another patch after I include his suggestions 20:16:46 <eche|off> great 20:16:48 <manas> He has suggested removing a number of parts (old reseed methods) 20:16:56 <manas> As well as removing support for lighttpd 20:17:06 <eche|off> I still do use the old methods, but thats fine 20:17:09 <manas> I don't know who if anyone is using lighttpd to run reseeds 20:17:26 <zzz> this is great work. backup owns the page but refuses to create html patches for his changes, and I refuse to be the html editor, so we've been stuck for a year. Thanks for moving us forward. 20:17:29 <manas> issue with not being able to set a certain HTTP header 20:17:55 <manas> :) 20:18:10 <zzz> manas for this one, when you're done, add a note in the zzz.i2p thread and I'll check it in 20:18:44 <manas> If anyone has comments on backup's proposed changes please post it. If there are no comments within a week, I'll share the updated patch and inform zzz. 20:18:57 <zzz> anything else on 5) ? 20:18:59 <manas> zzz: sure 20:19:16 <manas> Not on my end 20:20:03 <zzz> anything else for the meeting? 20:20:21 <eche|off> not from my side 20:20:28 <EinMByte> Am late, but about ntcp2 20:20:39 <manas> Hey EinMByte 20:20:40 <zzz> go ahead 20:21:00 <EinMByte> I can read through the latest draft 20:21:24 <EinMByte> Has a decision been made yet about which ciphers to support? 20:21:27 <manas> It's over here, by the way: `http://pinkpaste.i2p/show/246/` 20:21:39 <psi> there it is 20:22:19 <zzz> basically we've made no progress since the 1MB draft, and manas has just now merged it with the previous proposal 20:22:28 <zzz> anything else for the meeting? 20:22:58 <EinMByte> Ok, will read the draft. Someone should contact Winter 20:23:04 <EinMByte> (probably me) 20:23:11 * zzz grabs the baffer 20:23:24 * zzz *bafs* the meeting closed

0.9.28 Release

Mon, 12 Dec 2016 00:00:00 +0000

Update details

0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty. There are fixes for the IPv6 peer testing feature introduced last release. We continue improvements to detect and block peers that are potentially malicious. There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.

Present: dg, psi, sadie, str4d, Zerolag, zzz

Meeting Log

21:00:23 <zzz> 0) Hi 21:00:23 <zzz> 1) HOPE update (zzz) `http://zzz.i2p/topics/1968` 21:00:23 <zzz> 2) 0.9.27 update (zzz) 21:00:23 <zzz> 3) Summer of X update (sadie/str4d) 21:00:27 <zzz> 0) Hi 21:00:29 <zzz> hi 21:00:47 <psi> hi 21:00:48 <zzz> 1) HOPE update (zzz) `http://zzz.i2p/topics/1968` 21:00:48 <i2pr> [Slack/str4d] Hi 21:01:13 <zzz> ok, HOPE is in 2 1/2 weeks. The possible lunch meeting with Lance on Friday is still TBD 21:01:42 <zzz> please keep friday lunch open, I don't expect we will know if it's off or on until that week 21:01:49 <zzz> looking forward to seeing everybody there 21:01:54 <zzz> anything else on 1) ? 21:02:06 <i2pr> [Slack/str4d] I'm now guaranteed to not be there 21:02:20 <i2pr> [Slack/str4d] Timing has not been in my favour ;_; 21:02:51 <psi> i am not going to hope this year it seems 21:03:14 <i2pr> [Slack/sadie] I will be at HOPE 21:03:38 <zzz> 2) 0.9.27 update (zzz) 21:04:13 <zzz> .27 is progressing slowly, as expected. At this rate, the .27 release will be pushed from August to Sept. 21:04:31 <zzz> while we focus on X stuff, and perhaps, NTCP2 21:04:47 <i2pr> [Slack/str4d] Fine with me 21:04:50 <zzz> that OK with everybody? 21:05:02 <dg> There's nothing to rush on, so OK 21:05:09 <dg> ultimately we will release when we need to 21:05:28 <zzz> 26 seems really stable. The only thing is the bote class not found thing, which we're awaiting followup info for on trac 21:05:52 <dg> There was something to do with the Debian package which I found as an issue 21:05:56 <i2pr> [Slack/str4d] And that gives us a chance to get work done in August on plugins into .27 21:05:57 <zzz> and if it's what I think it is, we could fix it with a simple change and deb/ubuntu rebuild only 21:06:00 <dg> Will save it for a ticket though. 21:06:12 <zzz> anything else on 2) ? 21:06:38 <psi> does .27 affect anything in i2pd? 21:07:19 <zzz> there's ipv6 peer testing, yes. i2pd shouldn't bump to 27 until it's supported 21:07:39 <psi> okay 21:07:50 <zzz> doesn't have to be on the java schedule though 21:07:53 <zzz> anything else on 2) ? 21:08:42 <zzz> 3) Summer of X update (sadie/str4d) 21:08:51 <zzz> sadie, str4d, what's going on? 21:08:52 <i2pr> [Slack/str4d] Not yet, I think? 21:08:55 <i2pr> [Slack/str4d] Ah yep 21:08:55 <i2pr> [Slack/str4d] No 21:10:30 <zzz> perils of using a relay for the meeting? 21:10:40 <i2pr> [Slack/str4d] I think it's been going well so far 21:10:55 <i2pr> [Slack/str4d] We're a month in now, and have had three (IIRC) blog posts out about it 21:11:46 <zzz> ok, what are we doing in july? 21:12:02 <i2pr> [Slack/str4d] Apps 21:12:05 <i2pr> [Slack/str4d] Outreach 21:12:15 <i2pr> [Slack/str4d] So I'll be working with Tahoe-LAFS 21:12:29 <i2pr> [Slack/str4d] On their I2P integration 21:13:12 <zzz> any volunteers to work on transmission and/or libtorrent? Those seem to be swamps of brokenness right now 21:13:14 <i2pr> [Slack/str4d] And also submitting a PR to update lightning Browser's I2P library 21:13:45 <i2pr> [Slack/str4d] Yeah, it's never too late to pick up another API 21:13:59 <i2pr> [Slack/str4d] Other projects I'd like to see us help this month: 21:14:02 <zzz> the outreach part is key, lets get the word out via twitter and email 21:14:08 <psi> what was done in transmission before? 21:14:31 <zzz> there's a i2p fork for transmission, see the zzz.i2p thread 21:14:33 <i2pr> [Slack/str4d] psi, SAM support 21:14:52 <i2pr> [Slack/str4d] In libtorrent 21:14:54 <psi> that was before libsam3 wasn't it? 21:14:58 <psi> i'd guess it has totally bit rotted 21:15:09 <i2pr> [Slack/str4d] (I keep forgetting transmission doesn't use that) 21:15:23 <zzz> sadie, what do you have planned for July PR? 21:15:31 <i2pr> [Slack/str4d] Mmm, a clean fork might be easier 21:15:58 <i2pr> [Slack/str4d] As I was saying, the other projects I have ideas for: 21:16:01 <i2pr> [Slack/str4d] - IPFS (Go and Python impls) 21:16:27 <i2pr> [Slack/str4d] - OpenBazaar (will soon use IPFS) 21:16:34 <i2pr> [Slack/str4d] - ZeroNet 21:17:02 <i2pr> [Slack/str4d] Any of these would be good candidates for someone to help out 21:17:33 <villain> hello i2peeps :) zzz: I've just sent a patch for the website, hope it will be delivered 21:17:38 <psi> i have yet to figure out ipfs' contribution guide 21:17:45 <zzz> ok great. Anything else on 3) ? Sadie? 21:18:05 <zzz> thx villain, we're in the middle of a meeting, I'll look for it later 21:18:06 <psi> i'd love to get into IPFS but haven't figured out how. 21:18:25 <Zerolag> I'd love to get my hands on ZeroNet. See how well it goes over i2p. 21:18:28 <i2pr> [Slack/str4d] Psi, I can have a look this weekend at how they onboard 21:19:08 <psi> Zerolag: last time i checked adding i2p to zeronet should be pretty easy since they already have boilerplate for tor 21:19:11 <i2pr> [Slack/str4d] Zerolag, great! They are torrent-based, so would need modifying to our torrent spec 21:19:21 <psi> also, i2p.socket is getting there 21:19:33 <i2pr> [Slack/str4d] (to support clearnet and I2P torrents side by side) 21:19:54 <psi> zeronet uses mainline bittorrent? 21:20:01 <i2pr> [Slack/str4d] Not sure 21:20:17 <psi> i am pretty sure it doesn't but then again... 21:20:22 <i2pr> [Slack/str4d] (what impl they use) 21:20:36 <zzz> Anything else on 3) ? Sadie? 21:20:58 <i2pr> [Slack/str4d] psi, they user Bitcoin crypto and the bittorrent network 21:21:39 <i2pr> [Slack/str4d] I think Sadie might have double booked this meeting 21:21:49 <zzz> moving on then. anything else for the meeting? 21:22:21 <zzz> everybody ok with 9 PM again? I see echelon isn't here, maybe due to time change, maybe not 21:22:46 <psi> 9 pm works for me 21:22:46 <Zerolag> str4d alright, what is the i2p spec for torrent? 21:23:09 * zzz warms up the baffer 21:23:12 <i2pr> [Slack/str4d] Nothing else from me other than: pick a project and help them out! :-) 21:23:31 <i2pr> [Slack/str4d] 9pm is perfect for me 21:24:05 <Zerolag> I'll be here 9pm for sure 21:24:15 <i2pr> [Slack/str4d] Zerolag, see the I2P website (Docs -> Apps -> BitTorrent) 21:24:19 * zzz *baffffs* the meeting closed

Summer Dev roundup: APIs

Sat, 02 Jul 2016 00:00:00 +0000

Summer Dev is in full swing: we’ve been busy greasing wheels, sanding edges, and tidying the place up. Now it’s time for our first roundup, where we bring you up to speed on the progress we are making!

APIs month

Our goal for this month was to “blend in” - to make our APIs and libraries work within the existing infrastructure of various communities, so that application developers can work with I2P more efficiently, and users don’t need to worry about the details.

I2P on Maven Central

Mon, 13 Jun 2016 00:00:00 +0000

We’re nearly half-way into the APIs month of Summer Dev, and making great progress on a number of fronts. I’m happy to announce that the first of these is complete: the I2P client libraries are now available on Maven Central!

This should make it much simpler for Java developers to use I2P in their applications. Instead of needing to obtain the libraries from a current install, they can simply add I2P to their dependencies. Upgrading to new versions will similarly be much easier.

0.9.26 Release

Tue, 07 Jun 2016 00:00:00 +0000

I2P is now a proposed site on Stack Exchange! Please commit to using it so the beta phase can begin.

Update details

0.9.26 contains a major upgrade to our native crypto library, a new addressbook subscription protocol with signatures, and major improvements to the Debian/Ubuntu packaging.

Tue, 22 Mar 2016 00:00:00 +0000

Update details

To prevent the problems caused by the ancient commons-logging library, we have removed it. This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled. The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.

CCC Recap

Sat, 23 Jan 2016 00:00:00 +0000

Attending: Sadie, Colin, lazygravy, zzz, hottuna, kytv, cacapo, and eche|on.

Start

The project has had another successful year at CCC. We would like to thank the volunteers at 32C3 for all of their help in organizing this event and for being accommodating hosts for us. Many I2P contributors were able to attend this year’s Congress due to many of the generous donations from supporters like you to the project.

Just like previous years we were located in Noisy Square, located near the EFF’s table. This proved to be an ideal spot for us as our table was almost always busy with current and new users who were interested in I2P, many of whom we wouldn’t have otherwise had the ability to talk to.

I2P Dev Meeting - December 30, 2015

Wed, 30 Dec 2015 00:00:00 +0000

Quick recap

Present: cacapo, comraden1, dg, eche\|on, hottuna, kytv, lazygravy, psi, str4d, zzz

Meeting Log

09:49:14 <zzz> 0) Hi 09:49:14 <zzz> 1) Meeting structure and goals 09:49:14 <zzz> 2) PR 09:49:14 <zzz> 3) Project Management 09:49:14 <zzz> 0) Hi 09:49:16 <zzz> Hi 09:49:30 <zzz> 1) Meeting structure and goals 09:49:30 <zzz> First of all I apologize for the horrendous time for this meeting for our North American folks. 09:49:30 <zzz> This will be a little different from our usual meeting structure because it's mostly in-person here at CCC. 09:49:31 <zzz> We will attempt to relay the highlights to IRC. 09:49:33 <zzz> We will also be taking notes here. 09:49:35 <zzz> Now let me give a preamble for this meeting. 09:49:49 <zzz> As you all should know, Sadie was a huge part of the organization and success of I2PCon in Toronto. 09:49:49 <zzz> We all saw her talent and enthusiasm in Toronto, and obviously she wants to do more for I2P going forward. 09:49:49 <zzz> As we got to work with her before and during the Con, we learned that she has extensive Project Management and PR experience, 09:49:49 <zzz> both with Tor and out in the real world. 09:49:49 <zzz> What I asked her to do after the Con was to get to know our project better, to understand our current structure and processes, 09:49:52 <zzz> and to come back with recommendations on what we could do better and how she could help us. 09:50:04 <zzz> Since then, she's had several long conference calls with tuna, me, str4d, psi, and others, 09:50:04 <zzz> and reviewed our website, trac, and current processes. 09:50:04 <zzz> Also, psi has named her Assistant PR Director and she is tweeting on the @GetI2P account and helping to get the word out about I2P. 09:50:06 <zzz> She is now ready to give us some recommendations. 09:50:06 <zzz> While my original question to her was "how can you help us?", the answer coming back is 09:50:06 <zzz> more like "here's the things we need to fix so I can effectively help", 09:50:08 <zzz> followed by the actual things she could do for us, or more precisely how we can all work together more effectively. 09:50:19 <zzz> What I'd like to do today is to hear her recommendations and discuss them each briefly. 09:50:19 <zzz> Many of these topics tend to spark long discussion and I'd like to contain that so we aren't here all day. 09:50:19 <zzz> For each recommendation, I'd like to get a commitment from one of you to follow up. 09:50:19 <zzz> If the recommendation is uncontroversial and we have consensus, that commitment would be to implement it. 09:50:20 <zzz> If it needs further research or we don't agree, that commitment would be to review our options and 09:50:21 <zzz> come up with a plan, or a counter proposal, or a list of options to be discussed at a future meeting. 09:50:23 <zzz> These commitments and due dates will be noted and tracked. 09:50:25 <zzz> I don't want to get bogged down on any one thing so I'll be looking for volunteers to follow up most things. 09:50:42 <zzz> I want to emphasize that I asked Sadie to do this and give us her opinion based on her previous experience. 09:50:42 <zzz> We may not agree but we should listen and carefully consider her recommendations. 09:50:42 <zzz> I2P is its own little snowflake and not everything may be appropriate for us, 09:50:42 <zzz> but she's gotten to know us pretty well this year, so let's hear what she's got. 09:50:43 <zzz> We will of course be able to take suggestions from others but I have a feeling that Sadie's got a lot of things covered already. 09:51:24 <zzz> We're going to first talk about PR and then Project Management. 09:51:24 <zzz> Both are very large topics and there will be overlap. But let's try to keep them as separated as we can. 09:51:54 <zzz> *** end of paste for topic 1), we will start in with 2) in a few minutes. thanks *** 09:58:39 <hottuna> str4d: heya we should have a talk about the DH stuff we're using 09:59:30 <str4d> hottuna, you referring to the NTCP and SSU handshakes? 09:59:55 <hottuna> i guess wherever DH is used 10:00:39 <hottuna> ok. lets talk about it after the meeting 10:00:47 <str4d> Sure 10:00:57 <str4d> According to `http://trac.i2p2.i2p/wiki/Crypto/CurrentSpecs` it's just NTCP and SSU 10:01:21 <hottuna> zzz will be reading the long note above to us now 10:01:48 <str4d> (I still need to update that page ahead of my talk) 10:04:10 <psi> i think i'm here 10:06:33 <lazygravy> psi: yes, zzz posted a long message just before you joined. talking IRL right now 10:07:57 <hottuna> So what we're looking to do is to get commitments from people to fix a bunch of different topics 10:08:25 <hottuna> Some of the stuff we're going to cover will be controversial and some not 10:08:47 <hottuna> the non-controversial topics we're hoping to just assign a to a person and have that handled 10:08:56 <hottuna> Onto Sadie and PR 10:09:16 <hottuna> gravy and sadie have been writing blogpost 10:09:29 <hottuna> and are looking for more content 10:10:21 <hottuna> a lot of content is lost in the commit messages 10:10:38 <hottuna> where the author of the commit does not really record the importance of the commit 10:11:24 <str4d> Rather than scanning commit messages, the best/easiest place to look is history.txt 10:11:30 <hottuna> ideally we would like to publish a blog post at least every 2 months to keep some sense of momentum is kept 10:12:08 <str4d> That still doesn't give an indication of importance, but is contextually easier to handle and sifts out the commit chaff that doesn't make it into history.txt 10:13:04 <lazygravy> str4d: the point is that there is so many cool things happening, and no way to find out without following i2p closely. it should be easier for people to see the cool stuff 10:13:47 <str4d> Perhaps what might help (this would be rather radical) could be to restructure history.txt to organize items by importance (major/minor/bugfix), more like a changelog (or have a parallel changelog file) 10:14:13 <str4d> since as-is, the history file is really just an easier-to-parse commit log 10:14:30 <str4d> That said, it *is* convenient, so maybe parallel info would be better (if harder to maintain) 10:14:38 * str4d stops getting bogged down in specifics 10:14:41 <str4d> :P 10:14:59 <hottuna> lazygravy could act as an editor and sort of delegate the responsibility of writing content when that is appropriate 10:15:14 <str4d> Certainly making it easier to know what is going on is a plus, and I think some of the higher-level organization topics will help this 10:15:33 <str4d> (ie. a blog post writer can look there for the high-level overview instead of the commit log) 10:15:56 <psi> sounds rather similar to pair programming 10:16:10 <hottuna> next topic within PR 10:16:29 <hottuna> regarding having a reseed campaign and attracting new developers 10:16:46 <psi> (or more like married couple programming, the programmer and the programmer's wife) 10:17:11 <lazygravy> str4d: i.e. WTF encrypted lease sets are, or a cool highlight of kytv's debian repo 10:17:15 <hottuna> we would like to involve torontocrypto to attract more reseed host s 10:17:23 <lazygravy> s/i.e./e.g./ 10:17:24 <iRelay> lazygravy meant: str4d: e.g. WTF encrypted lease sets are, or a cool highlight of kytv's debian repo 10:18:25 <hottuna> We would like to generate a content package containing all info you would need to set up a reseed host should be available in one place 10:19:14 <hottuna> we need to articulate why reseeds are needed and important 10:19:18 <str4d> Mmm 10:19:42 <str4d> It could even be made as simple as "sudo apt-get i2p-reseed" 10:20:22 <lazygravy> str4d++ 10:20:23 <kytv> I was thinking of making docker images so it can be completely plug-n-play:ed 10:20:47 <psi> the go reseed was excessively easy to set up and use 10:20:56 <hottuna> hottuna/I volunteered to write a few paragraphs about why reseeds are needed and what they do 10:21:07 <hottuna> kytv: that would be amazing 10:21:23 <str4d> kytv++ 10:21:35 <str4d> Drop-and-go is the ideal 10:22:00 <str4d> Kinda like what was mentioned in one of the Tor talks yesterday, about how people could in future get a LetsEncrypt cert that comes with a free .onion 10:22:16 <str4d> (ie. the letsencrypt script sets up the Tor HS for the user) 10:22:38 <kytv> mdrollete's i2p-tools is available as a docker image, so maybe we (=I) could just polish up my I2P docker image (not yet advertised) so one could do it all by copy'n'pasting one command line and reseeding would "just work" 10:22:41 <hottuna> about developed onboarding, making the source code more accessible 10:22:42 <str4d> (that in itself would be super neat for I2P, but slightly different from what we need here) 10:22:55 <comraden1> kytv: docker for sure 10:23:01 <hottuna> str4d: could I convince you to add some links to the source code from geti2p.net? 10:23:04 <str4d> If reseeds are an appliance, it also makes it much easier to keep honest reseeds in sync 10:23:17 <str4d> hottuna, where? 10:23:18 <lazygravy> thought: we should get rid of the note from 0.7.6 on the download page 10:23:33 <kytv> (I'm more of an lxc guy but I'm learning docker so whatevs ) 10:23:45 <kytv> ja 10:23:50 <lazygravy> kytv: docker seems "so hot" right now, so it might be best 10:23:54 <hottuna> wherever it makes sense 10:24:08 <str4d> I believe there is at least one link to kytv's ViewMTN, but that's inside I2P 10:24:11 <hottuna> but the idea is to make it easier to get a quick look at the soruce code 10:24:13 <kytv> Move all docs for ancient stuff to /attic or smth related 10:24:19 <hottuna> to attract developers 10:24:33 <hottuna> str4d outside i2p and ideally from geti2p.net is what we would want 10:24:36 <str4d> I could add links to the new devs page to the Github page, but they would need to be clearly marked as read-only 10:24:50 <psi> if you really want to attract devs we should make the github alive more 10:24:52 <hottuna> yeah. 10:25:57 <str4d> Is the new dev page where you want the links? 10:25:57 <hottuna> that sounds like a simple straight forward step to take 10:25:57 <hottuna> just add a read-only link to github 10:25:57 <str4d> hottuna, which? Links, or github alive more? 10:25:57 <hottuna> would be an improvement 10:25:57 <str4d> ahk 10:26:05 <hottuna> str4d: can I write your name next to that? 10:26:24 <hottuna> that item that is 10:26:38 <str4d> Sure. I assume all of these will get issues created on Trac 10:26:51 <hottuna> not sure if they will. 10:26:57 <hottuna> will ask zzz 10:27:09 <str4d> Well yeah, probably not worth it for the smaller tasks 10:27:20 <str4d> As long as I get the list sometime :P 10:27:26 <hottuna> ok 10:27:36 <hottuna> i think zzz will do a zzz.i2p writeup 10:28:22 <kytv> it'll almost certainly go to zzz.i2p but perhaps also as tickets on Trac 10:28:41 <str4d> k 10:28:50 * str4d pulls up todo list to start adding items 10:32:43 <hottuna> we're talking about which usecasdes we should promote i2p for 10:33:13 <hottuna> and the consesus seems to be that we should promote usecases which we are good at. like bote 10:33:20 <str4d> Mmm 10:33:29 <str4d> We definitely need to push the peer-to-peer aspect 10:33:36 <hottuna> like torrents to potintiall 10:33:38 <hottuna> y 10:33:57 <hottuna> we would like to highlight these good uses on the main page 10:34:12 <hottuna> *what we would like to highlight 10:34:20 <str4d> That's something I2P should have a fundamental advantage with, due to the packet-switched nature and tunnel-level symmetry 10:34:33 <hottuna> yes. and there are other things we are good at 10:34:39 <str4d> And particularly apps that themselves inherently encourage contribution 10:34:41 <hottuna> and those things we should promote 10:35:05 <hottuna> and in the meantime we can keep on working on the things that we are not quite as good at 10:35:09 <str4d> (because I2P's need for contribution can then piggyback on the app's) 10:35:43 <hottuna> lazygravy, str4d, cacapo: could you work through the 3 best usecases for i2p 10:36:01 <hottuna> so that we then can present them properly on the frontpage 10:36:18 <str4d> Sure 10:37:03 <cacapo> yepp 10:37:08 <hottuna> when can you guys come back with something (recommendations or webstie changes)? 10:37:43 <hottuna> is a deadline for end of january ok? 10:37:55 <cacapo> ok 10:38:01 <hottuna> realting to PR: i2p.net becomes available soon 10:38:03 <str4d> Fine with me 10:39:04 <eche|on> 16.4.2016 it is for i2p,net 10:39:11 <str4d> I can say right now that if we are meaning "things that work well right now", you're really looking only at high-latency email (bote) and torrents. Soon we can add distributed datastorage too (once Tahoe gets native I2P client support) 10:39:24 * str4d is looking forward to i2p.net being recovered 10:39:33 <eche|on> tahoe will only be useable with parallel up/download 10:40:08 <str4d> I think it would be ideal to dovetail it with my proposal for dev services on i2p.i2p, have them parallel available in- and out-of-net 10:40:12 <hottuna> cacapo mentions i2p does not communicate a narrative about the project very well. or at all. 10:40:29 <lazygravy> str4d: tahoe has it's own UI problems... :/ (tho I adore it) 10:40:29 <hottuna> unlike to which has a lot of history and contextual history to it 10:41:03 <str4d> hottuna, what narrative does he mean? 10:41:09 <hottuna> relating to jake/snowden&/etc 10:41:42 <str4d> ah, narrative relating I2P history to world context? 10:41:43 <hottuna> comraden1: volunteers to do a writeup of the history of i2p 10:41:52 <str4d> (like the Tor HS talk did?) 10:42:05 <eche|on> history: zzz talk on i2pcon, my talk on 32c3 10:42:06 <hottuna> (didnt see that) 10:42:33 <str4d> also my talk at I2PCon had a bit 10:42:37 <hottuna> zzz, comraden1, lazygravy volunteered to do the actual writeup 10:42:41 <hottuna> psi: around? 10:42:53 <psi> yes 10:42:57 <hottuna> str4d: and so did Lance James' bit 10:43:34 <str4d> lazygravy, Tahoe UX should improve greatly once magic folders is released. UI-wise, still has work to do, but not as much as us :P 10:43:52 <hottuna> str4d, sadie, could the both of you help eachother out to do promo for the RWC talk? 10:44:03 <hottuna> ast call for PR related topics 10:44:06 <hottuna> Lest* 10:44:08 <hottuna> last* 10:44:49 <hottuna> alright, i'll take that as silence 10:44:50 <str4d> hottuna, yep, I'll keep in touch with Sadie 10:44:56 * str4d still has to prepare that talk :/ 10:45:04 <hottuna> Onto the next topic. PROJECT MANAGEMENT 10:45:34 <comraden1> str4d: also "history of how i2p started". I'm thinking of navy researching onion routing -> second generation onion router -> tor 10:46:40 <str4d> comraden1, mmm, you'll probably find a lot of that in the early I2P meeting logs on the website 10:47:15 <str4d> If you do go rooting around in there, feel free to write quick summaries of the meetings that I can add to them :P 10:48:11 <comraden1> str4d: zzz mentioned that he has a lot of it in his head and wanted to write a rough draft. I'm going to edit and make sure it is perfect before we release it 10:48:45 <str4d> +1 10:49:19 <dg> I remember speaking about it with zzz ages ago; if he has logs of that, it might be helpful 10:49:22 <hottuna> we're talking about what the actual goals of the project are 10:49:54 <hottuna> and that they are important to have written down somewhere in order to be able to do meaningful project management 10:50:29 <str4d> Would make for a good about page 10:51:16 <str4d> I've wanted to merge the various intro pages, but we could actually leverage them separately 10:51:36 <str4d> Turn https://geti2p.net/en/about/intro into a brief overview of I2P, both the network and the project 10:51:38 <iRelay> Title: Intro - I2P (at geti2p.net) 10:51:59 <str4d> Then make https://geti2p.net/docs/how/intro the *actual* "how does I2P work" page 10:52:00 <iRelay> Title: A Gentle Introduction to How I2P Works - I2P (at geti2p.net) 10:52:10 <str4d> Kinda sorta what they appear to be now, but properly split 10:53:12 <dg> hottuna: Where can I find the blogposts? 10:53:22 <dg> hottuna: I can only see one (`http://i2p-projekt.i2p/en/blog/2015/11/15/Community-Outreach)` 10:53:25 <iRelay> Title: Community Outreach - Blog - I2P (at i2p-projekt.i2p) 10:54:38 <lazygravy> dg: they don't exist aside from that 10:54:55 <lazygravy> and that was mostly a POC IMO. Next one should be published on 10Jan2016 on CCC 10:58:32 <hottuna> we're talking about whether we want to be managed 10:58:46 <hottuna> dg, str4d, psi: do you have any thoughts about having your work managed? 10:59:11 <psi> by who and how much management? 10:59:17 <hottuna> by sadie 10:59:26 <dg> open to it 10:59:42 <hottuna> and having it be relaxed as in deadlines. but not enforced deadlines 10:59:46 <hottuna> things are done when they are done 11:00:11 <hottuna> but mentally attaching a deadline to them might be a helpful tool 11:00:11 <dg> done when they're done but a bit of pushing/motivation 11:00:40 <psi> no thoughts until i eat breakfast 11:00:47 <hottuna> or at the very least knowing that someone else knows that a given task is on your pile 11:01:15 <hottuna> re project management: we'd like to get weekly/bi-weekly meetings up and runnning again 11:01:25 <hottuna> zzz has the goal of starting them up in february agin 11:01:27 <hottuna> again* 11:01:36 <hottuna> and then gradually handing them off to sadie 11:01:48 <hottuna> for that to happen sadie needs got on irc 11:01:56 <str4d> I'm good for it. I do tend to work better when I have someone(s) to bounce ideas off 11:03:23 <hottuna> zzz just committed to having a single roadmap written up by the end of february 11:03:23 <hottuna> splendid. 11:03:23 <hottuna> the consensus seems to be that being managed lightly is probably a good thing. 11:03:23 <hottuna> but anything heavy-handed would just turn this into work 11:03:23 <str4d> Sounds good. We can always adjust the level later once we have some experience with it. 11:03:23 * dg nods 11:03:23 <hottuna> *roadmap will be for end of jan, not feb 11:03:23 <hottuna> str4d: agreed 11:04:35 <str4d> FYI zzz, sadie and I will be meeting up at the beginning of March, would be good to keep that in mind re: things we can work on/discuss then. 11:05:52 <hottuna> re: trac tickets, sadie is volunteering to keep an eye on it and relay tickets to the right individual 11:06:05 <dg> Being able to observe our mechanics like trac/zzz.i2p/irc is important for Sadie to fully understand how we work anyway 11:06:16 <dg> Has she been able to do that w/o IRC access? 11:07:04 <hottuna> str4d: would you bi willing to help sadie out in that endeavour? 11:07:40 <str4d> I've had on my todo list for a while a weekly "look over new tickets" item, that I keep postponing because too much on 11:08:06 <str4d> But from next year, I'll endeavour to help sadie with that :) 11:08:49 <str4d> You may have noticed there's an "open" status now for tickets. I added that so we can differentiate between new tickets and ones we've seen but haven't had an opinion on necessarily 11:08:53 <hottuna> Last call for PROJECT MANAGEMENT topics 11:09:10 <dg> hottuna: see above 11:09:25 <str4d> My goal would be to have as few "new" tickets as possible, ie. moving them either to a relevant person/status, or "open" to at least acknowledge them as a valid ticket. 11:09:36 <hottuna> Last call for OTHER topics 11:09:48 <hottuna> dg: getting sadie on trac is key. and a requirement 11:10:00 <hottuna> I mean on IRC 11:10:17 <dg> okay 11:10:23 <str4d> I've had an IRC bouncer account for her for a while now 11:10:42 <hottuna> str4d: could we ask you to write up few items about what you learned about vulnerability response the the conf? 11:10:48 <str4d> All she needs is help getting her side connected, and she can then keep logs etc. without needing to stay connected all the time 11:11:40 <str4d> hottuna, you mean from talking to k8em0 at Kiwicon? 11:11:47 <hottuna> mhm 11:11:47 <dg> Also help with browser config/privoxy? 11:12:13 <str4d> I didn't learn a lot more than I already kinda knew, other than hearing in advance about the bug bounty program that Tor just announced 11:12:26 <zzz> we're proposing that we defer the VRP discussion to january 11:12:36 <hottuna> str4d: would making a tiny writeup make sense? 11:12:40 <str4d> k8em0 did say she was very impressed with our VRP ticket 11:12:45 <hottuna> like a zzz.i2p post? 11:12:55 <hottuna> or was it all kind of useless? 11:13:15 <str4d> Not useless, more confirming that our VRP ticket is on the right track 11:13:31 * zzz ******BAFFFFS***** the meeting closed, thanks everybody

0.9.23 Release

Thu, 19 Nov 2015 00:00:00 +0000

Hello I2P! This is the first release signed by me (str4d), after 49 releases signed by zzz. This is an important test of our redundancy for all things, including people.

Housekeeping

My signing key has been in router updates for over two years (since 0.9.9), so if you are on a recent version of I2P this update should be just as easy as every other update. However, if you are running an older version than 0.9.9, you will first need to manually update to a recent version. Once you have manually updated, your router will then find and download the 0.9.23 update as usual.

Community Outreach

Sun, 15 Nov 2015 00:00:00 +0000

A Call for Feedback

Let’s face it – our console needs improvement. Our site could use an update as well. We are looking for feedback on how to improve the usability of I2P for new and existing users!

I2P Dev Meeting - November 03, 2015

Tue, 03 Nov 2015 00:00:00 +0000

Quick recap

Present: abyss, amknesia, anonimal, dogedDEV, eche|on, kytv, Lady3Jane, lbt, obscuratus, psi, sadie_i2p, str4d, trolly, xmz, Z0rg1nc, zab@kyirc, zzz

Meeting Log

20:00:17 <zzz> 0) Hi 20:00:17 <zzz> 1) `http://dogecoindark.i2p/` console home page request, reconsideration from July 14 meeting `http://i2p-projekt.i2p/en/meetings/238` -- orig. request: `http://zzz.i2p/topics/236?page=2#p9999` -- result: `http://zzz.i2p/topics/236?page=3#p10078` -- possibly replaced by `http://doged.i2p/` 20:00:17 <zzz> 2) `http://exchanged.i2p/` console home page request: `http://zzz.i2p/topics/236?page=3#p10391` 20:00:17 <zzz> 3) `http://i2pwiki.i2p/` console home page request: `http://zzz.i2p/topics/236?page=3#p10437` 20:00:18 <zzz> 4) `http://lenta.i2p/` console home page request: `http://zzz.i2p/topics/236?page=3#p10439` 20:00:21 <zzz> 5) CCC preparation update from Oct. 6 meeting: `http://i2p-projekt.i2p/en/meetings/239` 20:00:22 <zzz> 6) forum.i2p replacement proposal (hottuna, dg) - followup from Oct. 6 meeting: `http://i2p-projekt.i2p/en/meetings/239` 20:00:25 <zzz> Note that several early comments on items 1-4 are on the agenda page `http://zzz.i2p/topics/1970` 20:00:27 <zzz> 0) Hi 20:00:42 <zzz> welcome to the 240th meeting of this great project, spanning 13 1/2 years 20:01:00 <zab@kyirc> hi 20:01:10 <anonimal> Hello 20:01:24 <iRelay> Title: zzz.i2p: How to get my Eepsite added to the Router Console home page (at zzz.i2p) 20:01:27 <zzz> for the new folks, this meeting is mainly for group decision-making, let's target 10 minutes or less for each agenda item 20:01:43 <iRelay> Title: zzz.i2p: How to get my Eepsite added to the Router Console home page (at zzz.i2p) 20:01:51 <zzz> and as a reminder, anybody else can schedule a meeting here at any time for any reason 20:01:53 <iRelay> Title: I2PWiki (at i2pwiki.i2p) 20:02:16 <zzz> 1) `http://dogecoindark.i2p/` console home page request, reconsideration from July 14 meeting `http://i2p-projekt.i2p/en/meetings/238` -- orig. request: `http://zzz.i2p/topics/236?page=2#p9999` -- result: `http://zzz.i2p/topics/236?page=3#p10078` -- possibly replaced by `http://doged.i2p/` 20:02:26 <iRelay> Title: zzz.i2p: How to get my Eepsite added to the Router Console home page (at zzz.i2p) 20:02:35 <iRelay> Title: I2P Development Meeting 239 - I2P (at i2p-projekt.i2p) 20:02:39 <zzz> is the dogecoindark.i2p operator here? 20:02:39 <iRelay> Title: I2P Development Meeting 239 - I2P (at i2p-projekt.i2p) 20:02:43 <iRelay> Title: zzz.i2p: Meeting Tues. Nov. 3, 8 PM UTC (at zzz.i2p) 20:03:17 <iRelay> Title: I2P Development Meeting 238 - I2P (at i2p-projekt.i2p) 20:04:34 <zzz> I saw a lot of negative comments about dogecoindark.i2p/doged.i2p on the meeting page. Anybody else wish to comment pro or con? 20:05:03 <psi> i think i2p should start taking a neutral stance towards cryptocoins in general 20:05:20 <zzz> what would you say our stance is now? 20:05:33 <psi> neutral 20:06:03 <zzz> so what do you mean 'start' taking a neutral stance? 20:06:06 <dogedDEV> yeah 20:06:11 <dogedDEV> im here 20:06:30 <dogedDEV> what was the negative comments? 20:06:32 <dogedDEV> ive removed all scripts, 20:06:35 <psi> not endorsing some coins over others 20:06:38 <dogedDEV> its just graphics and html now 20:06:54 <zzz> dogedDEV, please review them quickly, link is above 20:07:00 <dogedDEV> and ive moved alot of our source code over to the i2p based git repo 20:07:02 <anonimal> I spoke my peace in `http://zzz.i2p/topics/1970-meeting-tues-nov-3-8-pm-utc` 20:07:02 <str4d> hi 20:07:06 <iRelay> Title: zzz.i2p: Meeting Tues. Nov. 3, 8 PM UTC (at zzz.i2p) 20:07:51 <zzz> dogedDEV, please explain the name change, and respond to the objections about all the images. As of now you don't have any support at all, so you have about 2 minutes to convince us otherwise 20:08:34 <dogedDEV> well, ive been non stop building us out more on i2p 20:08:39 <dogedDEV> i built an i2p electrum server 20:08:49 <dogedDEV> i revamped the entire site after the complains it had widgets 20:09:00 <dogedDEV> which is why the name changed to i2p. i scrapped the old site and started fresh. 20:09:11 <dogedDEV> ive made quite a few tutorials to help users get on i2p 20:09:29 <dogedDEV> and doged.i2p is its permanent home 20:11:15 <dogedDEV> id like to think that if people increase their bandwidth the graphics will load faster. perhaps i will add a text only version in the near future to satisfy people with low bandwidths needs 20:11:15 <dogedDEV> i really enjoy i2p and have spread the word to many privacy concerned people globally about it, and its benefits 20:11:15 <zzz> but all of i2p is 'low bandwidth'. The problem is on your end, not your users 20:11:15 <dogedDEV> the images seem to load fast for me and other users who have tweaked their bandwidth 20:11:15 <zzz> not for me 20:11:15 <dogedDEV> i feel our site there loads just as fast as our onion site. 20:11:19 <dogedDEV> i have been focusing less on tor as of late and more on i2p. 20:11:21 <zzz> or the others who commented 20:11:27 <anonimal> Nor me, and I'm loading it again and waiting. 20:11:45 <anonimal> And clearnet sources are still being pulled. It's like nothing changed since we posted in that thread. 20:11:50 <dogedDEV> i can change the resolution on them i suppose 20:12:00 <zzz> no site in 2015 puts everything behind 200 images on the home page 20:12:02 <dogedDEV> whgere is it pulling from clearnet? 20:12:13 <dogedDEV> it shouldnt be communicating with any clearnet 20:12:17 <abyss> hello 20:12:24 <kytv> the index page 20:12:47 <zzz> right now i don't see it as 'broadly useful to the i2p community', which is our first critereon 20:12:56 <zzz> I see where you're headed but I don't think you're there yet 20:13:03 <dogedDEV> how is a crypto currency focused on privacy not useful? 20:13:06 <kytv> it's clearly better than it was. 20:13:08 <str4d> I'm loading the site right now 20:13:15 <zzz> is anybody here in favor of this request, please speak up now 20:13:23 <dogedDEV> i just loaded it, half the graphics have already loaded on my end 20:13:39 <str4d> Site took 13s to load HTML (but most of that was getting the LS) 20:13:44 <dogedDEV> and im not connecting to it locally or anything 20:13:48 <abyss> i works fine for me 20:13:50 <str4d> I've never loaded the site at its new addr yet 20:14:01 <str4d> Fastest image was 17s 20:14:10 <str4d> Slowest so far is 1min44s 20:14:25 <dogedDEV> i can absolutely lower the resolution on the graphics 20:14:34 <zzz> last time I tried I gave up after 10 minutes 20:14:42 <abyss> dogedev has been working hard on promoting privacy and pushing the clearnet cryptocoin community towards i2p 20:14:44 <str4d> 3min in, still not loaded 20:14:51 <anonimal> ^ same here, it's still loading. 20:14:53 <kytv> it's never loaded completely on my end 20:14:56 <eche|on> ok, started to load 1 min ago, lets wait 20:14:57 <str4d> dogedDEV, are you using the same I2P router for HTTP tunnel when testing? 20:15:14 <dogedDEV> no 20:15:14 <str4d> because if so, your connection won't be going through I2P 20:15:29 <zzz> we aren't doubting dogedDEV's commitment to i2p. we are evaluating the appropriateness of adding the site to the home page only 20:15:46 <dogedDEV> i suppose i can lower the res on the images, thereby decreasing image file sizes. 20:16:01 <str4d> dogedDEV, okay, now that some of the upper half of the site has loaded (dev resources etc.), I can see the problem 20:16:10 <dogedDEV> i just wanted it to look nice, but i suppose for the average user it would load slow. and performance is just as importance. 20:16:15 <str4d> You shouldn't need to use images for *ALL* of your content 20:16:22 <dogedDEV> important* 20:16:30 <anonimal> I appreciate the artistic merit, but why can't this be an opportunity for innovation? 20:16:32 <zzz> I'm proposing we reject this request. He can always resubmit some time in the future. Any objections? 20:16:42 <str4d> Not only does it make the site take ages to load, but it also makes the site unsearchable 20:16:52 <dogedDEV> there is innovation in the coin, even with i2p 20:16:57 <dogedDEV> any other i2p electrum servers out there? 20:17:34 <zab@kyirc> I'm all for getting into financial stuff but this is way too slow 20:18:01 <anonimal> It seems that the only person who cares about the website's vision is the author. 20:18:01 <dogedDEV> i working on an android app now that connects to our i2p electrum 20:18:01 <str4d> If what you like is the font, you can load that font via CSS 20:18:01 <zzz> we aren't doubting the innovation, or your overall project. Only the website. 20:18:01 <anonimal> I'm speaking solely on the site, this meeting is about the *site*. 20:18:01 <zzz> last call for discussion on 1) 20:18:01 <str4d> Most of what I can see on the website could be done in CSS, which would drastically cut down the required images and drastically improve site load times. 20:18:01 <dogedDEV> no, i did agree with the website vision, if the graphics are too large, i can decrease the size and even make a text only link, that just uses css 20:18:01 <abyss> anonimal, i like it 20:18:02 <anonimal> I agree with str4d 20:18:29 <kytv> no objections to rejecting. It's unbearably slow when it loads. 20:18:43 <dogedDEV> whens the next meeting? 20:18:43 <kytv> and now isn't one of those times... 20:18:47 <kytv> $ http_proxy=`http://127.0.0.1:4444` curl --silent `http://doged.i2p/` 20:18:50 <kytv> <html><head><title>408 Request Timeout</title></head> 20:18:51 <kytv> <body><h2>408 Request timeout</h2> 20:18:57 <zzz> and it isn't just the site itself - it's also the recent name change (which perhaps should restart the clock completely) and psi's objection to promoting _any_ coin 20:19:09 <iRelay> Title: DogecoinDark.i2p Official Site (at doged.i2p) 20:19:13 <zzz> ok, that's it for 1) 20:19:24 <str4d> dogedDEV, now that a bit more of the site has loaded, it does look very pretty. But I think that nearly everything down to at least the FB/twitter/etc. links could be done via CSS with a few images for the actual images. 20:19:24 <zzz> 2) `http://exchanged.i2p/` console home page request: `http://zzz.i2p/topics/236?page=3#p10391` 20:19:29 <dogedDEV> so since psi's coin promotion affects the judging, is anoncoin being removed? 20:19:38 <dogedDEV> because that would be silly 20:19:41 <iRelay> Title: zzz.i2p: How to get my Eepsite added to the Router Console home page (at zzz.i2p) 20:19:46 <str4d> So I'm -1 on 1) for now. 20:19:47 <zzz> is the exchanged.i2p operator here? 20:20:06 <abyss> zzz, hey i am here 20:20:31 <zzz> ok abyss please tell us about your site, and respond to any objections raised on the zzz.i2p thread 20:20:43 <psi> anoncoin is dead 20:20:47 <psi> (imo) 20:20:51 <dogedDEV> thats sad =\ 20:21:00 <dogedDEV> anywho, moving on. ill resubmit. 20:21:00 <abyss> psi, its not dead 20:21:26 <dogedDEV> im in favor of exchanged.i2p, if my opinion matters. 20:21:31 <abyss> ok zzz the main concern is that i am not reliable to be trusted with other peoples money 20:21:47 <zzz> tell us about the site first please 20:21:50 <dogedDEV> site loads quick, trades are quick. alot of doged users have traded there and without issue. 20:21:58 <abyss> ok 20:22:26 <abyss> Exchanged.i2p is a site where users can trade cryptocurrncies such as bitcoin litecoin anoncoin dogecoindark ect anonymously 20:22:47 <abyss> we have been operating since july 1 20:23:00 <abyss> alpha testing started june1 20:23:49 <abyss> also im been voched for by the anoncoin and dogecoindark development team 20:24:19 <abyss> anoncoin dev is not here currently but here is the link https://www.reddit.com/r/CryptoCurrency/comments/3cxk7k/exchangedi2p_anonymous_exchange/ 20:24:23 <iRelay> Title: Exchanged.i2p Anonymous Exchange : CryptoCurrency (at www.reddit.com) 20:24:24 <zzz> there seems to be two objections, that the site is too rough/early, and that we shouldn't be endorsing anything financial 20:25:17 <zzz> here's what I said in the request thread: We haven't had a request for an exchange before. While I don't feel that we are qualified to assess any market's legitimacy and stability, I think we should try, as there may be some sort of implied blessing by putting a link in the console. 20:25:28 <dogedDEV> by placing an icon on a menu, i dont see that as endorsing, personally. unless you also encouraged its use over other people applying for the same thing he is. 20:25:49 <zab@kyirc> the roughness makes load times fast and doesn't affect the usefulness 20:26:12 <zab@kyirc> for any trader fast response time is much more important than prettyness 20:26:13 <dogedDEV> i dig the ascii menus. reminds me of back in the day. 20:26:19 <abyss> i tried to create a design that would maximise usability 20:26:19 <dogedDEV> i think alot of users feel the same way. 20:26:19 <zzz> anybody have any opinion on this? Is it an endorsement? Should we attempt to verify? Or should we not put markets or trading platforms on the home page at all? 20:26:34 <dogedDEV> right, response time and the admin being around as long as he has, i think its a go. 20:27:00 <str4d> From a usability PoV I think it seems good (but have not made any trades) 20:27:15 <kytv> I'm more or less indifferent. My objection to #1 is the extreme slowness in loading. This one, at least, is *very* quick. 20:27:17 <dogedDEV> he even recently added an api at the request of an analytical site 20:27:17 <anonimal> Yes, since we have the power to pick and choose, every link becomes an implied endorsement. 20:27:24 <zab@kyirc> I'm definitely in favor of markets and exchanges and anything financial over i2p in general. It adds a dimension to the broad usability of i2p which helps attract people 20:27:27 <str4d> I have suggested there be a light theme too though, because the dark contrast is hard for some users 20:27:33 <zzz> has anybody here used this site for any trades, please speak up 20:27:37 <lbt> User-opinion here: I think that information should be easily findable, but also think it shouldn't be part of a router :o Maybe a a link to thematically sorted list of active domains or something on the router-console? 20:27:45 <str4d> (particularly blue on black, although the shade of blue is a bit better than last time) 20:28:10 <zab@kyirc> str4d: 80's mainframe colors FTW ;-) 20:28:27 <zzz> let's not get into detailed color advice here. Big picture, decision time. Yay or nay and why please. 20:28:38 <amknesia> Is there already a statement on the router homepage stating 'links below are not an endorsement but simply sites that have met the minimum guidelines to be posted on the homepage'? 20:29:03 <dogedDEV> yay - site loads quick, ive used it and it works as expected. abyss is always around and easy to get a hold of. 20:29:08 <dogedDEV> amknesia, thats a good idea. 20:29:35 <dogedDEV> i2p developers do not condone/endorse the sites listed in the console. 20:29:44 <zzz> Is it broadly useful to the i2p community/ 20:29:56 <zzz> explicit or not, it's an implied endorsement 20:30:02 <zab@kyirc> absollutely 20:30:20 <str4d> Broadly useful? IMHO yes. 20:30:31 <dogedDEV> as long as fiat doesnt get involved i think it makes a great addition. 20:30:39 <anonimal> Yes, broadly useful, and the site has improved somewhat in usability. 20:30:48 <zzz> has _anybody_ here actually used it for a trade? 20:30:48 <Lady3Jane> The endorsement is implicit, especially to newcomers and especially because a lot of links are indeed official 20:30:58 <anonimal> No. 20:31:07 <zab@kyirc> even if fiat is involved it's still a great addition 20:31:07 <dogedDEV> i have traded on it. 20:31:27 <anonimal>>The endorsement is implicit 20:31:28 <amknesia> zzz: I have, only a few satoshis worth of trade though. 20:31:28 <dogedDEV> small amounts, but over time, and its always worked 20:31:30 <str4d> But with fiat involved, it is harder for the site itself to be justifiably anonymous 20:31:33 <anonimal> Yes, and disclaimer would be useless. 20:31:33 <Lady3Jane> pilgrim-wu (who isn't here) is deeply involved in cryptoexchanges (even manages one based in W. China). He's used exchanged.i2p before. He loves it, zzz 20:32:25 <abyss> for those that are intrested i can give you a few doged's to trade with 20:32:25 <zzz> ok let's wrap this up. The consensus isn't clear to me, so please enter +1 for yes and -1 for no 20:32:32 <dogedDEV> +1 20:32:35 <str4d> From a "risk" level, if the site is only exchanging cryptocoins, then it is subject to the market forces of other exchanges wrt value 20:32:42 <abyss> that way you can test it out for yourself :) 20:32:45 <zab@kyirc> +1 20:33:33 <trolly> +1 20:33:33 <Lady3Jane> (I'm not sure if I have suffrage here, but...) +1 20:33:48 <anonimal> -1: No sex, drugs, money, or rock&roll in router console. 20:33:56 <kytv> = "neutral / not negative" 20:34:30 <abyss> +1 if my vote counts 20:34:33 <psi> +1 no drugs sex money rock/roll in router console 20:34:38 <trolly> no rock&roll?? OMG anonimal!! 20:34:41 <obscuratus> -1: Good site, but I agree it's an endorsement. 20:34:49 <psi> rather, -1 20:34:57 <abyss> psi, :) 20:34:57 <trolly> +1 drugs, sexs and rock&roll averywhere 20:35:01 <abyss> :( 20:35:09 <amknesia> Question: What about having a links page/site instead that isn't the homepage but is linked from it. This would avoid the homepage 'implied endorsement' which also making it easy for newbies to find sites they might be interested in. Are any of the current homepage sites set up to provide that? 20:35:21 <obscuratus> amknesia: +1 20:35:28 <lbt> amknesia: +1 20:35:29 <Lady3Jane> From a PR perspective, anonimal, I agree on the sex and drugs. We don't want the router to become the i2p equivalent of the hidden wiki. But why are currency exchanges inherently negative? 20:35:47 <Lady3Jane> router console* 20:35:56 <anonimal> I would lean towards amknesia's idea. 20:36:01 <dogedDEV> i think private networks have an indirect obligation to protect crypto, especially as of late. 20:36:05 <dogedDEV> but thats just my two cents. 20:36:05 <zzz> +1 from me (barely) 20:36:19 <str4d> Lady3Jane, The inherent problem with an anonymous currency exchange is that there is every chance the site could disappear with all funds, and no recompense 20:36:35 <dogedDEV> that can happen on any exchange 20:36:43 <dogedDEV> and has happened on clearnet exchanges. 20:36:51 <anonimal> ^ Then I see no reason to endorse yet another one here. 20:36:57 <amknesia> str4d: Just as a counterarguement: That has already happened with *PUBLIC* non-anonymous exchanges, so is that really any more of a threat? 20:36:57 <str4d> Has, yes. But there are avenues for at least partial recompense 20:37:08 <Lady3Jane> abyss: Beyond the typical eskrow system, do you have any contingencies to ensure to the public (but above all, to the devs who want to endorse you) that you won't skip town with a sack of bills? 20:37:17 <abyss> anonimal, becasue this one is private 20:37:25 <zzz> I count 4+ and 3-, but we could also declare that's too close and let's reconsider at a future meeting 20:37:31 <str4d> Lady3Jane, I don't actually see an escrow 20:37:37 <str4d> (at least not in the security list) 20:37:46 <str4d> I did want to ask about multisig too 20:37:58 <anonimal> And maybe we should review the standards for submission. 20:38:19 <abyss> there is no escrow or mutlisig because thats not really practice for an low latency exchange 20:38:29 <zzz> kytv, str4d, guns to your head, please vote + or - 20:38:32 <amknesia> Maybe it is time for a crypto-rep service? 20:39:05 <dogedDEV> similar to cryptoasian you mean? 20:39:17 * anonimal doesn't care who does what or where or when, this is only for java i2p's router console. 20:39:25 <zzz> last call for votes 20:39:27 <str4d> I am a tentative +0.5 at this stage. I think the site is beneficial for users, but the risks should probably be better-conveyed to users. 20:39:56 <dogedDEV> maybe abyss can put a disclaimer on the site? 20:40:10 <zzz> how about approved if he puts a disclaimer on there then? 20:40:16 <dogedDEV> and that would at least pacify the people voting nay because of risk 20:40:27 <abyss> i can do that 20:40:44 <str4d> There's always a risk, but as long as users are explicitly aware of the risks, I 20:40:46 <kytv> zzz: +1 (with disclaimer of sorts) 20:40:51 <str4d> 'm not opposed to it. 20:40:52 <zzz> we've spent too long on this, if we don't decide in the next 60 seconds I'm moving on anyway 20:41:04 <zzz> ok, sounds like approval if he adds the disclaimer 20:41:07 <zzz> anything else on 2) ? 20:41:20 <dogedDEV> zzz: when is the next meeting? 20:41:23 <amknesia> Is it difficult to make it probationary? 20:41:27 <fox> +1 for abyss's exchange, code is clean 20:41:32 <zzz> 3) `http://i2pwiki.i2p/` console home page request: `http://zzz.i2p/topics/236?page=3#p10437` 20:41:34 <amknesia> IE you could always move it after the next session if there are issues? 20:41:38 <zzz> is the i2pwiki.i2p operator here? 20:41:50 <iRelay> Title: I2PWiki (at i2pwiki.i2p) 20:42:33 <zzz> any discussion on i2pwiki pro/con? 20:42:43 <fox> isn't open4you.i2p just a zombie? 20:42:56 <zzz> please stay on topic everybody 20:42:56 * anonimal loading 20:42:59 <kytv> +1 for i2pwiki. It actually loads and the user makes backups available. 20:43:10 <str4d> dogedDEV, next homepage meeting will be week before 0.9.24 release 20:43:11 <psi> +1 i2pwiki 20:43:22 <fox> -1 open4you 20:43:31 <trolly> open4you.i2p works sometimes and sometimes no fox 20:43:31 <dogedDEV> i2host isnt loading it for me 20:43:31 <zzz> any objections to i2pwiki? 20:43:41 <zzz> please stay on topic everybody 20:43:43 <abyss> i think it is decent 20:43:44 <str4d> i2pwiki.i2p by default redirects to B32 20:43:53 <fox> trolly: it loads sometimes but i don't think they still give out hosting 20:43:54 <trolly> admin did not answer, I think open4you.i2p was hacked or something 20:43:57 <str4d> (at least for me) 20:44:03 <zzz> please stay on topic everybody 20:44:14 <anonimal> i2p slogans are still there. That was an issue before. 20:44:31 <trolly> he created admin2.ope4you.i2p later, but I can login only in admin.open4you.i2p 20:44:32 <zzz> is the slogan issue enough to reject it? 20:44:40 <abyss> str4d, i think thats a mediawiki issue, mine was having the same issue 20:44:45 <zzz> please stay on topic everybody. open4you is NOT the topic. 20:45:05 <str4d> Also, interesting - ugha.i2p is back up 20:45:19 <anonimal> Yes, because of some of the content. Other than that, I would +1. 20:45:30 <abyss> 2015-10 New wiki eepsite: As ugha.i2p was down from may 2015 to 2015-10-30, a new wiki was launched (`http://i2pwiki.i2p`). It is running on MediaWiki. Please move to this wiki. 20:45:30 <kytv> i2pslogans isn't an issue. That was also on ugha.i2p. Users can police that just as they could on ugha 20:45:31 <dogedDEV> -1 on i2pwiki.i2p 20:45:44 <abyss> *from ugha.i2p. front page 20:45:46 <iRelay> Title: I2PWiki (at i2pwiki.i2p) 20:45:47 <str4d> I am generally +1 for i2pwiki.i2p, but would really like the redirection issue fixed 20:45:53 <dogedDEV> Could not find the following destination: `http://i2host.i2p/cgi-bin/i2hostjump?i2pwiki.i2p/` 20:46:07 <iRelay> Title: I2HOST Jump (at i2host.i2p) 20:46:07 <str4d> dogedDEV, `http://nrbnshsndzb6homcipymkkngngw4s6twediqottzqdfyvrvjw3pq.b32.i2p` is the B32 for i2pwiki 20:46:11 <zzz> ok we have + from psi and kytv and str4d , - from anonimal and dogedev. Others please vote 20:46:14 <zzz> me: +1 20:46:16 <abyss> str4d, could it be a i2prouter issue? 20:46:17 <kytv> It's just an i2ptunnel setting I'm sure, it's not a mediawiki problem. 20:46:20 <iRelay> Title: I2PWiki (at nrbnshsndzb6homcipymkkngngw4s6twediqottzqdfyvrvjw3pq.b32.i2p) 20:46:24 <fox> topic isn't cleaning up /home? 20:46:24 <lbt> str4d: If you haven't noticed, check the status-page of uhga, it seems it was "up" all the time 20:46:26 <obscuratus> +1 20:46:49 <abyss> str4d, i find that when sites use relitive links the i2prouter defaults to the b32 20:46:53 <zzz> fox, we are on agenda item 3) 20:47:02 <fox> +1 i2pwiki it loads and is useful 20:47:23 <zzz> ok I count 6 + and 2 -, that sounds like approved, any final objections? 20:47:27 <abyss> +1 i think its usefull and works well 20:47:51 <anonimal> +1, I was wrong. 20:47:56 <zzz> last call for 3) 20:47:57 <anonimal> Slogans were fixed. 20:48:06 * anonimal saw cached version. 20:48:15 <zzz> 4) `http://lenta.i2p/` console home page request: `http://zzz.i2p/topics/236?page=3#p10439` 20:48:22 <zzz> is the lenta.i2p operator here? 20:48:35 <iRelay> Title: Lenta.i2p | (at lenta.i2p) 20:48:37 <zab@kyirc> +1 from me. It loads quickly, the news is real and the layout is pleasant 20:48:48 <zzz> this one appeared to have broad support on the zzz.i2p thread, and in #ru when I asked there a couple of weeks ago 20:49:12 <zzz> any other thoughts pro/con? 20:49:34 <kytv> = "neutral / not negative" 20:49:45 <trolly> is i2pwiki's admin around? 20:49:55 <zab@kyirc> having something catering to .ru users on the home page can be seen as a sign of good will 20:49:57 * anonimal No objections. xopowo. 20:50:08 <str4d> I have NFI what it says, but good that we reflect the Russian userbase. 20:50:14 <abyss> +1 for lenta.i2p 20:50:18 <zzz> sounds like approved to me. last call for 4) 20:50:21 <psi> +1 for lenta.i2p 20:50:43 <kytv> +0.5 based on approval from people who can read Russian 20:50:51 <str4d> Title for it should be in Russian, so users can instantly tell that it is a RU site 20:51:12 <amknesia> Uhmm, dumb question, but should there maybe be a split in links based on 'currently selected language' versus 'foreign language' links? 20:51:16 <str4d> (both so non-russian speakers don't click, and russian speakers do) 20:51:30 <str4d> amknesia, that's a thought I just had myself :) 20:51:50 <zzz> we can always tweak the name in the console 20:51:57 <zzz> 5) CCC preparation update from Oct. 6 meeting: `http://i2p-projekt.i2p/en/meetings/239` 20:52:02 <iRelay> Title: I2P Development Meeting 239 - I2P (at i2p-projekt.i2p) 20:52:34 <zzz> I just threw this agenda item in there in case there was something to discuss. i believe the banner and the candy and all that is under control. 20:52:47 <zzz> we finished the budget decisions at last meeting. 20:52:59 <zzz> If anybody has anything to bring up about CCC, now's the time, else we'll move on 20:53:56 <zzz> last call for 5) 20:54:31 <str4d> Nothing from me 20:54:36 <str4d> You kids have fun there 20:54:46 <zzz> 6) forum.i2p replacement proposal (hottuna, dg) - followup from Oct. 6 meeting: `http://i2p-projekt.i2p/en/meetings/239` 20:55:13 <zzz> ok the notes from last meeting are up (thx kytv) and at the end you'll see that hottuna and dg were due to come back with a proposal. 20:55:30 <zzz> hottuna and dg, you are up. However neither appears to be here? 20:56:05 <zzz> anybody else have anything on forum replacement that extends (not rehashes) the discussion from last meeting? 20:56:51 <str4d> I have something tangentially related that I'd like to tack onto the meeting if we have time. 20:56:56 <obscuratus> What about forums.i2p? 20:58:30 <zzz> ok, anything else on 6) ? 20:58:30 <str4d> I think a user forum is a good idea 20:58:30 <trolly> freedomforum.i2p works too 20:58:30 <str4d> And I think that having it clearnet-accessible (not just via inproxy) is a good idea 20:58:30 <obscuratus> str4d: +1 20:58:30 <zzz> the particular agenda item is whether there should be an 'official' replacement 20:58:30 <trolly> and we have anew forum.. `http://es.i2p` 20:58:30 <trolly> but is only Spanish, but anyone can create a channel in En, of course 20:58:39 <zzz> no site, 'official' or not, has requested to be on the console home page 20:58:42 <trolly> channel/thread * 20:58:54 <zzz> ok, anything else on 6) ? 20:59:01 <Z0rg1nc> mm, how you will protect new forum users if it will be down too? 20:59:07 <str4d> If we have people willing to maintain an official forum, I am +1 on it 20:59:14 <Z0rg1nc> *if not only admins aalowed to speak 20:59:39 * anonimal would really like dg's hottuna's presence before speaking up on 6) 20:59:44 <zzz> I'm +1 for lots of forums, -0.1 on an official one 20:59:50 <trolly> I can't say if http://es.i2p's admin would want to maintain official forum too, sorry 20:59:53 <amknesia> I move to shelve it for next discussion. 21:00:13 <str4d> +1 on tabling 21:00:16 <zzz> as hottuna and dg aren't here, let's table this 21:01:20 <zzz> 7) str4d go 21:01:20 <str4d> s/tabling/shelving 21:01:20 <str4d> Okay 21:01:20 <str4d> Here is an idea I have had rattling around my head for a few months now 21:01:20 <str4d> We define *.i2p.i2p as an unassignable space. 21:01:27 <str4d> And reserve it for use by I2P devs / services 21:01:48 <psi> +1 sounds fun 21:01:51 <str4d> This gets us around whatever funky stuff ever happens wrt I2P addressbook / naming space 21:02:05 <amknesia> Sounds like a plan to me. 21:02:07 <str4d> we define in the naming spec what Dest each 3LD refers to 21:02:19 <str4d> And can change it at any time 21:02:37 <str4d> (possibly by having an in-net hosts.txt that we host containing the current specified Dests) 21:03:08 <anonimal>>we define in the naming spec 21:03:21 <anonimal> And that would protect against maliciousness, yes? 21:03:50 <str4d> Yes. The spec is public and any malicious changes would be completely visible 21:03:55 <zzz> str4d, it's already blocked by stats.i2p registrar and I think most of the others. Not currently blocked in the addressbook import though. 21:04:23 <zzz> not sure what 'funky' stuff you have in mind 21:05:20 <str4d> zzz, the problem with the current addressbook system is that it is only pseudo-global. 21:05:36 <str4d> Now, that itself is debatable, for future 21:05:37 <eche|on> thats good 21:05:53 <str4d> But IMHO services run by *us* *should* be global. 21:06:23 <amknesia> Stupid idea: What about moving to a namecoin style setup with some sort of PoS system with a required amount of cpu time to retain your domains? 21:06:30 <str4d> Easiest way to do that is to define a section of the namespace as controlled by us. Logical section is *.i2p.i2p 21:06:39 <str4d> amknesia, that is outside the scope of this meeting topic 21:06:43 <zzz> str4d, maybe write up your proposal in the zzz.i2p naming subforum? 21:06:54 <amknesia> Ok 21:07:01 <str4d> zzz, will do, when I have time to do so (next month probably) 21:07:11 <zzz> ok, anything else on 7) 21:07:37 <zzz> anything else for the meeting? 21:07:40 <str4d> Heh, on that point, I also have another proposal: make proposals a bit more formal and visible 21:08:08 <zab@kyirc> unmute drz and merge fux (just kidding) 21:08:08 <zzz> ok, now you're just getting meta, so.... 21:08:14 <str4d> Brief 8) 21:08:28 <zzz> 8) str4d go 21:08:30 <str4d> zzz, legit topic, promise :) 21:08:48 <str4d> Right now, all proposals are proposed on zzz.i2p 21:08:54 <str4d> Their general visibility is IMHO poor at best 21:08:57 * anonimal looks forward to str4d's post 21:09:17 <zzz> agreed, so propose something better :) 21:09:24 <str4d> Take e.g. the hostname service feed improvement, getting lost 21:09:46 <zzz> i'm not holding my site precious. You have a proposal? 21:09:54 <str4d> I propose that proposals be formally stored in the I2P website repo, and made visible 21:10:09 <zzz> fine w/ me 21:10:15 <str4d> With links to the canonical discussion thread on zzz.i2p 21:10:22 <str4d> Originally I planned on a separate new repo 21:10:32 <zzz> can you set that up/ 21:10:32 <str4d> But the I2P website serves two purposes: 21:10:36 <zzz> ? 21:10:37 <str4d> - Define spec of the I2P network 21:10:47 <str4d> - Document the reference implementation (Java) 21:10:55 <zzz> anybody have any objections? 21:11:03 <xmz> no 21:11:11 <str4d> And since the specs are already part of the website, I simultaneously propose to elevate their position 21:11:27 <zab@kyirc> as long as the proposals are plain text - don't put binaries in mtn pls 21:11:28 <anonimal> Where would it go on the site? 21:11:38 <str4d> And define them as non-translatable for simplicity 21:11:46 <str4d> zab, hell no 21:11:59 <str4d> anonimal, currently they are at /langcode/docs/specs/* 21:12:03 <str4d> (the specs) 21:12:04 <zzz> I think str4d already has carte blanche for minor website organization 21:12:12 <zzz> so can we wrap this up? 21:12:17 <zzz> anything else on 8) ? 21:12:20 <str4d> I propose instead having /spec/* for specs, and /spec/proposal/* for proposals 21:12:46 <str4d> zzz, yes, but this also goes into proposal processes 21:12:49 <zzz> lets not use a meeting for discussing website path details 21:12:56 <anonimal> I only ask because the site's layout is TMI at once for my taste, imho. 21:13:08 <str4d> end goal is that people outside I2P can then view our proposals. 21:13:22 <str4d> anonimal, redesign is ongoing, save it for later :) 21:13:25 <zzz> agreed and I didn't hear any objections 21:13:27 <zzz> anything else on 8) ? 21:13:30 * anonimal :) 21:13:44 <zzz> anything else for the meeting? 21:13:54 <anonimal> Yes, briefly. 21:14:04 <zzz> 9) anonimal go 21:14:04 <abyss> so did exchanged.i2p make it with a disclaimer? 21:14:18 <abyss> something like "Disclaimer: trading cryptocurrencies is risky, trusting anonymous people with your money is also risky. " 21:14:32 <zzz> abyss yes 21:14:33 <zzz> 9) anonimal go 21:14:45 <abyss> \o/ 21:14:46 <anonimal> str4d's *i2p.i2p made me think of the IETF comments made at I2PCon and https://blog.torproject.org/blog/landmark-hidden-services-onion-names-reserved-ietf 21:14:49 <iRelay> Title: Landmark for Hidden Services: .onion names reserved by the IETF | The Tor Blog (at blog.torproject.org) 21:15:05 <amknesia> abyss: Don't forget the 'Please ignore the man behind the website with the virtual suitcase and fueled dc3' :) 21:15:13 <anonimal> So the question is: 21:15:27 <xmz> could also add that the service is not endorsed in any way by the i2p project (sorry cant see.all of the prior discussion, im on my phone) 21:15:49 <zzz> we're on 9), please stay on topic 21:16:09 <anonimal> Are we pushing for IANA? 21:16:12 * anonimal sorry lag 21:16:26 <str4d> anonimal, yes. I am I2P's representative in that process. 21:16:58 <anonimal> Yay! Anything to report? 21:17:02 <str4d> I have also volunteered to be on the design committee that is going to propose changes/improvements to the RFC 6761 process 21:17:31 <str4d> .i2p was proposed along with .onion, .gnu, .bit and a few others by the GNUnet team 21:17:40 <zzz> great, thanks for continuing to do that str4d 21:17:42 <str4d> That sat around for several years being kicked back and forth 21:17:56 <zzz> I'm sure you can fill him in more after the meeting 21:17:58 <anonimal> Yes, thank you str4d. 21:18:05 <zzz> anything else on 9) ? 21:18:09 <zzz> anything else for the meeting? 21:18:31 <str4d> well... 21:18:34 <str4d> (jk ;) 21:18:40 <anonimal> lol 21:18:47 <sadie_i2p> ha 21:19:01 <zzz> thanks everybody. /me ****bafs**** the meeting closed

I2P Dev Meeting - October 06, 2015

Tue, 06 Oct 2015 00:00:00 +0000

Quick recap

Present: cacapo, comradenosebleed, dg, eche|on, hottuna2, postman, str4d, zzz

Meeting Log

19:59:41 <zzz> 0) Hi 19:59:41 <zzz> 1) 32C3 Budget 19:59:41 <zzz> 2) Other 32C3 todo items - banner, etc. 19:59:41 <zzz> 3) RWC Budget 19:59:44 <zzz> 0) Hi 19:59:47 <zzz> Hi 19:59:50 <eche|on> hi 19:59:53 <dg> hi 19:59:59 <zzz> 1) 32C3 Budget 19:59:59 <cacapo> hi 20:00:23 <zzz> ok, the plan is to do what we did for Toronto, which is to set an overall budget and let echelon handle the details 20:00:43 <hottuna2> i love soylent and you 20:00:46 <hottuna2> oups 20:00:47 <zzz> echelon, what's the total of the travel requests for funds that you got 20:01:06 <eche|on> currently it is roughly 4k and 2 BTC 20:01:56 <hottuna2> as calculated how? 20:02:03 <zzz> ok, were there any excessive requests or request from any randoms that we need to discuss, or was everything reasonable? 20:02:41 <eche|on> all reasonable, non above 1k euro so far, so... all fine 20:02:52 <eche|on> some did wrote too much information, haha 20:03:22 <zzz> and about how much more to pay for CCC tickets, a dinner, gummy snakes and such? 20:04:06 <eche|on> I think dinner will be 500+x, tickets will be 100 each (at 10 ppl roughly) and snakes and small stuff in the 200-300 20:04:24 <eche|on> dinner for 20+x 20:05:04 <zzz> so that's 1800 euros + 4K travel + ~500 for 2 BTC is 6300 euros total, right? 20:05:53 <eche|on> yeah, but we will not scratch up to that, IMHO some of the travel fund will be payed in BTC, and dinner could be cheaper... 20:05:59 <eche|on> so lets say 6k 20:06:34 <eche|on> last year we did have had 1257 without travel costs 20:06:38 <zzz> that sounds pretty reasonable to me, let's throw it open to discussion... what do people think? 20:06:39 <eche|on> and a few tickets 20:07:13 <hottuna2> does that mean we'll be reaching our 10% spending goal per year? 20:07:31 <eche|on> sure 20:07:53 <hottuna2> as in we'll be below 10%? 20:08:01 <zzz> doubt it, we have ~250K and we only spent 4-5K on toronto iirc 20:08:02 <eche|on> sure 20:08:22 <eche|on> wait, 150k, not 250... 20:08:49 <zzz> either way, we're well under 10%, back of the envelope 20:09:02 <eche|on> and currently we spent 5.3k this year 20:09:19 <hottuna2> ok. i'm happy with that. 20:09:22 <zzz> any objections to a 6K Euro budget for CCC? 20:10:05 <zzz> great 20:10:41 <zzz> as always eche|on I think we prefer to reimburse people, but we can pay in advance if people really need it to buy tickets, right? 20:11:25 <hottuna2> is there a way to know how much you'll be reimbursed for? 20:11:25 <eche|on> correct 20:11:44 <zzz> I think we just approved 100% of people's requests, correct? 20:11:49 <eche|on> yes 20:12:05 <zzz> ok, so whatever you asked for is what you'll get hottuna2 20:12:13 <hottuna2> ok 20:12:23 <zzz> thank you very much eche|on I think this process worked well 20:12:27 <zzz> anything else on 1) ? 20:12:53 <zzz> 2) Other 32C3 todo items - banner, etc. 20:13:05 <eche|on> banner is still in toronto 20:13:10 <eche|on> poster - we need a poster 20:13:28 <zzz> DECT phones part 2? banner? poster? what needs to be done, any volunteers? 20:13:35 <eche|on> we need a table (I try to get into wiki and make some page about our group) 20:13:45 <hottuna2> who has the banner? 20:13:57 <hottuna2> I do not have it. 20:13:57 <str4d> j0 20:13:58 <eche|on> it was at toronto hacklab 20:14:13 <hottuna2> should I bring the podium graphic from i2pcon? 20:14:40 <zzz> hottuna2, can you be in charge of finding the banner in Toronto and bringing it? 20:14:53 <eche|on> DECT phones could be done, but I do not know, everyone has a mobile, Wifi available... 20:15:13 <zzz> maybe twitter DM has rendered DECT obsolete 20:15:15 <hottuna2> zzz, will do. 20:15:19 <eche|on> hottuna2: there was a twitter discussion with sadie about the banner and let her bring it to hamburg 20:15:23 <dg> i'm just going to twitter 20:15:41 <dg> irc if no response 20:15:50 <hottuna2> do we need any other marketing type of material? 20:15:50 <eche|on> table needs to be reserved asap 20:15:59 <eche|on> stickers 20:16:06 <zzz> eche|on, you volunteered to reserve the table? 20:16:28 <eche|on> a folder (3 columns, folded) with basic informations would really help, but not available 20:16:44 <eche|on> zzz: I can try to reserve the table on 26th ahead of cinema 20:16:56 <eche|on> or better: I try my best to reserve it 20:17:00 <dg> usual place, or? 20:17:10 <eche|on> dg: would be best, noisysquare 20:17:11 <zzz> yeah, but you volunteered to sign up on the wiki, right echelon? 20:17:13 <dg> just a question: how big is the table usually? 20:17:24 <eche|on> yeah, I try to do the wiki, also 20:17:28 <zzz> 8-10 20:17:30 <cacapo> eche|on: didn't we have a folder contest a while back 20:17:31 <dg> eche|on: ah good 20:17:32 <hottuna2> Sadie says Hi from twitter 20:17:36 <dg> zzz: so room for everyone? 20:17:38 <eche|on> the table is mostly a round table for 8-10, or a square table 20:17:51 <dg> hottuna2: she needs2irc 20:17:56 <zzz> we're never all there at the same time, not to worry 20:17:58 <eche|on> cacapo: yeah, but the results of fodler contest were not useable AFAIR 20:18:03 <hottuna2> that's what I'm telling her 20:18:20 <dg> alright :) 20:18:34 <zzz> there was also the idea of USB stick giveaways, I looked into it, looks like $2 in bulk for small-capacity 20:18:41 <dg> i'm waiting for schedule so i can plan my day 20:18:42 <eche|on> `http://echelon.i2p/29c3/` 20:18:46 <iRelay> Title: 29C3 I2P contest (at echelon.i2p) 20:18:51 <dg> know when to duck in/out 20:19:29 <eche|on> dg: usual we meet in 10-12am and leave after 1am... 20:19:47 <zzz> so re: poster, who is looking into that? 20:19:48 <eche|on> zzz: the USB sticks are nice 20:20:03 <eche|on> but I do not know if really useful 20:20:13 <hottuna2> so the 2015 wiki for 32c3 does not appear to be open yet 20:20:28 <eche|on> hottuna2: correct 20:20:36 <dg> eche|on: past my bedtime ;) fits my lie ins 20:20:43 <zzz> I'm not humping hundreds of USBs across the ocean. Dunno if too late to get logo'ed ones 20:20:46 <dg> is the CCH open all night? 20:20:58 <eche|on> dg: CCH is open 24/7 20:21:08 <zzz> let's defer talk about CCC basics and logistics for now 20:21:20 <dg> ok, thx eche|on 20:21:22 <zzz> this agenda item is for prep only 20:21:36 <eche|on> zzz: 2 weeks time on one sender 20:22:07 <zzz> anybody want to volunteer for a poster or for USB sticks? 20:22:29 <zzz> and what was the answer on stickers? 20:22:32 <eche|on> but a USB stick/card is around 4-6 eeach 20:22:48 <zzz> I saw them for about $2 on ebay 20:22:58 <hottuna2> i'm not sure i'm I understand the idea behind the usb sticks 20:23:08 <zzz> but those weren't customized I dont think 20:23:15 <dg> would we bundle i2p, just put our logo on it, or...? 20:23:22 <zzz> both 20:23:44 <hottuna2> not sure I feel that's a good use of money. if we were tails it would've been a different story 20:24:41 <eche|on> I am not really a fan of USB in this pricy area, as we would need 100+x, thats at least 500 20:24:45 <eche|on> for printed ones 20:24:47 <zzz> ok 20:24:51 <eche|on> with a less use 20:25:10 <zzz> so lets skip the USB sticks. What about stickers? How's the supply over there? Did you bring them all over here or? 20:25:17 <str4d> hottuna2: we don't even need to give aaway the USBs 20:25:24 <eche|on> I still got stickers left 20:25:42 <comradenosebleed> zzz: i have a bunch of stickers that tuna gave me as well, i don't mind bringing them with me 20:25:44 <str4d> If they are decent enough, could sell at cost 20:25:45 <eche|on> but some of the toronto connections wanted to create a new design AFAIK. 20:25:55 <comradenosebleed> (sorry tuna, i'm trying to give out as many as i can) 20:26:05 <dg> i might have some stickers 20:26:11 <eche|on> str4d: I do not like to sell and handle some money beside my debit card on CCC 20:26:16 <zzz> eche|on, you have enough for CCC or you need comradenosebleed to bring some? 20:26:30 <hottuna2> do we want to get some more t-shirts 20:26:40 <eche|on> I got enough for CCC, but thats my last I got 20:26:53 <comradenosebleed> i probably have 200 or so sitting on my desk, i have no problems bringing them with me 20:27:07 <eche|on> so I need a new design, or I get another 10k with the same design 20:27:13 <hottuna2> and a separate question, do we want to sell them? 20:27:23 <hottuna2> eche|on: I would like to get a new design made 20:27:33 <hottuna2> before new stickers are ordered 20:27:36 <zzz> let's defer buying more stickers for now if we have enough for CCC and there's potential for a new design 20:27:44 <eche|on> right 20:27:51 <zzz> no, I don't think we should sell them 20:27:53 <dg> will bring some anyway 20:28:02 <hottuna2> zzz, agreed. 20:28:12 <str4d> no one sells stickers at cons :P 20:28:21 <str4d> The advertizing alone covers it 20:28:22 <hottuna2> still, do we want to get more t-shirts? 20:28:43 <eche|on> hottuna2: we can ask in zzz.i2p for visitors (i2p team) needing/wanting a shirt. at least dg and str4d need them 20:28:46 <str4d> (oh wait, t-shirts, nvm) 20:28:46 <eche|on> yes 20:28:56 <zzz> I say no to t-shirts. too much of a hassle to sell, and pretty much everybody has one, right? 20:29:05 <str4d> I don't 20:29:11 <str4d> I won't be at CCC tho 20:29:13 <eche|on> and postman postman !?? 20:29:20 <eche|on> oh, sry... 20:29:20 <dg> postman is joining us btw :) 20:29:29 <zzz> for the one-offs, they can buy it on spreadshirt 20:29:40 <zzz> if they want 20:30:04 <str4d> That was my plan :) 20:30:19 <zzz> what was the answer on the poster? Maybe tuna and sadie will do something, maybe not? 20:30:22 <dg> will get one too, no need to order more for the project 20:30:37 <zzz> is the timothy leary poster still around? 20:31:27 <hottuna2> zzz, so no t-shirt for dg or postman? 20:31:37 <hottuna2> I don't mind ordering/bringing them. 20:31:40 <postman> hey, i would take one 20:31:49 <eche|on> `http://echelon.i2p/29c3/user5/poster/final_with_garlic.jpg` 20:32:03 <eche|on> zzz: that one? 20:32:06 <dg> I'd like a yellow one if you've got one but I'll order it myself if not 20:32:43 <hottuna2> dg, postman what sizes are you? 20:32:45 <zzz> sounds like it's between tuna and postman and dg to figure out t-shirts, whether tuna orders them or the others just order their own 20:32:56 <eche|on> t-shirt costs can be refunded on 32C3 for team members 20:33:03 <dg> yeah sorry we'll leave it for later :) 20:33:26 <zzz> ok, so the project will reimburse for t-shirts for those that don't have them 20:33:34 <zzz> any objections to that? 20:33:41 <eche|on> we did pay the other shirts already 20:33:48 <zzz> yup 20:34:31 <zzz> ok, sounds like we don't have a poster answer atm, but no big deal if we don't get one 20:34:31 <eche|on> date for dinner pre-announce? 20:34:32 <hottuna2> no 20:34:32 <hottuna2> that's how it's been done previously 20:34:39 <zzz> yes eche|on that's the leary poster 20:35:09 <zzz> eche|on, you have a proposal for which nite for dinner? 20:35:42 <eche|on> hmm, 27th is a bit early, but still fine. 28th or 29th are fine, too. But I need to wait for talk schedule 20:36:03 <zzz> ok, maybe let's pencil in 28th, subject to change 20:36:08 <zzz> anything else on 2) ? 20:36:09 <eche|on> We can do the 27th, its sunday, first evening, all are jet-lagged, no one wants beer, cheap^^ 20:36:49 <zzz> last call for 2) 20:36:51 <dg> no thanks for 27th 20:37:20 <zzz> 3) RWC Budget 20:37:36 <zzz> eche|on, any requests for RWC funding? What's the total? 20:37:51 <eche|on> yeah, thats a bit non-anon, as I got one request of 500 for hotel costs at RWC 20:38:20 <zzz> sounds reasonable, any objections? 20:38:25 <eche|on> no 20:38:30 <eche|on> if the paper is good, all fine^^ 20:38:51 <eche|on> and it is 2016, new year, new 10% *g* 20:39:24 <zzz> I encourage anybody that can get to RWC to check it out, it's a good conference 20:39:35 <zzz> anything else on 3) ? 20:39:40 <eche|on> to far away from me 20:39:53 <eche|on> although interesting, sure 20:39:55 <dg> too far & incompatible w/ CCC 20:40:50 <zzz> ok, any other topics? I know i shot down i2pcontrol, 32c3 talk, and forum replacement over on the zzz.i2p thread, but if anybody wants to discuss _briefly_ speak up now 20:41:33 <hottuna2> yeah. i'd like to talk about forum.i2p 20:41:38 <hottuna2> do we want to replace it? 20:41:52 <dg> just wrt forum replacement, we're open to it and discussing it. if anyone thinks it's a good idea for us to do it, hit up postman/myself/eche|on. we're in a position to run one, but we dunno if there's much support 20:42:33 <zzz> I'll paste in my position from zzz.i2p, others may disagree, that's fine 20:42:35 <hottuna2> i think we should have a public facing place for discussions 20:42:54 <zzz> My consistent view has been that users will vote with their feet, let a thousand flowers bloom, etc. etc. It's not necessary or even wise for us to anoint a replacement. One or more are free to apply for placement on the console home page following our usual process. If somebody wants to set up a forum site, they should do so, 20:43:18 <hottuna2> I don't agree. 20:43:19 <dg> hottuna2: while I'm very open about a forum, what is not open about zzz.i2p? for the record it's unlikely a forum.i2p run by postman/echelon/myself will be on clearnet 20:43:43 <hottuna2> I think we should have a clearnet forum. 20:43:47 <zzz> zzz.i2p is not open to all topics 20:44:01 <hottuna2> interacting with i2p now is like interacting with a brick. 20:44:06 <zzz> forums get _hammered_ by spiders via inproxies 20:45:15 <zzz> and hammered by spam via inproxies 20:45:15 <hottuna2> there's the irc and zzz.i2p. that is it as far as public communications go with i2p 20:45:15 <hottuna2> how are we to attract people new to anonymity tools if we're not even available to these people? 20:45:15 <eche|on> zzz.i2p is dev talk, a user talk forum would be nice, but it cannot be run on clearnet 20:45:15 <zzz> I'd like to see more use of the blog on our website by the PR team 20:45:16 <hottuna2> I get that running a forum is highly inconvenient. 20:45:19 <eche|on> forum.i2p is currently a good forum, I keep it as clean as I like 20:45:36 <dg> administering one is fine, clearnet is going to be difficult. It's possible but... 20:45:38 <zzz> forum will be dead by year-end due to rekey 20:45:38 <hottuna2> but our blog does not support communication both ways. the lbog is just a broadcasting tool. 20:45:53 <dg> I see that clearnet would be helpful for support though. 20:46:02 <hottuna2> so this is a relevant topic to try to deal with as soon as possible. 20:46:38 <zzz> anybody wants to run a (or "the") forum replacement? go for it, you don't need anybody's permission 20:46:42 <hottuna2> support and also attracting new developers. showing people the topics we are discussing is a way to attract developers and people of all skill-levels 20:46:50 <str4d> I don't see a simple way to add a blog without going beyond the near-static approach 20:47:19 <dg> the irc2p team is up for it, but I don't know how to handle the clearnet problem 20:47:21 <zzz> hottuna2, nobody's saying a forum isn't a good thing 20:47:47 <str4d> comment section to the* 20:47:53 <hottuna2> so we agree that having one would be helpful to us? 20:47:55 <eche|on> dg: forum.i2p was clearnet, it did not went out well, was closed and all is fine 20:48:09 <zzz> I declared forum.i2p dead back in January. There's been plenty of time. 20:48:16 <hottuna2> and we also agree that we want to reach out and attract newbies to join i2p? 20:48:23 <dg> eche|on: it would be helpful for user supports though 20:48:36 <hottuna2> having it be more than a vaporware goal requires action 20:48:37 <eche|on> dg: not worth the hassle 20:48:42 <zzz> hottuna2, agreed forums are good. Not sure if one of us needs to run one. And not sure I've heard anybody volunteering. 20:49:08 <dg> I don't care about handling the spam, I just want to remain anonymous and you can't do that while running a clearnet site 20:49:23 <eche|on> yes 20:50:46 <hottuna2> dg, could I or someone else rent the root server? 20:50:46 <eche|on> but really, you do not want the i2p forum clearnet 20:50:46 <hottuna2> and you have access to it through i2p+ssh? 20:50:46 <zzz> so perhaps dg as admin combined with some server resources could be a solution 20:50:46 <dg> hottuna2: That's something we can discuss if you (or someone else) is comfortable with the cost 20:50:46 <hottuna2> eche|on: I want the forum to be clearnet and on i2p 20:50:46 <eche|on> hottuna2: you will loose it. 20:50:46 <eche|on> forum.i2p has had massive spam issues 20:50:46 <dg> eche|on: I know clearnet can be a problem but a lot of users like it as a support mechanism 20:50:46 <dg> irc is not for everyone, especially where we have the "deep sleep chamber" 20:50:46 <eche|on> thats why it was closed down 20:50:46 <zzz> sure, clearnet a nice dream, maybe solveable, maybe not 20:50:50 <eche|on> forum.i2p is still a good support channel 20:50:54 <hottuna2> dg, i'm comfortable with that, and also think that i2p would re-imburse an forum server 20:51:24 <dg> happy to try it and if it doesn't work, we'll be i2p only. I don't know about i2p reimbursing it (not my decision though), but then again, i2p already reimburses core services... 20:51:25 <comradenosebleed> How many moderators were around on the forum while it was clearnet? If we had more mods we would be able to trim down on abuse, spam, etc. 20:51:35 <hottuna2> eche|on: eche|on: would i2p sponsor a forum machine? 20:51:35 <dg> comradenosebleed: afaik it was just eche|on 20:51:43 <eche|on> comradenosebleed: we did have had at least 5-10 people 20:51:49 <dg> hottuna2: I'm happy to admin in any case, just don't want to put a burden on you. 20:51:53 <eche|on> but a damned stupid guy spammed and did some DDOS 20:52:06 <hottuna2> dg, would you volunteer to set up and admin a clearner+hidden forum? 20:52:07 <zzz> dg maybe you can estimate bandwidth/processing power requirements and put together a proposal? 20:52:25 <dg> hottuna2, zzz: OK, i'll work with hottuna2 on that and we can figure out a proposal 20:52:36 <dg> hottuna2: as long as I can be anon still, no problem 20:52:38 <hottuna2> getting a quite powerful server from hertzner is about 30/month 20:52:42 <zzz> I'm still not in favor but willing to listen 20:52:55 <zzz> we have spare VM's now but depends on load 20:53:02 <zzz> ok anything else on forum? 20:53:06 <zzz> anything else for the meeting? 20:53:11 <eche|on> also while being clearnet you cannot hsot a lot of topics which are right now in forum.i2p 20:53:11 * zzz warms up the baffer 20:53:28 <hottuna2> zzz, eche|on: re spare vms, do we want to place all of our infrastructure on the same host? 20:53:30 <eche|on> e.g. you will need a native russian guy for the forum to admin it 20:53:31 <comradenosebleed> I volunteer myself as a mod if we put up a clearnet forum. As much as I hate to suggest cloudflare to host it, they do have excellent ddos prevention 20:54:01 <hottuna2> comradenosebleed: noted 20:54:02 <eche|on> and tha tone would need to know the rules of the country the host is hosted in (hetzner is german, german has some strange laws, e.g.) 20:54:15 <zzz> you all feel free to continue the forum talk, however I... am... 20:54:23 <eche|on> baffing! 20:54:25 <zzz> .. *baffing* the meeting closed

0.9.22 Release

Sat, 12 Sep 2015 00:00:00 +0000

Update details

0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures. To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart. When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity. If all goes well, we will accelerate the rekeying process in the next release.

I2PCon: Mission Accomplished

Thu, 20 Aug 2015 00:00:00 +0000

I2PCon has been a giant success. For us, the I2P contributors, it represents a leap forward in terms of what we’re capable of pulling off as a community, how we communicate the usecases of I2P and reach out to privacy conscious individuals.

By arranging this event, we’ve also grown our community. People who’ve previously only lurked on our irc channels, or run our software or possibly hadn’t even heard of I2P are now a part of our community.

0.9.21 Release

Fri, 31 Jul 2015 00:00:00 +0000

Update details

0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills, and use bandwidth more effectively. We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback using the new “multisession” capability for those sites that don’t support ECDSA.

The speakers and the schedule of the I2PCon in Toronto 2015 have been announced. Have a look on the I2PCon page for details. Reserve your seat on Eventbrite.

I2PCon

Thu, 16 Jul 2015 00:00:00 +0000

I2PCon is the first event of its kind. It has two short term goals. Where the first one is to provide the general public with an event where knowledge about privacy and privacy concerns can be obtained. The second goal is to further the I2P project and its community. This will take the shape of technical discussions about cryptography, anonymity and I2P centric topics.

There is a larger and more long-term goal of this event, and it is to build a community of privacy-conscious individuals. By connecting people who recognize the importance of privacy, we would like to provide a forum where this community can grow.

I2P Dev Meeting - July 14, 2015

Tue, 14 Jul 2015 00:00:00 +0000

Quick recap

Present: chlorelium, dg, EinMByte, hottuna, lazygravy, psi, RN, str4d, z3r0fox, zzz

Meeting Log

20:01:40 <hottuna> 0) Hi 20:01:40 <hottuna> 1) I2PCon: Status update 20:01:40 <hottuna> 2) I2PCon: Liqueur license ($25) 20:01:40 <hottuna> 3) I2PCon: Allow photos without explicit consent? 20:01:40 <hottuna> 4) I2PCon: Allow videos? 20:01:40 <hottuna> 5) I2PCon: Arrange schedule of event 20:01:43 <hottuna> 6) dogecoindark.i2p home page request 20:01:54 <chlorelium> aloha! Nice to be here with you all today. 20:02:02 <z3r0fox@oftc> o/ 20:02:07 <EinMByte> Hi 20:02:13 <hottuna> ***** 0) ***** 20:02:19 <hottuna> Hello@all 20:02:36 <hottuna> Does anyone have any questions or anything that should be added to the agenda? 20:02:43 <RN> hi 20:03:00 <str4d> hi 20:03:00 <lazygravy> Hi 20:03:01 <EinMByte> Do we have a livestream? (for con) 20:03:15 * RN has input for #3 but will wait till it comes up 20:03:31 <lazygravy> EinMByte: sounds like talk for #4 20:03:38 <hottuna> EinMByte, no. nothing like that has been organized. let's add that discussion to 4) 20:03:46 <hottuna> anything else? 20:03:49 <EinMByte> ok 20:04:04 <chlorelium> one thing 20:04:06 <chlorelium> donations 20:04:15 <chlorelium> I was talking with dnj about donations at i2pcon 20:04:22 <chlorelium> not sure how we're handling that 20:04:25 <chlorelium> we should hash that out today. 20:04:40 <hottuna> let's add that as 7) 20:05:08 <hottuna> ok. 20:05:13 <hottuna> **** 1) **** 20:05:19 <hottuna> 1) I2PCon: Status update 20:05:37 <hottuna> So.. the current status is that we're finalizing most aspects of the event. 20:06:00 <hottuna> We have all of our speakers verified. 20:06:16 <hottuna> The next step is constructing a schedule 20:06:27 <hottuna> And lastly making a 2nd announcement 20:06:48 <EinMByte> How many participants do we have right now? Do we know that? 20:06:52 <hottuna> Containing more details, like schedule and whatever else might be useful. 20:07:06 <EinMByte> Do we have a webpage? Do we need one? 20:07:07 <hottuna> EinMByte, that is a good question. And something chlorelium has brought up. 20:07:19 <hottuna> Hacklab can seat 40people 20:07:21 <EinMByte> Like a page on geti2pNet 20:07:32 <EinMByte> s/geti2pNet/geti2p.net 20:07:42 <hottuna> EinMByte, I've voted against making a website due to the amount of work that would entail. 20:07:44 <chlorelium> hottuna: actually got a revised number, it 48 chairs, though it's a squeze 20:08:28 <hottuna> So speaking of the number of attendees, chlorelium requested that we try to keep track of the number somehow,. 20:08:39 <EinMByte> hottuna: well, an enitre website might be a little bit too much. But at least a page with the information? 20:08:44 <hottuna> The current idea is an evenbrite page where people can sign up. 20:09:11 <chlorelium> EinMByte: I was thinking an Eventbrite page. Mostly I don't want a situation where we seat 48 people and 200 show up :) 20:09:30 <chlorelium> Hacklab has an eventbrite account, I can set something up shortly. 20:09:39 <lazygravy> hottuna: whatever is used, it should be made sure it doesn't block tor connections. I am sure most people would like to sign up over it. 20:10:03 <hottuna> Could we squeeze more than 48 people in there if some are left to stand? 20:10:03 <EinMByte> chlorelium: well, you can always give people a token that they need to show on entrance 20:10:11 <hottuna> Just to give us some margins 20:10:16 <dg> \o. 20:10:31 <hottuna> EinMByte, we have the announcment, and we're going to make another annoucnement in the smae style as the first 20:10:37 <chlorelium> hottuna: yes, it's standing room for probably 80+ 20:10:53 <chlorelium> lazygravy: noted re: TOR 20:10:56 <hottuna> other than that I don't have any volunteers for building a webpage. 20:11:44 <chlorelium> EinMByte: eventbrite generates "tickets"; doesn't need real name or real phone # though, it can be anonymous signup through tor with throwaway email 20:11:50 <chlorelium> EinMByte: so that can be the token of sorts 20:12:02 <hottuna> it sounds pretty good. 20:12:16 <EinMByte> That's good. Eventbrite seems good. But we should probably link to it on the I2P website 20:12:29 <EinMByte> (can be in a blog entry I suppose) 20:12:43 <hottuna> EinMByte, we will on the second announcement and probably from the first one too. 20:12:54 <EinMByte> ok 20:12:58 <hottuna> it's only there to give us an estimate of the number of participants 20:12:59 <RN> mmm... I suppose an I2P internal mirror of event brite would be a bit much... 20:13:21 <dg> RN: unlikely though somebody (I?) could ask. depends on how big they are, and if we have any contacts 20:13:35 <hottuna> :P 20:13:38 <hottuna> that's being pretty optimistic 20:13:56 <hottuna> we're also working on a flyer for the event 20:13:56 <RN> yeah, put that in the notes for "next time" 20:14:09 <EinMByte> So cholerlium, you set up the eventbrite page? 20:14:18 <hottuna> i was hoping to have an early version of it ready now, but will likely get to see it later tonight 20:14:19 <chlorelium> EinMByte: sure, I'll do that doay 20:14:21 <chlorelium> *today 20:14:43 <hottuna> splendid, the sooner we have a link, the sonner we can startp ublishing it 20:14:45 <chlorelium> EinMByte: I can at least generate the URL for posting, and we can populate it with content later if need be 20:15:27 <hottuna> Ok, anything else anyone would like to add? 20:15:36 <RN> sooner url is generated, sooner if it is tor-friendly can be tested 20:15:38 <EinMByte> *chlorelium 20:16:11 <z3r0fox@oftc> Regarding info in the second announcement, ppl may want to know if they'll be able to plug in 20:16:53 <hottuna> z3r0fox: nice catch 20:17:00 <chlorelium> z3r0fox: plug in to power, network, or what? 20:17:01 <lazygravy> Plug in being Internet access? 20:17:14 <chlorelium> power we have :) 20:17:18 <z3r0fox@oftc> Both... 20:17:28 <str4d> I've used Eventbrite via Tor before, it worked fine for me 20:17:30 <str4d> (back in 2013 registering for RWC 2014) 20:17:42 <RN> thx str4d 20:18:08 <chlorelium> so 20:18:12 <chlorelium> power: 20:18:17 <chlorelium> we have many large power strips 20:18:26 <RN> network? wifi? 20:18:31 <chlorelium> some of them hang from the ceiling, we could potentially run them under/behing rows of seats 20:18:37 <chlorelium> network is mostly through wifi 20:18:51 <hottuna> str4d, thanks 20:18:51 <chlorelium> we regularly handle 30+ people on the guest network 20:18:57 <chlorelium> we also have piratebox, if anyone cares :) 20:19:21 <chlorelium> I'll ask our ops person how many connections the guest network can accomodate before going to shit 20:19:27 <hottuna> ok. so we'll ahve some power at the very least and wifi for ~everyone 20:19:58 <chlorelium> yup 20:20:13 <chlorelium> this is also a helpful item in getting headcount before-hand 20:20:22 <EinMByte> good 20:20:22 <chlorelium> we can plan ahead for wireless needs 20:20:27 <hottuna> alright. anything else for 1)? 20:20:30 <dg> Somebody a few days ago by the name of 'saltire' messaged me, inquiring about setting up a relay between OFTC and IRC2P for #torontocrypto. He hasn't messaged me since, and #torontocrypto has no relay (just ChanServ and I). Would saltire, or somebody else from the TC side, be able to set one up? 20:20:48 <dg> I could probably do it because OFTC allows Tor, but I'd prefer a TC person. 20:21:13 <hottuna> dg, possibly. I know saltire from meatspace. 20:21:24 <hottuna> dg, could we save that until after the meeting? 20:21:28 <RN> mmm.... lag? or is network not available...? 20:21:31 <dg> hottuna: np 20:21:40 <hottuna> ok 20:21:45 <hottuna> **** 2) **** 20:21:48 <hottuna> 2) I2PCon: Liquor license ($25) 20:21:53 <hottuna> We're getting one. 20:21:54 <hottuna> Today. 20:22:03 <hottuna> No worries, we've got this. 20:22:06 <chlorelium> paperwork for that is almost filled out, just have to file 20:22:14 <lazygravy> :-) 20:22:21 <chlorelium> already called the LCBO, they'll have someone there until 9pm EDT to accept our app 20:22:25 <chlorelium> and actually the deadline is tomorrow night 20:22:30 <zzz> is license for consumption, sales, or both? 20:22:37 <lazygravy> BYOB? 20:22:38 <hottuna> So with the license there are some obligations we have to fulfill. Like not getting people shitfaced. 20:22:49 <hottuna> zzz, consumption. 20:22:54 <hottuna> lazygravy, no. 20:23:00 <chlorelium> license does not allow for sale. It's for consumption only. if we want a sale license the cost jumps to $75 20:23:11 <hottuna> having a license is not compatible with BYOB 20:23:17 <EinMByte> So that means drinks are free? 20:23:18 <chlorelium> BYOB is a no-no. BYO is illegal at public events like this 20:23:30 <hottuna> EinMByte, yes. but only a small amount. 20:23:32 * RN pouts about non-attendance "awww man... they'll even have beer!!!" :( 20:23:45 <hottuna> We're talking about 1-2 beers / participant depending on how many show up 20:23:46 <chlorelium> (and normally we wouldn't care, but guaranteed gov't types will show up and someone somewhere will complain about a lack of license) 20:23:59 <hottuna> And how generous eche|on is feeling 20:24:06 <zzz> fine. we have a bucket for donations (topic #7) 20:24:18 <chlorelium> We can have more alcohol for sale, but it means pitching in $50 extra for that license 20:24:24 <chlorelium> application process is essentially the same, though 20:24:25 <EinMByte> hottuna: ok. Do you have some systems for keeping track of who has already had their drink? Or do you think this won't be a problem? 20:24:41 <hottuna> zzz, as long as the donation bucket isn't explicitly for booze we should b efine 20:24:58 <hottuna> EinMByte, not really. but we don't plan on bringing tons. 20:25:02 <chlorelium> just FYI: if we take donations at the door and hand out drink tickets, we need a "sale" license since that's viewed as an indirect sale 20:25:26 <chlorelium> that doesn't mean we're prohibited from taking donations and giving drink tickets, but we can't do it in that order with a "no sale" license o_0 20:25:29 <chlorelium> liquor laws are silly 20:25:59 <EinMByte> hottuna: let's just assume honesty then 20:25:59 <chlorelium> EinMByte: I think honesty is a good policy :) 20:25:59 <hottuna> EinMByte, that's the idea. 20:25:59 <hottuna> Anything else on 2)? 20:26:14 <chlorelium> just a note 20:26:21 <chlorelium> once we get the license (in a week) 20:26:32 <chlorelium> we'll have to go to the LCBO with the license to do the purchasing 20:26:45 <chlorelium> whomever is bringing alcohol can't just pick up a bunch and then bring it 20:26:58 <chlorelium> there's something about the LCBO keeping track of sales 20:27:15 <hottuna> ok. that shouldn't be too much of a problem. 20:27:21 <chlorelium> I think they want to make sure you're not buying $1K of beer for a single event :) 20:27:30 <chlorelium> the license will probably get mailed to the lab 20:27:35 <chlorelium> I can get in touch when it does. 20:27:44 <hottuna> splendid 20:28:07 <hottuna> **** 3) **** 20:28:08 <hottuna> 3) I2PCon: Allow photos without explicit consent? 20:28:13 <chlorelium> so 20:28:23 <hottuna> Does anyone have a strong opinion? 20:28:31 <chlorelium> Hacklab default policy has almost always been "not without explicit consent" 20:28:47 <chlorelium> we can suspend that, however there's a good chance there will be members in the space who are not there for the con who might not want their pictures taken 20:29:04 <hottuna> alright, I guess that makes this choice a whole lot easier for us. 20:29:19 <chlorelium> We could have colour-coded nametags or something to communicate consent, if people like that idea. 20:29:31 <hottuna> Does anyone have any problems with not allowing photos to be taken? 20:29:41 <hottuna> (without explicit consent) 20:30:26 <hottuna> Does anyone want to add anything to 3)? 20:30:46 <dg> 3) being photo consent? 20:30:49 <str4d> I think explicit consent is fine 20:30:52 <hottuna> yes 20:30:53 <z3r0fox@oftc> It'll have to be made clear at the door, because phones 20:31:07 <lazygravy> str4d: that method seemed to work good at HOPE. 20:31:10 <EinMByte> I agree, some people will not want their picture taken 20:31:20 <dg> As long as explicit consent is fine and there's an understanding that people will remove pictures if asked 20:31:23 <chlorelium> z3r0fox: sure, we'll make a sign 20:31:27 <RN> yes 20:31:33 <RN> I missed all of three 20:31:44 <hottuna> excellent 20:31:56 <str4d> The nametag idea is a nice one. Maybe the Eventbrite page could have a tickbox for consent (yes/no/undecided) 20:32:14 * psi scrolls 20:32:26 <chlorelium> str4d: that's been done for non-hacklab events before 20:32:37 <EinMByte> str4d: good idea 20:32:39 <chlorelium> it doesn't even have to be a nametag, so much as a coloured piece of paper 20:32:46 <str4d> Nametag with green == fine. Without == must ask. 20:32:50 <str4d> chlorelium: nice 20:32:53 <RN> I have something to add to three and will just spam-paste it about 9 lines... 20:33:07 <hottuna> str4d, chlorelium: i'm not sure I would like to organize all of that I'd rather keep it barebones and like a simple rule 20:33:10 <RN> make an itoopie mask that people who don't want to be photographed can hold up in front of their face when picture is taken.... 20:33:10 <RN> easier than trusting someone else to photoshop the itoopie mask in later 20:33:10 <RN> mascott exposure == good pr | fun | inexpensive 20:33:10 <RN> requrired materials (assembly requrired) 20:33:10 <RN> paper plates 20:33:11 <RN> yellow spray paint 20:33:15 <RN> large tounge depressors 20:33:17 <RN> staples (that go through wood) or glue/tape 20:33:19 <RN> black marker or black paint & brush 20:33:39 <hottuna> RN: If anyone wants make a mask, that would be perfect! 20:33:46 <chlorelium> :D 20:33:49 <RN> give them out at the door... it starts the conversation about photos 20:33:55 <psi> are masks allowed still? 20:33:59 <hottuna> i'm putting it in the sure, why not bin. 20:34:02 <psi> like, anti protest laws etc 20:34:12 <dg> I imagine it's ok in a private space 20:34:17 <hottuna> we're not protesting. I think. and also indoors. 20:34:26 <psi> okay 20:34:27 <hottuna> anyway, can we move on? 20:34:35 <hottuna> **** 4) **** 20:34:35 <str4d> And it's not a mask as much as a masque 20:34:48 <hottuna> 4) I2PCon: Allow videos? 20:34:48 <hottuna> Video livestream? 20:34:58 <chlorelium> psi: the mask laws don't apply 20:35:01 <dg> Yes yes yes yes yes if somebody is willing to do it. 20:35:07 <chlorelium> ianal, but I'm pretty sure of that one :P 20:35:13 <str4d> Videos / livestream partly ties in to #3 20:35:18 <lazygravy> Will the speakers be okay with this? 20:35:25 <dg> Make it clear that it's being recorded and indicate where people can sit if they want to be free from cameras 20:35:26 <hottuna> I don't think we have anyone willing to do all of the video work. 20:35:31 <hottuna> Nor do we have the equipment. 20:35:34 <z3r0fox@oftc> Since the expert videographer couldn't make it, I could set a couple HD cams up to point at the presenters to save the presentations for later. But there were some reervations. 20:35:37 <EinMByte> I think we definitely need a lifestream, as I suggested earlier 20:35:37 <dg> zzz mentioned something for Twitter 20:35:46 <EinMByte> *live 20:35:48 <RN> I'm not talking about wearing a mask... but I think we've moved on... 20:35:52 <str4d> dg: Periscope 20:35:57 <dg> str4d: That's it 20:35:59 <zzz> I propose to just periscope the talks from the @i2p account from my phone. I have a baby tripod and phone mount 20:36:25 <zzz> a real tripod would be better if anybody can bring one 20:36:29 <str4d> Does Periscope allow video to be saved, or purely an ephemeral livestream? 20:36:41 <RN> is periscope persistant? 20:36:44 <zzz> dunno 20:36:50 <hottuna> z3r0fox: if I could leave the responsibility of making video happen on your shoulders (including the work afterwards) 20:36:56 <dg> I might be able to just dump the stream anyway 20:36:59 <hottuna> i would be pretty happy about it 20:37:15 <z3r0fox@oftc> zzz: Is that something that could be good enough to edit for Youtube? I have 1 tripod, two HD cams, can get another tripod for 2 camera shoot if needed then I'd volunteer to editand put on Youtube or distibute provately, whatever 20:37:26 <hottuna> if not and no one else is stepping up, we're not going to have video. 20:37:50 <psi> if we do video we should also have an eventual i2p torrent 20:38:11 <hottuna> z3r0fox: so that means you'd go the full length and organize all of it? 20:38:14 <zzz> i've just played with periscope for a couple minutes. Not an expert. 20:38:16 * RN agrees with psi 20:38:29 <z3r0fox@oftc> hottuna: Yeah, it's not a big deal, simple edits. I just wouldn't want to lose document of presentations, assuming presenters are okay with being filmed. 20:38:34 <zzz> If we have nobody to do anything better, periscope is our fallback 20:38:38 <hottuna> psi, I agree about distributing it through bittorrent. 20:38:39 <dg> Woo! livestreamer (a Python tool) supports Periscope (http://docs.livestreamer.io/plugin_matrix.html). I and others could easily dump the stream to disk with it. 20:38:41 <iRelay> Title: Plugins Livestreamer 1.12.2 documentation (at docs.livestreamer.io) 20:39:09 <RN> nice find dg 20:39:13 <z3r0fox@oftc> hottuna: Yeah, not much equipment to set up. I'll talkk with chlorelium about sightlines and warning people about being filmed offline 20:39:13 <hottuna> dg, livestreaming is a bit more work to make actually work. 20:39:28 <str4d> Okay, so we have zzz's phone and two HD cams from z3r0fox. More than enough to get video 20:39:34 <hottuna> z3r0fox 20:39:35 <hottuna> sounds good 20:39:37 <dg> hottuna: Yes, but if we have to use periscope via zzzphone, persistence isn't an issue. 20:39:42 <RN> although a secondary recording kept on the periscoping device would be ideal in case of stream outages.... 20:39:46 <str4d> Pertinent issues: 20:40:01 <str4d> a) Each speaker would need to give consent/no 20:40:15 <hottuna> re live streaming: Does anyone want to assume the responsibility of making that happen? 20:40:44 <str4d> b) Cameras need to be set up such that they either only film the speakers, or provide plenty of blindspots for attendees who don't want to be filmed. 20:40:46 <hottuna> str4d, a) I think we could handle that at the event (if we don't have any complaints earlier) 20:40:49 * RN passes note to hottuna and chlorelium "make sure to give zzz's device highest QOS and firewall clearance... " ;) 20:40:57 <chlorelium> str4d: that's doable 20:41:04 <chlorelium> lol 20:41:09 <str4d> c) We would also want to record the presentation itself, via a screen recorder 20:41:10 <zzz> I'll do periscope. with my fancy $1 tripod and $4 mount 20:41:11 <chlorelium> I'll talk to ops :) 20:41:16 <dg> zzz: showoff 20:41:26 <str4d> (so it can be spliced into the final edit) 20:41:34 <z3r0fox@oftc> str4d: Good point about the slide decks, hmm 20:41:55 <hottuna> I guess a screen recorder could be set up. 20:42:14 <dg> decks is going to be easy, we can just ask them all to provide at the end 20:42:17 <str4d> It *could* be handled post- if we had the slides themselves, but probably easier to just edit a third video stream in rather than inserting slides 20:42:19 <z3r0fox@oftc> str4d: I could just use the slides probably unless the presentation's animated 20:42:25 <hottuna> z3r0fox: could the video be made without a screen recorder (but with the presentations crammed in there somehow)? 20:42:34 <hottuna> z3r0fox: perfect 20:42:55 <hottuna> So far I haven't had any takers on organizing live-streaming 20:42:56 <z3r0fox@oftc> hottuna: yeah I would just pull them in as images on another video 'channel' in kdenlive 20:43:06 <dg> At CCC, the recorders tend to just alternate between the speaker and the presentation as for when it is pertinent. 20:43:11 <zzz> if you all want to get your questions answered about periscope, install it on your phone and play around with it. follow the @i2p acct and i'll do a test later in the week 20:43:13 <EinMByte> slides should probably be uploaded somewhere 20:43:15 <str4d> yeah, could just display static slide from PDF/PowerPoint/whatever while playing audio from another video stream 20:43:20 <hottuna> So unless that changes, we won't have it. Which isn't a problem. 20:43:24 <dg> They show the slide for long enough for you to read, show the speaker when they get excited/haven't changed slide in a while, then go back to the slide, etc 20:43:32 <dg> hottuna: zzz is doing periscope 20:43:45 <hottuna> zzz, are you doing periscope? 20:43:49 <zzz> your phone will bleep at you when I go live ;) 20:43:50 <dg> yes 20:43:56 <dg> <&zzz> I'll do periscope. with my fancy $1 tripod and $4 mount 20:44:04 <zzz> yes 20:45:06 <zzz> if zerofox has a tripod for me that would be even better. would keep it from being knocked over, but not req'd 20:46:23 <z3r0fox@oftc> zzz: Just have one at the moment, I was going to look into getting a second one used for cam 2 (second shot angle)... but I may have oneof those small tabletop ones somewhere as well 20:47:00 <zzz> ok. bring duct tape ;) 20:47:11 <hottuna> ok. thats confirmation enough 20:47:13 <hottuna> i'm leaving it in your hands 20:47:13 <hottuna> alright, anything else regarding 4)? 20:47:13 <hottuna> *** 5) **** 20:47:13 <hottuna> 5) I2PCon: Arrange schedule of event 20:47:13 <hottuna> I can't say I ahve a lot to say about it yet, but the contents of day#1&&day#2 is as follows 20:47:14 <hottuna> 15 Aug 20:47:14 <hottuna> tentative time: 2PM - midnight Not necessarily in this order 20:47:15 <hottuna> Nick Johnston: "TOS and PII - What happens to your data when the company gets bought and sold?" Different terms of service from popular web apps 20:47:18 <hottuna> Keynote: Guest speaker 1 (1 hour) (before cryptoparty or after?) "Privacy vs. Intelligence - Why can't we all just get along?" 20:47:21 <hottuna> Dinner break - where/when? 20:47:21 <hottuna> Short I2P General presentation, by zzz: "Growing the Network, Spreading the Word" 20:47:23 <hottuna> Cryptoparty presentation, by ?? (j?) 20:47:23 <hottuna> Cryptoparty, by j (how long?) 20:47:25 <hottuna> 16 Aug 20:47:25 <hottuna> tentative time: 12AM - 8 PM Not necessarily in this order 20:47:26 <hottuna> Confirmed guest speaker 2 (1 hour) "I2P Monitoring and Filtration" (requested time: early) 20:47:29 <hottuna> Confirmed guest speaker 1 (1 hour) "Anonymity protocols and malware - Why they fail" 20:47:31 <hottuna> I2P Technical presentation, by zzz: "The Connection Limit Challenge" 20:47:33 <hottuna> I2P Technical discussion, led by (zzz??) Topics TBD 20:47:34 <hottuna> I2P App Dev Intro, by psi 20:47:35 <hottuna> The Agony and the Ecstasy of I2P on Android, by str4d (via skype) 20:47:36 <hottuna> i2pd presentation by orignal Title: "i2pd"; requested time: 15 minutes 20:47:38 <hottuna> Roadmap meeting. led by zzz: When is 1.0? Crypto migration schedule (RI, snark) (EC vs. Ed), LS2, NTCP2, new DH, Java 7, SAM 3.2, Jetty 9, 12-month plan 20:47:41 <hottuna> Organizational meeting, led by zzz: Finances, roles, PR, servers and services, CCC planning 20:47:43 <hottuna> Dinner break - where/when? Order sandwich/pizza delivery? Guest speakers probably need to be before the break, as they may be flying out. 20:47:44 <hottuna> 20:47:45 <hottuna> forgive the slightly chaotic nature of it at the moment 20:47:46 <hottuna> sorting it out and fixing it is what's going to happen next 20:47:51 <hottuna> there's not much to add to 5), but now you all know what I know. 20:47:51 <hottuna> does anyone have anything else to add to 5)? 20:48:13 <hottuna> everyone is aware of what they're going to do/speak about? 20:48:34 <dg> is orignal OK now? 20:48:36 <psi> i still need to flesh out my talk all the way 20:48:37 <EinMByte> seems good, should be online somewhere though 20:48:46 <hottuna> dg, he was always ok for a short talk? 20:48:49 <dg> EinMByte: it is 20:48:57 <psi> i was thinking workshop but it seems like it's a talk 20:49:01 <dg> hottuna: he was reluctant to speak at all, and wasn't sure what to say 20:49:13 <dg> I think he might need a bit of prompting for subjects 20:49:19 <psi> probably easier to do a talk 20:49:20 <EinMByte> dg: link? 20:49:34 <hottuna> psi, would a short talk be ok? we could move it to the crypto party part of this? 20:49:59 <hottuna> dg, ok. I'm going to have to confirm orignal a second time. 20:50:07 <hottuna> i will do it OOB from this meeting 20:50:19 <dg> EinMByte: `http://trac.i2p2.i2p/wiki/MeetupToronto2015` 20:50:20 <psi> cryptoparty time makesss sense 20:50:28 <dg> i2p2.de if you're in the clearnet, but why are you? ;) 20:50:34 <EinMByte> dg: thanks 20:51:19 <hottuna> ok. next topic? 20:51:30 <chlorelium> question: how much of this is i2pcon and how much is cryptoparty 20:51:38 <psi> for my workshop i was going to have people write the example echo client serve 20:51:41 <hottuna> ehm. good question. 20:51:52 <chlorelium> like, are we running a cryptoparty as a separate event, or are we just having the TC folks give presentations, or what? 20:51:54 <hottuna> we don't have enough crypto party stations at this point 20:52:02 <hottuna> so it's going to be heavily I2PCon 20:52:13 <hottuna> and a crypto party to the etent we can find crypto party volunteers 20:52:31 <dg> if anyone is willing to help others setup popular crypto tools like OTR, obviously I2P, Tor, etc., then that'd be appreciated 20:52:36 <chlorelium> so this sounds like i2pcon with some involvement from TC, rather than one event nested inside another 20:52:41 <dg> Tails and that sort of thing. 20:52:59 <hottuna> chlorelium, the crypto party bit of day#1 will probably be scheduled for the lunch break and onkly be like an hour or two 20:53:51 <chlorelium> hmm 20:53:52 <chlorelium> okay 20:54:09 <chlorelium> so hottuna mentioned irl just now that more volunteers are needed for the cryptoparty aspect 20:54:22 <chlorelium> TC is the best for that, I'm not able to help so much in that area 20:55:06 <chlorelium> not sure how everyone wants to run that. 20:55:42 <EinMByte> Can we go to 6)? I have some comments and must leave soon 20:55:47 <chlorelium> you could run the cryptoparty as sort of a socialization session 20:55:51 <chlorelium> sure 20:55:56 <hottuna> EinMByte, sure 20:56:03 <hottuna> **** 6) **** 20:56:08 <hottuna> 6) dogecoindark.i2p home page request 20:56:17 <EinMByte> The website uses a lot of "external" stuff 20:56:36 <EinMByte> That is, it uses resources from various non-i2p websites 20:56:48 <dg> The owner didn't really get the problem with that, but after speaking with him, he agreed that it's problematic in some cases. He felt it was ok to keep Facebook/Twitter share buttons. 20:57:01 <hottuna> zzz, EinMByte 20:57:05 <zzz> this is my agenda item, hottuna may i have the floor? 20:57:25 <hottuna> zzz, please 20:57:28 <EinMByte> Also, we already have anoncoin.i2p. Do we really need more cryptocurrency links? 20:57:43 <zzz> thank you hottuna 20:57:53 <zzz> the request is here `http://zzz.i2p/topics/236?page=2#p9999` 20:58:03 <iRelay> Title: zzz.i2p: How to get my Eepsite added to the Router Console home page (at zzz.i2p) 20:58:06 <zzz> in the form of answers to the questions in the first post of that thread 20:58:16 <zzz> is the operator of the site here? 20:58:29 <dg> no, i've pinged him in another chan, he's been idle for 5m so give him a moment 20:59:50 <EinMByte> Note also that the website needs javascript to load, which may be a problem for some people (like me) 21:00:11 <zzz> ok, while we wait, does anybody have any comments pro or con? 21:00:48 <hottuna> i don't really know what the website is 21:01:08 <dg> It's a cryptocoin which supports I2P 21:01:24 <hottuna> is it straight up dogecoin? 21:01:34 <zzz> re: 1MB's comments, we don't have external resource links or js use as criteria for rejection at the moment 21:01:37 <dg> no, it's dogecoin forked to have I2P support 21:02:05 <EinMByte> The main problem (appart from technical stuff which can be fixed of course) I see is that we already have anoncoin on the homepage 21:02:09 <zzz> let's go back to the basics. is this of general interest to the i2p community? 21:02:11 <EinMByte> which is a very similar project 21:02:29 <EinMByte> So I'm not sure if we need another cryptocurrency on the homepage 21:02:52 <dg> "We need more of everything" -- I don't know if it's a bad thing to have more than one. Got to account for the bus, and the bus almost hit Meeh.. he was gone for a while and Anoncoin is only recovering now. 21:03:06 <zzz> we don't ever want just one of anything, and ANC is on life support anyway 21:03:26 <EinMByte> I agree that "we need more of everything". But I don't think that applies to the homepage 21:04:09 <zzz> does anybody here use dogecoindark? 21:04:41 <zzz> anybody have any other comments? 21:04:43 <dg> abyss does, but he's not in here (and doesn't appear to be around at the moment). He runs a market. 21:04:52 <dg> I'm on the fence. I don't really mind. 21:05:42 <zzz> anybody strongly in favor or strongly against? 21:05:52 <EinMByte> Well, if there is interest from other people I'm ok with it BUT only if the external resource issue is resolved 21:05:58 <hottuna> im mildy in favor 21:06:08 <EinMByte> (until then, strongly against, after that neutral) 21:06:27 <psi> can i be strongly indifferent? :D 21:06:34 <hottuna> doesn't hurt. I quess the fact that is depends on lots of external stuff is kind of bad. And there should be some kind of warning perhaps 21:06:38 <EinMByte> That said, there should be a ruled wrt to external resources because it's a pretty serious problem 21:07:12 <zzz> so you think home page eepsites should not load clearnet css/images? should that be a criterion? 21:07:32 <hottuna> possibly? 21:07:45 <EinMByte> zzz: I think no eepsite should do that yes. Especially not the ones on the home page 21:08:13 <dg> it shouldn't be a blanket. if they have a good excuse we might allow it, not that I can think of any 21:08:13 <EinMByte> In this case, it's probably not intentionally malicious 21:08:22 <EinMByte> But it could be 21:09:25 <RN> I agree that outernet resources should be strongly discouraged 21:09:25 <zzz> it's not a good user experience though 21:09:25 <zzz> ok let's table this topic without a final decision for now 21:09:25 <zzz> back to you hottuna thank you 21:09:25 <hottuna> ok :) 21:09:39 <hottuna> **** 7) **** 21:09:41 <hottuna> 7) I2PCon: donations 21:09:51 <EinMByte> Didn't zzz already comment on this? 21:09:57 <EinMByte> Anyway, bye. 21:10:05 <hottuna> EinMByte, cya 21:10:42 <chlorelium> So originally we were told that all donations collected during the con would be given to the hacklab 21:10:54 <chlorelium> this came from dnj, through f3ndot 21:11:02 <chlorelium> dnj and I discussed this the other day as well 21:11:19 <chlorelium> It's not actually a big deal though; if i2p wants some/all of the donations, we can arrange for that 21:11:21 <zzz> I don't recall anybody promising that 21:11:26 <dg> nor do I 21:12:29 <chlorelium> I'm just going to have to tell the hacklab membership. I doubt they'll be particularly upset 21:12:29 <zzz> hottuna, did you make that promise? 21:12:29 <chlorelium> hmm, interesting. so there's a bit of broken communication somewhere. 21:12:29 <dg> I think it's reasonable to give a contribution for the services but I don't remember a commitment 21:12:29 <hottuna> no. It must've come up between dnj and f3ndot 21:12:29 <hottuna> I havent really touched the topic of donations before 21:12:39 <hottuna> So, what are our requirements for donations? 21:12:42 <hottuna> Do we have ny? 21:12:43 <hottuna> *any 21:12:43 <hottuna> Do we care? 21:12:55 <hottuna> Could we have separate donation boxes? 21:12:59 <zzz> i propose we have a single bucket and we split it 3 ways i2p/TC/hacklab after covering booze costs 21:13:13 <hottuna> Or one with which we split? 21:13:23 <dg> boxes sounds good but risks saturation of any funds.. a bucket would be good 21:13:25 <hottuna> zzz, that sounds good to me. 21:13:37 <hottuna> :p 21:13:37 <chlorelium> zzz: if we have the donation bucket cover booze before it's split, we need a $75 event permit 21:13:38 <dg> i'm sure the topic of I2P finance/project scale will come up in the talks which means people may be willing to donate something anyway 21:13:41 <zzz> we are paying for the hacklab services already 21:13:54 <hottuna> does anyone mind the idea of splitting the contents of the donation box? 21:13:57 <chlorelium> ontario law is that the hosting org needs to absorb all alcohol costs 21:14:10 <zzz> who is the hosting org? 21:14:12 <dg> if people really want to give to us, they can do that 21:14:19 <dg> zzz: oh. then between i2p/tc depending on how much tc helps with 21:14:41 <zzz> whose name on the permit? 21:14:44 <chlorelium> zzz: hacklab is on the application 21:14:47 <hottuna> so the donations aren't tied to booze. and let's not say that they are. it would just be a problem for everyone involved. 21:15:51 <zzz> yeah but you realize we can't give you 1/3 of gross 21:17:07 <hottuna> zzz, are you saying that we don't want to hand 1/3rd over to hacklab? 21:17:07 <zzz> so hacklab, not i2p, is buying all the beer? 21:17:07 <zzz> who is buying the beer? 21:17:07 <hottuna> technically yes, practically no. 21:17:08 <chlorelium> ^ this 21:17:18 <hottuna> eche|on, or someone will walk to the booze-store with the permit and buy what we need. 21:17:26 <zzz> ok then lets not get all techical/practical about donations 21:17:46 <str4d> Okay, so hacklab is being paid for venue hire, and will increase their invoice to cover their beer costs, no? 21:17:59 <hottuna> str4d, no. 21:18:09 <hottuna> we're paying for beer. 21:18:11 <str4d> Then I'm confused 21:18:20 <hottuna> it will come out of eche|ons pocket 21:18:27 <str4d> hottuna: I was speaking technically 21:18:34 <hottuna> hacklab isn't monetarily involved in it 21:18:43 <chlorelium> str4d: that's understandable, the permitting process is ridiculous. incidentally, I apologize in advance for how complicated all of this is. 21:18:44 <str4d> (since they are required by law to cover it, no?) 21:19:09 <hottuna> ah. technically they're buying booze, practically we (echelon) are 21:19:17 <str4d> I just want to make sure that asses are covered 21:19:21 <str4d> K 21:19:26 <chlorelium> pretty much. you can take the permit to the LCBO, or we can do it 21:19:30 <chlorelium> as long as the costs are covered. 21:19:52 <hottuna> i think we have this sorted out well enough. 21:19:55 <str4d> So on any invoice, it would appear as "venue: $X. booze: $Y. Already paid: $Y. Due: $X." 21:19:59 <str4d> K 21:20:03 <chlorelium> you're renting the lab space, essentially, which in this case makes you a representative of the venue. or that's what I'm going to say if anyone asks. 21:20:24 <chlorelium> str4d: sure. we generally don't invoice people, but that can be arranged no problem. 21:20:29 <zzz> so i'm back to my original proposal, we have a single donation bucket, and that above and beyond certain (cough) expenses, we graciously split the rest, if any, 3 ways with TC and hacklab 21:21:16 <str4d> chlorelium: not sure if invoices are required by law, is the thing. You could say better than me :) 21:21:31 <hottuna> zzz, do we really want to go about it that way. 21:21:33 <zzz> assuming TC wants any $$ 21:21:38 <hottuna> i'd rather do it properly. 21:21:44 <dg> what is properly? 21:22:02 <zzz> ^^ what is properly, indeed? 21:22:02 <chlorelium> zzz: incidentally, how much did you discuss renting the lab space for back in april (or whenever this was worked out)? 21:22:05 <zzz> let's hear your proposal 21:22:15 <hottuna> properly as not have any boze money taken out of the donation box. 21:22:21 <zzz> chlorelium, tuna did the negotiations 21:22:22 <hottuna> my proposal is we split it 3 ways 21:23:01 <zzz> if you don't want to take booze money taken out of donations, then let's spend $50 more and sell the beer 21:23:17 <hottuna> does anyone want to stand there and sell beer? 21:23:42 <zzz> otherwise i2p is giving several dollars to TC and hacklab for every beer that we give away! 21:23:43 <str4d> If we spend $50 more, then we *can* take booze money out of donations 21:24:02 <str4d> (IIUC) 21:24:16 <zzz> or else have three buckets 21:24:23 <hottuna> str4d, I guess that is correct. but do you really know that we'll get 50$ in donations? 21:24:39 <hottuna> i think we're overthinking this. 21:25:05 <hottuna> the donations are _not_ going to be anywhere near the expenses we've had putting this event on 21:25:33 <zzz> giving 2/3 of our donations away starting at first dollar, when we're paying for the beer is a terrible idea 21:25:34 <hottuna> we're talking about $50-$100 worth of beer. 21:25:38 <hottuna> that's not a lot. 21:25:43 <chlorelium> hey 21:25:45 <chlorelium> so 21:25:47 <chlorelium> let me check the regulations 21:25:54 <chlorelium> I think I need to re-read some wording 21:26:05 <chlorelium> essentially, we can't tell people to donate to cover beer cost 21:26:18 <chlorelium> if people donate and we take money out of the pot to cover that, it might be fine 21:26:26 <chlorelium> the wording is ambiguous in the doc I read 21:26:31 <chlorelium> as for splitting the pot 21:26:52 <hottuna> chlorelium, if that is legal, let's do that. 21:27:04 <chlorelium> do it whichever way you would like. I'm not hung up on it. $150/day was pledged by i2p/tc for use of the space, and I'm happy for that 21:28:17 <str4d> There's also the fact to consider that hacklab is being paid for services rendered, vs. TC and I2P effectively volunteering. 21:29:30 <chlorelium> str4d: absolutely 21:29:40 <chlorelium> okay, here's the wording from the agco permit. 21:29:44 <chlorelium> Will alcohol be sold? 21:29:44 <chlorelium> You must answer yes to this question if you are 21:29:44 <chlorelium> collecting money for alcohol either directly, through 21:29:44 <chlorelium> the sale of alcohol or drink tickets at the event (e.g. 21:29:46 <chlorelium> cash bar, sale of drink tickets), or indirectly through 21:29:49 <chlorelium> the sale of admission, membership fees or the collection 21:29:51 <chlorelium> of money for alcohol before the event. 21:29:54 <chlorelium> so I think we're in the clear 21:30:08 <hottuna> So it's all basically fine. 21:30:19 <chlorelium> I called AGCO about this and they gave me a really wishy-washy answer. so all is well, I think. 21:30:32 <hottuna> (donations - beer_costs) / 3 21:30:40 <dg> I don't think hacklab should get any donation cut 21:30:51 <dg> They're being helpful but we are paying them for services 21:31:01 <hottuna> dg, they're not making a lot of money here. 21:31:22 <dg> Can we pay more for the beer licence, include that in what we pay them, and split donations between I2P and TC (depending on how much help TC gives)? 21:32:30 <hottuna> dg, if we do a donation box, it's ok to subtract money from the donated amount to cover beer costs according to the text above 21:32:39 <hottuna> so we dont need a fancier license 21:32:44 <dg> oh, cool 21:32:45 <str4d> So while I have no objections to hacklab receiving some of the donations, perhaps the split could be e.g. 1:2:2? 21:32:51 <dg> (I didn't get any text) 21:32:56 <hottuna> I would like to give them a part of the donations since A) they were promised it (by J it would seem) 21:33:05 <zzz> this is going to be a lot more than $50 worth of beer. I'm going to drink $50 worth myself. 21:33:20 <dg> that's what I thought ;). people at hacker cons like beer. a lot 21:33:44 * fox reminds you all not to cheap out on beer or buy anything american 21:34:07 <chlorelium> so hottuna's laptop just craped out 21:34:21 <dg> let's not honor other people's promises 21:34:27 <chlorelium> so I just talked to two other hacklab board members 21:34:33 <zzz> I don't give j's promises to hacklab any weight, no. 21:34:49 <chlorelium> we're cool with just $300 for the space usage, and covering the $25 alcohol license if that's cool 21:34:53 <hottuna> B) because they're part of the same community we are. 21:34:57 <chlorelium> you can keep the donations 21:35:12 <chlorelium> and sorry for all of the miscommuncation :( 21:35:18 <hottuna> i would still like to split it 3 ways. 21:35:29 <hottuna> does anyone else want to split it 3 ways? 21:35:35 <zzz> I'm ok with 1/1/1 split after (cough) costs 21:35:44 <zzz> and with covering their $25 21:35:50 <str4d> hottuna: I suggested maybe 1/2/2 split 21:35:50 <hottuna> zzz, that's what im proposing 21:36:07 <str4d> (unless people don't like hard math :P) 21:36:17 <hottuna> str4d, let's not do anything fancy here. 21:36:28 <hottuna> i would prefer an equal split 21:36:43 <hottuna> doing anything else just implies a bunch of stuff. 21:37:23 <hottuna> have a managed to convince everyone of a (donations-beer)/3 split? 21:37:28 <chlorelium> to be clear: I'm very happy to host y'all here, I just wanted to make sure everyone was on the same page. I don't want to cause any rancor. The love of money is the root of all evil :) 21:37:40 <dg> ok, but let's have an emphasis on I2P's size and need for more donations during talks. People can seek out our donation info if they want to 21:37:59 <hottuna> Sure, let's cram it in there somewhere. 21:38:25 <hottuna> str4d, dg, zzz: is that ok? 21:38:34 <str4d> So to summarize, we have hacklab saying "We don't need donations", hottuna saying "You *will* take donations", and everyone else not really minding either way? :P 21:38:53 <hottuna> yes. that sums it up. 21:38:54 <str4d> For the record, I don't mind a 1/1/1 split 21:38:59 <chlorelium> str4d: pretty much :P 21:39:00 <dg> hottuna: ok from me 21:39:00 <hottuna> want to do it my way? 21:39:23 <str4d> (after (cough) costs) 21:39:23 <hottuna> ok. 21:39:29 <hottuna> yes. 21:39:31 <hottuna> ok. 21:39:41 <hottuna> ok I tihnk we're done here. 21:39:46 <hottuna> anything else? 21:39:51 <dg> in general or i2pcon? 21:39:56 <hottuna> either 21:40:02 <str4d> psi: you still around? 21:40:06 <zzz> yes 21:40:19 <dg> ok, i2pconish: 21:40:20 <dg> <+dg> Somebody a few days ago by the name of 'saltire' messaged me, inquiring about setting up a relay between OFTC and IRC2P for #torontocrypto. He hasn't messaged me since, and #torontocrypto has no relay (just ChanServ and I). Would saltire, or somebody else from the TC side, be able to set one up? 21:40:22 <dg> <+dg> I could probably do it because OFTC allows Tor, but I'd prefer a TC person. 21:40:38 <dg> hottuna: Could you speak to saltire for a follow-up? 21:40:43 <psi> str4d: yes 21:41:17 <hottuna> dg.. sure 21:41:20 <hottuna> one se 21:41:22 <hottuna> c 21:41:38 <str4d> If saltire was asking if they could set it up, they only have to ask the network ops and the owner of the #torontocrypto channel on Irc2P 21:41:45 <zzz> reminder that relays to irc2p require irc op permission (although dg is one) 21:41:52 <hottuna> dg, I pinged him. 21:42:01 <hottuna> im leaving the rest of this up to the two of you. 21:42:18 <hottuna> saltire is typically available on #torontocrypto @ OFTC 21:42:20 <dg> thanks, and thx for the reminder, i would like to liaison with them if they could get back to me 21:42:43 <dg> If nobody's too exhausted from 3h of I2PCon and donation shoving... 21:42:48 <hottuna> :P 21:44:00 <hottuna> ok 21:44:00 <hottuna> this meeting is officially over 21:44:00 <hottuna> baf's the meeting hammer

0.9.20 Release

Tue, 02 Jun 2015 00:00:00 +0000

0.9.20 contains many important bug fixes, and several changes to increase floodfill capacity in the network.

Routers configured for 32-64 KB of shared bandwidth may now become floodfill, and routers configured for 512 KB or more of shared bandwidth will have higher connection limits. These changes may cause your router to use more resources. If the router becomes too busy, the best way to reduce usage is to lower the bandwidth settings in your console. If that doesn’t help, you may now disable automatic floodfill on the advanced configuration page in the console.

Toronto Meetup

Tue, 02 Jun 2015 00:00:00 +0000

The I2P team is proud to announce that we are going to host a meetup in Toronto on August 15-16. A number of members of our community will be attending and are going to host talks, workshops and discussions about and relating to I2P. This event is not just for I2P people though, it’s meant for everyone.

If you’re curious about I2P, interested in privacy/cryptography/anonymity or just want to come by and talk to us, please do. This is an event for everyone. If you’re not familiar with any of these topics, come by anyway and we’ll show you how I2P works and what you can do with it.

I2P Dev Meeting - May 05, 2015

Tue, 05 May 2015 00:00:00 +0000

Quick recap

Present: cacapo, dg, eche|on, hottuna, psi, str4d, xmz, zzz

Meeting Log

20:00:23 <zzz> 0) Hi 20:00:23 <zzz> 1) Toronto meeting (Aug. 15-16) planning 20:00:27 <zzz> 0) Hi 20:00:29 <zzz> hi 20:00:35 <eche|on> hi 20:00:51 <psi> just about the time for the meeting? 20:00:53 <zzz> 1) Toronto meeting (Aug. 15-16) planning 20:01:03 <dg> hi 20:01:14 <zzz> 1a) review where we're at 20:01:19 <zzz> 1b) volunteers 20:01:32 <zzz> 1c) do we move forward 20:01:37 <zzz> 1a) review where we're at 20:02:00 <zzz> hottuna, please give us an update on the planning, venue, and projected costs 20:02:20 <hottuna> Hi@all 20:02:24 <psi> hi 20:02:50 <str4d> hi 20:02:53 <hottuna> So, we've reserved two 8-hour slots at hacklab in Toronto for the 15-16 Aug. 20:03:20 <hottuna> The slots are 150CAD each 20:03:46 <hottuna> This is the venue: https://hacklab.to/ 20:03:48 <iRelay> Title: hacklab.to - Toronto's hacker collective (at hacklab.to) 20:04:07 <hottuna> The initial plan is to have two separate events. 20:04:37 <xmz> hi 20:04:44 <hottuna> 15Aug: I2P general presentation + I2P Cryptoparty 20:05:28 <hottuna> 16Aug: Have a technical presentation leading into discussions about various upcoming issues 20:06:10 <hottuna> Ideally I'd like to have a better itinerary for both of these days by the end of this meeting. 20:07:09 <psi> is lodging self serve or is that "taken care of"? 20:07:13 <hottuna> Additionally we've through J@torontocrypto secured a lounge-like space in a house in toronto for other/late-night planning/hacking/etc 20:07:55 <hottuna> psi, lodging can be offered for free at said lounge (which is a house on the opposite side of toronto) 20:08:14 <xmz> transport to and from lounge? 20:08:46 <hottuna> Public transit shouldn't be too bad. Something like a 25 minute subway ride. 20:08:46 <xmz> I guess we arrange our own. I'll have a car so I can ferry a few folks 20:08:54 <eche|on> 8h slots, times? 20:08:55 <xmz> oh that's not bad 20:09:11 <eche|on> cars in a city... 20:09:25 <zzz> ok thanks tuna, i'd like to open it up for questions and comments now, before we get into details on the agenda or volunteers 20:09:28 <xmz> you have a point there eche|on 20:09:42 <xmz> toronto traffic can be quite bad 20:10:01 <eche|on> 2 8h slots are fine, times of those? and I assume we come, sit down, get power and WiFi 20:10:03 <zzz> anybody have any general questions or comments? 20:10:14 <eche|on> and some technical stuff provided 20:10:18 <dg> will there be streams, and are we expecting on advertising this? if so, how? 20:10:54 <hottuna> eche|on, 8h slots: they're evening slots so I think we'd have to be out of hacklab sometime around 00:00 20:10:54 <hottuna> J has offered to organize the crypto party part of 15Aug. 20:11:23 <eche|on> midnight is fine, which makes it 4pm to 12pm 20:11:32 <hottuna> eche|on: power, wifi, chairs, tables, etc are available 20:11:32 <xmz> that's good 20:11:48 <xmz> if there's enough upstream available streaming is definitely an option 20:11:52 <eche|on> fine for me so far. 20:12:17 <eche|on> streaming is not such a big issue, we do have root server with traffic free to distribute, if we want 20:12:26 <hottuna> xmz, I'm not sure they have a crazy internet connection. 20:12:42 <hottuna> also streaming might not be acceptable for privacy reasons 20:12:56 <hottuna> and additionally would be quite a bit of work to organize 20:13:01 <str4d> Yah, that's a topic up for discussion 20:13:01 <xmz> yeah 20:13:14 <dg> how about advertisement? 20:13:19 <eche|on> yeah, I am not in favour of streama, just twitter and instagram^^ 20:13:34 <str4d> But technically, it wouldn't be hard. We don't need 1080p upstream ^^ 20:13:36 <eche|on> ads, we do ads on zzz and forum already, or what ads? 20:13:49 <fox> so first one to hack the public wifi AP wins? 20:13:57 <hottuna> dg, J has offered to do a bit of advertisment, and since he's done a few crypto parties in toronto, i think we'll have no issues drawing a crowd. 20:14:06 <dg> ads for general public, i'm not sure how big a following the hacklab have? 20:14:14 <dg> hottuna: thanks, that's what I was looking for 20:14:14 <hottuna> the i2p twitter/website be helpful too 20:14:30 <dg> I am pleasantly surprised by how many can attend 20:14:48 <zzz> "j" is eager to fire up the publicity, i've asked him (via tuna0 to hold off until we have this meeting, figure out who is doing PR on our side, and can do a coordinated announcment 20:14:52 <hottuna> fox, a guest network is available 20:14:54 <eche|on> I am in favour of a I2P even twith "some" guest 20:14:55 <xmz> yeah I'm glad it's being held in Toronto. if it were anywhere else it would be hard for me to attend. 20:15:09 <dg> it'd be great if he could come here too. 20:15:12 <dg> (j) 20:15:38 <hottuna> dg, J is distracted by meatspace today 20:15:56 <hottuna> the one thing J asked us for is an itinerary for Aug16 20:16:02 <dg> hottuna: I don't think it'd kill to setup a bouncer! He has been saying he'll come for a while 20:16:41 <eche|on> so, sa/su each 4pm to midnight 20:16:42 <zzz> anybody have any other general questions or comments, or any objections to doing this at all? 20:16:58 <eche|on> I vote for I2P lunch on sunday before hacklab 20:16:59 <xmz> no objections only encouragement here 20:17:06 <xmz> that's a good idea 20:17:15 <psi> it's effectively sa to monday morning right? 20:17:24 <eche|on> It would be nice to get some I2P folks together and meet, anything else, a surplus in my view 20:17:52 <zzz> let's avoid the temptation to discuss small details. For example, i suspect the hours may change, the agenda isn't yet set, we don't need to talk about bouncer setup 20:18:02 <hottuna> eche|on, yes - as far as I know. That window might be shifted an hour back or forth though. 20:18:16 <eche|on> yeah, it is ok 20:18:38 <eche|on> so the lodge for lounge is for the night-swarmers to make through the night 20:18:41 <psi> hottuna: what is general talk vs technical talk? 20:19:03 <hottuna> psi, that is a good question. and something we will have to decide. 20:19:05 <eche|on> general talk: I2p, what it is, how it works, technical talk: what is the protocol 20:19:22 <eche|on> hottuna: but the lodge with sleeping plac is sa-mo, or? 20:19:30 <hottuna> for 15Aug, we'd like to target a more general crowd. So anything that non-i2p people would understand 20:19:31 <xmz> are there any guides/walkthroughs planned for people new to I2P? 20:19:33 <dg> s/kill/kill him/ 20:19:34 <str4d> I won't be in attendance (as stated before), but I have no high-level objections 20:19:34 <iRelay> dg meant: hottuna: I don't think it'd kill him to setup a bouncer! He has been saying he'll come for a while 20:19:34 <eche|on> and the lounge does make noise to the sleeping guys? 20:20:06 <hottuna> xmz, a crypto party which basically is a group walktrhough/workshop is planned for 15Aug 20:20:14 <xmz> that's great 20:20:33 <psi> I want to do a short i2p app dev intro 20:21:16 <psi> we should really show off the ease of developing with i2p <-- workshop idea 20:22:26 <hottuna> psi, and i2p app dev intro would be nice for 16Aug I suppose 20:22:30 <str4d> ++ 20:22:43 <str4d> That would dovetail nicely with Android 20:22:45 <hottuna> eche|on, re lounge: I would like to confirm the details about it with J, Sat-Mon does sound appropriate 20:22:45 <dg> that would be nice psi 20:22:45 <hottuna> str4d, would you like to talk about android? 20:22:45 <eche|on> in this case I go into my own hotel room ;-) 20:22:45 <psi> i'd need to drag along a copy of monotone so we don't wait 5 hours for it to sync 20:22:45 <zzz> yeah i envision sat. as a public thing, and sun. as a dev meeting / hackathon, open to public but probably just us. Also we could do a 2nd public presentation on Sun. if the first is "sold out" 20:22:45 <str4d> hottuna: it's probably a good idea to do so, what with me being the de-facto Android project lead :P 20:22:46 <eche|on> sounds reasonable, zzz 20:23:15 <hottuna> str4d, I'll sign you up for 16Aug and talking about android then? 20:23:36 <str4d> Yah 20:24:12 <hottuna> psi, I signed you up for an i2p app dev intro. is that ok? 20:24:22 <psi> yes 20:24:29 <zzz> ok let me transition to 1b) volunteers 20:24:44 <zzz> we've never done this before. It's not going to happen unless somebody is in charge. 20:24:44 <hottuna> danke. 20:24:57 <zzz> No one person can do it all. 20:25:19 <zzz> We need somebody in overall charge of this, and several people to own various pieces. 20:25:20 <eche|on> people in charge, I vote for: hottuna local contact to book the venue and the lounge, I pay 20:25:49 <zzz> If anybody thinks this will be easy... think again 20:26:08 <hottuna> i'm up for continuing doing general coordination, which is what I've been doing this far. 20:26:13 <zzz> and if we don't find enough people to volunteer, let's cancel the whole thing now before we go speding money 20:26:32 <zzz> so here's my list from my post, which may be over the top too much, but we can start here: 20:26:47 <zzz> - Overall Meeting Head Planner (??) 20:26:47 <zzz> - Finance (echelon) 20:26:47 <zzz> - PR / Marketing (psi) 20:26:47 <zzz> - Facilities / Logistics (hottuna) 20:26:47 <zzz> - Overall Schedule (??) 20:26:47 <zzz> - Crypto Party Planning (??) 20:26:49 <zzz> - Crypto Party Presentation (??) 20:26:51 <zzz> - Deep technical presentation (zzz) 20:26:53 <zzz> - i2pd presentation / planning session (orignal) 20:26:58 <zzz> - Android presentation / planning session (str4d via skype) 20:26:59 <zzz> - Roadmap / technical sessions lead (??) 20:27:01 <zzz> - Eating / drinking location picker (orignal) 20:27:03 <zzz> - Hotel / crash house picker (hottuna) 20:27:05 <zzz> - Snacks coordinator (echelon) 20:27:07 <zzz> - Stickers (echelon) 20:27:09 <zzz> - Video / audio recording (??) 20:27:53 <eche|on> I am in favour of not really planing much of the talks. we do have some volunteers in here to do some talks 20:28:18 <zzz> right. I don't want to do planning here at this meeting. I want to pick people in charge and let them do it 20:28:39 <zzz> and the overall person in charge can run all subsequent meetings 20:28:45 <hottuna> I'm volunteer for arranging the overall schedule too. 20:28:52 <xmz> cryptoparty planning will have to be co-ordinated with J right? 20:29:01 <xmz> or is he going to handle all of it 20:29:04 <hottuna> J has volunteered to organize the crypto party 20:29:17 <zzz> ok, so hottuna as the overall person in charge and the guy in charge of schedule? 20:29:52 <str4d> +1, he is best placed to keep track of it all 20:29:56 <eche|on> if he is up for it? 20:31:16 <zzz> ok hottuna? 20:31:16 <hottuna> im okay with that. it's probably easier that way 20:31:17 <hottuna> as for crypto party presentation, I'm not sure what it should contain 20:31:17 <hottuna> i am. 20:32:02 <str4d> hottuna: I assume this means you will definitely be in Toronto for the party? (It was in the air earlier) 20:32:02 <zzz> anybody ever been to a crypto party? 20:32:08 <psi> i have 20:32:22 <psi> as far as i can tell it's like a mini con 20:32:30 <hottuna> str4d, I'm planning to be in toronto. so unless some kind of disaster strikes I will be, 20:33:01 <cacapo> hi - echelon and i did a small cryptoparty at 29c3 20:33:16 <zzz> great. psi can we nominate you to work with J on both PR and the crypto party? 20:34:43 <psi> yup 20:34:43 <psi> (now that this is solid ima buy my travel stuff) 20:34:43 <hottuna> cacapo, eche|on: would you like to have part in the crypto party? 20:34:43 <hottuna> psi, do you have the contact details of J? 20:34:44 <cacapo> hottuna: sure I'm game 20:34:54 <eche|on> I was just a helper for I2P part, I will be in toronto, but mostly as a backup :-) 20:34:55 <str4d> hottuna: I assume this means you will definitely be in Toronto for the party? (It was in the air earlier) :P 20:34:56 <str4d> erk 20:34:58 <str4d> sry 20:35:10 <psi> hottuna: not at the moment 20:35:25 <hottuna> I'm not exactly sure about what has to be done. ideally you would coordinate that with J 20:35:28 <psi> hottuna: forward them to me when you have the chance 20:35:30 <str4d> psi: not solid until 1c) 20:35:38 <zzz> who would like to work on - or give - a presentation, on either day? 20:36:12 <psi> i'll help wingman a presentation if anyone needs it 20:36:13 <zzz> i can do one each day, but i think we should have several short ones, not one big one by one guy 20:36:28 <eche|on> right 20:37:37 <zzz> hottuna, looks like orignal had to leave, can you catch up with him later to see what he can volunteer for, maybe an i2pd presentation or technical session, or a trip to a bar/ 20:38:13 <hottuna> zzz, so psi and str4d offered two technical ones for aug16 20:38:17 <hottuna> zzz, i'll try to catch up with orignal, yes. 20:38:23 <zzz> anybody else want to volunteer for anything at this time? 20:39:56 <zzz> ok it sounds to me like we have the important assignments made. 20:40:06 <eche|on> not much, Ill be around 1 or 2 days earlier and have a look around 20:40:23 <zzz> so 1c) does it sound like we have adequate staffing to proceed on this? 20:40:33 <hottuna> i'd say so. 20:40:48 <eche|on> are we more than 5 persons who will be around? ;-) 20:41:14 <zzz> I want to make sure we don't put too much on tuna's back. Let's all help out to make this a success 20:41:33 <eche|on> yeah, make a plan on zzz.i2p about the talks 20:41:35 <zzz> ok if tuna isn't panicked then I guess we're in good shape 20:41:52 <hottuna> I'm not panicked. 20:41:54 <eche|on> and hottuna should gimme the contact to pay 20:42:11 <zzz> I expect hottuna will run several more meetings over the coming weeks and months to get ready 20:42:15 <hottuna> eche|on, could that be done in cash in meatspace? 20:42:27 <hottuna> I think we'll need wiki-page to organize around. 20:42:40 <eche|on> cash is also OK, but all I can pay in advance is better, my credit/debit card is not really unlimited^^ 20:42:53 <psi> i have a wiki that i can dedicate 20:42:57 <psi> potentially 20:43:00 <zzz> i want to add a 1d) financial support to the agenda 20:43:13 <zzz> 1d) financial support 20:43:32 <hottuna> may I suggest: https://trac.i2p2.de/wiki/MeetupToronto2015 20:43:33 <eche|on> we got money to give out. 20:43:49 <zzz> traditionally we've only reimbursed people $200 or so for conferences 20:44:19 <zzz> i hear some people may need significantly more in order to attend 20:44:28 <eche|on> str4d: your issue was mostly the money problem to attend? 20:44:44 <str4d> eche|on: no, timing 20:44:51 <zzz> what's the maximum we would be willing to give per-person? or alternatively, how much money would people need in order to attend? 20:44:51 <eche|on> ha, no, I do mix some names.. 20:44:52 <str4d> (well, money too) 20:44:59 <zzz> $500? $1000? $2000? 20:45:11 <eche|on> IMHO flights from europe are 1200 both ways 20:45:19 <eche|on> and IMHO thats what kytv needs to attend 20:45:33 <eche|on> if he/she can stay somewhere $cheap and good 20:45:45 <zzz> if anybody has a hard number they need, speak up now 20:45:53 <eche|on> kytv: now is your time. 20:46:09 <zzz> or, how much do people think is reasonable? 20:46:27 <eche|on> I think, we can pay a lot of different stuff, but I would like to pay more on travel cost and less on having booze on the event 20:46:35 <eche|on> (is it pronounced booze?) 20:47:13 <hottuna> eche|on, having people over is more important yes. 20:47:16 <psi> hm 20:47:23 <hottuna> (it's booze, yes) 20:47:28 <zzz> or, another way to ask, how much should we spend total on this event? 20:48:01 <eche|on> currently on the list to pay for me: location, some snacks/coffee/coffebreak, a dinner/lunch for I2P. 20:48:20 <psi> all my costs would be just transit and i would need to figure that part out, probably air, maybe bus/train 20:48:43 <zzz> would $10K be out of line to spend? 20:48:50 <eche|on> I would pay kytv (and any other dedicated I2P contributor) 1200 for the flight, and each other up to 500, if they want it 20:49:20 <hottuna> eche|on, that sounds reasonable 20:49:25 <str4d> $10k would need to be heavily justified 20:49:33 <eche|on> and that would sum up to 10k roughly 20:50:04 <str4d> But with good justification, I wouldn't be against it 20:50:59 <eche|on> ok, 5k-10k in that area 20:51:24 <hottuna> should we re-imburse the complete travel costs do something like 50% or 75%? 20:51:27 <zzz> what about up to $1500 reimbursement for core team members, and up to $2500 for 'special cicrumstances', i.e. you really need it 20:51:36 <eche|on> I would pay up to 10k, the only issue: if we do this an regular base, it is a bit hard to pay 10k each year 20:51:38 <hottuna> eche|on, i think something closer to 5k then 10k would be easier to agree on 20:51:56 <zzz> eche|on, remind us, how much money do we have atm? 20:52:10 <eche|on> wait a sec 20:52:37 <str4d> On current HoF: 44.6k euro and 537.7 BTC 20:52:50 <eche|on> roughly 41k euro, 534 Bitcoin and 700 Litecoin on my side 20:53:19 <eche|on> 534 btc each 210, LTC is 1.2 each 20:53:52 <fox> person experience for cheap room and board motel 6 has gotten much nicer accross north america 20:53:59 <xmz> I can help out with setup/teardown etc. 20:54:50 <hottuna> what type of expenses would we like to reimburse a person for? total expense for the trip? only flights? flights+hotel? 20:55:02 <fox> inn type place are nice if you want breakfast though 20:55:22 <zzz> usually we just do it no-questions-asked, whatever you spent money on 20:56:13 <str4d> But given the scale of this expenditure, we probably do want to have some reasonable restrictions 20:56:33 <eche|on> I vote for travel expenses 20:56:34 <zzz> sure. 20:56:41 <eche|on> as the lounge is cheap and available 20:56:55 <psi> hottuna: so to clarify would i or would i not have to personally book a hotel 20:56:59 <psi> (For me) 20:57:04 <xmz> Could have some setup for accepting donations at the event 20:57:04 <eche|on> and food/drinks is same like @home, if you want to 20:57:25 <hottuna> psi: you would have to do the booking. book whatever you like. echelon will reimburse you 20:57:33 <psi> okay 20:57:45 <zzz> how about max of US$ 1K for north americans, 1500 euros max for europeans, 2000 euros max for 'special circumstances' 20:58:20 <eche|on> zzz: fligst US to CAD are <1000$ ? 20:58:22 <cacapo> with 5K-10K and a lot of key persons in place why not call it a Summit - slightly more official 20:59:00 <zzz> shouldn't be more than $400 20:59:04 <zzz> but I haven't looked 20:59:12 <zzz> and it may be driving distance for some 20:59:44 <zzz> we've never reimbursed 100% for anybody 20:59:44 <eche|on> I want to note again and ask: if we do that amount, we need to clarify, the reimbursements for 32C3 and the next few events will be as usual ~200, if not some special stuff happens 21:00:03 <hottuna> eche|on, agreed 21:00:47 <zzz> I'm just throwing out proposals, somebody please agree/disagree too high/low 21:00:48 <eche|on> it is kinda unfair, but could be seen as a kind of advertising 21:01:00 <eche|on> zzz: I agree, with the added note 21:01:46 <zzz> look at it another way, i think we should spend at least 10% of our money a year. Maybe 15-20%. 21:02:04 <eche|on> hmm 21:02:19 <zzz> because 10 more years would be a long time at this 21:02:58 <eche|on> we got 7k donations in 2014 and spent 11k (in euro alone) 21:03:55 <hottuna> zzz, if wo do the percentile thing let's start low. 21:03:57 <eche|on> this year we got ~600 euro and spent 3k 21:04:21 <eche|on> 10% is nice for me currently 21:04:30 <eche|on> would need to convert some BT to again... 21:04:31 <zzz> including btc we have ~150K euros 21:05:00 <eche|on> I call BTC somewhat "play-stuff" and unless they are in in here, I do not really count them much. 21:05:30 <eche|on> sure, the exchange rate is 210 currently, but I will never be able to exchange 400 BTC at once. 21:05:38 <hottuna> I agree with eche|on. btc arent 100% reliable for doing that kind of math 21:06:10 <eche|on> so, with agreeing on max 10k for this event, Ill exchange some BTC 21:06:33 <eche|on> I just want to be on the safe side and have some kind of "reserve" in . 21:06:40 <zzz> you can offer people extra if they take rembursement in BTC 21:06:54 <eche|on> sure, I do this all the time. thats the benefit of BTC 21:07:08 <eche|on> you can pay folks with them, but you cannot rely on it. 21:07:50 <hottuna> eche|on, zzz, psi, dg: do we all agree on a 10k hard cap for expenses relating to this event? 21:07:53 <eche|on> but yeah, we do have the money 21:08:02 <zzz> ok how about this, we budget 10K euro for the total event. Actual per-person max depends on how many people go, "special cicrumstances" requests, etc., to be determined later 21:08:03 <psi> hard cap yes 21:08:20 <hottuna> zzz, sounds good. 21:08:44 <eche|on> Hmm, hard cap is interesting, but depends on the local costs for snacks^^ 21:09:07 <eche|on> we can hard cap the expenses for people to attend. 21:09:15 <eche|on> and that would be 8 or 9k? 21:09:24 <zzz> but everybody be smart. You can't drive to Toronto and book a $400 a night hotel and expect to get it all covered 21:09:55 <eche|on> zzz: travel expenses, or travel&hotel? 21:10:23 <zzz> dunno 21:10:35 <eche|on> also: list of people to prefer (aka: people who already did a lot, people giving a talk, other) 21:10:38 <hottuna> eche|on, given that there is a lounge available for free Im not opposed to the idea of only travel expenses 21:10:47 <zzz> usually it's flight + hotel, but we've never come close to a full reimbursement before so it didn't matter 21:11:39 <str4d> I think 10k budget for now, do a roll call so we know who *will* be going, then we will be better placed to budget reimbursement 21:11:50 <eche|on> I sum my opiono: cap 8k for travel expenses of participants, with some level of importance to the people 21:12:00 <zzz> ok 21:12:32 <str4d> (roll call from core people) 21:12:34 <zzz> let's wrap it up for now, we'll ask people to email echelon with how much they would need later 21:12:37 <hottuna> eche|on, agreed. 21:12:51 <hottuna> alright 21:12:54 <zzz> ok everybody who is going and wants reimbursement from the project say 'aye' 21:12:56 <zzz> aye 21:13:02 <eche|on> aye ;-) 21:13:04 <hottuna> https://trac.i2p2.de/wiki/MeetupToronto2015 now contains some information. 21:13:12 <psi> aye 21:13:19 <hottuna> if you signed up for a responsibility, please help maintain this page 21:14:17 <zzz> ok eche|on, please check with kytv later and see how much he would need to attent 21:14:22 <hottuna> cacapo ?? 21:14:24 <zzz> anything else on 1d? 21:14:47 <cacapo> hottuna: aye i'm going if I can wrestle down my boss 21:15:12 <cacapo> I'd happily take a small reimbursement in BTC 21:15:14 <hottuna> zzz, no 21:15:24 <zzz> it will take a few days to figure out who's going . 21:15:49 <zzz> for a couple people the reimbursement amount may enter into the decision, but for most probably not 21:15:59 <zzz> anything else on 1) ? 21:16:14 <zzz> any other (non-toronto) topics to discuss? 21:16:46 <zzz> first meeting in 6 months, gotta look for the baffer 21:17:15 <zzz> thanks to everybody and especially to the volunteers 21:17:26 <zzz> ahh there it is 21:17:40 <eche|on> great 21:17:49 <eche|on> time for bed now^^ 21:17:52 * zzz *bafs* the meeting closed

0.9.19 Release

Sun, 12 Apr 2015 00:00:00 +0000

0.9.19 has several fixes and improvements for floodfill performance. Many of you saw high CPU usage after 0.9.18 was released. This was caused by a combination of increased encryption usage, the big influx of Vuze users into the network, reduced floodfills due to tighter performance requirements, and some longstanding bugs. Things should be a lot better after most of the network has updated. As always, the best way to reduce CPU usage is to lower your bandwidth limits.

0.9.18 Release

Sun, 22 Feb 2015 00:00:00 +0000

0.9.18 contains several bug fixes and performance improvements. We have shortened the startup time, and reduced latency throughout our network protocols. We’ve increased the default connection limits for the fastest routers, and reduced the thread usage in i2ptunnel. UPnP fixes should improve handling of external device changes. CPU usage in high-bandwidth routers may be reduced thanks to some NTCP fixes.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

31C3 trip report

Tue, 20 Jan 2015 00:00:00 +0000

Attending: Apekatten , Echelon , Hottuna , Marielle , Meeh , Sindu, zzz

We were, for the second year in a row, at a great location in the Congress, in Noisy Square , right next to the EFF table. Being part of Noisy Square has really increased our visibility and helped many people find us. Thanks to Noisy Square and the 31C3 organizers for a great Congress.

We also thank Gabriel Weinberg and his fabulous search engine DuckDuckGo for their support of open source anonymity tools and their generous contribution to I2P in 2014. Funding from DuckDuckGo and others helped support our attendance at CCC. This is the primary annual meetup for I2P developers and it is critical to our success.

Android app releases

Mon, 01 Dec 2014 00:00:00 +0000

It has been some time since I last posted updates about our Android development, and several I2P releases have gone by without any matching Android releases. At last, the wait is over!

New app versions

New versions of I2P Android and Bote have been released! They can be downloaded from these URLs:

The main change in these releases is the transition to Android’s new Material design system. Material has made it much easier for app developers with, shall we say, “minimalist” design skills (like myself) to create apps that are nicer to use. I2P Android also updates its underlying I2P router to the just-released version 0.9.17. Bote brings in several new features along with many smaller improvements; for example, you can now add new email destinations via QR codes.

0.9.17 Release

Sun, 30 Nov 2014 00:00:00 +0000

0.9.17 is primarily a bugfix release, but it also continues our migration to stronger cryptographic signatures.

We have moved the news feed system used for the news on your console and the latest router version indication to a signed format using RSA 4096-bit keys for enhanced security.

New eepsites and servers will be ECDSA-signed by default, if ECDSA is available. There is now a warning in the console sidebar if ECDSA is not available. For RedHat users, we have reports of successful installs of the BouncyCastle Provider (bcprov) jar to add ECDSA support.

I2P Dev Meeting - November 25, 2014

Tue, 25 Nov 2014 00:00:00 +0000

Quick recap

Present: dg, eche|on, EinMByte, JekabsR, kytv, orignal, psi, str4d, zzz

Meeting Log

20:04:39 <str4d> Yo 20:04:44 <str4d> It's meeting time 20:06:47 <str4d> zzz, psi, kytv, Meeh, dg 20:07:30 <psi> it is? 20:07:39 <psi> ah tuesday 20:09:03 <zzz> present 20:09:48 <orignal> meeting? 20:10:11 <str4d> orignal: discussing Java I2P's todo list 20:10:35 <str4d> While we wait for others to show up: `http://trac.i2p2.i2p/wiki/Roadmaps/1.0` 20:10:41 <kytv> Present as well, though I'm usually useless when it comes to these things. 20:11:37 <str4d> I have adjusted the Gantt chart on the page above (that I set up for the 0.9.13-0.9.16 dev cycle) to show what I think we did. 20:13:30 <zzz> interesting 20:14:06 <zzz> multiple dests per tunnel <-- hasn't happened 20:14:22 <str4d> Hasn't? Okay, my bad. 20:14:27 <zzz> findbugs pass <-- has happened, but can always do it again 20:14:56 <str4d> Multi-sessions per I2CP - that hasn't happened either *derp* 20:14:56 * str4d fixes 20:15:48 <zzz> wow, we had a good year (imho) 20:16:38 <eche|on> yes, we had 20:17:14 <str4d> zzz: yeah, I called it part of the audit prep specifically, but you are right. 20:17:39 <zzz> investigate new DH <---- I would say only half done, w.r.t NTCP2 anyway 20:20:26 <str4d> Gantt doesn't easily show half-done :P 20:20:34 <str4d> Reload page, fixes 20:21:36 <str4d> Okay, so that is what we got done last cycle. 20:21:36 <zzz> not done then 20:23:45 <str4d> The purpose of this meeting is to start planning what is to be done next cycle. 20:23:46 <zzz> I would like to reiterate that a 3-5 release planning cycle seems to be very helpful in focusing our minds and our resources 20:23:47 <str4d> (When I update the Gantt chart, I will leave the half-done ones there and push them forward) 20:23:47 <str4d> At the previous meeting I asked attendees to come up with a few points each of things they want to see done on I2P, and around I2P 20:23:47 <str4d> Please can we paste those now? 20:24:21 <str4d> +1 20:24:36 <str4d> And now we have evidence for it! 20:26:15 <zzz> without getting into what's more important than what, I think almost everything that's shown and unfinished on the gantt chart is still important 20:27:01 <str4d> I agree. 20:27:07 <str4d> I still want to see what ideas people came up with over the last week, if any. 20:27:45 <str4d> Here's mine: `http://pastethis.i2p/show/jF2RkHwrIPkCb0yOpI7l/` 20:27:46 <iRelay> Title: Paste #jF2RkHwrIPkCb0yOpI7l | LodgeIt! (at pastethis.i2p) 20:28:07 <eche|on> I am out of options, I do see to get I2P out, with the help of bote android, i2p messenger is a option, a XMPP server, and syndie. Sorry, I still see syndie important. 20:28:27 <str4d> eche|on: great, thanks! 20:28:43 <str4d> Keep 'em coming :) 20:28:53 <eche|on> and with the android app there come restricted routes 20:28:54 <zzz> my list of new things: solving the red hat ECDSA problem, migrating to EdDSA, Jetty 9 / Java 7, expand the Vuze userbase, and more marketing / outreach / partnerships / embedding 20:29:36 <str4d> For logging perpetuity, I will write my ideas here too: 20:30:11 <str4d> Todo in I2P: Routerconsole UX analysis and redesign; Take ideas from Tor's HS 2.0 design and apply to I2P Destinations; Bandwidth scheduling. Todo around I2P: Website theme improvements; Implement I2P-Bote fetching relays; Research 20:30:23 <zzz> another one: orchid: fix it or kill it 20:30:32 <str4d> +100 20:31:13 <kytv> WRT the RedHat/Gentoo ECDSDA problem, maybe we could/should display a message in the sidebar (or logs) with a download link. Or maybe ask the user if 'we' should download it into ./lib 20:31:35 <zzz> another one: test improvements, test hardware, windows testing 20:31:58 <str4d> kytv: nice ideas (but discussing them can wait for another meeting :) 20:32:03 <zzz> another one: spend more money 20:32:36 <zzz> another one: China 20:32:58 <str4d> Between these ideas and the not-completed list on the page above, we have a good pool of potential projects. 20:33:34 <str4d> My goal is to get these projects tidied up, formalized and published on the website's todo page 20:34:11 <str4d> Having poked around other projects' todo pages, this is the format I am proposing: 20:34:11 <str4d> `http://pastethis.i2p/show/nvexU3ZvSFOI6L5DrrqM/` 20:34:12 <iRelay> Title: Paste #nvexU3ZvSFOI6L5DrrqM | LodgeIt! (at pastethis.i2p) 20:34:54 <eche|on> nice idea 20:35:10 <kytv> Ditto on Orchid 20:35:10 <kytv> My main "TODO around I2P" is with regards to testing. Not automated testing with software, per se, but any of our services going live without any sort of testing...just [poof], "it's live...dunno if it works though." 20:35:12 <kytv> In I2P: Making the Installer install to the user directory in Windows to avoid any sort of permissions problems. It should be easy, but I don't know how. 20:35:16 <kytv> Chrome did that (maybe still does it?) 20:35:41 <str4d> My ideal end result: users can go to the todo page and find a list of all the ideas we have for projects in and around I2P. 20:36:11 <zzz> another one: GSoC 20:36:14 <str4d> There will be a tag cloud up the top that they can click on to filter projects that require certain skils 20:36:17 <str4d> skills 20:36:21 <zzz> another one: summertime meetup 20:37:54 <zzz> another one: GNS investigation 2nd pass? 20:38:28 <str4d> mmm 20:38:54 <zzz> or maybe, just another discussion w/ those guys will do 20:39:09 <str4d> Right now, I am going to cull from the Gantt the tasks we have completed. 20:39:27 <zzz> can you save it and start a new one? 20:39:29 <str4d> zzz: which of the bottom few have been completed (SSU replay detection etc.)? 20:39:38 <str4d> Sure, I can. 20:39:49 <zzz> it's kinda nice to show that we actually accomplish things 20:40:19 <eche|on> zzz: most of the stuff was done by you IMHO 20:40:35 <EinMByte> id I miss the meeting? 20:40:37 <zzz> I think I've reported everything that was on the wrong side of completed or not 20:42:39 <str4d> New chart up 20:43:55 <str4d> zzz: which of the three down the bottom should be pushed forward? I think client locking is still an issue? 20:43:59 <zzz> I'd like to see much more planning and focus on the non-coding things in the next few months. Far too many things are either quite disorganized or not happening in anything approaching a disciplined or steady pace 20:44:09 <str4d> (client tunnel locking) 20:44:18 <str4d> zzz: I agree. 20:44:34 <str4d> This will IMHO be helped by working on the todo page. 20:44:56 <str4d> If we can explain the non-coding projects in a way that newcomers can understand and do, it also helps us. 20:44:59 <zzz> not 100% sure atm what that client locking item is, but i think it's still unfinished 20:45:08 <str4d> (Likewise for coding projects) 20:45:32 <zzz> yup 20:45:53 * str4d pushes streaming improvements forward too 20:46:03 <str4d> Can I cut SSU session replay detection then? 20:46:04 <dg> Do you mean the duplicate issues? 20:46:18 <dg> The way we'd get tunnels that don't unregister from I2PTunnel, and won't allow new ones? That sort of thing? 20:46:30 <zzz> str4d, I'll have to get back to you re: SSU replay, not sure atm 20:46:45 <dg> I'd like to see less tunnel death rather than throughput 20:46:59 <str4d> dg: that might be it. There is also the separate issue of the I2PTunnel startup locking the UI 20:47:29 <zzz> put 'tunnel death' on there as a new item, why not 20:48:01 <dg> str4d: Forgot about that! 20:48:03 <str4d> k 20:48:39 <zzz> I think the locking thing I have some unchecked in code for, been dragging along for 18 months or so, but still not right 20:48:40 <str4d> Next: look through the ideas above. Which ones should go on *our* 6-month sheet (ie. which should I add to Gantt)? 20:50:16 <psi> EinMByte: meeting in progress 20:50:21 <psi> (no) 20:51:51 <zzz> I suggest everything go on there for now, then we later talk about priorities, or let the gantt dependencies tell us what to do next? 20:52:52 <str4d> mmk 20:53:04 * str4d is pulling out the list from above and tidying it up now 20:53:08 <EinMByte> psi: oh great. 20:54:08 <psi> potential item: benchmark tunnel throughput and message drop rates 20:54:26 <str4d> EinMByte: do you have any ideas for our todo list? 20:55:15 <EinMByte> NTCP2, possibly. Although it would be long term 20:56:39 <str4d> EinMByte: for reference: `http://trac.i2p2.i2p/wiki/Roadmaps/1.0` 20:56:53 <EinMByte> thanks 20:57:04 <EinMByte> (was about to ask) 21:00:23 <str4d> Here is the list of everyone's ideas: 21:00:24 <str4d> `http://pastethis.i2p/show/K0fGRb2708ADbCTZ9u9K/` 21:00:25 <iRelay> Title: Paste #K0fGRb2708ADbCTZ9u9K | LodgeIt! (at pastethis.i2p) 21:01:01 <str4d> Nearly all of these can be turned into projects for the website todo page. 21:01:36 <str4d> Next discussion topic: which of these (and the ones on the Gantt currently) are more important for us to do in the next six months? 21:02:48 <psi> restricted routes is probably the most important item IMO 21:02:50 <EinMByte> with respect to syndie, maybe: I was working on this plugin - no time now though). This might be one of the things that can (?) bring more attention to syndie. 21:03:20 <dg> str4d: Tunnel death is absent and I feel that's quite important 21:03:37 <EinMByte> If anyone is interested in doing firefox / icedove plugin development: you know what to do 21:03:37 <str4d> dg: it's there (tunnel thread locking) 21:03:41 <str4d> I thought that's what it was 21:03:49 <dg> oh, sorry str4d, I meant when connections are abruptly terminated 21:03:54 <dg> my bad 21:04:04 <str4d> Ah, k 21:04:55 <EinMByte> psi: I agree restricted routes are important. But I also think we should realize that it will take quite some time to implement 21:05:21 <EinMByte> (not sure how much of the design / concept has been done) 21:05:35 <dg> In I2P: restricted routes, RedHat's ECDSA issues, Tor's HS 2.0, then the rest. Around I2P: Vuze userbase, GSoC, research, benchmark, then the rest. 21:06:04 <dg> I agree with EinMByte.. the router console redesign is important but that could take an indeterminate amount of time. 21:07:15 <EinMByte> str4d: one more thing, possibly. I know some reasearchers who have developed a new concept for a DWSE (distributed web search engine), they might be interested in developing this as an I2P application 21:07:42 <str4d> EinMByte: nice! 21:07:49 <EinMByte> Since most DWSEs right now don't really work well, it would be very interesting to have this IMHO 21:08:01 <zzz> no, by 'tunnel death' I meant 3-minute tunnel breakage, the Vuze guy's datagram test, etc. Distinct from local i2ptunnel locking issues. 21:08:07 <EinMByte> It's also something I would consider implementing 21:08:20 <dg> I wasn't thinking of precisely 3-minute but that was included. 21:08:34 <EinMByte> (with help, hopefully) 21:09:03 <str4d> k, reload Gantt page 21:10:34 <EinMByte> str4d: anyway don't count on this too much, it depends on whether I2P users are actually interested in something like this. 21:11:14 <EinMByte> Also, I'm not sure about the GNS stuff. In any case it shouldn't have a high priority. 21:11:56 <str4d> Updated new ideas paste: `http://pastethis.i2p/show/1qxHbkWjD27N7SdzNJZL/` 21:11:57 <iRelay> Title: Paste #1qxHbkWjD27N7SdzNJZL | LodgeIt! (at pastethis.i2p) 21:12:35 <zzz> i'd say 4 broad categories are the highest importance: 1) near-term crypto migration continuing (addressbook, muiltidest, etc) 2) longer-term crypto planning/research (DH, LS2, NTCP2) 3) all things testing 4) all things non-coding 21:13:48 <EinMByte> zzz: is that in order of importance? 21:14:05 <str4d> ECDSA issues fall into the first category; Tor HS 2.0 falls into the second category. 21:14:21 <zzz> no. roughly equal importance 21:14:44 <str4d> So the only item not represented in those categories is restricted routes 21:15:28 <jenkins@kyirc> Starting build #556 for job i2pd (previous build: SUCCESS) 21:15:30 <jenkins@kyirc> Project i2pd build #556: SUCCESS in 8.2 sec: `http://jenkins.killyourtv.i2p/job/i2pd/556/` 21:15:31 <jenkins@kyirc> * orignal: eliminated NTCPServerConnection 21:15:32 <jenkins@kyirc> * orignal: moved NTCP client code to Transports 21:16:34 <EinMByte> maybe NTCP2 is not *that* important 21:16:50 <zzz> and the reason I grouped them like that and say equal priority is that it's probably 4 separate groups of people for those 4 categories that could each make progress 21:17:08 <EinMByte> or, at least before we can start propertly on the NTCP2 we need to do a lot of research, also answer a few very important questions 21:17:33 <jenkins@kyirc> Project i2pd (Linux x86) build #33: SUCCESS in 1 min 47 sec: `http://jenkins.killyourtv.i2p/job/i2pd%20(Linux%20x86)/33/` 21:17:44 <EinMByte> zzz: indeed 21:17:51 <JekabsR> it is interesting that i2p network tends to bring all fast routers together 21:17:58 <jenkins@kyirc> Starting build #33 for job i2pd (Linux x64) 21:18:03 <zzz> right. "NTCP2" is just shorthand for a bunch of stuff that may or may not actually result in something called "NTCP2" 21:18:34 <JekabsR> and they do not prefer slow routers 21:18:40 <EinMByte> Yes. In any case if we change the transport layers it's extremely important not to make mistakes, as that would probably break I2P entirely. 21:19:19 <psi> JekabsR: slower routers are still used just not as much 21:19:43 <jenkins@kyirc> Project i2pd (Linux x64) build #33: SUCCESS in 1 min 52 sec: `http://jenkins.killyourtv.i2p/job/i2pd%20(Linux%20x64)/33/` 21:20:05 <EinMByte> zzz: if 2 is "research", then you are right though 21:20:33 <EinMByte> it can be done simultaneously 21:21:52 * str4d is reworking the Gantt into these four categories (plus an Other category) 21:22:12 <JekabsR> but there is a problem - client like destinations rarely get fast router connections 21:22:40 <eche|on> no? 21:22:46 <psi> JekabsR: not entirely sure if that is accurate 21:23:46 <zzz> str4d, did we forget Android, or is that a separate roadmap? 21:23:59 <str4d> zzz: we have forgotten it 21:24:01 <eche|on> JekabsR: hidden mode routers do have some issues, but other do get fast connections, as enough fast routers are available and do have free capacity 21:24:26 <str4d> Technically I2P Android falls into the "in I2P" category 21:24:35 <psi> oh another reasearch question: how much capacity does i2p actually have right now? 21:25:14 <zzz> maybe a 5th category for android makes more sense 21:25:46 <zzz> but I'm not hung up on categories. I just mentioned the 4 as a quick way to communicate what I think is important 21:25:54 <JekabsR> because they tend to create small number of really fast connections and large number of slow connections 21:26:11 <dg> [citation needed] 21:26:15 <JekabsR> my router started to drop slow tunnels 21:26:24 <str4d> zzz: I think it was a good idea 21:26:56 <str4d> Refresh Gantt page now 21:27:07 <eche|on> JekabsR: https://geti2p.net/_static/pdf/I2P-PET-CON-2009.1.pdf 21:30:12 <eche|on> JekabsR: tunnels are dropped only on end of tunnel lifetime and if own tunnels need the capacity. 21:30:29 <str4d> If you refresh `http://trac.i2p2.i2p/wiki/Roadmaps/1.0` you will now see the headings, each with a six-month bar. This gives an indication of how much time there is to fit everything in. 21:32:43 <str4d> Now that we have some ideas for the next six months, we need to start planning times. 21:33:18 <str4d> And who is going to tackle what. 21:33:52 <JekabsR> my console frequently reports that it has too many incoming connections and tunnels are partially rejected. How i2p decides which one to reject? 21:34:08 <dg> 'too many incoming connections'? 21:34:21 <dg> JekabsR: a meeting is currently ongoing, you may want to wait until it's over 21:35:00 <str4d> I would also like some volunteers to help turn the list of ideas into a working projects page on the website todo 21:35:12 <JekabsR> NTCP connections: 425. Limit: 425. Timeout: 2 min. 21:35:30 <JekabsR> UDP connections: 1149. Limit: 1275. Timeout: 4 min. 21:36:14 <JekabsR> limits are hit 21:37:42 <JekabsR> router is using 80% of CPU power 21:38:23 <str4d> Anyone? 21:39:36 <kytv> JekabsR: 1) meeting underway, you may want to wait; 2) look at `http://127.0.0.1:7657/peers#help` 21:41:16 <JekabsR> kytv: will check it out 21:41:44 <zzz> str4d, i think you lost everybody after an hour 45. Maybe declare victory for now and we'll make more progress at another time? 21:41:45 <str4d> Let's try some more specific questions. 21:41:52 <str4d> Or that./ 21:41:55 <JekabsR> 330,0 / 342,4 KBps my current load 21:42:06 <str4d> Yah, we have definitely made good progress. 21:42:30 <JekabsR> and torrent uploads at 2 - 5kb speed :( 21:44:17 <str4d> Thanks for the discussions, everyone! 21:44:20 * str4d warms up the baffer 21:44:20 * str4d ***bafs the meeting closed

I2P Dev Meeting - November 18, 2014

Tue, 18 Nov 2014 00:00:00 +0000

Quick recap

Present: dg, eche|on, Meeh, orignal, psi, RN, str4d, zzz, Full log is partly reconstructed from scrollback, iRelay dropped in and out early on.

Meeting Log

<zzz> 0) Hi <zzz> 1) Reimbursement for 31C3 attendees (zzz, echelon) <zzz> 2) Purchase of test/build boxes (zzz, kytv) <zzz> 3) 0.9.17 and/or 0.9.16.1 release schedule (zzz) <zzz> 4) Reseed status and new admin (zzz) <zzz> 5) SU3 news test before 0.9.17 (zzz, echelon, psi) <zzz> 6) 6-month roadmap, NTCP2 etc. (str4d, rescheduled from Oct. 28) <zzz> 7) New developer topics (str4d) <zzz> 0) Hi <zzz> Hi <dg> hi, was able to make it. <str4d> Hi <orignal> hi <zzz> I'd like to keep items 1-5 short, 5-10 minutes each. I'll then turn it over to str4d for the remaining items to run for as long as he likes. <zzz> 1) Reimbursement for 31C3 attendees (zzz, echelon) <zzz> We've traditionally paid for conference tickets for project members and I think there is broad consensus to continue this <RN> hi <zzz> Since CCC last year was so productive, I propose that we provide additional funds to support people and encourage them to attend <zzz> Not a full reimbursement, but just partial support. I propose 200 euros each, on top of the ticket. <zzz> thoughts/discussion? <eche|on> no problem with me <str4d> The ticket is 150 euro IIRC? <RN> sounds reasonable to me... 350... 20:04:02 <zzz> I think the ticket is 100-120 euros 20:04:43 <eche|on> ticket was 80 euro last time 20:04:43 <str4d> https://events.ccc.de/congress/2014/wiki/Static:Tickets 20:04:46 <iRelay> Title: Tickets - 31C3_Public_Wiki (at events.ccc.de) 20:05:01 <zzz> In addition, if there is anybody that would require a higher level of support to be able to attend at all, they should speak up now 20:05:16 <RN> what's the date? 20:05:29 <eche|on> 27th til 30th december <zzz> sounds like we have agreement for the general idea. Any discussion on the exact amount? * RN can not attend.... <RN> but I think extra over ticket is good for incedentals and accomodations.... <str4d> I have no objections to 200 euro + ticket <eche|on> so, who is going and who would get the money? ;-) <RN> would 200 cover two days hotel, or all four? <zzz> I assume it would be about 8 people, same as last year, for budgeting purposes <eche|on> RN: depends on the hotel, it would cover a hostel for sure <str4d> RN: depends where you go <eche|on> ok, not the amount of people is a problem, but I would not like to pay a newbie that money, just because she/he read about it. no issue for "well known" people <zzz> right <str4d> https://events.ccc.de/2014/10/14/31c3-special-terms-at-generator-hostel/ <str4d> Special 31C3 deal. Double rooms are available for 70.00 Euro, a bed in a six-person dorm 17.00 Euro per night. <zzz> this is in no way a complete coverage of hotel/food/plane. Just a little help to encourage team members to attend <zzz> last call for discussion on 1) <str4d> With two people sharing the double above, the 200 euro would cover the hotel <RN> still sounds resonable to me... <zzz> ok, sounds like we have agreement <eche|on> sure <RN> :) <zzz> 2) Purchase of test/build boxes (zzz, kytv) <zzz> we have limited test coverage for windows and mac. <zzz> zab used to test with mac, he's gone; meeh has a mac but it died and/or he ran out of time <zzz> so I wanted to ask if we could get more test coverage if we bought win or mac boxes for kytv and/or others <RN> my mac is too old to help... and I blew up the powerstrip it used to plug into... <Meeh_> zzz: what do I need to test ? <zzz> these could be used for other things too (e.g. laptops might be nice) <Meeh_> got OSX 10.9 and 10.10 <eche|on> I do have a win box, but not the time. we still do have 2 win 8 licenses <Meeh_> tell me and I'm doing it now <zzz> Meeh_, running dev builds. Do you run them now? <dg> when we say 'test coverage', what do we mean? <zzz> is anybody running dev builds on windows? <Meeh_> no sorry, new mac.. just a day ago since my lenovo died, marielle had to buy me one <Meeh_> so I just installed java <Meeh_> give me a sec and I'll build and start <RN> yeah, cuz depending on the time and level of test coverage... I got an XP +pos_ready running test builds 20:14:15 <dg> i could if needed to but that'd be in a VM and I wouldn't e using it intensely 20:14:25 <dg> just seeing if it works after uptime, try some eepsites, run some snark, check for errors 20:14:30 <dg> I don't know if I'd hit all the errors a real user would 20:14:47 <zzz> my question is, can we encourage anybody to do more dev build testing if we bought them dedicated boxes? 20:15:31 <str4d> There are two kinds of testing we would benefit from: people manually doing QA on the builds, and CI servers running on Windows and Mac. 20:15:39 <eche|on> not me. I got all hardware/software, but not the time/mood for intensive test 20:15:49 <zzz> yes str4d 20:16:09 <RN> or what if the box was set up with some kind of "safe-via-i2p" remote access for the dev team... 20:16:17 <Meeh_> zzz, I can always do OSX testing, if I'm not replying on IRC, try twitter or meeh@mail.i2p since both will alert my phone 20:16:24 <str4d> This topic appears to be about QA, but what would it take to get e.g. a Mac CI server hooked into kytv's jenkins? 20:16:47 <Meeh_> for a CI yes 20:16:48 <zzz> anybody that would do more if we bought them hardware? 20:16:59 <Meeh_> unfortunally I must move my mac from time to time 20:17:22 <eche|on> <= missing the free network connection so far. 20:17:23 <Meeh_> what hardware, what teting in what OS? (regardless of paying hw) 20:17:26 <zzz> Meeh you seem to be having less time lately, not more 20:17:37 <zzz> windows and mac 20:17:41 <eche|on> I already do run one I2P node on my address. But hm, I could run windows on IPv6 20:17:48 <Meeh_> yes, cleared up a lot in RL that took time 20:17:53 <RN> if the rest of my infrastructure wasn't constanly a mess I'd volunteer a home for a box.... 20:18:26 <Meeh_> fyi, i2pd/i2p will be available from au,ru,nl,uk,de,no,us-w,us-e in about a hour 20:18:34 <Meeh_> downloadable 20:18:39 <zzz> ok let's not worry about who in particular. eche|on if we found somebody, do we have the budget to buy some hardware? 20:18:40 <Meeh_> CDN 20:18:47 <zzz> Meeh please stay on topic 20:18:52 <eche|on> zzz: we do have fund, for sure 20:19:02 <eche|on> btw, Meeh, did the money arrive ? 20:19:17 <zzz> ok I propose that we end this topic and look for volunteers in the coming weeks 20:19:18 <RN> check me in 6 mo if I've stabilized the deamons... 20:19:24 <zzz> eche|on, please stay on topic 20:19:34 <zzz> any other discussion on 2) ? 20:20:03 <Meeh_> oh, sorry I forgot to reply. it's paid and done.. I guess I got the money but marielle transfered at the same time so need to double check. but quite sure. thanks 20:20:07 <dg> i'd like to hear from kytv 20:20:18 <Meeh_> eche|on: ^ 20:20:28 <dg> pm guys 20:20:40 <zzz> let's put this on the agenda to revisit for the next meeting 20:20:51 <str4d> +1 20:20:51 <zzz> 3) 0.9.17 and/or 0.9.16.1 release schedule (zzz) 20:21:07 <eche|on> I vote for 0.9.17 20:21:18 <zzz> At one point I wanted to do a 0.9.16.1 release to fix the SSU bug but I'm pretty much over it 20:21:21 <dg> Nothing's fallen down.. so 0.9.17. 20:21:21 <eche|on> in 2-3 weeks 20:21:41 <zzz> I'm now proposing a "mini" 0.9.17 release the weekend of Nov. 29 20:22:00 <zzz> i.e. a 4 week cycle to fix bugs, well before the christmas break 20:22:02 <str4d> There are several reports on forum.i2p that 0.9.16 network has slowed, and participation at nodes is down. 20:22:03 <RN> "mini?" 20:22:22 <zzz> mini as in limited changes, and not a full 6-7 week cycle 20:22:25 <str4d> IDK if the SSU bug could be causing that... 20:22:37 <RN> ah... yes... mini... good plan... 20:22:43 <zzz> pretty much what's in mtn now. About 13K lines of diff, but most of that is eddsa test changes 20:22:49 <orignal> sure it does. becuase dropped packets 20:23:10 <zzz> btw, my expl. build success stats are up significantly since the .16 release. Don't know why 20:23:11 <RN> so sounds like yesses for do a mini release <zzz> the SSU bug is actually just an irritation, I don't think it's the cause of any real problems <zzz> ok let's declare tag freeze and shoot for a release in 11 days <zzz> anything else on 3)? <eche|on> so 0.9.17 in 2 weeks <RN> wooohooo! <str4d> Are the release host operators available then? <dg> yup. <str4d> (Remembering that Nov 29th is just after Thanksgiving) <dg> It doesn't take long for me, it won't be an issue. <zzz> we'll assume so for now and slip as necessary. i'll be around but in a turkey semi-coma. perfect for building. <dg> It's mostly echelon you need anyway <zzz> 4) Reseed status and new admin (zzz) <zzz> This is just a brief announcement for those that don't know. <Meeh_> yeo <zzz> Due to time constraints, Meeh has moved the reseeed admin job to 'backup' <Meeh_> which is clearly the best at the moment :) <zzz> backup is not on irc but he can easily be contacted backup@mail.i2p or on the reseed subforum on zzz.i2p <zzz> thanks to meeh and backup for a smooth transition <Meeh_> but I think logstash will be interesting for the reseed admin soon <Meeh_> which I collect from mine <eche|on> thankjsgiving is no issue here in europe <zzz> backup is working on getting the remainder of sites onto su3, improving monitoring, and recruiting new hosts <zzz> so please give backup your full support. <str4d> Aye :) <dg> :) <zzz> also work with him if you have SSL / TLS issues he's discovered <zzz> anything else on 4)? <Meeh_> I can provide reseed from russia and australia now <Meeh_> if wanted <Meeh_> as well <Meeh_> nothing more on 4 from me <eche|on> Meeh_: ask baclup^^ <zzz> great, contact your new leader ;) <zzz> 5) SU3 news test before 0.9.17 (zzz, echelon, psi) <eche|on> aah <zzz> .17 include a switch to su3 news. <eche|on> thats a topic <eche|on> I need to test it 20:29:17 <zzz> I'd like to have eche|on add a news item, build the su3, so we can test it before the .17 release 20:29:43 * str4d is thinking through the current spec to ensure it is optimal 20:29:52 <zzz> all dev builds should be pulling from news.su3 now but since there's been nothing new since the release, it needs a test 20:30:07 <eche|on> I will try to generate a .su3 the next days 20:30:25 <zzz> would also be ideal, but not required, if psi would create a cert and check it in, since he's the backup but can't currently create his own su3 file 20:30:45 <dg> why can't he? 20:32:24 <zzz> str4d, also review the XHTML whitelist in the code please 20:32:24 <zzz> great, thanks eche|on 20:32:24 <str4d> Will do. 20:32:24 <eche|on> zzz: script was in mtn? 20:32:24 <zzz> eche|on, yes, i2p.scripts 20:32:24 <zzz> I know str4d has proposed writing the XML by hand, and thats what i did for the .16 release, but perhaps a search for a feed writer would be helpful 20:32:24 <zzz> don't know 20:32:24 <zzz> anything else on 5) ? 20:32:24 <str4d> What I would actually propose is: 20:32:51 <str4d> - Find a program for writing Atom feeds. 20:33:22 <str4d> -- If nothing suitable, write a Python script that converts a directory of XHTML entries into a feed...? 20:33:56 <zzz> yup 20:33:56 <str4d> - Store the info on the release versions etc. in a separate config file, and have a script that inserts it into the atom feed. 20:34:19 <zzz> str4d, please do that spec review in the next couple days 20:34:26 <str4d> K 20:34:38 <zzz> anything else on 5) ? 20:35:26 <zzz> 6) 6-month roadmap, NTCP2 etc. (str4d, rescheduled from Oct. 28) 20:35:26 <zzz> 7) New developer topics (str4d) 20:35:38 <zzz> I hand the meeting and the baffer to str4d at this time 20:35:48 <str4d> Ooooooooo 20:35:56 * str4d grins gleefully 20:35:56 <Meeh_> and I might have news at the end 20:35:58 <Meeh_> of meeting 20:36:02 <Meeh_> so HL me str4d please :) 20:36:25 <str4d> Okay, I can't remember what exactly I was planning to say in 6) when I originally proposed it.. 20:39:31 <str4d> So I'll start with 7) and see if it comes back to me. 20:39:31 <str4d> Despite the website revamp, the information we make available there is not well organized or clear. 20:39:31 <str4d> And with the last year's increased focus on privacy and security, we really need to make the most of the current environment. 20:39:57 <str4d> We have several locations with information on possible projects, tasks etc. but nothing clear, or up-to-date 20:41:06 <str4d> `http://i2p-projekt.i2p/en/get-involved/todo` 20:41:06 <str4d> `http://i2p-projekt.i2p/en/get-involved/roadmap` 20:41:06 <str4d> `http://i2p-projekt.i2p/en/docs/overview/performance/future` 20:41:06 <str4d> `http://i2p-projekt.i2p/en/get-involved/develop/applications` 20:41:06 <str4d> The last two links I'll leave for now, but at the very least I want us all now to look at the todo and roadmap pages now. 20:41:17 <str4d> like, now 20:41:20 <str4d> ;P 20:41:40 <iRelay> Title: Roadmap - I2P (at i2p-projekt.i2p) 20:41:42 <iRelay> Title: Future Performance Improvements - I2P (at i2p-projekt.i2p) 20:41:45 <iRelay> Title: Application Development - I2P (at i2p-projekt.i2p) 20:42:08 <str4d> The todo page is mostly filled with tasks that seem to have been completed. Of the tasks that are left, how many of them are still relevant? 20:43:49 <zzz> the wiki page on trac and the various threads on zzz.i2p are probably much more relevant 20:44:13 <str4d> Probably. But they are not visible to outsiders. 20:44:41 <str4d> "Hi, you want to help out with I2P? Go hunt for something to do on zzz.i2p" 20:44:49 <zzz> right 20:44:56 <str4d> I'm not saying we duplicate information. 20:45:50 <str4d> But I think the website should contain a concise overview of what we think is important for I2P, with links to more information as desired. 20:45:52 <str4d> This feeds in well to a future GSoC project. 20:46:16 <str4d> As usual, talking like this isn' 20:46:23 <str4d> t going to get much done :P 20:46:33 <zzz> is a group review now on IRC going to work, or do we need a volunteer to redo it all, or would a couple hours spent at CCC do it? 20:47:19 <str4d> Group review right now won't work. And after what I went though with the website, I don't think it's fair to put this all on one person. 20:47:40 <eche|on> I vote for a "lets do work a bit on it and if not done on CCC, do it at table 20:47:45 <zzz> maybe it's fair if it isn't you... 20:48:02 <str4d> CCC is pretty close, so that would be ideal. But we would need to get the website etc. updated *very* quickly, so we can point people to it. 20:49:32 <zzz> if your intent is this is in the context of a broader effort to apply for GSoC please make that clear 20:50:14 <str4d> I would very much like to get a GSoC student on board, but that is a separate topic. 20:50:50 <zzz> if not for GSoC, what's the reason for "very quickly"? 20:51:20 <str4d> zzz: I just meant that, if the work is done *at* CCC then we can't capitalize on it *at* CCC. 20:51:32 <zzz> oh, ok 20:52:08 <str4d> We would instead need to say "check the website in x days" which doesn't leave as good an impression. 20:53:46 <zzz> so your goal is to have a good answer for people that walk up and ask 'what do you need'? 20:53:53 <str4d> On the website, /todo is ancient. /roadmap is sparse. /performance/future is separated, and /develop/applications is a bunch of topics bundled into one. 20:53:56 <str4d> zzz: yes. 20:54:19 <str4d> People who are interested in I2P can look at the website and immediately see how their skills will be most useful. 20:54:44 <str4d> Top of the list: UI designers ^_^ 20:54:53 <zzz> but the people that ask that generally have never run i2p, so my answer is 'install it and run it for a couple weeks, then ask on irc' 20:55:52 <str4d> I don't think running I2P needs to be a predicate for helping. 20:55:52 <zzz> but yeah, the other answer is 'ui, crypto, ..." 20:56:25 <str4d> IMHO if you tell someone to wait a few weeks, often the enthusiasm can be displaced by something else. 20:56:28 <str4d> Right, but we need to be more specific. 20:56:28 <zzz> but realistically is anybody going to start devving who hasn't ever used it? 20:56:59 <zzz> i can't imagine volunteering to code for some software i've never used. 20:58:33 <str4d> No, but we can start engaging with them while they start using I2P. 20:58:33 <zzz> sure. agreed with all. An up-to-date todo list is a sign of a serious project. 20:58:58 <str4d> Okay, action time: 20:58:58 <RN> it is talking about 6.x and older on there... 20:59:07 <dg> something else is whether or not we're going to drop stop-and-go, etc 20:59:16 <dg> people point to our docs and say "wow, they'll have it/do" 20:59:33 <str4d> dg: ? 21:00:43 <> RN@kyirc leans forward on chair... 21:01:06 <dg> and uh, delays 21:01:30 * RN feels nostalgic 21:02:35 <str4d> Over the next week, can everyone here draw up two lists. One with features and improvements they would like to see in I2P itself, the other with features and improvements in the I2P ecosphere (this is things like new apps and services, dev work on existing apps, research, code review etc.) 21:02:35 <str4d> Doesn't need to be long, but I think if we all contribute a few points to each, even if some are duplicates it will be a good jumping off point. 21:02:35 * str4d will draft up an outline of how the content will be presented on the website (what content will go where etc.) 21:03:29 <RN> do we have a reasonable survey mechanism? on forum or zzz? 21:03:31 <zzz> yeah, if you setup the framework we can fill it in 21:03:53 <str4d> zzz: always seems to be the case ;P 21:04:33 <str4d> Who is available this time next week for a "meeting"/group discussion? 21:04:57 <RN> I might be 21:05:55 <str4d> The sole topic will be sorting through the lists people show up with, and organizing them into the content sections I will present. 21:05:59 <zzz> sure 21:06:20 <dg> me too 21:06:31 <RN> do you want lists i2pmailed to you? 21:06:50 <RN> or contribute to a thread on fourm or trac or??? 21:07:44 <str4d> RN: if you can't make it to the meeting, message me a link to pastethis.i2p 21:08:31 <str4d> Otherwise, just bring it to the meeting. 21:08:38 <RN> k 21:08:41 <str4d> Rather than a discussion on zzz.i2p, this time I want to try independent brainstorming without being influenced by what has already been posted. 21:09:16 <str4d> After the meeting, we will have something that can be posted on zzz.i2p or the wiki (probably there) for further discussion and editing. 21:11:36 <str4d> Does anyone else have more to say on 7)? 21:11:45 * str4d is done for this meeting 21:11:59 <str4d> Otherwise I'll go back to 6) briefly 21:13:30 * RN awats the baffing or the handoff of the baffer 21:13:54 * str4d assumes nothing. 21:14:00 <str4d> 6) 6-month roadmap, NTCP2 etc. (str4d, rescheduled from Oct. 28) 21:14:39 <str4d> I *still* can't remember where I wanted to go with this topic, but it dovetails nicely into 7. 21:14:52 <str4d> Previous large-scale dev work has been approximately 6-monthly, and we are about at the end of a cycle. 21:15:38 <str4d> Aside from the continual move towards new crypto, we should decide where to focus development effort for the next six months. 21:16:07 <str4d> NTCP2 is one suggestion, and PT development and integration 21:16:11 <eche|on> I am afk now 21:16:21 <str4d> o/ eche|on 21:16:49 <str4d> Formalizing our todo list will IMHO help us as much as it will help prospective new developers. 21:17:13 <str4d> At a minimum, we need to ensure that zzz's paper list of development stuff is bus-proof ;) 21:18:44 <Meeh_> what's the current topic? 21:19:24 <str4d> Meeh_: I think everyone is done with my ranting now, so I'll hand over to you :) 21:19:28 <RN> 6-mo roadmap... 21:19:53 <str4d> For 6) I think we can talk about it next week, after we have discussed peoples' lists. 21:20:00 <str4d> s/it/it more/ 21:20:01 <iRelay> str4d meant: For 6) I think we can talk about it more next week, after we have discussed peoples' lists. 21:20:31 <Meeh_> ah, thanks 21:21:23 <Meeh_> well, I've meanwhile you had meeting now, done what I said I should do, and it's giving i2p a lot of more download mirrors 21:21:48 <RN> :) 21:21:55 <str4d> Yay! 21:22:03 <dg> awesome 21:22:03 <Meeh_> in some hours, download.i2p.io should work for al, and should resolve based on latency and geoip 21:22:06 <Meeh_> none recorded from my site 21:22:07 <Meeh_> dns thingy 21:22:14 <Meeh_> they also got names 21:22:17 <Meeh_> I will list them now 21:22:31 <Meeh_> the domain mentioned was a shared domain 21:23:45 <Meeh_> jp01-mirror.i2p.io, nl01-mirror.i2p.io, no01-mirror.i2p.io, ru01-mirror.i2p.io, uk01-mirror.i2p.io, use01-mirror.i2p.io, usw01-mirror.i2p.io 21:24:00 <Meeh_> all will answer on both http(s) 21:24:19 <Meeh_> oh, de01 will also emerge 21:24:38 <Meeh_> but NL01 and DE01 is probably not up before tomorrow, however all other should work in short time 21:25:01 * RN hugs Meeh_ 21:25:09 <Meeh_> I've also gotten my windows and apple certificates 21:25:32 <Meeh_> so I will ve signing builds for i2pd on OSX and Windows, to escape the 2untrusted publisher" blocker/alerter 21:25:42 <Meeh_> also 21:26:20 <Meeh_> every i2p team member can have their own mail account @ i2p.io OR alias, with clearnet access for that matter 21:26:31 <Meeh_> for examle marielle has m@i2p.io, and I got mv@i2p.io 21:26:39 <Meeh_> short'n clean :D 21:27:09 <Meeh_> other than that, sorry for not beeing more around, but t I hope RL stuff are done now and I can continue here :) 21:27:51 <Meeh_> at last, a OSX and Windows build of i2pd is released tomorrow or tonight. 21:27:53 <Meeh_> thanks for listening! 21:28:12 * RN hugs Meeh_ more 21:28:41 <Meeh_> hehe, thanks RN:) 21:29:02 <str4d> Meeh_++ 21:29:16 <dg> str4d, zzz, Meeh_++ 21:29:32 <Meeh_> str4d, this can/could include f-droid too if you want 21:29:45 <str4d> Meeh_: is there a CDN setup for these servers, or are they "individual"? That is, how should the website mirrors list be updated? 21:30:04 <Meeh_> kytv: one server to rule them all.. remember if you publish to the one you got access to, all servers get it 21:31:42 <Meeh_> str4d: I'm partly done with the DNS balancing 21:31:42 <Meeh_> meaning it react to closest mirror 21:31:42 <Meeh_> so we could use one domain for all 21:31:42 <str4d> Okay, so the only download link that people will see is download.i2p.io 21:31:42 <Meeh_> but guide was bind9 and I'm running powerdns on the needed server so just need to ... find their way of doing the same 21:31:42 <str4d> (for this mirror system) 21:31:55 <Meeh_> yes, or if we will ... embrase it, we can write all 21:31:58 <str4d> F-droid on this would be ideal too. 21:32:51 <Meeh_> yes, right now it's just simple rsync, but I upgrade to openstack swift proxy at each location once I see high demand 21:33:07 <Meeh_> then it will be a REST url to publish updates too 21:33:15 <Meeh_> even zzz an do it himself from his browser with right credentials 21:33:31 <Meeh_> (when swift is added) 21:33:47 <Meeh_> reason I didn't right now was becasue it would have taken a hour or two more 21:33:49 <Meeh_> at least 21:34:00 <Meeh_> so then I did't catch the meeting :p 21:34:20 <str4d> Either as https://fdroid.i2p.io/repo/ and https://fdroid.i2p.io/archive/, or https://download.i2p.io/fdroid/repo/ and https://download.i2p.io/fdroid/archive/ 21:34:42 <str4d> Second option is probably better, then we don't need separate HTTPS certs. 21:34:51 <psi> is i2p.io going to be an inproxy? 21:34:51 <Meeh_> pick whatever *.i2p.io/* and you can use the https wildcard 21:34:58 <Meeh_> your chooise 21:35:01 <Meeh_> nope 21:35:04 <Meeh_> i2pd's page 21:35:14 <Meeh_> subsite of PS 21:35:24 <Meeh_> ofc. linking to geti2p.net as well 21:36:02 <Meeh_> see it as a readme page more or less, both on i2p as network and i2pd as the client 21:36:21 <Meeh_> not all ready, so if you got input, please write 21:37:47 <str4d> Meeh_: sounds good. If you have a wildcard cert then I'll choose fdroid.i2p.io (or f-droid.i2p.io, which would be technically correct) 21:37:56 <str4d> Yah, go with f-droid.i2p.io 21:38:08 <Meeh_> sure, we add it 21:38:16 <str4d> Okay, the meeting is IMHO done. Any final requests for topics? 21:38:27 <Meeh_> do you want access as well, and setup your own vhost in nginx? 21:38:35 <Meeh_> same server as kytv 21:38:46 <Meeh_> got access to 21:39:00 <Meeh_> I think you had actually, or has 21:39:15 <Meeh_> because of early f-droid setup 21:39:22 <str4d> I do, yes - it's how I uploaded the existing f-droid stuff 21:39:22 <Meeh_> IIRC 21:39:32 <str4d> Anyway 21:39:34 * str4d warms up the baffer 21:39:43 <Meeh_> sign in, check if your pw work, tell me if not and I make sure you can sudo 21:39:55 * str4d ***bafs the meeting closed 21:40:13 * RN dances a thanks for a good meeting dance

0.9.16 Release

Sat, 01 Nov 2014 00:00:00 +0000

0.9.16 is a significant step forward in our plan to migrate from DSA to ECDSA and then EdDSA cryptographic signatures, and makes several other changes to increase your anonymity and security. Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures by default. In addition, we’ve fixed a large number of serious bugs, including console lockups.

Changes in router data structures will require i2pcontrol plugin users to update to version 0.0.9.

0.9.15 Release

Sat, 20 Sep 2014 00:00:00 +0000

0.9.15 adds preliminary support for Ed25519 EdDSA signatures. It includes a new persistent configuration backend for i2psnark and fixes several issues with i2psnark’s handling of file names. There are several improvements to speed up SAM. Plugins now support stronger signatures in the su3 file format. Plugin installation via the console, which was disabled in 0.9.14, is re-enabled.

We have supported ECDSA signatures since 0.9.12, and we would like to start using ECDSA by default. Unfortunately, some of you are still running older I2P versions, and for others, their distribution or Java runtime does not support ECDSA. Red Hat (RHEL, Fedora) distributions are reported to be missing ECDSA. Some have fixed the Java issues by upgrading from Java 6 to Java 7; others have had success with installing the “unlimited strength policy files”. We’ve added information about missing crypto to the log file and the /logs page in the console. After you update to 0.9.15, please check if you are missing ECDSA support, and attempt to fix it if necessary. This is particularly important for those that run popular eepsites and services.

Android test release on Google Play in Norway

Sat, 23 Aug 2014 00:00:00 +0000

I2P Android has existed for over three years. In that time, it has evolved from a simple test project into a usable, useful Android port of the I2P router. Our eventual goal has been to release I2P Android on Google Play, to make it easier for users to discover, install and use I2P on their Android devices. After much work improving the user interface, fixing bugs and testing, we think that I2P Android is finally ready to go where the users are.

The birth of Privacy Solutions

Fri, 15 Aug 2014 00:00:00 +0000

Hello all!

Today we announce the Privacy Solutions project, a new organization that develops and maintains I2P software. Privacy Solutions includes several new development efforts designed to enhance the privacy, security, and anonymity for users, based on I2P protocols and technology.

These efforts include:

The Abscond browser bundle.
The i2pd C++ router project.
The “BigBrother” I2P network monitoring project.
The Anoncoin crypto-coin project.
The Monero crypto-coin project.

Privacy Solutions’ initial funding was provided by the supporters of the Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-profit type of organization registered within the Norwegian government registers. (Kind of like US 501(c)3.)

0.9.14.1 Release

Sat, 09 Aug 2014 00:00:00 +0000

0.9.14.1 includes fixes for the “Add Torrent” form in i2psnark and some other web forms. We’ve restored the ability to install plugins via the console, but you must first edit your router.config file (in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\I2P) to add the line routerconsole.enablePluginInstall=true. Other rarely-used advanced features that were removed in 0.9.14 may be restored by adding the line routerconsole.advanced=true.

As usual, if configured with the default “Download and Verify”, the router will automatically download the update and display a button to restart. However, due to a bug in 0.9.14, if your update is configured for “Notify only”, the download button will not be displayed. You must change your configuration to “Download and Verify” or “Download, Verify, and Restart” to update.

I2P 0.9.14 Release

Sat, 26 Jul 2014 00:00:00 +0000

0.9.14 includes critical fixes for XSS and remote execution vulnerabilities reported by Exodus Intelligence. As an added precaution, we have disabled several advanced configuration features in the router console, including installation of new plugins. We plan to re-enable these in a future release after additional review.

Due to I2P library changes, I2P-Bote users must upgrade their plugin to version 0.2.10 to work with I2P 0.9.14. Your router should update the plugin automatically after the router restarts.

I2P Dev Meeting - July 14, 2014

Mon, 14 Jul 2014 00:00:00 +0000

Quick recap

Present: eche|on, Meeh, psi, zzz

Meeting Log

20:00:11 <zzz> 0. Hi 20:00:11 <zzz> 1. Select new PR Manager (zzz) 20:00:19 <zzz> 2. Replace mtn.i2p2.i2p in default i2ptunnel.config (zzz) 20:00:23 <zzz> 0. Hi 20:00:29 <zzz> Hi 20:00:49 <zzz> 1. Select new PR Manager (zzz) 20:00:50 <zzz> 1) PR Manager. orion has resigned. I nominate psi and Meeh as excellent candidates. Others may throw their name in for consideration below, or at the meeting. You may also wish to volunteer as an assistant. Duties include: 20:00:50 <zzz> - Frequent tweeting using @geti2p 20:00:50 <zzz> - send stickers to people who ask 20:00:50 <zzz> - Speak at conferences and meetups 20:00:50 <zzz> - Answer the press@i2pmail.org mail (generate and distribute a new GPG key for it) 20:00:52 <zzz> - Outreach, make contact with people/groups we want to work with; form strategic alliances 20:00:55 <zzz> - Misc. promotion, support, and communications duties 20:00:56 <zzz> - Maintain positive attitude 20:00:56 <Meeh> Hi 20:01:11 <psi> ? 20:01:13 <psi> hi 20:01:38 <zzz> Is either psi or Meeh willing to serve? Are there any other volunteers or nominations? 20:01:50 <psi> I am willing to serve if desired 20:02:24 <eche|on> available here but not for that job, sorry 20:02:27 <psi> I can also obtain orion's stickers 20:03:23 <zzz> Meeh are you willing to serve or would you rather throw your support to psi? 20:04:49 <zzz> anybody else have any comments? 20:04:59 <Meeh> I can do both, what I mean is I can both serve, and I will ofc. support psi if he's doing it 20:05:45 <psi> pr "team" then? 20:06:12 <Meeh> why not, I can't go to the US so I need anyone there anyway 20:06:21 <psi> works 20:06:27 <zzz> My guess is that psi might have more time than Meeh for this? 20:06:57 <psi> yeah i have buttloads of free time right now and probably for a while 20:07:24 <Meeh> but no problems covering EU/Asia/Africa 20:07:34 <Meeh> Yes in some points I think too 20:07:44 <zzz> Meeh has never had buttloads of time since I've known him 20:08:00 <Meeh> however, I think I can contribute a lot wrt tweeting, speak at conferences, and some outreaching 20:08:17 <zzz> how about psi as head and Meeh as assistant? 20:08:26 <psi> i dont do public speaking so i can outsource that to Meeh 20:08:36 <psi> sounds good 20:08:44 <Meeh> sounds good to me too 20:08:47 <Meeh> I can do the public 20:08:58 <zzz> any objections or other comments? 20:09:44 <zzz> ok great 20:10:28 <zzz> I'll get psi the twitter password. Please get the stickers from orion. 20:10:44 <psi> got it 20:11:19 <zzz> Also please generate and distribute a GPG key for press@, and get welterde to fix up the mailing list accordingly 20:11:27 <zzz> speaking of welt... 20:11:33 <eche|on> .... 20:11:36 <zzz> 2. Replace mtn.i2p2.i2p in default i2ptunnel.config (zzz) (Down since June 12 - possible replacements mtn.killyourtv.i2p or mtn.i2p-projekt.i2p) 20:11:52 * psi nominates kytv's 20:12:05 <zzz> eche|on, kytv_ would either of you care to volunteer? 20:12:15 <zzz> we can't put both in one tunnel as that confuses mtn 20:12:56 <zzz> any others that have been up and running for a while? 20:13:01 <eche|on> you can enter mine, I try to keep it up running as always 20:14:24 <zzz> ok, echelon it is I guess 20:14:37 <eche|on> kytv does a lot of jobs already 20:15:07 <zzz> both of them seem very reliable, so doesn't matter much 20:15:27 <Meeh> mtn.meeh.i2p hs ben running for a year now 20:15:29 <zzz> it's not any more work, maybe just a tiny bit more traffic, probably not even noticeable 20:16:25 <eche|on> can we create 3 tunnels and enable only one? 20:17:55 <zzz> nice meeh, good to know 20:17:55 <zzz> anything else on 2) ? 20:17:55 <zzz> any other topics for the meeting? 20:18:19 <psi> do we have a backup irc? 20:18:39 <psi> it seems that if some/all of postman's stuff goes down we're screwed 20:19:17 <psi> mail+irc is postman so what is the backup meetup in the event postman's stuff is non functional 20:19:29 <zzz> sure we could make 3 tunnels but seems like just added clutter to me 20:19:37 <psi> i have been wondering this for a while now... 20:20:28 <eche|on> ok, right, within 6 weeks release time we can change it fast enough, also really interested people can get in here. Also I can push the key to $trusted person 20:21:54 <zzz> we have 3 IRC servers 20:21:54 <zzz> there is no backup for postman himself... 20:21:54 * zzz warms up his short baffer for the short meeting 20:21:54 * zzz ***bafs the meeting closed

I2P Dev Meeting - July 01, 2014

Tue, 01 Jul 2014 00:00:00 +0000

Quick recap

Present: bgwcb, eche|on, kytv, Meeh, psi, str4d, zzz

Meeting Log

20:00:32 <zzz> 0. Hi 20:00:32 <zzz> 1. I2P on Google Play (meeh / str4d) 20:00:32 <zzz> 2. Tablet testing (zzz) 20:00:37 <zzz> 0. Hi 20:00:39 <zzz> Hello 20:00:51 <zzz> 1. I2P on Google Play (meeh / str4d) 20:01:12 <eche|on> hi 20:01:13 <zzz> Meeh, str4d, please tell us about your plans for Google Play 20:03:31 <zzz> ok, I'll give you what I know 20:03:56 <zzz> Meeh has an existing but unused account; he's going to give str4d access too; 20:04:35 <zzz> he;s got a dev build up on it now that's invite-only; they plan to make it available to all with the 0.9.14 build; 20:04:55 <eche|on> a dev account should not be the big problem at all 20:05:06 <zzz> they plan to have two versions, one free and one "donate" for a cost of ~$2.50 20:05:18 <eche|on> yeah 20:05:30 <bgwcb> why? 20:05:49 <zzz> Meeh would relay the funds to echelon monthly (assuming it was enough to make it worth it, and meeh didn't have any expenses) 20:05:50 <eche|on> It will have some issues with registration as I2P, but he/she will do it fine 20:05:52 <bgwcb> and for what you need google play? 20:06:14 <zzz> apparently lots of apps have donate versions, take rate is maybe 1% of the free version 20:06:47 <eche|on> it is a fine idea 20:06:50 <zzz> everybody has google play; only the few have f-droid or amazon or load directly from a website 20:07:03 <eche|on> I do not think much money will come in, but better than nothing 20:07:05 <zzz> that's what i know, more or less. Comments? 20:07:22 <eche|on> comment: registration as I2P will be a mess, but else, go ahead 20:08:08 <zzz> somebody unknown has reserved, but not published, net.i2p.android.router. Meeh is attempting to get it back. 20:08:11 <bgwcb> what differenses are in free between donate? 20:08:21 <eche|on> bgwcb: none ;-) 20:08:33 <zzz> it's not a big deal but it would prevent dup detection with existing installs from website or f-droid 20:08:33 <bgwcb> wow 20:08:33 <eche|on> except the donation of the buy-field. 20:08:44 <bgwcb> good idea, in you sleeped genius 20:08:49 <psi> hi 20:08:57 <eche|on> zzz: so the registration works via the java classes and not the project name? 20:09:34 <zzz> the class is essentially the name, or unique identifier. meeh and str4d are investigating 20:09:48 <psi> re: donate version, will it have "more features" ? 20:09:54 <zzz> we're also trying to find nextloop, our f-droid guy, for assistance 20:10:02 <psi> or is it just another package? 20:10:11 <eche|on> psi: no, just a function for "you got the donation version" ;- 20:10:18 <eche|on> in about screen IMHO 20:10:37 <eche|on> balm for the soul "you are something better than anyone else, you did pay us some!" 20:10:38 <psi> neat 20:10:41 <kytv> (belated 'hi') 20:10:53 <zzz> any comments on a donate version? 20:10:56 <psi> epeen 20:11:21 <zzz> any objections to a donate version? or to google play at all? 20:11:28 <eche|on> zzz: go ahead, I would add a different about text in the app itself 20:11:47 <eche|on> I once have had the idea to sell every android version, but no need to 20:12:29 <zzz> if you're interested in what Meeh has so far or want to test his version of the app, contact him 20:12:50 <eche|on> which is a nice guide to TOP2 ;-) 20:13:01 <zzz> last call for comments on google play 20:13:28 <kytv> +1 for google play, more users is good 20:13:50 <psi> +1 for google play as well, since more users means more feedback 20:14:14 <kytv> (not sure about +1 for 'requiring payment' but donations are A-OK) 20:14:36 <Meeh> *reading backlog* 20:14:39 <zzz> 2 versions, free and not. prediction is 99% will choose free 20:15:12 <kytv> yeah, I got that. That's perfectly fine. 20:15:25 <zzz> Meeh inb4 last call, let's give him a couple minutes to read backlog and elaborate 20:17:56 <Meeh> hm, yea. 20:18:13 <Meeh> well, I would like to add a topic actually, which in a way is connected with this 20:18:24 <Meeh> but in a way not in anyway either 20:18:55 <zzz> Meeh, last call for comments on 1) 20:19:04 <zzz> anything I got wrong? 20:20:04 <Meeh> I would gladly do it, and the two-app with donations seems like a good idea still :) 20:20:05 <Meeh> no, it was right about the namespace etc 20:20:05 <Meeh> you got it right 20:20:06 <zzz> ok then. end of 1). 20:20:07 <zzz> 2. Tablet testing (zzz) 20:20:42 <zzz> We don't have enough android testers and devs now. We're about to get a lot more users. So we definitely need more testers and devs. 20:20:49 <Meeh> HL me when I can add 3), it's a big topic. and it would probably interest many 20:21:03 <Meeh> need to work more on the topic while 2) 20:21:05 <zzz> ok 3) meeh on the list 20:21:08 <zzz> back to 2) 20:21:41 <zzz> I'd like to propose reimbursing people who would like to buy an Android device that promise to do testing or development. 20:22:13 <zzz> Say, up to $200 each for up to 8 people, Enough to buy a 7" tablet, or to partially fund a phone or 10" tablet 20:22:31 <zzz> I'd also like to fully fund a 10" tablet for str4d, up to $400 or so 20:22:44 <zzz> comments? volunteers? 20:23:24 <eche|on> my comment is already on record, go ahead. 20:23:25 <str4d> hai 20:23:27 <str4d> ary for l8ness 20:23:36 <eche|on> but do not buy chinese spyware devices^^ 20:24:07 <zzz> we've already bought some devices for devs but we really really need testers 20:24:47 <str4d> sry* 20:24:55 <zzz> this would be for people already part of the dev community, e.g. psi, orion, dg, kytv, echelon, etc 20:25:23 <zzz> who wants one? i think this would be a great use of project funds 20:26:00 <kytv> I'm always open for testing, but I have no tablet and don't know how useful any feedback I could give would be. That said, I can test and supply (hopefully) valid reports. 20:26:21 <zzz> ok, there's one. great. 20:26:48 <zzz> as usual, ask echelon, our treasurer, for reimbursement 20:26:52 <Meeh> I could test too, but my pad is starting to get simewhat old 20:26:56 <Meeh> somewhat* 20:27:18 <zzz> I really like the 7" android tablets. Great for testing and general use. And you don't risk horking your phone. 20:27:50 <zzz> last call for comments on 2) android tablets for testing 20:28:23 <str4d> Choice of device is important 20:28:30 <eche|on> (I do NOT pay apple products, lol) 20:28:37 <Meeh> I can help test, but for guaranteen the testing it would probably need a buyin of a new tablet 20:28:53 <str4d> The opportunity we have here is to provide a range of device *sizes* as well as screen *densities* 20:29:21 <zzz> if we let each person pick their own phone or tablet, that should provide the assortment needed 20:29:55 <zzz> ok, moving on to 3) Meeh's unknown topic. 15 minutes max. 20:29:57 <zzz> go Meeh 20:29:59 <str4d> (e.g. my 7" tablet is 600x1024 pixels, and falls into the -sw600dp category) 20:32:03 <Meeh> ok, I decidedto come back (since I've been away a whhile) with a supprise, some have might heard of it, and some seen some of it.. but simple saying I've made a "I2P browser bundle" which is probably ready for win32 and osx within 24hours 20:32:29 <Meeh> turn on your tor plugins and see https://hideme.today/dev/ 20:32:35 <iRelay> Title: The Abscond bundle (at hideme.today) 20:32:39 <Meeh> that's the featureset and "face" of it 20:32:57 <psi> wait wut 20:33:01 <psi> a browser bundle? 20:33:05 <Meeh> I'm trying to get i2p more eaiser to get into.. because that's always the complaint I get 20:33:08 <Meeh> yes 20:33:17 <Meeh> more too, since it's 100% portable 20:33:26 <Meeh> you can put it on a usb stick 20:33:39 <Meeh> launch it on any machine.. do a mod, and you can cross boot it too 20:33:42 <psi> neat 20:33:43 <str4d> psi: Tor Browser with I2PButton 20:33:46 <Meeh> as in same install on win,linux,osx 20:33:58 <Meeh> more or less as str4d said yes :) 20:34:38 <Meeh> so, do any of you have comments etc on this, ideas, ++, ? 20:34:49 <psi> where can i get it? 20:34:56 <Meeh> thinking it was good with some feedback before release 20:34:57 <psi> looks like the gitlab instance is locked 20:35:11 <Meeh> I will push the final code and make it available some hours now after the meeting 20:35:21 <psi> okay 20:35:23 <Meeh> 've not finished with a complete build set 20:35:38 <Meeh> so I need to tell you how to compile and set all parts together 20:35:44 <eche|on> comment: lots of work. 20:35:47 <eche|on> but great. 20:36:13 <Meeh> I've focused most on a prototype/proof of consept rather than a build system 20:36:54 <Meeh> so I took the torbrowser itself and rebranded it, torbutton is almost rewritten to work 100% with i2p instead of tor, 20:37:17 <Meeh> the launcher is written from scratch by me, much because of the jre part 20:37:34 <Meeh> therefore all old build scripts from tor fails 20:37:43 <Meeh> and isn't easily mod.able 20:38:36 <psi> orchid included? 20:38:59 <Meeh> yes, it's some i2p plugins as well as browser plugins included 20:39:06 <psi> neat 20:39:16 <Meeh> i2p plugins mostly for getting people interested, like i2p-bote 20:39:23 <Meeh> and browser plugins for privacy 20:40:20 <Meeh> the idea is to have a build script that easily build a new bundle for osx,linux,win32 on each i2p release 20:40:37 <Meeh> and ofc. browser update etc, but that will require manually work 20:40:53 <Meeh> but I've included in my future plan to maintain that 20:42:25 <zzz> ok, anything else on 3) ? 20:43:02 <zzz> anybody have any other topics? 20:43:14 <Meeh> no it was mainly all. if anyone on win32 wants to test please yell out, because after anoncoin experience that needs most testing 20:43:55 <Meeh> and I see I go emtpy for coffeine if I don't run out and buy, back in 10. takes 5min each way :) 20:44:24 <zzz> ok great. A reminder that anybody can call a meeting on any topic at any time. 20:44:35 * zzz *bafs* the meeting closed

I2P 0.9.13 Release

Thu, 22 May 2014 00:00:00 +0000

0.9.13 includes fixes for firewalled routers, netdb lookup improvements, and a big SusiMail update. Of course, there’s also the usual collection of bug fixes and translation updates.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

zzz has updated his GPG keys, and the release files are signed with his new keys. His new key fingerprint is: 2D3D 2D03 910C 6504 C121 0C65 EE60 C0C8 EE72 56A8

I2P Dev Meeting - May 06, 2014

Tue, 06 May 2014 00:00:00 +0000

Quick recap

Present: bgwcb, dg, eche|on, EinMByte, hghoster, kytv, nombra, Nyakov, psi, topiltzin, user, Yi, zzz

Meeting Log

20:00:37 <zzz> `http://zzz.i2p/topics/1618` 20:00:43 <bgwcb> well, start it? 20:00:46 <iRelay> Title: zzz.i2p: Meeting Tues. May 6 - 8 PM UTC (at zzz.i2p) 20:00:57 <zzz> 0. Hi 20:00:57 <zzz> 1. hiddengate.i2p console home page request (see next post for details) 20:00:57 <zzz> 2. OMGWTFBBQ Summer Europe - echelon 20:00:57 <zzz> 3. 0.9.13 release schedule 20:01:06 <zzz> 0. Hi 20:01:09 <zzz> hello 20:01:11 <eche|on> hi! 20:01:15 <psi> hello 20:01:16 <topiltzin> hi 20:01:23 <nombra> o/ (reconnected just in time) 20:01:38 <kytv> hola 20:01:49 <Yi> what is it? 20:01:50 <zzz> Most of these items should be short, let's limit them to 15 minutes each 20:02:00 <hghoster> hi all 20:02:05 * mokosoul sneaks away before anyone notices it was here at the meeting. 20:02:08 <zzz> 1. hiddengate.i2p console home page request 20:02:16 <zzz> see the link above for details 20:02:42 <zzz> hghoster is the requester for hiddengate.i2p. would you please tell us a little about the site? 20:03:52 <hghoster> HiddenGate is a project for Russian I2P users. Target: publish online/offline "Vestnik I2P" paper which introducec to I2P and guides how to reach it. 20:04:00 <hghoster> we have wiki, forum, imboard 20:04:06 <EinMByte> Hi 20:04:47 <EinMByte> hghoster: so... can we say it's a kind of help-site 20:05:03 <hghoster> so.. we already published first version of paper. also few guys continues fill wiki with new techinal articles 20:05:04 <kytv> for convenience, the ToS in EN: `http://hiddengate.i2p/wiki/ToS#Terms_of_Service` 20:05:04 <zzz> ok, thanks. Anybody have questions or comments? I especially would like comments from Russian speakers 20:05:08 <iRelay> Title: HiddenGate Wiki: HiddenGate Wiki (at hiddengate.i2p) 20:05:27 <bgwcb> hghoster: censored imageboard, but it's probably good because we, good russian anonymous, don't love cp 20:05:29 <EinMByte> I've visited the website earlier, and it looks good 20:05:50 <EinMByte> one thing I would like to mention though: the homepage is all in russian 20:05:55 <hghoster> EinMByte: yes. our target is to make some platform where is new users will not see cp, etc some shock content 20:06:15 <hghoster> just for politics discussions, some interests, etc. no trash, no cp 20:06:48 <hghoster> EinMByte: but there is one or two pages in English, for example ToS. wait a mmt plz 20:07:08 <EinMByte> So, maybe an english introduction would be nice? 20:07:08 <EinMByte> (even if the rest of the site is in russian) 20:07:08 <EinMByte> That sounds good 20:07:14 <zzz> hghoster has posted a English and Russian ToS as required: `http://hiddengate.i2p/wiki/ToS` 20:07:18 <iRelay> Title: HiddenGate Wiki: HiddenGate Wiki (at hiddengate.i2p) 20:07:20 <EinMByte> zzz: considering the amount of russian users, I think this would be a good addition 20:07:22 <hghoster> zzz thank you 20:07:48 <EinMByte> Well, I'd just like at least one english sentence on the homepage 20:08:05 <EinMByte> because visiting hiddengate.i2p was quite confusing for me 20:08:31 <EinMByte> and I suppose it would be like that for most non-russian I2P users 20:08:45 <EinMByte> nevertheless, I do agree with the proposal 20:09:18 <zzz> any other comments from the Russian users here - bgwcb denixx_ Nyakov ? 20:09:38 <hghoster> we may place some welcome text on the top of first page explainig for non-russian users where they are 20:10:12 <EinMByte> hghoster: this is what I mean 20:10:19 <hghoster> i'm logging our converstation and we'll discuss it later too 20:10:21 <hghoster> i think they may sleep :) but bgwcb not 20:10:22 <Nyakov> I think this is good idea 20:10:36 <bgwcb> i think if hiddengate get in start-home page it fill hiddengate of some good content 20:10:37 <hghoster> okay, i'll remember this, thank you 20:10:49 <EinMByte> After all, I assume that's what users coming from the control panel will see: the front page 20:10:49 <zzz> hghoster, I got some comments last week in #ru that your site had very little content on it. What are your plans to add more content? 20:10:53 <Yi> i think it's ok 20:11:12 <zzz> we do not want "dead" sites on our home page 20:11:17 <user@kyirc> +1 for the welcome sentence. the domain name is in English and I could have gotten to the site too, and then not even knowing what it is is kinda frutrating, even if the rest will be unintelligible for me anyway 20:11:53 <bgwcb> and it's good idea because they heaven't cp. new arrivals may be affraid darkness networks because it's shelter for pedofiles and terrorists 20:11:59 <hghoster> certainly plans are good :) there is another guy "Glavred", he is idea-creator of this project. i am workiing on it like admin. also there is few guys who continuing fill wiki 20:12:37 <hghoster> offcourse it fills not so fast as we want. but we continue our work anyway. until someone like mr. P will not close internets 20:12:48 <bgwcb> but, then i will be want to get on start page `http://rus.i2p` with comment it's have a some shock-content 20:12:50 <hghoster> sorry for my poor english 20:13:00 <iRelay> Title: I2P Wiki (at rus.i2p) 20:13:13 <zzz> no need for sorry, you are doing fine :)( 20:13:40 <zzz> ok, any other comments? I have not heard any objection so far? 20:13:53 <dg> Sounds good to me. 20:13:54 <EinMByte> zzz: regarding "dead" sites - look at it like this: if a site makes the homepage, this may very well increase traffic 20:14:09 <EinMByte> so, that could have a positive effect on content too 20:14:12 <dg> Furthermore, we can always remove a site if it's 'dead' 20:14:21 <EinMByte> exactly 20:14:45 <kytv> no issues here, but an introductory sentence or two in English (to match the language of the hostname) would be welcome. 20:15:26 <user@kyirc> the console tooltip could/should already mention it's in Russian. am pro 20:16:08 <hghoster> site is hosting outside of russia, so i think there no problems with it. also i'm c++er and have good work, so money not a problem. the main thing is how to propagand i2p more effectively. we hope that paper helps us 20:16:32 <hghoster> kytv: yes, certainly 20:16:48 <zzz> ok then, hghoster we approve your request and I will add it for 0.9.13. Thanks for attending the meeting and good luck with your site 20:16:48 <bgwcb> i'm for it to appear on front-page 20:16:48 <zzz> thanks also to our friends from #ru for helping us out 20:16:50 <psi> (c++ers are invited to help with i2pd and i2pcpp) <-- off topic 20:16:59 <zzz> moving on 20:16:59 <zzz> 2. OMGWTFBBQ Summer Europe - echelon 20:17:01 <zzz> eche|on, tell us about it 20:17:03 <hghoster> thank you all! 20:17:08 <bgwcb> thank you all it was an interesting 20:17:19 <eche|on> the BBQ 20:17:38 <eche|on> we always wanted to do a BBQ, I can offer to host one in this summer, in graz, austria 20:17:45 <eche|on> if we want to do one 20:18:18 <eche|on> money for drinks/food is available in funds IMHO, just the part about people to visit this BBQ is a topic... 20:18:28 <EinMByte> would be nice, but I would probably not attend (for reasons of anonimity) 20:18:35 <zzz> when? 20:18:46 <eche|on> I am more about end of august, september timeframe 20:19:21 <zzz> not to conflict with DEFCON, first week of August 20:19:33 <eche|on> right, I know 20:19:48 <bgwcb> It's good idea 20:19:58 <EinMByte> zzz: can I quickly append two things: one question about just mail, another about derbycon (offtopic, sorry) 20:20:11 <psi> on the topic of conferences orion and I are going to probably most likely be at derbycon 20:20:17 <eche|on> and I know not much people will come over, and I can only provide a place for bbq, no sleeping facility 20:20:23 <zzz> EinMByte, you will be number 4 on the agenda 20:20:33 <EinMByte> zzz: thanks 20:20:46 <zzz> psi, derbycon will be number 5 on the agenda 20:20:52 <psi> okay 20:20:56 <EinMByte> eche|on: bbq is definitely a good idea 20:21:05 <EinMByte> iff you can get enough people to attend 20:21:38 <bgwcb> but why is hosting outside of russia? 20:21:38 <zzz> anybody who is interested in a Graz BBQ late August / early Sept., please type "yes" or "maybe" 20:21:53 <EinMByte> zzz: attending or just support 20:22:09 <zzz> attending. 20:22:15 <zzz> I will say "maybe" 20:22:37 <bgwcb> maybe 20:22:56 <psi> "maybe" (if i can get there which is a very unlikely thing) 20:23:11 <eche|on> hm, I think I will start a questionaire in forum.i2p ? 20:23:26 <eche|on> graz is very good reachable by plane via Frankfurt ;-) 20:23:40 <eche|on> but thats expansive. I do know. 20:24:14 <zzz> eche|on, not a lot of support... perhaps a meetup or BBQ at a conference would be more popular? 20:24:17 <EinMByte> I too think it's best to move this matter to a forum or something 20:24:51 <bgwcb> where owned? 20:24:52 <eche|on> zzz: that would be better. if we find a conf which fits? 20:24:52 <bgwcb> sorry, where exactly 20:24:54 <EinMByte> 5? 20:24:54 <bgwcb> ? 20:24:55 <zzz> I would love a meetup in summertime, but combined with conf may make more sense 20:24:57 <eche|on> this year I do not have time to get to Las Vegas 20:25:45 <eche|on> (again) 20:25:48 <eche|on> but if you want to do something, the cash is available^^ 20:25:48 <zzz> ok, lets defer this topic for more research, maybe we can talk again in a couple weeks with ideas 20:25:48 <eche|on> I keep a eye on this 20:26:03 <EinMByte> good 20:26:14 <zzz> moving on 20:26:18 <zzz> 3. 0.9.13 release schedule 20:26:46 <zzz> we're about 4 weeks since 0.9.12 and our normal 5-8 week cycle gives us a release in late May 20:27:02 <dg> only 4.. 20:27:11 <zzz> rfree has been doing good research on the problems in 0.9.12 with firewalled routers and that -14 seems to help a lot 20:27:17 <EinMByte> what about those supposed problems with 0.9.12, have they been resolved (if there were any)? 20:27:19 <zzz> so he's recommending a release soon. 20:27:28 <EinMByte> oh right 20:27:50 <zzz> it seems to be only with firewalled routers, but that means all TAILS users too 20:27:56 <eche|on> zzz: how far have you come with susimail, done? 20:28:12 <zzz> yes I'm about done with susimail for now 20:28:24 <eche|on> ok, and Tails, next release at which date? 20:28:25 <zzz> so susimail + firewall fixes sounds good enough for a release 20:28:32 <eche|on> aka which date we need to be done? 20:28:33 <zzz> so maybe in either 2 weeks or 3? 20:28:58 <user@kyirc> -0 was bad for me, on lin, nonfirewalld, -4 fix reachablility. then on xp with firewall -0 was alsmot unusable. -14 works great 20:29:04 <eche|on> currently no problem with a shorter cycle 20:29:24 <user@kyirc> dunno about the console locking prob though, which was on -14 20:29:36 <zzz> checkin deadline May 16 or 23, and release May 19 or 26 20:29:47 <eche|on> may 16 would be better (29th is holiday) 20:29:50 <dg> I say 16/19 provided there's no deadlocks and stuff. 20:30:10 <dg> If user's still suffering, hold off. 20:31:10 <zzz> OK let's shoot for the 16th for a deadline and a release on the 19th. If we have unresolved problems then we will push it back 20:31:20 <EinMByte> ok 20:31:45 <user@kyirc> on the xp it's perfectly fine. the console thingy in MY case can be caused by myself, since I tried a plugin that was still depending on an older version of jetty. maybe that changed something in my settings, for the problems remained after removing the plugins. but that's just in MY case 20:32:14 <user@kyirc> if no one else has that problem, then -14 is a good release candidate, imho 20:32:49 <zzz> moving on: 4) EinMByte Just Mail 20:32:49 <EinMByte> yes, just a minor question 20:32:49 <EinMByte> orion: ding 20:32:54 <EinMByte> So my question was: has orion been able to get in touch 20:33:07 <EinMByte> and second of all: what the hell are they doing 20:33:16 <EinMByte> imho, it doesn't seem like it can work 20:33:20 <zzz> he got a reply and copied me, it didn't really say much 20:33:26 <EinMByte> so I think they need some advice 20:33:30 <EinMByte> zzz: could you paste 20:33:38 <EinMByte> I'm interested 20:34:04 <EinMByte> as I wrote on `http://zzz.i2p/topics/1614,` I doubt about their ideas 20:34:10 <iRelay> Title: zzz.i2p: Just Mail Kickstarter (at zzz.i2p) 20:34:28 <EinMByte> * the feasability of their ideas 20:35:09 <zzz> I'll paste it onto that thread after the meeting.. It's just marketing b.s., doesn't really explain anything. 20:35:26 <EinMByte> alright, thanks 20:35:44 <zzz> anything else on Just Mail? 20:35:47 <EinMByte> I think that will do for 4, it doesn't seem like this is going to work out 20:36:12 <EinMByte> (I'm sorry for the people who invested in it, too) 20:36:25 <zzz> moving on 20:36:37 <zzz> 5) DerbyCon EinMByte psi orion 20:36:55 <psi> i believe that orion and I will be able to attend derbycon 20:37:00 <EinMByte> again, I wanted to know the status on that 20:37:07 <EinMByte> okay, any talks yet? 20:37:20 <psi> i was hoping you two could give one 20:37:29 <zzz> `http://zzz.i2p/topics/1579` 20:37:33 <iRelay> Title: zzz.i2p: Derbycon Louisville Sept. 24-28 (at zzz.i2p) 20:37:44 <EinMByte> zzz: no chance of you giving a talk? 20:38:20 <zzz> A chance, but I vote for our PR guy orion 20:38:24 <EinMByte> also, does anyone know whether or not these talks are being broadcasted? 20:38:50 <psi> if they are you could always dress like the unibomber (str4d) 20:39:25 <zzz> psi, orion, I recommend you contact Adrian immediately to find out the CFP schedule and process and find out what kind of talk would be appropriate 20:39:35 <psi> okay 20:39:46 <zzz> This is mainly an InfoSec conf, much different from DEFCON/HOPE/CCC etc 20:40:39 <EinMByte> It is important that we have a talk, because that will definitely spread the word 20:40:54 <EinMByte> (also more chance of academic research) 20:41:13 <zzz> speaking of HOPE: `http://zzz.i2p/topics/1507` 20:41:19 <iRelay> Title: zzz.i2p: HOPE X (at zzz.i2p) 20:41:36 <zzz> and DEFCON: `http://zzz.i2p/topics/1556` 20:41:42 <iRelay> Title: zzz.i2p: DEFCON 2014 (at zzz.i2p) 20:42:07 <zzz> anyway, psi and orion, if you guys go to DerbyCon there's a chance I'll go too. 20:42:18 <zzz> eche|on, Louisville BBQ? 20:42:22 <EinMByte> in an ideal world, we'd have a talk on all of those conferences 20:42:30 <psi> ooh that sounds nice, BBQ in KT 20:42:51 <zzz> KY 20:43:02 <psi> it's KY? dang 20:43:50 <zzz> two or three of you should co-author a talk and leave me out of it. That would be best :) 20:44:00 <zzz> anything else for the meeting? 20:44:10 * zzz warms up the baffer 20:44:14 <user@kyirc> it's not a topic on the agenda, but I think, we should start thinking about our official in-network homepage. www.i2p2.i2p is ugly. it was chosen in order to match the public internet domain of i2p2.de. since this one is not our main address anymore, we should also think about a nicer in-network domain. i2p.i2p for instance. dunno if geti2p.i2p makes sense, as you don't need to _get_ i2p anymore. 20:44:23 <eche|on> zzz: louiesville, time, place? 20:44:39 <zzz> `http://zzz.i2p/topics/1579` 20:44:44 <iRelay> Title: zzz.i2p: Derbycon Louisville Sept. 24-28 (at zzz.i2p) 20:44:53 <user@kyirc> not urgent, but maybe something to think about, and easy to "fix" 20:45:22 <EinMByte> yes, new homepage would be nice 20:45:22 <eche|on> hm, at this date I wanted to be in scotland 20:45:30 <zzz> user, that's welterde. In the router console we have removed all references, we now point to i2p-projekt.i2p 20:45:59 <user@kyirc> which is not perfect either, because of the k 20:45:59 <zzz> thanks everybody for a good meeting 20:46:09 <eche|on> would need a check on timetables 20:46:20 <EinMByte> zzz: one last thing, do you plan on having regular meetings 20:46:30 <user@kyirc> as it's a link it's not that much of a problem, but still an english-language name would be better, imho 20:46:44 <EinMByte> (unless that's already the case?) 20:47:02 <zzz> EinMByte, we schedule meetings as-needed. Anybody can schedule a meeting at any time for any topic. 20:47:17 <EinMByte> zzz: alright 20:47:23 <user@kyirc> what's wrong with i2p-project.i2p ? already registered by someone else? 20:47:47 <eche|on> but louisville is nice to reach and central 20:47:50 <zzz> EinMByte, `http://zzz.i2p/topics/1491` 20:47:55 <iRelay> Title: zzz.i2p: Project Meetings (at zzz.i2p) 20:48:37 <EinMByte> I'm thinking about an i2pcpp meeting 20:48:42 <EinMByte> but I need to discuss with orion 20:48:44 <zzz> if we are going to DerbyCon we should try to convince Lance to go too 20:50:03 <eche|on> ok, I keep this in head and I went off for bed 20:50:04 <eche|on> cya later 20:50:19 <zzz> any talk will have to be kickass to be accepted. DerbyCon was small the first year but this is the 4th year I think. We have a little bit of inside track with irongeek but it's not just his show. 20:50:55 <EinMByte> btw, I'm willing to look at slides etc etc. Not sure if it would help a lot but you never know 20:51:51 <EinMByte> anyway, bye

I2P Dev Meeting - April 22, 2014

Tue, 22 Apr 2014 00:00:00 +0000

Quick recap

Present: hottuna, nombre\_, psi, str4d, zzz2

Meeting Log

20:32:31 <str4d> Hi all 20:34:53 <str4d> 0) Hi 20:34:53 <str4d> 1) TODO 0.9.13-0.9.16 `http://zzz.i2p/topics/1600` 20:34:53 <str4d> 2) New transport for Tor PTs `http://zzz.i2p/topics/1551` 20:34:53 <str4d> 3) Any items that emerge from 1) 20:34:53 <str4d> Post-meeting activity: Stress-testing Mumble (voice chat over I2P) 20:35:07 <iRelay> Title: zzz.i2p: TODO 0.9.13 - 0.9.16 (at zzz.i2p) 20:35:10 <iRelay> Title: zzz.i2p: Supporting Tor Pluggable Transports (at zzz.i2p) 20:35:29 <str4d> 0) Hi 20:35:57 <hottuna> Hello 20:37:37 <str4d> Anyone else? 20:38:01 <str4d> zzz2 orion psi kytv meeh_ 20:41:17 <str4d> Hopefully some of them will turn up. 20:41:17 <str4d> 1) TODO 0.9.13-0.9.16 `http://zzz.i2p/topics/1600` 20:41:22 <iRelay> Title: zzz.i2p: TODO 0.9.13 - 0.9.16 (at zzz.i2p) 20:41:26 <zzz2> here 20:41:58 <str4d> At zzz's request we started a discussion thread to propose ideas for the I2P roadmap moving forward. 20:42:27 <str4d> There was a lot of chatter, but no actual consensus was reached. 20:43:14 <str4d> I summarized some of the initial suggestions on the roadmap page `http://trac.i2p2.i2p/wiki/Roadmaps/1.0` 20:43:17 <iRelay> Title: Roadmaps/1.0 I2P Bugtracker (at trac.i2p2.i2p) 20:45:01 <str4d> zzz2: I see you have been getting stuck into susimail (yay) 20:46:19 <zzz2> yeah, fell down that rathole while we try to decide what's really important 20:52:07 <str4d> I think that it was useful work, if only because there is a long-standing bug about login problems, and susimail is one of the first apps that users are going to try 20:52:08 <str4d> `http://trac.i2p2.i2p/ticket/747` 20:52:12 <iRelay> Title: #747 (Login problems with Susimail) I2P Bugtracker (at trac.i2p2.i2p) 20:54:45 <psi> str4d: ohai 20:54:47 * psi is late? 20:55:19 <str4d> yes psi is 20:55:25 <str4d> Nothing much has happened yet :/ 20:55:58 * psi scrolls up 20:56:07 <str4d> To summarize what has been going on since the RFC was put out: 20:56:18 <str4d> - zzz has worked on susimail 20:56:59 <str4d> - psi has been getting his head around PTs, new DH and JNI 20:57:23 <str4d> - I have been working on I2P-Bote Android, and now Java EdDSA 20:57:39 * psi has been spending the entire day fleshing out the structure of PT for i2p 20:58:59 <zzz2> if str4d and psi are making progress on EdDSA, 25519, and PTs, then I think the best use of my time is moving forward on new sig algo migration, e.g. multiple dests down a tunnel, and some sort of addressbook support 21:00:27 <jenkins@kyirc> Starting build #581 for job I2P 21:01:01 <zzz2> whats the status of psi mtn keys and dev agreement? I've gotten nothing in the mail. 21:01:23 <str4d> psi signed the dev agreement, I pushed it to the website 21:01:36 <str4d> (so his pub keys are on record) 21:02:10 <zzz2> his key fingerprint is on there too? 21:02:32 <zzz2> if so I'll add him and announce it 21:03:02 <psi> my gpg fp is on my twitter 21:03:05 <str4d> not the fingerprint, but the key itself is 21:03:47 <zzz2> it needs to be in that sample monotonerc template file. psi maybe you can do that as your first test of mtn skills? 21:04:23 <jenkins@kyirc> Yippee, build fixed! 21:04:24 <jenkins@kyirc> Project I2P build #581: FIXED in 3 min 55 sec: `http://jenkins.killyourtv.i2p/job/I2P/581/` 21:04:36 <psi> i can get that 21:04:40 <psi> i already did that locally 21:04:53 <str4d> zzz2, psi, I have updated the roadmap Gantt - `http://trac.i2p2.i2p/wiki/Roadmaps/1.0` 21:04:56 <iRelay> Title: Roadmaps/1.0 I2P Bugtracker (at trac.i2p2.i2p) 21:05:21 <psi> the monotone key fp for my NOT transport key is "1ceb85b992114bae1bcb156ef238f8f3044a6bfe", -- ampernand@gmail.com 21:06:04 <psi> i can get my transport key fp as well 21:06:29 <zzz2> ok great, welcome to the team! As I tell everybody, please be careful, practice on www first 21:06:30 <str4d> psi: you need to send that to eche, kytv and welt 21:06:43 <str4d> +1 21:06:56 * kytv got it and is adding it to his server 21:07:08 <zzz2> psi, we have very precise instructions on how to do all this on the web page... :) 21:07:27 <psi> i will review that 21:07:38 <zzz2> e.g., send me mail (but no longer needed for you) 21:08:15 <str4d> How does the Gantt roadmap look to everyone now? Are there any items that seem unrealistic, or any that are missing 21:08:16 <str4d> ? 21:09:37 * psi reviews roadmap 21:09:43 <jenkins@kyirc> Project I2P UnitTests build #528: SUCCESS in 5 min 6 sec: `http://jenkins.killyourtv.i2p/job/UnitTests/528/` 21:09:57 <jenkins@kyirc> Starting build #82 for job I2P-Android 21:09:59 <str4d> zzz2: I suggest that you get the new GPG keys item out of the way sooner rather than later ;) 21:10:19 <zzz2> str4d, please tell us what it's telling you about what's important 21:10:33 <str4d> psi: are you finding much overlap between your PTs work and NTCP2? 21:10:34 <zzz2> yes I'll do it before the next release, I promise 21:11:24 <str4d> IMHO there are three things that are important: 21:11:32 <jenkins@kyirc> Project I2P-Android build #82: SUCCESS in 1 min 34 sec: `http://jenkins.killyourtv.i2p/job/I2P-Android/82/` 21:11:40 <str4d> 1) progress on the crypto upgrade - now finally getting underway 21:12:01 <psi> str4d: at the moment, i have yet to look at ntcp2 21:12:13 <str4d> (continuing on from the prep work) 21:13:28 <zzz2> 1) "now getting underway" ? I've been busting ass on it for 6 months 21:13:32 <str4d> 2) Audit prep - IMHO we need to get on top of our threat model etc. ASAP 21:15:33 * psi afks for 30 minutes 21:15:33 <psi> unexpected event bbl 21:15:33 <psi> i will look at scrollback later 21:16:21 <zzz2> There seems to be some confusion out there about "new signing crypto". It's done, it's out there in 0.9.12, it works. For destinations. 21:17:06 <zzz2> The "only" thing not done is migrating existing published destinations to a new one. 21:21:13 <str4d> yes, which first relies on choosing a new one, which IMHO should be Ed25519, which relies on getting a fast impl. 21:21:15 <str4d> And at the same time, I agree that the remaining required migration infrastructure should be implemented. 21:21:16 <str4d> <str4d> For years we have left it to the side and worked on what we think is beneficial to users, but IMHO if we want to start getting more research interest, and utilize it effectively, we need to be more conscious of what I2P can and cannot achieve. 21:21:17 <str4d> <str4d> I know you have zzz ;P 21:21:18 <str4d> <str4d> (I was specifically referring to the part of it involving the actual new crypto) 21:21:19 <str4d> <str4d> thank you for the effort you have put into getting it this far :) 21:21:20 <str4d> <str4d> 3) Usability, UX - this is a third important point that is not on the Roadmap chart 21:21:22 <str4d> <str4d> Well - zzz's susimail work falls into that category, as does streaming improvements 21:21:41 <str4d> <str4d> But also important is reviewing our error and help pages, and how we aid the user in getting their jobs done. 21:21:41 <str4d> (after my "2) Audit prep" line) 21:22:00 <str4d> I need to go AFK in 10-15 mins 21:22:50 <str4d> And since psi is AFK, I'm dropping "2) New transport for Tor PTs" from this meeting 21:23:55 <str4d> zzz2: in your opinion, what do we need to do before organizing a meeting with Lance re: threat model? 21:24:59 * str4d would like to try for a meeting with Lance in May 21:26:04 <str4d> so we need to work out what we need to do before then, so we can organize the meeting with enough time to finish that first. 21:29:27 <zzz2> I disagree that we first have to choose. 21:29:59 <zzz2> Or, that we can choose now (P256) and choose again later when more options are available. 21:30:02 <MTN@kyirc> [ I2P ] compile fix [zzz@mail.i2p] `http://killyourtv.i2p/viewmtn/revision/info/12396c3ee88d1194482fc2cc3751db1169cc52e3` 21:30:34 <zzz2> We could switch the default for new dests to P256 in 0.9.13 if we want. 21:30:35 <str4d> zzz2: if we get to the stage where the naming system can cope with dynamic enc choices, then I agree 21:31:05 <zzz2> P256 is clearly better than DSA 21:31:34 <str4d> I also agree there. 21:31:43 <zzz2> I think the P256 haters better take a step back and think about how bad DSA 1024 is. 21:32:03 <MTN@kyirc> [ WWW ] adding psi's transport key [kytv@mail.i2p] `http://killyourtv.i2p/viewmtn/revision/info/029163d2d446f10ab1a129b559802fabac2ef8b7` 21:32:52 <str4d> zzz2: I understand your point. 21:33:39 <zzz2> re: audit and Lance, it's always a good time. you have an audit process update for us from the mailing list? 21:33:40 <str4d> Part of my reason for wanting to get EdDSA working before the switch is that based on what you have said in threads before, I wouldn't look forward to switching Dest signing algo twice. 21:34:14 <str4d> yes, the second time would be a bit easier because multi dest support etc. would be there, but the naming side is still the weakness. 21:34:48 <zzz2> for servers you don't want to switch twice, but for clients it doesnt matter 21:35:04 <str4d> good point. 21:35:23 <str4d> Is there anything that would prevent new Dests talking with old ones? 21:35:31 <nombre_> so i gather you guys are doing crypto upgrades? is there perhaps a page that goes into detail on what all you're planning? and on a 25519 implementation, you could just use nacl via jni, or kalium, tho that might be somewhat limiting 21:35:34 <zzz2> and even for servers, if you switch to P256 it hardly seems worth it to switch again, unless some really bad news comes out about P256 21:35:54 <str4d> If not, it could be a good idea to get clients onto P256 sooner 21:36:08 <zzz2> new dests can talk to old and vice versa, as long as both are on 0.9.12 or later 21:36:39 <str4d> zzz2: http://blog.cr.yp.to/20140323-ecdsa.html is reason enough for me to not want to stay on ECDSA 21:36:43 <iRelay> Title: cr.yp.to: 2014.03.23: How to design an elliptic-curve signature system (at blog.cr.yp.to) 21:37:56 <str4d> not for any one single point (yet), but if we can get an effective, *correct* implementation of EdDSA, I think it would be very beneficial to switch 21:38:27 <str4d> nombre_: `http://trac.i2p2.i2p/ticket/856` 21:38:30 <iRelay> Title: #856 (Crypto review/migration) I2P Bugtracker (at trac.i2p2.i2p) 21:38:30 <str4d> (and links therein) 21:38:40 <nombre_> thx str4d 21:38:53 <zzz2> nothing there tells me to delay getting rid of DSA though. There's nothing in there that makes me panic about P256 either. Is there anything better than P256? sure. 21:39:15 <str4d> zzz2: no real updates as such from the OpenITP mailing list, there hasn't been much real activity lately. 21:40:38 <zzz2> I allowed for 65536 signing algos and I implemented 7. 65529 to go, we can add a few every release if we like. 21:43:27 <str4d> zzz, I would support moving clients to p256 in 0.9.13 21:44:47 <str4d> but if the server transition is still not going to be smooth, I'd rayher hold off a bit and see how EdDSA work goes. 21:45:49 <nombre_> as would i (not that my opinion counts for anything), nist ecdsa is better than dsa, even if some of us tinfoilers won't feel secure until its 25519 21:46:48 <nombre_> dest/b32 breaking is sorta a given tho yes? 21:47:13 <str4d> it's taken a long time and a lot of work to get to this point, no sense rushing at the last minute 21:49:48 * RN pokes head in and looks around 21:54:36 <zzz2> there's 1) clients 2) new servers and 3) existing server migration. 21:54:43 <zzz2> 1 and 2 we can do now, 3) takes a lot more work. 21:54:59 <zzz2> 1 and 2 breaks compatibility with old routers, i2pcpp, and i2pd though, until they catch up 21:55:16 <nombre_> so is there someone working on finding/creating a java implementation of 25519? and whats the estimated timeframe on when it would be usable? 21:55:28 <nombre_> i assume with p256, its already doable because thats included in bouncy castle? 21:55:52 <zzz2> p256 is in the jvm 21:56:06 <nombre_> ah even better 21:56:17 <zzz2> we have 25519 java now but it's far too slow to be usable. str4d and psi are trying to speed it up 21:57:39 <nombre_> hmm well not knowing anything about crypto, i would think using jni would be the simplest way to speed it up. perhaps i should look into 25519 more to understand what parts of it are the bottlenecks 23:02:36 <str4d> No one actually ended it when I went afk, so: 23:02:53 * str4d *baf*s the meeting closed.

0.9.12 Release

Mon, 31 Mar 2014 00:00:00 +0000

I2P now requires Java 6 or higher. We strongly recommend that you upgrade to Java 7. If you are still using Java 5, you must upgrade your Java before installing I2P 0.9.12.

0.9.12 adds preliminary support for ECDSA-signed Destinations. It contains several fixes for the handling of Delivery Status Messages (acknowledgements) and those messages are now end-to-end encrypted for increased security.

We have upgraded to Jetty 8. Jetty 8 is almost identical to Jetty 7, so there are no complex configuration file conversions as there have been in past Jetty upgrades. No manual changes should be necessary.

Search Engine DuckDuckGo Awards Invisible Internet Project $5000

Wed, 12 Mar 2014 00:00:00 +0000

Somewhere, NH – Internet search company DuckDuckGo donates $5000 to the Invisible Internet Project (I2P) as part of their yearly open-source donation program. The award was granted on the basis of nominations by members of the public on the DuckDuckGo community portal. With an emphasis on privacy, DuckDuckGo provides a search engine which does not track its users or store personal data. I2P is an anonymous network intended to protect individuals from dragnet surveillance regularly performed by ISPs and governments.

I2P Dev Meeting - March 11, 2014

Tue, 11 Mar 2014 00:00:00 +0000

Quick recap

Present: AK-47, eche|on, efkt, inscrut\_, kytv, orion, psi, str4d, topiltzin, zzz

Meeting Log

20:00:26 <zzz> 0. Hi 20:00:26 <zzz> 1. anoncoin.i2p console home page request (Meeh) 20:00:26 <zzz> 2. Git (Meeh) 20:00:26 <zzz> 3. Echelon reduced services / incorporation 20:00:26 <zzz> 0. Hi 20:00:27 <zzz> Hi 20:00:33 <zzz> Let's limit each topic to about 15 minutes 20:01:43 <eche|on> hi 20:02:02 <orion> Hi. 20:02:29 <inscrut_> hi eche|on 20:02:39 <inscrut_> o/ orion 20:02:48 <topiltzin> hi 20:04:08 <inscrut_> yo topz 20:05:15 <str4d> hey 20:05:26 <topiltzin> netsplit 20:05:54 <str4d> boo 20:05:59 <str4d> hiss 20:06:15 * inscrut_ lobs a tomato 20:08:58 <topiltzin> alright, meeting's over. Move along now 20:09:01 <eche|on> on topics 0-2 I am rather more or less "go ahead". 20:09:12 <zzz> ok lets try this again 20:09:12 <zzz> <zzz> 0. Hi 20:09:12 <zzz> <zzz> 1. anoncoin.i2p console home page request (Meeh) 20:09:12 <zzz> <zzz> 2. Git (Meeh) 20:09:12 <zzz> <zzz> 3. Echelon reduced services / incorporation 20:09:12 <zzz> <zzz> 0. Hi 20:09:12 <zzz> <zzz> Hi 20:09:12 <zzz> <zzz> Let's limit each topic to about 15 minutes 20:09:12 <zzz> <zzz> For 2 and 3, which are large and oft-discussed topics, let's focus on where we are now and what to do next, not how we got here 20:09:12 <zzz> <zzz> I don't expect to reach any decisions on 2 or 3, but it would be nice to come up with next steps for research if necessary 20:09:12 <zzz> <zzz> Also, background on the agenda items are at the link in /topic above. 20:09:12 <zzz> <zzz> 1. anoncoin.i2p console home page request (Meeh) 20:09:12 <zzz> <zzz> Meeh are you here? 20:09:12 <zzz> <zzz> skipping 1 and 2 20:09:12 <zzz> <zzz> 3. Echelon reduced services / incorporation 20:09:12 <zzz> <zzz> eche|on, are you here? 20:09:44 <zzz> so we skipped 1 and 2 and are on 3. eche|on the floor is yours 20:10:12 <eche|on> due to a lot of private and non private issues, I reduced my services and will reduce some more 20:10:20 <eche|on> e.g. false.i2p is down 20:10:48 <eche|on> which service will be next I cannot tell currently, I will keep on being the money guy for this year at least 20:11:27 <eche|on> I just got some thoughts now tha I could not stop I2P from loosing money due to fraud and other stuff, it gets harder 20:11:54 <eche|on> also the more money, the tougher it gets, esp. with companies donation money to us, which we should spent on "useful" stuff. 20:12:17 <orion> I'd like to interject. 20:12:19 <eche|on> it is all not really clear, more a "feeling", I know, but I just want to inform you 20:13:33 <AK-47> Thanks for the time it lasted, anyway. 20:13:33 <psi> hi 20:13:33 <zzz> eche|on, you have any specific proposals to bring to us today? 20:14:30 <zzz> two possibilities that may lessen your workload slightly - making orion "asst. treasurer - U.S. $$" and Meeh "asst. treasurer - BTC/altcoin" --- would either of those help at all? 20:14:31 <eche|on> my propopsal: think hard about getting incorporated and if not 20:14:50 <eche|on> a $ treasurer will help for $ donations, sure 20:15:00 <eche|on> and meeh for alt/btc would be fine, too 20:15:43 <inscrut_> is it possible to publicise the books? perhaps as a dual-entry ledger? 20:15:52 <eche|on> books? 20:16:01 <eche|on> `http://echelon.i2p/donations/index.html` 20:16:09 <iRelay> Title: Donations (at echelon.i2p) 20:16:26 <orion> I want to make two separate proposals. The first one is thus: We should keep the money spread out in multiple currencies (dollar, euro, *coin). 20:16:39 <orion> And they should be held in different jurisdictions. 20:16:40 <eche|on> my bigger problem/fear is the amount of nearly 40k in my hand. as this is "official" my money, for the law. not I2p. 20:17:54 <str4d> hmm. So if you independently have financial trouble, legally you would need to wipe out I2P funds. 20:18:15 <eche|on> correct 20:18:32 <eche|on> thats the problem with being not a legal entity 20:18:54 <eche|on> and thats why I do not want more than 50k here, more or less 20:21:36 <orion> eche|on: Before considering incorporation, do you agree that the money should be held in both different currencies and jurisdictions? 20:21:43 <eche|on> I do not have big problems (personal) with more than 50k, but if there are problems, I2P will loose, which is not my intention 20:22:05 <zzz> there's some benefit in keeping a $$ account. Much of our income and expenses is in $$ and we lose lots in the round-trip conversions 20:22:13 <eche|on> orion: a US based $ account is usefull and if someone wants it: yes 20:22:34 <orion> I will volunteer to hold USD in an account. 20:23:40 <zzz> is it managable for mutliple ppl to hold money and yet roll up the totals and transactions on the hall-of-fame page? 20:24:25 <eche|on> it is possible due to mtn/git hosting of our webpage 20:24:42 <eche|on> we would need a table/section for each currency 20:25:06 <str4d> displaying it is simple 20:25:07 <eche|on> if we want to divide ONE currency upon 2+x people, they need to interact good 20:26:58 <zzz> eche|on would remain treasurer and responsible for keeping the totals, with assistants responsible for keeping track of their part? 20:27:00 <eche|on> about incorporation: 50k is not worth the hassle IMHO, but there IS a risk 20:27:16 <eche|on> zzz: would be fine. 20:27:30 <zzz> incororation does very little to reduce risk 20:27:50 <eche|on> but it takes the risk off me ;-) 20:29:03 <orion> I have a proposal that doesn't involve incorporation: a trust fund 20:29:03 <str4d> doesn't prevent willful money loss, but prevents legal loss due to personal insolvency 20:29:06 <zzz> so the proposal is to make orion an assistant treasurer - U.S. --- any objections or further discussion on that? 20:29:07 <topiltzin> don't spend the bitcoins on acid 20:29:09 <str4d> I second orion's nomination 20:29:59 <zzz> ok sounds like a done deal, eche|on and orion can work out the details. 20:30:16 <eche|on> addendum to the topic list: 20:30:24 <eche|on> 4. 50BTC Bitcoin client bounty 20:30:43 <zzz> We're about at the end of our 15 minutes. Any next steps on incorporation or proposals or things to do or research re: incorporation? 20:30:53 <eche|on> 50BTC is alot of money for a plugin of I2P btc. Proposal: reduce to 10 and 40BTC into general fund 20:31:05 <zzz> ok ech you're on the list for #4 20:31:15 <orion> topiltzin: I won't. :x 20:31:29 <zzz> last call for topic 3 20:31:35 <orion> zzz: Trust fund. 20:31:52 <orion> I want to propose that as a cheap alternative to incorporation. 20:32:25 <zzz> ok, how about if you write up a proposal and post it somewhere and we can discuss at a future meeting? 20:32:41 <str4d> With e.g. What are the legal differences? 20:33:46 <zzz> declaring end of topic 3 20:33:50 <zzz> back to topic 1 20:33:52 <zzz> 1. anoncoin.i2p console home page request (Meeh) 20:34:09 <zzz> any discussions agreement or objections to anoncoin.i2p on the home page? 20:34:44 <eche|on> go ahead, add it 20:35:41 <zzz> anoncoin could be about to go big and Meeh's working on marketing it more to the I2P community 20:35:48 <zzz> last call for 1 20:36:22 <eche|on> I would be carefull about "getting big" even litecoin did not got big, its all a bit of a hype, but hey, great anoncoin is known for I2P 20:36:40 <eche|on> to bad snowden did no marketing for I2P 20:36:49 <zzz> heh. 20:37:03 <zzz> but talk to Meeh if you have any questions about his plans 20:37:06 <str4d> I couldn't view the website, but I have no obvious objections. 20:37:08 <eche|on> will do 20:37:16 <zzz> end of 1. I'll add it. 20:37:17 <zzz> 2. Git (Meeh) 20:37:30 <efkt> +1 for anoncoin 20:37:38 <orion> No objections for anoncoin. 20:37:39 <eche|on> git - no real objection, except the resume issue and a need for a howto 20:37:40 <zzz> any thoughts on git? 20:37:56 <zzz> is there a resume issue? 20:38:08 <str4d> Pros: 20:38:12 <eche|on> afaik GIT does not resume 20:38:16 <str4d> Everyone knows it 20:38:24 <orion> Wait, what is resume? 20:38:32 <orion> What is the context of this topic? 20:38:50 <zzz> `http://zzz.i2p/topics/1588` <--- context 20:38:56 <iRelay> Title: zzz.i2p: Meeting Tues. Mar. 11 8 PM UTC (at zzz.i2p) 20:38:57 <topiltzin> If the connection breaks during a fetch/clone/pull/push 20:39:03 <eche|on> orion: on a big clone/pull/... tunnel breaks, does git start over from beginning or in middle of transaction? 20:40:11 <str4d> Everything supports it 20:40:12 <str4d> Can sign or approve commits with GPG keys 20:40:12 <str4d> orion: possible mive from mtn to git 20:40:12 <str4d> Cons: 20:41:09 <str4d> - Resume not supported (if a pull fails partway you have to start from beginning) 20:41:09 <str4d> - local timezone stored in commit 20:41:09 <str4d> (fix with alias git='TZ=UTC git') 20:41:41 <zzz> HH recently accepted a pull request on github i2p.i2p. If he can do that, why switch to git? Is real git better than exporting? 20:42:05 <topiltzin> real git would be anonymous as we wouldn't be using github 20:42:42 <topiltzin> there are other issues with exporting - changes since last export not visible until the next export 20:42:49 <zzz> I thought the point was to make github pulls easier 20:43:26 <zzz> if a new contributor has to run git inside i2p, did we really make it any easier for him? 20:43:58 <topiltzin> if we did what? 20:44:14 <zzz> switched to git, whatever that means 20:44:37 <topiltzin> I assume we would have in-i2p as well as clearnet git servers, much like we have them in mtn now 20:45:46 <topiltzin> and they would sync periodically just like now. Conceptually everything stays the same, all we change is the software 20:45:53 <zzz> I guess I dont know how pull requests work so I'll stop asking questions 20:47:30 <topiltzin> pull request is like saying: "Please sync from my git repo" 20:47:56 <topiltzin> on a conceptual level there is very little difference between git and mtn. It's surprising how similar their mechanisms are 20:47:56 <zzz> how about a straw poll - anybody who has an opinion, type in ++, +, 0, -, or -- for strongly in favor/in favor/neutral/opposed/strongly opposed to moving to git 20:48:05 <topiltzin> ++ 20:48:08 <orion> ++ 20:48:17 <eche|on> 0 20:49:02 <zzz> 0 20:50:14 <zzz> any volunteers to research further and report back? 20:51:08 <topiltzin> any specifics on what to research? 20:51:28 <zzz> we have e.g. viewmtn, trac, and some mtn stuff embedded in our build scripts that would all need to be addressed. Anybody to make a list of what would be required and how much work 20:51:59 <zzz> and whether the resume issue is a serious problem or not 20:53:01 <zzz> well then, lets put it back on Meeh since it's his agenda item. We'll ask him to report back at a future meeting. 20:53:10 <zzz> anything else on 2? 20:53:12 <topiltzin> I'll take a look, although I imagine kytv would know best about the build scripts, no? 20:53:42 <zzz> the build stuff is mostly my doing 20:53:52 <zzz> end of 2) 20:53:59 <zzz> 4. 50BTC Bitcoin client bounty - echelon go 20:54:39 <eche|on> ok, the native bitcoin client still has 50 BTC leftover for the task of "integrating btc client into I2P client", aka: plugin 20:55:38 <eche|on> there is already a btc client for I2p (IMHO giv made it) and he got 68 BTC and 30 from the bounty for the standalone client 20:56:08 <eche|on> now: 50 BTC is A LOT for making a plugin. I would like to split it, e.g. 10 BTC for plugin, 40 for general fund 20:56:28 <str4d> even 10BTC is a lot. 20:57:12 <kytv> (1BTC is a lot) 20:57:22 <kytv> (for a plugin) 20:59:04 <eche|on> I do not know, thats why I set it on topic 20:59:16 <eche|on> I do not want to be the bad guy "stealing" money from bounties 21:02:42 <zzz> no objections to splitting it 21:03:00 <eche|on> ok 21:03:09 <eche|on> will do so 21:03:22 <zzz> anybody else with thoughts on 4) 21:03:45 <kytv> just to be clear: no objections on splitting. 21:03:52 <zzz> anything else for the meeting? 21:04:23 * zzz encourages people to discuss things between meetings 21:04:41 <kytv> (big objection to 50BTC going to a plugin...i mean http://coinmill.com/BTC_EUR.html#BTC=50) 21:04:45 <iRelay> Title: Convert Bitcoins (BTC) and Euros (EUR): Currency Exchange Rate Conversion Calculator (at coinmill.com) 21:04:53 <zzz> and reminds that anybody can schedule a meeting on any topic at any time 21:05:06 * zzz *bafs* the meeting closed

Malware at i2pbrowser.net

Sun, 16 Feb 2014 00:00:00 +0000

We have recently been made aware of the existence of i2pbrowser.net. This website copies our homepage and download page, and attempts to trick users into downloading Windows malware.

There are several indicators that point to i2pbrowser.net being a malware site:

The domain was registered on February 10th, 2014.
The download URLs for Windows, Mac OSX, Linux, Android etc. all link to the same .exe file.
The .exe is only 741 KB; the official Windows installer for I2P is 13 MB.

We have not examined the malware ourselves, but it does not appear to be very sophisticated; it is not integrated into or bundled with the I2P software. Information security expert Lance James posted a tweet labelling it as “a standard dark comet rat”.

0.9.11 Release

Sat, 08 Feb 2014 00:00:00 +0000

0.9.11 continues improving LeaseSet lookup and storage to prevent an attacker from correlating a Destination with a Router. It adds support for the Orchid outproxy plugin which is available at plugins.i2p. There is a reduction in memory usage due to fixes in the transports. We have some I2CP protocol improvements that will provide better lookup facilities and authorization protection for external clients. Of course, there’s also the usual collection of bug fixes. All users should update.

0.9.10 Release

Wed, 22 Jan 2014 00:00:00 +0000

0.9.10 changes the mechanism for doing LeaseSet lookups, making it more difficult for an attacker to correlate a Destination with a Router. It also fixes character encoding bugs in susimail, and includes lots of other bug fixes and translation updates. Most of you will update via torrent, using the new “su3” update format with stronger keys.

We recently attended 30C3 and Real World Crypto , making several new connections and formulating big plans for 2014. Thanks to those who supported our attendance with their donations!

Syndie 1.105b Release

Tue, 21 Jan 2014 00:00:00 +0000

This is the first stable release since February 2013. It is essentially the same as 1.104b-7-rc, with some translation updates.

All binaries and source packages are at syndie.de and syndie.i2p. Plugins are available at plugins.i2p and stats.i2p.

For those of you upgrading from 1.103b, you will find syndie startup and shutdown much faster due to the new version of HSQLDB.

Wed, 02 Oct 2013 00:00:00 +0000

0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some people. New installs and non-Windows platforms are not affected, however all platforms will automatically update even if running 0.9.8.

See the Trac ticket for details and workarounds. See the 0.9.8 release notes for information on IPv6 and other changes.

Due to recent attacks, logins are disabled on Trac and new registrations are disabled on zzz.i2p. Until those services are restored, please report all bugs on IRC freenode or IRC2P #i2p-dev.

0.9.8 Release

Mon, 30 Sep 2013 00:00:00 +0000

0.9.8 includes the long-awaited support for IPv6. It’s enabled by default, but of course you need a public IPv6 address to use it. Configuration is on the ’network’ configuration tab in your console. We also have anonymity improvements including padding of SSU packets and longer router private keys.

30% of you will update via in-network torrent in this update cycle.

IPv6 Details

IPv6 is enabled and preferred by default. If you have a public IPv6 address and you are connecting to another router with a published IPv6 address, it will connect via IPv6. There is a new IPv6 configuration section on /confignet in the router console. If IPv6 is causing problems you may disable it there.

I2P Dev Meeting - September 10, 2013

Tue, 10 Sep 2013 00:00:00 +0000

Quick recap

Present: dbowie, dg, efkt, EpicCoffee, Pseudonemo, psi, topiltzin, trolly, welterde, zzz

Meeting Log

20:00:31 <zzz> 0) hi 20:00:38 <zzz> 1) website revamp (str4d) 20:00:55 <zzz> 2) console home page request for `http://open4you.i2p/` 20:01:03 <iRelay> Title: open4you.i2p (at open4you.i2p) 20:01:11 <zzz> 3) disable outproxy (topiltzin / dg) 20:01:20 <zzz> 4) netdb project update (hottuna) 20:01:23 <zzz> 0) hi 20:01:25 <zzz> hi 20:01:30 <dg> hi 20:01:35 <topiltzin> hi 20:01:42 <zzz> more info and links at `http://zzz.i2p/topics/1460` 20:01:55 <zzz> let's try something new and limit each agenda item to 15 minutes 20:02:00 <iRelay> Title: zzz.i2p: Meeting Tues. Sept. 10, 8 PM UTC (at zzz.i2p) 20:02:03 <zzz> 1) website revamp (str4d) 20:02:07 <zzz> go str4d 20:04:12 <zzz> skipping 1) for now 20:04:17 <zzz> 2) console home page request for `http://open4you.i2p/` 20:04:21 <iRelay> Title: open4you.i2p (at open4you.i2p) 20:04:28 <zzz> is the open4you requester here? 20:05:53 <zzz> skipping 2) for now 20:05:59 <zzz> 3) disable outproxy (topiltzin / dg) 20:06:05 <zzz> go dg or topiltzin 20:06:05 <dg> \o 20:06:13 <dg> I'll take it first. 20:06:50 <dg> Hi all, I've been mulling this over for some time: I think the outproxy for HTTP (and possibly HTTPS) being included by default isn't aligned with our goals; 20:07:25 <dg> most of the time, when asked on IRC about outproxying, community members recommend Tor and not to touch the outproxy for many/any uses 20:07:38 <dg> "we leave that to Tor" is something that's thrown around a lot 20:08:22 <dg> the outproxy is centralized which is obviously a big issue, there's problems with Tor having thousands of exit nodes even, let alone us having just one 20:08:43 <dg> security issues aside, it's a usability problem. What if someone trying to use I2P thinks I2P is just really slow because google.com loads slow? Oh, and it's in German? Huh? 20:09:14 <dg> We haven't built in the code for outproxying as a 'real' measure for a reason: we don't want to do it and hidden services are our target 20:09:58 <dg> I feel we're putting users at risk by inserting the outproxy by default and (possibly) confusing their perception of what I2P is and what it does. 20:10:04 <dg> iniial pitch over 20:10:17 <zzz> topiltzin, you have anything to add? 20:10:52 <topiltzin> that's a good list; I can also see KillYourTV 's point that the functionality should not be removed 20:11:22 <zzz> ok let's throw it open to comments from others 20:11:23 <topiltzin> but I strongly agree with dg that it's better to steer users away from using i2p for clearnet surfing 20:12:17 <dg> Someone (Pseudonemo) has suggested an explanation page as to why clearnet websites will not load and possibly a Tor recommendation. 20:12:19 <welterde> a plugin that outproxies via tor locally would be nice.. 20:12:45 <dg> welterde: funny you say this.. jtor was introduced by ioerror to zzz a few weeks back. 20:13:26 <welterde> dg: yeah.. that's what I was thinking about.. should be much cleaner than having to rely on an external running component 20:13:52 <dg> So, thoughts? 20:13:54 <efkt> Usually the only time I observe topic of I2P's in discussion is answering questions like "Why doesnt it work like I want it to?" and supplying alternatives like Meeh's outproxy or just using Tor. Having the option for the outproxy is a good thing, and having users knowing that there is such an option is also nice. 20:13:56 <zzz> I'm against removing it - it's a limited feature, yes, but what it does it actually does pretty well. We won't improve the usability of it by disabling it. We'll just make things harder and more confusing. 20:14:45 <EpicCoffee> I think overall I agree with zzz (since my entrance) 20:14:58 <zzz> perhaps when we have a better solution (a tor plugin) then we could disable echelon;s by default 20:15:19 <trolly_> options are always good, and I use the outproxies a lot, I know of course not to trust outproxies communications 20:15:21 <dg> Why should we do something that we (mostly) acknowledge is something Tor is better for? It seems like we're letting down people by even trying, it's a false impression. A well designed explanation page could ease the confusion/hardness 20:15:46 <dg> I don't suggest we remove the capability, just the default 20:15:47 <zzz> sounds like dg is mainly describing a documentation / education problem, that won't be fixed by disabling it. 20:16:24 <topiltzin> it would not be fixed but would be avoided 20:16:31 <dg> I don't know why the user should be trusting a third party by installing I2P 20:16:36 <zzz> i2ptunnel is scary and I'd rather not have to point people in there to turn it on 20:16:36 <EpicCoffee> Some people do not use tor and will not use tor for various reasons. They can have use for an I2P outproxy. 20:17:12 <topiltzin> kytv's proposal to have a warning page that makes things clear would be a proper solution, no? 20:17:16 <trolly_> dg you are right, EpicCoffee too 20:17:26 <EpicCoffee> On rare occasions I use the outproxy, mostly to check out links sent in i2prc 20:17:42 <dg> I understand we can say "well, the user should read" or similar but.. should we let them shoot themselves in the foot so easily? 20:17:49 <trolly_> like me EpicCoffee 20:17:51 <zzz> to look at it another way, while it's on by default on the i2p side, it always takes affirmative action by the user to enable it in the browser. So you could say it is not on by default now, if you consider the browser too. 20:18:09 <EpicCoffee> If the link cannot be loaded through the outproxy, I am unlikely to load it through the clearnet. 20:18:32 <dg> it takes affirmative action to browse eepsites, it is still confusing. If someone is aware of the risks, they can add the outproxy. 20:18:37 *** trolly_ is now known as trolly 20:18:37 <dg> Or load the maybe-coming tor plugin 20:18:49 <EpicCoffee> I'm sure I'm not alone in this. 20:18:49 <EpicCoffee> lol 20:18:55 <zzz> does eche|on have an opinion? 20:19:03 <dg> This isn't an attack on echelon either but should we be trusting a single person with all outproxy traffic? 20:19:12 <dg> Regardless of who it is, it's a single point and a single person 20:19:37 <zzz> would you rather trust one person you somewhat know, or 3000 people you don't? 20:19:41 <dg> An assumption could easily be made that I2P is performing a tor like mechanism 20:19:57 <dg> 3000 people I don't 20:20:10 <zzz> coming up on the 15 minute mark. do we have any sort of consensus? anybody else that has a thought on this? 20:20:34 <welterde> imho we shouldn't disable it until we have the tor plugin 20:20:37 <Pseudonemo> I think dg is primarily arguing from the perspective of new users. They don't know eche|on. 20:20:51 <topiltzin> +1 Pseudonemo 20:20:59 <dg> *I* know eche|on, as a result, I don't mind the outproxy much but yes. 20:21:04 <dg> welterde: I can agree on this compromise. 20:21:21 <EpicCoffee> nobody should use an outproxy for anything sensitive. that should be a given lol. 20:21:22 <dg> Let's leave it there? 20:21:33 <topiltzin> assuming a tor plugin is in the works at all.. which it isn't 20:21:54 <zzz> ok, interesting topic, thanks for bringing it up dg. May be worth talking about again after a while, whether we have a tor plugin or not 20:21:59 <topiltzin> it is an education problem so it would be best to solve it through education 20:22:16 <dg> zzz: no problem, thank you. 20:22:39 <zzz> any volunteers to look at the education / documentation issue and propose some improvements? 20:22:42 <EpicCoffee> topiltzin: I don't think I would like a tor plugin in i2p. My opinion on that is I don't like/trust tor. 20:22:55 <dg> EpicCoffee: moved topic, save for next time :) 20:23:16 <zzz> last call for volunteers and then we are done with this topic 20:23:43 <zzz> ok then. 20:24:04 <zzz> skipping 4) as hottuna is not here 20:24:04 <zzz> lets circle back to 1), is str4d here? 20:24:45 <zzz> skipping 1) again 20:24:49 * EpicCoffee must be oblivious to the "list" 20:25:01 <dg> EpicCoffee: you weren't here for the start, will pm. 20:25:09 <zzz> 2) open4you.i2p, which we will discuss whether or not the requestor is here. 20:25:12 <EpicCoffee> ah thank you dg 20:25:13 <zzz> open4you are you here? 20:25:15 <topiltzin> EpicCoffee: channel is logged real-time `http://killyourtv.i2p/irclogs/%23i2p-dev.2013-09-10.log` 20:25:54 <zzz> the request is at the bottom of `http://zzz.i2p/topics/1429` 20:26:03 <iRelay> Title: zzz.i2p: 0.9.8 Release Summary (at zzz.i2p) 20:26:44 <zzz> as a refresher, since we haven't done this in a while, my personal guidelines are at `http://zzz.i2p/topics/236` 20:26:49 <iRelay> Title: zzz.i2p: How to get my Eepsite added to the Router Console home page (at zzz.i2p) 20:27:09 <zzz> has anybody used this site? Does anybody have any thoughts about putting it on the console? 20:27:30 <dg> If open4you doesn't turn up, can I propose one? 20:27:31 <dg> loading the guidelines now 20:27:36 <topiltzin> I like that the operator is upfront about what he can and cannot guarantee 20:28:08 *** trolly is now known as trolly_ 20:28:14 <topiltzin> but besides that (positive) impression there isn't much to say... 20:28:15 <zzz> we are considering open4you only today, at least in item 2). If you like you can have a new item 5) dg 20:28:28 <EpicCoffee> I believe there should be available hosting on i2p, however I'm not sure I would trust a host lol. I'm conflicted on the hosting topic so I'll step aside on this one 20:28:29 <dg> zzz: ok, thx 20:28:42 <zzz> his TOS looks ok to me 20:29:03 <zzz> it's a new category not currently on the console so that's a plus 20:29:03 <dg> i know of no clients from open4you.i2p so I can't vouch for it but if the owner can turn up another time, I'm fine with discussing it again 20:29:56 <dg> no vouches makes me suspicious 20:30:24 <zzz> the recent FreedomHosting thing makes eepsite hosting interesting 20:31:13 <dg> I get the gist this is free, right? 20:31:19 <zzz> do we have any questions that the requestor must answer for us to make a decision? or can we make a decision today? 20:31:33 <zzz> I didnt see whether it was free or not. the faq is only in russian. 20:31:45 <topiltzin> it's free 20:31:45 <dg> If it's free, why not? There's no risk of a scam and it's definitely of 'interest'. 20:31:49 <dg> "9 months work free web hosting in i2p." 20:31:58 <dg> sorry guys, I was under the impression it was bitcoin 20:32:19 <topiltzin> still, we have no idea if it actually works 20:32:46 <dg> Should we bite the bullet and find a volunteer to test it at some point from now to the release? 20:32:55 <dg> If it doesn't work, we pull it 20:33:15 <zzz> I'm inclined to say yes now. I don't know what one person testing it would prove. We can always pull it later. 20:33:33 <dg> well, testing it at least works. There's not much else we can test. 20:33:39 <zzz> I would hope people are at least vaguely aware of the trust issues involved in hosting 20:33:41 <dg> yeah, I'm also a yes. 20:34:10 <zzz> there's no reason it shouldn't work. For one, I dont see any evidence of an automated process. 20:34:12 <dg> Any other votes? 20:34:26 <dg> it seems to be email drivne 20:34:28 <dg> driven 20:34:43 <zzz> last call for opinions / objections 20:34:57 <topiltzin> by works I mean whether the operator will actually do what he says he will do 20:35:14 <psi> do we have any testimonies from users on open4you? 20:35:22 <topiltzin> as opposed to set up an eepsite and abandon it 20:35:24 <dg> no 20:35:28 <topiltzin> psi: none, that's the problem 20:35:31 <dg> topiltzin: if that happens, we can remove it. 20:35:39 <dg> the owner is at least somewhat active as he requested 20:35:48 <dg> I'm for it. 20:35:53 <psi> yeah, i'd say not to go ahead with endorsement , first we get a test user in 20:35:56 <zzz> my guess is he has almost no business so far. Let's give him a trial period of a couple of I2P releases with it in the console, and if its bogus then we pull it 20:36:09 <psi> or... if we endorse put a big fat warning on it 20:36:10 <dg> zzz: +1 20:36:27 <psi> hmm 20:36:33 <psi> zzz has a good point 20:36:42 <psi> but... still 20:36:49 <dg> psi: it is free 20:36:56 <zzz> psi pls clarify are you objecting or not 20:36:56 <topiltzin> I'll email him the next few days 20:36:58 <psi> oh? it is? 20:37:04 <dg> yes 20:37:08 <psi> i am voicing caution 20:37:13 <psi> no objection 20:37:16 <topiltzin> I guess I might as well put zab.i2p back up 20:37:22 <dg> I thought it was bitcoin but it isn't 20:37:25 <dg> It's free so.. I don't care much about testimonies yet 20:37:30 <dg> :) 20:37:40 <dg> topiltzin: You for or against? 20:37:52 <topiltzin> abstaining 20:38:00 <zzz> sounds like we have no objections and it's approved? if I'm wrong please speak up 20:38:01 <topiltzin> I will test his hosting the next few days though 20:38:05 <dg> 2 for, 0 against 20:38:12 <psi> abstain 20:38:19 <welterde> abstain 20:38:26 <EpicCoffee> im curious how files are transferred to open4you hosting account 20:38:47 <dg> EpicCoffee: ftp (huh?) or via a control panel it seems. 20:39:07 <psi> sftp? 20:39:18 <zzz> ok I'll email him to get a logo and check the stuff into the console. Any of you so inclined, please sign up and report back 20:39:34 <zzz> if it's bogus or doesnt work, we can always pull it just before the release. 20:39:35 <dg> "1 GB of available space, php5, mysql, ftp access, 3 tunnel \ 2 hop" 20:39:40 <dg> +1 20:39:48 <welterde> psi: doubt it.. 20:40:01 <zzz> and that ends item 2) 20:40:18 <zzz> no sign of hottuna or str4d so we're on to 5) dg's request 20:40:20 <zzz> dg go 20:40:29 <welterde> although it should work better over i2p (you know.. passive/active mode and so for ftp..) 20:41:36 <dg> I propose `http://salt.i2p/` (not my site, efkt's) for inclusion in the router console. salt.i2p contains; a helpful, large wiki of eepsites and guides; xmpp; an IRC channel which is probably most active one on IRC2p 20:41:51 <iRelay> Title: salted (at salt.i2p) 20:42:00 <dg> It provides a lot of eepsite 'starting points' and is SFW. 20:42:02 <EpicCoffee> ill say +1 for salt 20:42:07 <EpicCoffee> I like the salt wiki 20:42:16 <topiltzin> yep, #salt pwnz +1 20:42:18 <dg> salt has grown to be a great resource for me and others in the community 20:42:28 <dg> the channel is #salt ftr 20:42:52 <zzz> we really can only take requests from the eepsite owner. Could you ask him to apply following the guidelines on `http://zzz.i2p/topics/236` ? then we can consider it for 0.9.9 20:42:54 <welterde> +1.. pretty much what that old wiki used to be now.. 20:43:06 <iRelay> Title: zzz.i2p: How to get my Eepsite added to the Router Console home page (at zzz.i2p) 20:43:33 <zzz> I'm not familiar with the site 20:43:55 <zzz> I don't think we want to start adding sites w/o permission 20:44:14 <dg> He was active not long ago, he may shoot up in a second 20:44:23 <dg> I agree with not adding w/o permission 20:44:34 <dg> figured it was worth a shot though 20:44:43 <zzz> paging efkt 20:44:49 <efkt> You have my permission as long as everyone's happy with it. I created the site with some of I2P's possible policies and ideas in mind about what content is appropriate for I2P. Im open to discussion if you don't like some of what might be there (Just saying) 20:44:53 <EpicCoffee> efkt is the owner of salt? I presume such based on observations. 20:44:59 <dg> Yes, EpicCoffee. 20:45:10 <efkt> Thus the disclaimer on the front page, explicit policies about gore/pr0n/etc 20:45:43 <efkt> The wiki is not open to edit unless we end up knowing you, so it is unlikely to be vandalized. 20:46:03 * EpicCoffee also points out the salt xmpp 20:46:17 <dg> the XMPP is popular too and comes with guides. :) 20:46:50 <topiltzin> yeah salt is pretty damn great.. has a real community feel to it 20:46:59 <zzz> if you want to do it right now please answer the following questions. If it's too much to do now we can discuss in about 6 weeks before the next release 20:47:00 <EpicCoffee> so long as users of it realize the admins can see what is said if not encrypted (I think the wiki article on it highly encourages otr) 20:47:06 <efkt> We have enough XMPP servers floating around that in the future it might not be a bad idea to list a few in the console. Most of us running servers have S2S happening. 20:47:07 <zzz> - An email address 20:47:07 <zzz> - The URL to link to 20:47:07 <zzz> - The URL of your English terms of service if available or necessary 20:47:07 <zzz> - If the site is not in English, a brief description of the site in English 20:47:07 <zzz> - (Optional) A URL to a transparent png icon to display. Size must be 32x32 (subject to change). If no icon is provided the icon will be "toopie". We will copy this icon into the router console source and serve it locally. 20:47:10 <zzz> - If an icon is provided, the license of the image. 20:47:12 <zzz> - (Optional) A one or two-word label in English. If not provided we will use example.i2p 20:47:14 <zzz> - (Optional) a few words or a sentence in English for a popup (tooltip) 20:48:19 <efkt> efkt@mail.i2p 20:48:23 <efkt> site: `http://salt.i2p` 20:48:27 <iRelay> Title: salted (at salt.i2p) 20:48:38 <efkt> site terms of service - Theres a disclaimer on the front page: `http://salt.i2p` 20:48:43 <iRelay> Title: salted (at salt.i2p) 20:49:15 <efkt> I dont have a 32x32 icon to provide speedily but it would be the same as our favicon, a black star with transparent or white background 20:49:47 <efkt> label name can be simply "salt" 20:49:59 <EpicCoffee> efkt I can make a quick 32x32 icon if you want. well as quick as i2p will allow lol 20:50:25 <zzz> we can give you a week for the icon :) 20:50:32 <zzz> how long has the site been up? 20:50:34 <efkt> EpicCoffee: If you like. Its just like the favicon - the black "anarchist star", you see the same kind of shape all over google images. It takes only a moment really 20:50:40 <efkt> zzz: august 2012, IIRC 20:51:21 <dg> `http://salt.i2p/wiki/index.php/Main_Page#Tutorials` 20:51:21 <efkt> Honestly, I'm very surprised I get so many users unable to reach the site as its not part of the default addressbook (or the XMPP) - Yet we get a lot of newcomers being directed there through IRC. Sorry to step off topic. 20:51:35 <iRelay> Title: Salted Wiki (at salt.i2p) 20:51:41 <efkt> zzz: Oh, and the blurb "Cryptomunitions and tutorials' 20:51:46 <dg> Yeah, it's a problem (in addition to the annoying addressbook-not-found bug) when introducing users. 20:52:20 <zzz> anybody on the console home page is automatically added to the default address book 20:52:42 <efkt> Oh. That will be helpful for anyone who is new to I2P coming to IRC2P to explore. 20:52:52 <efkt> one headache solved :) 20:52:59 <dg> 1/2. 20:53:05 <dg> no xmpp.salt.i2p ;) 20:53:32 <zzz> efkt to me your terms of service are insufficient for a wiki that we would recommend, as it describes only what you are not responsible for. It does not say what type of content if any is disallowed. 20:54:03 <zzz> If anything goes then I cannot support the request. 20:54:04 <efkt> zzz: Even though noone is allowed to edit the wiki, at all, unless I have personally vetted them and given them an account? 20:54:19 <dg> efkt: I believe he's saying the actual rules are unclear. pr0n, etc. 20:54:41 <efkt> Hrm. 20:54:53 <zzz> there are no rules stated at all. 20:54:56 <dbowie> 32X32 blackstar.jpg, base64 encoded: `http://pastethis.i2p/show/5437/` 20:54:57 <iRelay> Title: Paste #5437 | LodgeIt! (at pastethis.i2p) 20:55:00 <zzz> wrt allowed content 20:55:54 <efkt> I can easily add something. It's not a problem, only mulling over what "extra" things to add - Content such as Gore, Rape, Torture, Snuff, or weird sex will never be allowed on the site 20:56:23 <dg> so, family friendly - safe for work etc? 20:56:53 <zzz> I don't think we should ask you to draft a content ToS in the next 30 seconds. Want to think about it and come back in a few weeks? 20:57:06 <efkt> At this time no I cannot say salt is family friendly or safe for work. The onionland page explicitly links to drug onions. 20:57:43 <efkt> zzz: Yes, I'd like that at least - Id rather work with everyone and produce something desirable that's useful to I2P 20:59:22 <EpicCoffee> EpicCoffee: any image hosts on i2p? 20:59:24 <zzz> my philosophy is that anything similar to postman's tracker rules are acceptable. 20:59:24 <zzz> I don't want to tell you how to run your site or how to write your rules. You do what you like and then we'll decide if we want it in the console. 20:59:24 <zzz> but you can survey the links we have now and get a feel 21:00:36 <zzz> we're past 15 minutes so can we ask you to come back in a few weeks? Any site that has that much support from the folks here I think would be a good addition to the console, if you can work out the ToS stuff. 21:01:36 <efkt> I'm happy to work out a ToS, and to talk about anything on the site the community feels doesn't belong. Thanks zzz. Yes that's fine 21:02:13 <zzz> great. glad to hear about a new site I wasn't familiar with. I'll check it out. email me or post on zzz.i2p when you pull it all together 21:02:19 <zzz> and that's the end of 5) 21:02:25 <zzz> last call for str4d for 1) 21:02:36 <zzz> hottuna still not here for 4) 21:02:47 * zzz warms up the baffer 21:03:50 * zzz *bafs* the meeting closed 21:07:16 <zzz> thanks everybody, good meeting

0.9.7.1 Release

Sat, 10 Aug 2013 00:00:00 +0000

This unscheduled release disables the RouterInfo verification messages that were used in the attack published in the UCSB paper, which should make correlating a LeaseSet and a Router much more difficult. We have also included a limited number of other fixes listed below. Our 0.9.8 release, which will include IPv6 support, is still on-schedule for late September.

As usual, we recommend that all users update to this release.

RELEASE DETAILS

Anonymity Improvements

Disable RouterInfo verification messages

Other

Extend inbound tunnel expiration
i2prouter: bashism fix
i2psnark: increase max piece size, mime type updates
New reseed host
New update hosts, thanks Meeh and dg
Streaming: RTO changes
Updater: Increase update-via-torrent to 30 percent
UPnP fix for some hardware

SHA256 Checksums

293f445196a2f35c4d580f65b548135399e1f4443450b5ecf1cc53b1203fdad1 i2pinstall_0.9.7.1_windows.exe
9fae874a4d680f50f5efd7be70cfcf55f2f4687e011bde9c4b4899bafb002e97 i2pinstall_0.9.7.1.jar
7b73bdb23c53798054741cbaa4e7d8cce832ee566fbb17df0c803d0c22d099e1 i2psource_0.9.7.1.tar.bz2
69ca22a77a2de87f726d86555317f8688891d31f5312cf71d5a43febe2729b38 i2pupdate_0.9.7.1.zip
f59c9c80349c328b3e912113a3842146f647ff22ae323cef6b1e56a23f8c8cf1 i2pupdate.su2
52d1f32e2a72091da10312853e5df6bced12cb97770ba20732f2d9d6c4d2f5fe i2pupdate.sud

0.9.2 Release

Fri, 21 Sep 2012 00:00:00 +0000

0.9.2 includes extensive low-level changes to improve the performance and efficiency of the router. We have updated our UPnP library, to hopefully make UPnP work for more people. I2PSnark now has DHT support, but it is not yet enabled by default, as we plan to do more testing during the upcoming 0.9.3 development cycle.

As usual, there’s also lots of bug fixes in this release, so updating is recommended.

Files are available on the download page .

0.9.1 Release

Mon, 30 Jul 2012 00:00:00 +0000

0.9.1 includes a large number of bug fixes in i2psnark, some streaming lib improvements, home page changes, new themes, and translation updates. Upgrading is recommended.

Files are available on the download page .

RELEASE DETAILS

I2PSnark

Fix several bugs in downloading torrents with skipped files
Fix places where rarest-first was not honored
Fix handling of encoded magnet links
Additional inbound connection limits
Immediate closing of connections with handshake errors
Blocklist peers with multiple handshake errors
Delay “ballooning” files on disk until required, to speed torrent adds
Store partial pieces in temp files to greatly reduce memory usage when leeching
Remove peers restriction when leeching torrents with large pieces
Improve configuration of open and private trackers
Prevent configuration of default trackers as private
Improved display and control of torrent file downloads
Reduced number of threads
Faster startup and shutdown of torrents
Allow clearing of message box
New light theme
Torrent info page updates and cleanups
Fix problems with restarted torrents
Delay tunnel close at shutdown to ensure trackers are notified
Better UI behavior during tunnel startup and shutdown

Bug Fixes

Prevent shutdown hangs caused by buggy plugins
Fix for Raspberry Pi crashing
Fix rare job queue hang
Fix routing key modifier rarely not updating at midnight
Fix excessive padding in some AES-encrypted messages
Fix occasional gunzip failures
Several fixes to streaming lib to speed recovery after dropped packets and improve retransmit behavior
Fix bug that reduced reuse of tunnels

Other

Ports are now passed through the SOCKS and HTTP proxies to support eepsite virtual hosts. See http://zzz.i2p/topics/1182 for setup instructions.
I2PTunnel configuration changes now take effect immediately. No tunnel restart required.
Summary bar iframe removed, refresh is now via Javascript only
Reduce netDB flood redundancy
Reduce stats publishing frequency
Minor router console changes
New Hungarian and Greek translations
Completed Italian translation
Updates to Dutch, Finnish, French, German, Spanish, and Swedish translations
Update geoip to Maxmind 2012-07-04
Theme updates
Theme support for SusiMail and SudiDNS; new dark themes
I2PTunnel and SusiDNS now iframed with summary bar
Console home page now shows news summary in summary bar
Console home page icon updates
Console summary bar now configurable
Change the HTTP proxy error code from 404 to 500
Cleanups for efficiency in netdb and I2CP
Increase timeout for internal uses of eepget to improve reliability

SHA256 Checksums:

0727af83988e82f32e0972a9e12c72ac14c3c0da0815c5902193d6b13d356371 i2pinstall_0.9.1_windows.exe
39c19c0df042ad231a14fdf1c20e4927651a2af0f0cf734b46eba0d2b8419314 i2pinstall_0.9.1.jar
8603c928a210ced77b6498bf8ee07cb000be9641adc389b34c3c8a10ac4f0677 i2psource_0.9.1.tar.bz2
136b74435b93aededef5884d39cfbc513f57184b74c8481580bcd5324aa23b1a i2pupdate_0.9.1.zip
4f07fee850d56fada06f0aeabb5bb46c6172bad72411e07bf4f6a8e0d76d8acd i2pupdate.su2
c039b423983789d914a1d02d3703b3c1aa36c87165e132419ff39b5d184ef480 i2pupdate.sud

0.9 Release

Wed, 02 May 2012 00:00:00 +0000

The 0.9 release concludes over a year and a half of work on the 0.8.x series, in which we greatly improved the performance and security of the router, and the scalability of the network.

In the 0.9 release we migrate to Jetty 6 for the console and eepsite web server, and introduce a simplified router console home page. This release is network-compatible with prior releases, however see below for important information on compatibility with existing eepsites, plugins, and webapps. Upgrading is recommended.

0.8.13 Release

Mon, 27 Feb 2012 00:00:00 +0000

The 0.8.13 release contains several bug fixes and a couple of new features. We are pleased that the last release significantly improved performance, and the network is running well despite continued rapid growth. Upgrading is recommended.

Files are available on the download page .

RELEASE DETAILS

This is likely to be the last release before 0.9, in which we will migrate to Jetty 6, and introduce a simplified router console home page. Monitor the news section of your the router console in the coming weeks for more information on the next release.

0.8.12 Release

Fri, 06 Jan 2012 00:00:00 +0000

The 0.8.12 release fixes several message corruption bugs, some present since 2005. It also contains a redesign of the router’s congestion control, and continued optimization of CPU and memory usage. We are hopeful that these changes will improve network performance. Upgrading is recommended.

Files are available on the download page .

RELEASE DETAILS

This release contains several big changes that should help network reliability and performance.

The first two changes are fixes for major UDP packet transmission bugs, described below. The third change is fixes to the decompressor. Fixing these should eliminate a big source of message delivery failures.

0.8.11 Release

Tue, 08 Nov 2011 00:00:00 +0000

As you all have noticed, the unprecedented network growth starting October 5th has dramatically increased network congestion, especially on evenings (UTC) and weekends. The last two releases contained a few changes that we hoped would relieve the pressure, but unfortunately these measures have been only modest successes. The primary issue is to limit the number of direct router to-router connections in the network. This isn’t a new problem; we’ve been working on it for several years, with good results. However, the recent growth pushed us over the edge once again.

0.8.10 Release

Thu, 20 Oct 2011 00:00:00 +0000

Release 0.8.10 includes two changes intended to reduce the number of router-to-router connections, and therefore improve tunnel build success rates and general reliability. Of course, there’s also a few bug fixes and translation updates.

Files are available on the download page .

RELEASE DETAILS

Major Changes

Disable tunnel testing as it forces too many router connections
Select outbound endpoint - inbound gateway paths that are closer, using an XOR metric, to reduce router connections

Bug Fixes

Fix exceptions at shutdown
Fix concurrency errors in SSU
Fix timeout message on POST

Other

Increase max tunnels, reduce router info expiration
Add gunzip support to eepget to reduce reseed bandwidth
Finnish, Italian, Russian, and Swedish translation updates

SHA256 Checksums:

8494640d29b1b7969118169a7ae1c56bc5a07f354ec883734687bf09eef0e35c i2pinstall_0.8.10.exe
e5832bb49f46b0b6620e8492e6fc6454de4107b84bca5a4b35461c6b7ac0575e i2psource_0.8.10.tar.bz2
64bcd1fdd478cfda987c1d4906d94b3f20a0555bd4037aefa7a09af4f39a0e99 i2pupdate_0.8.10.zip
5620113f4e19768e15af0a9c8bc670ca443e9983a0d4868997800ee215790c51 i2pupdate.su2
39bfbfebbf77d660081fe1ce282f642fb15ed9cd170901f54a954bc986eadaf5 i2pupdate.sud

0.8.9 Release

Tue, 11 Oct 2011 00:00:00 +0000

The 0.8.9 release has several performance improvements, and many changes to handle the continued rapid growth of the network. It uses a new iterative method for Kademlia network database lookups that should be more reliable and efficient. There are also several improvements to our SSU (UDP) transport protocol that should help reliability and efficiency. We have made several changes to improve tunnel build success rates. And, of course, there are lots of bug fixes and translation updates.

Ipredator Summer of Code

Sat, 03 Sep 2011 00:00:00 +0000

itoopie and I2PControl are launching!

I’m happy to announce that itoopie and I2PControl are available publicly.

itoopie is a graphical interface intended as a compliment to the I2P Router Console. The aim of itoopie is to provide an interface that is simpler and has a lower learning curve than the I2P Router Console.

I2PControl is an I2P plugin providing a JSONRPC interface for the I2P router. The interface supports setting basic settings (bandwidth, ports etc.), reading many stats and is provided over an SSL encrypted HTTP connection.

0.8.8 Release

Tue, 23 Aug 2011 00:00:00 +0000

I2P release 0.8.8 enables the new hosts.txt database to speed hostname lookups and store additional information on hostname entries. It also includes improvements to speed a router’s integration on startup. There is new code to detect and react to large clock shifts that should help a router recover after suspend/resume of the computer.

There are new translations for Danish and Ukrainian and lots of updates in other languages. Also included are, of course, a large collection of bug fixes, performance improvements, and updates to deal with the continued rapid expansion of the network.

0.8.7 Release

Mon, 27 Jun 2011 00:00:00 +0000

I2P release 0.8.7 contains several upgrades to long-neglected components, including the Naming Services, graphing, the native CPU ID and BigInteger libraries, crypto implementations, and the wrapper.

Thanks to new contributor KillYourTV who was instrumental in implementing and testing these upgrades, with additional support from sponge and hottuna.

CPU ID enhancements are by hottuna, generously funded by Relakks and Ipredator - thanks to Peter Sunde and Jan-Erik Fiske for their support.

Ipredator Summer of Code

Mon, 06 Jun 2011 00:00:00 +0000

I have been commissioned to contribute code to I2P during the summer of 2011, implementing a control protocol and a client for this protocol (similar to Vidalia for Tor). This work was the idea of Jan-Erik Fiske of ViaEuropa and Peter Sunde of flattr and The Pirate Bay fame and its funding will be generously provided by Relakks and Ipredator.

Current information can be found on zzz’s forum and #i2p-dev on chat.freenode.net

Cheers

// hottuna (or Robert)

0.8.6 Release

Mon, 16 May 2011 00:00:00 +0000

The 0.8.6 release contains more peer selection defenses to resist powerful attackers, and tweaks to adjust to the recent rapid growth in the network. Upgrading is recommended.

Please help grow the network. Get involved , spread the word, and donate ! If you find a bug, please enter a report on gitlab. We are still looking for help on new and existing translations. Please volunteer on IRC #i2p-dev.

Files are available on the download page .

0.8.5 Release

Mon, 18 Apr 2011 00:00:00 +0000

The 0.8.5 release contains a few bug fixes and performance improvements, and lots of translation updates. As usual, upgrading is recommended.

Files are available on the download page .

Release details:

Lots of router console HTML fixes
i2psnark magnet handling fixes
SusiMail Translation support by “duck”
Continuing work on the Arabic translation by “hamada”
Completion of the French translation by “magma”
Completion of the Spanish translation by “punkibastardo” and “user”
Other translation updates
Better support for text-mode browsers
Profile display improvements
Tunnel build request queue limiting
Require nonce to change console language
i2psnark improved logging of errors
i2psnark improved metainfo handling
Use the reseed server as a backup time source
Change profile file extension from .dat to .txt.gz
Change all i2ptunnels to 3 hops for new installs
Add all bogons to blocklist for new installs
More efficient use of entropy for padding

SHA256 Checksums:

6ae6b196352e1053c4e7b91edc575330d108ff9abfc2746ea3c3b2e3fd467006 i2pinstall_0.8.5.exe
de9fa105c1335d58609689a942d3e6a508ca824fc8b27a34c1c0b09fc7e0167b i2psource_0.8.5.tar.bz2
7e4c1835dfd7aaa42d84cf4646f5858a37efa027f43a26eb98360e3cb4750ac8 i2pupdate_0.8.5.zip
efea978f3e4e955b9afa05847dc4ebb83c8df3651adeb717769e32a908bc5f53 i2pupdate.su2
1b6eca94b7938f5c61c26b4482c89919bdfbc7c41aee7735f8f561c01c3a29d3 i2pupdate.sud

0.8.4 Release

Wed, 02 Mar 2011 00:00:00 +0000

The 0.8.4 release contains some performance improvements and important bug fixes. Also, i2psnark now supports magnet links. As usual, upgrading is recommended.

Files are available on the download page .

Release details:

Fix a severe memory leak in router I2CP session management that caused router crashes for people running the Robert bittorrent client
Fix a bug from 0.8.2 that filtered cookies in the HTTP Server tunnel, causing authentication problems for some eepsites (I2P Sites)
Several fixes for rare NPEs

I2PSnark

Magnet and “maggot” link support
Peer Exchange
Metadata transfer
Details page enhancements
Bandwidth limiter improvements
Bug fixes

Other

More performance improvements
Adjustment to peer selection, to hopefully use more of the available network capacity
Translation updates
Start of a new Arabic translation by ‘hamada’

SHA256 Checksums:

2b9f82b2c236cedcb6d394557a366ea3e181ca244461375a810709b2f7d4e881 i2pinstall_0.8.4.exe
e454880a753963361e43d65da69542c4e8caa62d2646e8ce851b2f95fd9e735c i2psource_0.8.4.tar.bz2
5c6632b5f97e02296ad2d3d5f108b472d6766967a037d96421ad36fa5f2e60a9 i2pupdate_0.8.4.zip
155cd3ca7d174c30367dfa147b11a0c55fb6e85680a0aeda126afcb5e141db42 i2pupdate.su2
465060129520ad115a3823e625def94b8ebafdd28c6ab9b27e125afed70cf851 i2pupdate.sud

0.8.3 Release

Mon, 24 Jan 2011 00:00:00 +0000

The 0.8.3 release contains several performance improvements, including reduction of threads and memory usage, and faster I2CP (client-router) communication.

There is also new SSL router console support, a new reseed configuration page including HTTP proxy support for those behind restrictive firewalls, a new I2CP configuration section including I2CP-over-SSL support for remote clients, a new server connection limits and blacklist configuration section for enhanced DoS protection, and a new HTTP proxy jump server configuration section so you may easily add alternative jump servers. Statistics are now limited by default to reduce memory usage; the full set of statistics may be re-enabled on the stats configuration page. There are also bug fixes, of course, so as usual, upgrading is recommended.

0.8.2 Release

Wed, 22 Dec 2010 00:00:00 +0000

The 0.8.2 release includes extensive bug fixes and theme updates in the router and in i2psnark. There are also optimizations to reduce memory usage in i2psnark. The HTTP and SOCKS proxies now support local and remote authorization. Upgrading is recommended.

I2P will be at 27C3 in Berlin the week of December 27th. Look for the I2P people there and ask for I2P stickers!

0.8.1 Release

Mon, 15 Nov 2010 00:00:00 +0000

The 0.8.1 release contains the usual collection of bug fixes and performance tweaks. There is also a new i2psnark theme and several translation updates. Upgrading is recommended.

Please help grow the network. Give the developers feedback on IRC #i2p or forum.i2p2.de and get involved , spread the word, and donate ! We are still looking for help on new and existing translations. Please volunteer on IRC #i2p.

Files are available on the download page .

I2P Dev Meeting - September 08, 2010

Wed, 08 Sep 2010 00:00:00 +0000

Quick recap

Present:

Meeting Log

22:02 <@Mathiasdm> okay 22:02 <@Mathiasdm> meeting time 22:03 <@Mathiasdm> 0) Hello 22:03 <@Mathiasdm> 1) Website content progress 22:03 <@Mathiasdm> 2) Website backend progress 22:03 <@Mathiasdm> 3) Location for dev discussion 22:03 <@Mathiasdm> 4) Task appointing + handling of disagreements 22:03 <@Mathiasdm> 5) Status updates 22:03 <@Mathiasdm> 6) Upcoming dev conferences 22:03 <@Mathiasdm> okay 22:03 <@Mathiasdm> 0) Hello 22:04 <@Mathiasdm> Welcome to the 208th dev meeting! (shamelessly stolen from badger :p) 22:04 * Mathiasdm pokes everyone 22:04 <eche|on> *poke* 22:04 * Mathiasdm pokes zzz, thanks for the op 22:06 <@Mathiasdm> hm, more poking needed to wake everyone up? zzz badger dr|z3d dream duck eche|on hottuna postman sponge superuser ReturningNovice (sorry :)) 22:06 <eche|on> *POKE* 22:06 <@Mathiasdm> sorry, eche|on :p saw your poke 22:08 <duck> moin 22:08 <@Mathiasdm> moin duck 22:09 <hawk> * Mathiasd1 pokes welterde 22:11 <@Mathiasdm> okay, waiting a bit longer then, since there's only 3 of us so far 22:11 <@Mathiasdm> anyone who wants to join in, just poke back 22:11 <whitenoise> *poke* 22:11 <@zzz> ack 22:12 <@Mathiasdm> aha, lead dev, good :) 22:13 <@Mathiasdm> and just to be sure as many people as possible can join in, waiting 2 more minutes and then starting 22:14 <@Mathiasdm> 1 more minute now 22:14 <superuser> mooin 22:15 <@Mathiasdm> right on time, superuser ;) 22:15 <@Mathiasdm> hi all 22:15 <superuser> ;-) 22:15 <superuser> hi Mathiasdm 22:15 <superuser> and all 22:15 <@Mathiasdm> 1) Website content progress 22:15 <@Mathiasdm> as we probably all know, I2P development is currently halted due to the specs overhaul 22:16 * Mathiasdm hands the hot potato to zzz, so he can talk about the specs overhaul progress 22:16 <eche|on> right 22:17 <@zzz> it's been 7 weeks, progress is slow. I'm working on i2cp right now, I've spent several hours on it already 22:17 <@zzz> need other ppl to chip in both on what they've promised to do, and on the stuff that is unclaimed 22:17 <@zzz> eot 22:18 <@Mathiasdm> okay 22:18 * Mathiasdm will get started again tomorrow, now dev environment is set up again 22:18 <@Mathiasdm> others having something to say about it, go ahead :) 22:19 <@Mathiasdm> guess not 22:19 <@Mathiasdm> hm 22:19 <@Mathiasdm> 2) Website backend progress 22:19 <eche|on> I think is is great form the peoples doing it. 22:19 <@Mathiasdm> oh 22:19 <@Mathiasdm> sorry :) 22:21 <@Mathiasdm> we're skipping 2) for now, unless welt comes in 22:21 <@Mathiasdm> 3) Location for dev discussion 22:22 <@Mathiasdm> this is related to `http://zzz.i2p/topics/719` 22:22 <@Mathiasdm> I quote: 22:22 <@Mathiasdm> "* Post developer discussions on zzz.i2p. What I mean is: IRC is a highly 'volatile' medium, where not everyone is online all the time, and not everyone logs. It's a great medium for a short discussion, but do consider posting a short write-up on zzz.i2p, so others can join in on the discussion." 22:22 <eche|on> dev discussion is a hard topic. IRC is nice, but not reliant neither an archive 22:22 <@Mathiasdm> yes, agreed 22:23 <@Mathiasdm> but there are many things to chose from 22:23 <@Mathiasdm> zzz.i2p, forum.i2p, mailing list 22:23 <@Mathiasdm> well, okay, 3 things :p 22:23 <eche|on> I would suggest some central point of archive 22:23 <eche|on> with a backup. 22:24 <@Mathiasdm> yes 22:24 <@Mathiasdm> but setting up distributed storage for this sounds like a hard thing :p 22:24 <@Mathiasdm> though mailing list is doable, I guess 22:25 <@Mathiasdm> mailing list is 'kinda distributed' 22:25 <eche|on> :-) 22:25 <superuser> isn't the website itself already distributed? 22:25 <@Mathiasdm> anyone else, ideas? 22:25 <eche|on> a mailinglist is a good solution, to 22:26 <superuser> could also go there 22:26 <@Mathiasdm> yes, but that doesn't include the forum, superuser 22:26 <eche|on> rightm website is in monotone 22:26 <@Mathiasdm> true 22:26 <superuser> no, I don't mean the forum, but website itself 22:26 <superuser> aren't old dev meetings available there somewhere too? 22:26 <@Mathiasdm> but it's hard to discuss when you have to check your discussions into monotone :p 22:27 <superuser> true 22:27 <@Mathiasdm> perhaps with the new backend welt is working on, it'll be more doable 22:27 <superuser> would only be of interest for archiving, not for keeping discussing 22:28 <@Mathiasdm> for a temporary way, I would propose: if you keep a big discussion on IRC, post a few notes on _a_ persistent medium 22:29 <@Mathiasdm> be it zzz.i2p, mailing list or forum 22:29 <@Mathiasdm> I know, that's a bit vague 22:29 <eche|on> I vote mailinglist ++ 22:29 <@Mathiasdm> hm, welt, are mailinglist instructions on the website somewhere? 22:29 <superuser> you mean welt's nntp service? 22:29 <@Mathiasdm> mailing list sounds good to me too, eche|on, but I wonder if it will work to get everyone to use it? 22:29 <eche|on> currently no ml available 22:29 <@Mathiasdm> yes, superuser 22:29 <@Mathiasdm> er 22:29 <@Mathiasdm> or what was it 22:29 <@Mathiasdm> I think so 22:30 <@Mathiasdm> eche|on: welt set a few ml's up this summer 22:30 <eche|on> nntp is news server 22:30 <@Mathiasdm> but not widely used yet 22:30 <@Mathiasdm> yes, indeed, but there's a mailing list now too 22:30 <@Mathiasdm> but I don't have the location here 22:30 <@Mathiasdm> zzz, duck: opinions? 22:31 <superuser> I have no mailing list info so far, just seen welt's and Mathiasdm's and ReturningNovice's posts on news server 22:32 <@zzz> I'm not a big fan of an ML but I'll use it if ppl want. welt's seems to be a big secret atm 22:33 <duck> I think zzz.i2p is fine 22:33 <@Mathiasdm> imho anything not-irc would be useful (I like IRC, as said before, but too much dev discussions are unfolloweable) 22:33 <eche|on> zzz.i2p is fine, but: irc discussions needs to be copied intoi AND somehow a kind of backup would be nice 22:34 <@Mathiasdm> hm, maybe I can set s omething up like 22:34 <@Mathiasdm> er 22:34 <@Mathiasdm> what was it called 22:34 <@Mathiasdm> 2 or 3 years ago 22:34 <@Mathiasdm> trevorreznik.i2p? 22:36 <@Mathiasdm> how about: we keep using zzz.i2p, and we start using a mailing list, and try to make sure IRC discussions don't stay IRC-only? 22:36 <duck> all major design stuff is already on zzz.i2p 22:36 <eche|on> better: try keep using zzz.i2p and copy IRC into it. 22:36 <duck> I dont see your problem 22:37 <superuser> what if zzz one disappears 22:37 <superuser> s//? 22:37 <duck> dev/design 22:37 <@Mathiasdm> for example, everything sponge posts (just an example, sponge :p) about seedless and bob is often irc-only discussion 22:38 <duck> I dont think a mailinglist will result into sponge documenting his protocol and api 22:38 <duck> but sure, give it a try 22:39 <@Mathiasdm> nooo, that's not what I meant, duck 22:39 <@Mathiasdm> as said, I don't care if it's on zzz.i2p or on mailing list 22:39 <@Mathiasdm> I just don't want it to be IRC-only, those discussions 22:39 <@Mathiasdm> but yes, you have a good point too 22:39 <@Mathiasdm> that some things will perhaps stay irc-only 22:39 <duck> then go talk to sponge 22:39 <@Mathiasdm> it was an example 22:40 <duck> (which you might be doing through this meeting ofc) 22:40 <duck> ok, understood 22:40 <@Mathiasdm> :) 22:41 <@Mathiasdm> okay, I guess if everyone just tries to post things on zzz.i2p (or mailing list -- but we'll wait for welt :p), that's settled 22:42 <@Mathiasdm> for now, at least 22:42 <@Mathiasdm> anyone have anything to add on this? 22:44 <@Mathiasdm> okay 22:44 <@Mathiasdm> next 22:44 <@Mathiasdm> 4) Task appointing + handling of disagreements 22:45 -!- Moru [kvirc@irc2p] has joined #i2p-dev 22:45 <@Mathiasdm> currently, tasks (displayed on http://www.i2p2.de/team.html ) are appointed/chosen by people simply changing the webpage 22:45 <hawk> <preforce> Title: Team - I2P (at www.i2p2.de) 22:45 <@Mathiasdm> so if you want to do a task, you just do it, and you add yourself to the webpage 22:45 <@Mathiasdm> which is good, I guess :) 22:46 <eche|on> if someone disagree: discussion in IRC/zzz.i2p 22:46 <@Mathiasdm> yes, disagreeing is the point 22:46 <eche|on> but people need checkin-rights to change, means: need som etrust from existant devs 22:46 <@Mathiasdm> there was disagreement this summer, and we didn't really handle that 22:46 <@Mathiasdm> true, eche|on 22:47 <@Mathiasdm> how do we resolve a discussio if the people disagreeing can't come to agreement? 22:47 <@Mathiasdm> vote or something? 22:47 <@Mathiasdm> that's what I was wondering about 22:48 <@Mathiasdm> suggestions? 22:48 <eche|on> last line of defense was noted once 22:48 <eche|on> which was zzz 22:48 <@Mathiasdm> last line of defense? 22:48 <@Mathiasdm> ah 22:49 <whitenoise> what about a third better solution? 22:49 <duck> if all else fails; resort to zzz 22:49 <eche|on> but voting is a nice idea, but I think a solution will be found ahead 22:49 <@Mathiasdm> if the third solution is definitely better, the two parties will choose that one ;) 22:50 <@Mathiasdm> hm, okay 22:50 <@Mathiasdm> just out of curiosity, zzz, you agree to being 'the last line of defense'? :) 22:50 <@Mathiasdm> it sounds okay to me, but do you want that yourself? 22:51 <@zzz> not particularly. my rule is whoever is actually doing something is in charge. ppl that do nothing but talk and piss other ppl off are not. 22:52 <@zzz> there's plenty of work to go around. 22:53 <@Mathiasdm> okay :) sounds good 22:53 <@Mathiasdm> anyone have additional comments? if not, next item 22:53 <superuser> generally "the one who does it is in charge" sounds good 22:53 <superuser> but what if two parties actually do 22:53 <superuser> and still go in opposite directions? 22:54 <superuser> I guess in that case a voting mechanism would not be too uncool 22:54 <@Mathiasdm> true 22:54 <@zzz> if it's code I can pick. I'm definitely not the last line of defense for the website. welt and echelon are. 22:55 <@Mathiasdm> well, if discussion happens and a solution cannot be found, there can be a vote or someone (zzz, welt?) can pick 22:55 <@zzz> they would pick a winner by pulling privs from the loser. 22:56 <@Mathiasdm> *only if it's a nasty discussion, I would hope ;) friendly disagreements shouldn't result in losing privs :p 22:57 <eche|on> right 22:58 <@Mathiasdm> okay then 22:58 <@Mathiasdm> next point 22:58 <@Mathiasdm> if that's okay 22:58 <@Mathiasdm> 5) Status updates 22:58 <eche|on> ok 22:59 <@Mathiasdm> I will start 'collecting' status updates this weekend, I think 22:59 <@Mathiasdm> I was going to do so last week, but caught up in work 22:59 <eche|on> great. go ahead. 22:59 <@Mathiasdm> basically, simply 'what did you do last week?' and 'what are your plans for next week?' 23:00 <@Mathiasdm> and I'll post them a bit summarized on the website 23:00 <@Mathiasdm> suggestions are always welcome :) 23:00 <@Mathiasdm> okay, final point (added only a bit before starting the meeting) 23:00 <@Mathiasdm> 6) Upcoming dev conferences 23:01 <@Mathiasdm> -who's going to 27c3? 23:01 <@Mathiasdm> -who's going to brucon? 23:01 <@Mathiasdm> -any others? 23:02 <@Mathiasdm> I will certainly attend brucon, and most likely 27c3 for a day (and will stay in berlin for a few days) 23:02 <whitenoise> Mathiasdm, I added 1 more point 10 min. before the beginning. 23:02 <@Mathiasdm> oh? sorry, didn't see 23:03 <@Mathiasdm> okay, will do that in a minute, whitenoise 23:03 <whitenoise> ok 23:03 <whitenoise> thanks 23:03 <@Mathiasdm> nobody remarks on dev conferences? 23:04 <@Mathiasdm> then: 7) Promoting the usage of the bittorrent protocol inside I2P: pros and cons 23:04 * Mathiasdm hands hot potato to whitenoise 23:04 <whitenoise> Ok, so we discussed this a little bit with duck 23:05 <whitenoise> While it's a good way for cover traffic and network growth, it may lead to the notoriety of I2P as a illegal file-sharing network 23:05 <eche|on> I decided to not attend to 27c3 23:06 <@Mathiasdm> ah, too bad, eche|on 23:06 <@Mathiasdm> true, whitenoise 23:06 <whitenoise> On the other hand... 23:06 <superuser> I think, bt should not be empahsized more than other services, but i2p be promoted as general use network 23:07 <superuser> oh, he had not yet finished... 23:07 <@Mathiasdm> he might be lagging, give him a bit :) 23:08 <whitenoise> if we don't promote this protocol, in some not very near future, if the business model for selling digital media is not changed, the pressure on torrent users will be higher, so they will start looking for ways to hide 23:08 <whitenoise> which can lead to my first point (notoriety) anyway 23:08 <whitenoise> but it's doubtful, of course 23:08 <Moru> Hello! Excuse me for butting here... sad but true, promote it as filesharing and you will have loads more users and plenty of developers joining. Mabe even get funded by those that wants to use a safe filesharing platform. 23:09 <@Mathiasdm> simply promoting it would not do that, imho 23:09 <@Mathiasdm> and whitenoise, you are right about notoriety 23:09 <@Mathiasdm> but are we promoting it? 23:10 <whitenoise> Imo, right now we don't 23:10 <@Mathiasdm> and bittorrent in itself is not causing the notoriety, file sharing is (imho important distinction, but perhaps not in this discussion) 23:10 <@Mathiasdm> (and hi, Moru) 23:11 <whitenoise> Well, bittorrent is the most used way, that's why I talk about it 23:11 <whitenoise> of course, it may be emule or anything else 23:11 <@Mathiasdm> how would you see promoting it? 23:12 <whitenoise> For example, current simple users have some difficulties setting everything up 23:12 <whitenoise> We could make info about bittorrent more conspicuous 23:13 <@Mathiasdm> hm, yes 23:13 <whitenoise> description more simple 23:13 <whitenoise> and so on. 23:13 <@Mathiasdm> but that's (imho) more a general I2P problem 23:13 <whitenoise> maybe improve i2psnark a little 23:13 <@Mathiasdm> I2P could become a lot more conspicuous :p 23:13 <whitenoise> yes 23:14 <whitenoise> but doing it (as well as advertising it on twitter, for example) will surely attract some users 23:14 <@Mathiasdm> yes 23:14 <@Mathiasdm> well, I agree, and I hope we will more towards making everything clearer (better usability and such) in the near future 23:14 <whitenoise> so, the question is, I guess, what we should do and what we shouldn't 23:15 <whitenoise> improve description but don't advertise as a filesharing network, maybe? 23:15 <@Mathiasdm> what we should do (once development of 0.9 starts) is imho take a look at the 'pain points' of usability 23:15 <eche|on> laready got some ideas of those 23:17 <@Mathiasdm> yes, I2P description would help; console overhaul (perhaps? I don't know) would help 23:17 <@Mathiasdm> eche|on: didn't we have a .pdf with usability remarks from a conference you went? 23:17 <eche|on> hm 23:18 <@zzz> i have it 23:18 <eche|on> need to look for it, but we had some issues over all. 23:18 <@Mathiasdm> have a link, zzz? 23:19 <@Mathiasdm> okay, we could focus on it a bit after the website specs? 23:20 <@zzz> `http://zzz.i2p/files/petcon-usability-long.pdf` 23:20 <@Mathiasdm> thx 23:20 <eche|on> thats a nice idea 23:21 <@Mathiasdm> okay then 23:21 <@Mathiasdm> other remarks or ideas, whitenoise? 23:21 <whitenoise> hm... 23:22 <@Mathiasdm> you are of course always free to start working on website usability improvements too 23:22 <eche|on> just wait for some mails with contact data to pay out some money ;-) 23:23 <whitenoise> well, I guess we decided to improve usability in general without any accent on bittorrent, right? 23:23 <whitenoise> :-) 23:23 <@Mathiasdm> that looks like it, yes, whitenoise 23:23 <@Mathiasdm> I will mail you my bank account, eche|on, just send me the money ;) 23:23 <@Mathiasdm> okay then 23:23 <@Mathiasdm> 8) cookies for everyone who attended 23:24 <eche|on> *g* 23:24 <@Mathiasdm> ===Meeting over=== 23:24 <@Mathiasdm> thanks all :) 23:24 <eche|on> COOKIES! 23:25 <@Mathiasdm> don't eat all of them 23:25 * Mathiasdm pokes eche|on

0.8 Release

Mon, 12 Jul 2010 00:00:00 +0000

In early 2009, shortly after our attendance at 25C3, we released version 0.7 of the I2P Anonymous Network. Over the next 15 releases in 18 months we have worked to improve the usability of the I2P software and increase its performance, security, and reliability - all while dealing with unprecedented growth in the network.

In recognition of these accomplishments, we are declaring the start of the 0.8 series. The 0.8 release is fully compatible with all 0.7.x releases. This release contains several bugfixes, a new Dutch translation, and completion of the German translation. As always, users are encouraged to upgrade.

0.7.14 Release

Mon, 07 Jun 2010 00:00:00 +0000

The 0.7.14 release contains the usual collection of bug fixes and performance tweaks. There are also some i2psnark improvements and more fixes for plugins. Upgrading is recommended.

Files are available on the download page .

0.7.13 Release

Tue, 27 Apr 2010 00:00:00 +0000

The 0.7.13 release contains several changes and bug fixes to improve performance. It also includes improvements for the plugin support that was introduced in the last release. The new, smaller tunnel build message is enabled, to reduce overhead and increase build success.

Of course, there is the usual assortment of bug fixes as well. Upgrading is recommended.

0.7.12 Release

Mon, 15 Mar 2010 00:00:00 +0000

The 0.7.12 release contains support for user-generated plugins. These plugins may contain console web applications, themes, translations, or standalone programs. Some plugins are already available for testing. We are hopeful this support will enable rapid development of innovative i2p applications.

The release fixes the blank-page bug when an eepsite(I2P Site) is not reachable, and also improves handling of clock skews and IP changes. It adds support for a new, smaller tunnel build message, that will be tested in this release and enabled in the next release.

0.7.11 Release

Mon, 15 Feb 2010 00:00:00 +0000

The 0.7.11 release fixes several issues, some related to clocks, which prevented new routers from quickly integrating into the network. It also fixes the installer for 64-bit Windows. The release includes an update to Jetty 5.1.15 to fix this vulnerability .

As usual, the release contains more anonymity and performance improvements, and an assortment of bug fixes. Upgrading is recommended.

Please give the developers feedback on IRC #i2p or forum.i2p2.de and get involved , spread the word, and donate ! We are still looking for help on new and existing translations. Please volunteer on IRC #i2p.

0.7.10 Release

Fri, 22 Jan 2010 00:00:00 +0000

0.7.10 closes some recently-discovered vulnerabilities related to the way routers communicate with floodfill peers. Network database stores and verifies are moved from exploratory to client tunnels, and are encrypted.

Also, to improve anonymity, router’s fast peer set is now limited to a maximum of 30. The release also fixes a bug causing Windows installs to fail when the install or user path contained a “\r” or “\n”. Upgrading is recommended. Please give the developers feedback on IRC #i2p or forum.i2p2.de and get involved or donate ! We are still looking for help on new and existing translations. Please volunteer on IRC #i2p.

0.7.9 Release

Tue, 12 Jan 2010 00:00:00 +0000

0.7.9 fixes several longstanding bugs causing message corruption. We are hopeful that network performance will improve once it is widely deployed. There are other changes that should help router reachability and tunnel build success rates. The release also includes additional translation support, and a full Russian translation by “forget” which was sponsored by “russiansponsor”.

There are more changes to reduce memory and CPU usage, and other bug fixes. Upgrading is recommended. Please give the developers feedback on IRC #i2p or forum.i2p2.de and get involved or donate ! We are still looking for help on new and existing translations. Please volunteer on IRC #i2p.

I2P 0.7.8 Release

Tue, 08 Dec 2009 00:00:00 +0000

Release 0.7.8 contains initial support for router console translations, and changes to the floodfill system which lay the foundation for supporting large growth in the network.

To prevent easy blocking of I2P by malicious firewalls, the release randomizes the I2P port for new installs. For existing installs, please help those who are vulnerable to blocking by changing UDP from 8887 to a random port on and adjusting your firewall if necessary.

I2P 0.7.7 Release

Mon, 12 Oct 2009 00:00:00 +0000

I2P version 0.7.7 contains several anonymity improvements. The use of session keys for crypto was completely reworked, and I2PSnark now uses its own tunnels for tracker communication. Work continues on improving the router console, including conformance to HTML standards and better support of UTF-8.

Work also continues on increasing speeds, both by reducing the number of session keys transferred, by improving the methods of dropping messages during overload, and by reducing drops by high-bandwidth routers. There is a new unsigned update option for those of you that would like automatic updates to bleeding-edge development versions.

I2P 0.7.6 Release

Fri, 31 Jul 2009 00:00:00 +0000

I2P version 0.7.6 contains additional fixes for network stability issues related to tunnel building and connection limits. While the 0.7.5 release greatly improved the congestion that appeared UTC evenings and weekends, it was not eliminated; this release should improve the situation further.

This version also has new console themes by dr|z3d, which may be selected on the new UI configuration page. Sorry, the new themes are not available for IE browsers.

I2P 0.7.5 Release

Mon, 29 Jun 2009 00:00:00 +0000

I2P release 0.7.5

I2P version 0.7.5 foremost addresses network stability issues by adjusting how exploratory tunnels are built if a router nears its connection limit, and also by distinguishing between connected peers and other non-failing peers while picking them for inclusion in tunnels.

This version also delivers fixes to installer behaviour on Windows, to the Router Console, NTCP transport and UPnP mechanism.

Additionally, version 0.7.5 changes the “news.xml” file location where I2P routers check whether a new version is available. Instead of the old URL (http://complication.i2p/news.xml) a new location (http://echelon.i2p/i2p/news.xml) will be used. If your router uses default updater settings, it will start using the new URL automatically. If not, you will need to visit “configupdate.jsp” on the Router Console, and change it manually.

I2P 0.7.4 Release

Sat, 13 Jun 2009 00:00:00 +0000

I2P release 0.7.4

I2P version 0.7.4 introduces notable new features like GeoIP capability and UPnP support. While the former can become a basis for geographically aware tunnel-building, the latter should immediately enable more routers to accept inbound TCP connections, helping distribute workload more evenly.

Inbound NTCP is now enabled automaticaly if the router does not appear firewalled, and default bandwidth limits for new installations are increased.

In addition, multiple bugfixes and updates are included, addressing issues with the NTCP transport, BOB protocol, connection limiting, behaviour of new I2PTunnel options and the SusiDNS user interface. Improvements to the Router Console are likewise included. Updating is recommended.

I2P 0.7.3 Release

Mon, 18 May 2009 00:00:00 +0000

I2P release 0.7.3

I2P version 0.7.3 contains several buxfixes and improvements, includes a lot of maintenance work and new versions of both the SAM and BOB application gateway protocols.

A patch to I2P’s internal web server Jetty is included to correct SusiDNS behaviour on Windows. The way I2P nodes volunteer to participate in the Network Database is changed to avoid too many doing this simultaneously, and creation of new participating tunnels is now throttled before messages in existing tunnels start to get dropped.

I2P 0.7.2 Release

Sun, 19 Apr 2009 00:00:00 +0000

I2P release 0.7.2

The 0.7.2 release fixes multiple bugs and potential problems in I2P, while preparing ground for new functionality.

Threading issues with the SimpleTimer class should no longer occur, the NTCP transport should no longer encounter null pointer exceptions, and “abandoned” tunnels should finish operation correctly.

Support is added for accessing the Router Console over IPv6, a new message type enables I2CP applications to query the router’s bandwidth limits, an experimental desktop interface for managing the router is included for the first time (but not enabled automatically yet) and participation of a single peer in too many tunnels is prevented to improve reliability and safety.

I2P 0.7.1 Release

Sun, 29 Mar 2009 00:00:00 +0000

I2P release 0.7.1

The 0.7.1 release optimizes I2P towards better performance and introduces new features.

Multiple bugs are fixed, replacements to the SimpleTimer class should waste less time on object locking. Some old components are dropped and several classes refactored to avoid repeating code.

Support for encrypted LeaseSets (for creation of links over I2P which an adversary cannot obstruct by attacking its gateways) becomes more complete. New tunnel types like IRC server tunnels and new options like delayed start and idling of tunnels also gain support, along with improved usability of the I2P Socks proxy mechanism.

I2P Dev Meeting - February 10, 2009

Tue, 10 Feb 2009 00:00:00 +0000

Quick recap

Present: altGuest, badger, dream, eche|on, hottuna\_, l00kns33, unixfr3ak, welt, welterde, zzz

Meeting Log

20:58:32 <unixfr3ak> dev meeting eh? 20:59:27 -*- dream turns on devo 21:00:25 <welt> dream: ah.. glad you're here too :) 21:00:51 <badger> 0) Hello 21:00:55 <dream> you are? 21:00:58 <badger> 1) I2P 0.7 21:01:02 <badger> 2) Syndie 21:01:06 <badger> 3) Donations 21:01:15 <badger> 4) ???? 21:01:21 <badger> 5) A short poem recital by zzz 21:01:39 <badger> 0) Hello 21:01:53 <altGuest> hi 21:02:00 <badger> welcome all to the #207th dev meeting 21:02:05 <badger> 'lo 21:02:20 <hottuna_> 'lo! 21:02:40 <eche|on> welcome! 21:02:43 <zzz> so, let's start by covering what's happened since April 10 2007, if anything 21:02:48 <badger> Just to put that in perspective it's been nearly 2 years since hte last one 21:03:06 <badger> well... bush is out....obama in.... 21:03:36 <dream> lol USA 21:03:51 <badger> 1) I2P 0.7 21:03:56 <eche|on> I guess the 0.7 release note is a good idea what happend to I2P 21:04:20 <badger> Well it looks like the rollout of 0.7 has gone fairly smoothly 21:04:22 <badger> with about 84% network coverage now 21:04:29 <unixfr3ak> not bad 21:04:48 <eche|on> :-) 21:04:48 <hottuna_> How much ahs the network grown since 0.7? 21:04:48 <badger> A big cheer to the dev team and release crew for getting it out of the door 21:04:52 <unixfr3ak> one bug i may point out that i and another user have noticed though is 21:04:52 <hottuna_> or even since Christmas? 21:05:21 -*- welt waits for stats.i2p to load.. 21:05:28 -=- Sie sind nun als welterde bekannt 21:05:31 <badger> hottuna_: a fairly slow but steady growth if the stats are anything to go by 21:05:41 <unixfr3ak> adding new private hosts in susidns requirs manual editing of the privathosts.txt file 21:06:08 <welterde> zzz: wasn't that the bug you fixed recently? 21:06:18 <welterde> or was that sth different? 21:06:25 <eche|on> the stats shows a steady slow growing 21:06:35 <zzz> yeah, i broke it in 0.7, just fixed it yesterday, will be in -4 21:06:40 <eche|on> welterde: yes, he seens to have fixed it 21:07:05 <badger> something to look forward to in 7.0.1 21:07:14 <welterde> zzz: good.. that's done then 21:07:16 <badger> eerm 0.7.1 21:07:19 <eche|on> more users :-) 21:07:22 <zzz> sorry about that 21:07:35 <unixfr3ak> what are you guys going to do about network lag...its a growing problem it seems , on the weekends i2p seems overloaded 21:07:56 <welterde> maybe some more streaming lib tweaks? 21:07:57 <unixfr3ak> ethier i think more users is good 21:08:00 <badger> zzz: well you've fixed and improved enough stuff to be allowed the odd breakage :) 21:08:33 <hottuna_> I've suggested motivating user to share by having some ratio indicator on the console 21:08:57 <unixfr3ak> that sounds good 21:09:14 <eche|on> network load went big last month 21:09:17 <zzz> freak, i'm looking at tweaking the capacity calculation in the peer profiles just a little, to react better when things get busy. 21:09:20 <eche|on> months, looks fairly well so far 21:09:51 <hottuna_> zzz: wicked :) 21:09:55 <unixfr3ak> this may be ambitious bout how about using a cron job in linux or whatever windows uses to volunteer bandwidth to i2p when their computer is not being used 21:10:17 <zzz> these things have to be adjusted with great care though, and it takes a full release cycle to test any change 21:10:21 <hottuna_> a scheduler would be and awesome solution aswell 21:10:24 <unixfr3ak> to dumb it down 21:10:28 <badger> The publicity push for release 0.7 seems to have had a marginal effect on numbers, but not nearly the impact I would have hoped for 21:10:41 <unixfr3ak> detect when network / cpu is idle and use it/ dont use when it is 21:10:43 <welterde> zzz: that recent addition to I2CP doesn't allow that yet, right? 21:10:52 <badger> some good coverage in german news sites though 21:11:04 <badger> but slashdot/digg/reddit was rather pathetic 21:11:09 <zzz> allow what welterde ? 21:11:29 <welterde> zzz: to change the ratio/up-bw/down-bw from outside the routerconsole 21:11:29 <eche|on> badger: it needs some time for users to get known to it and keep steady with it :-) 21:11:32 <unixfr3ak> and a defult auto startup registry entry would be nice or a simple shell script for unix 21:12:04 <zzz> no welterde it has nothing to do with that 21:12:08 <hottuna_> dunno about the pr.. i suppose that our 'brand name' will grow every time we have a new release adn a pr wave to that 21:12:13 <welterde> zzz: thought so :/ 21:12:56 <zzz> hopefully the gulli interview w/ me will be published soon, but I haven't heard from him in a week 21:13:06 <unixfr3ak> is i2p ready to ask for volunteer bandwidth from sponsors? (other than me with my tiny connection) 21:13:39 <welterde> hmm.. that might be worth a try 21:13:50 <dream> I don't think anyone has ever said no to volunteered bandwidth. 21:14:12 <unixfr3ak> the tor network has a lot of sponsored nodes, but on the other hand a lot of nodes on the same subnet would be suspicious to users and offer someone more control over the network 21:14:37 <welterde> i think we "fixed" that already 21:14:59 <hottuna_> sponsoring would'nt be a bad idea 21:14:59 <hottuna_> jas a simple html tab on the mainpage? 21:14:59 <hottuna_> just* 21:15:05 <unixfr3ak> randomly placed nodes by individual volunteers seems to be safer 21:15:05 <unixfr3ak> but not as practical 21:15:15 <unixfr3ak> most people by nature will leech 21:15:44 <dream> I don't think that's necessarily true unixfr3ak, but it's good to prepare for non-participants. 21:16:21 <unixfr3ak> for example 21:16:40 <unixfr3ak> someone who just starts the i2p router, and has no idea what it does and runs i2phex 21:16:49 <unixfr3ak> constantly downloading 21:17:11 <unixfr3ak> mabye the defualt bandwith should be changed 21:17:22 <hottuna_> has been changed in 0.7 21:17:34 <unixfr3ak> or users should be asked for connection speed during the install for more accurate bandwith shareing limits 21:18:26 <unixfr3ak> or mabye a virus that installs i2p as a backdoor :P 21:18:34 <welterde> heh 21:18:40 <hottuna_> would be a great idea.. the installer should support that, right? 21:19:08 <welterde> the first or the second? :> 21:19:08 <unixfr3ak> my joke or asking the connection bandwith? 21:19:23 <welterde> first) probably yes 21:19:26 <unixfr3ak> it should be a line or 2 in a config file somewhere 21:19:39 <unixfr3ak> the one without the :P 21:20:59 <badger> download limits for users who don't share upstream bandwidth? 21:21:15 <unixfr3ak> sounds intresting 21:21:20 <unixfr3ak> but 21:21:33 <unixfr3ak> i dont think we should go to such desprate measures yet... 21:21:38 <dream> by default it shares up to 100% of the bandwidth unixfr3ak. once it gets a few client tunnels, the majority is spent on intermediate ones. 21:21:45 <welterde> don't routers already punish other routers, who don't route tunnels? 21:22:00 <unixfr3ak> yes 21:22:00 <dream> and I think i2p is already load balanced. I sure cannot download more than I upload on the bandwidth tab. 21:22:25 <unixfr3ak> i think so but, if many people leech at one time it will still put a hevy load on the network 21:22:32 <badger> perhaps this is just a case of being more informative to first time users 21:22:35 <unixfr3ak> especially if thier ips are dynamic 21:22:46 <eche|on> `http://stats.i2p/cgi-bin/tot.cgi?a=bandwidthReceiveBps.5m&s=365&u=y` 21:22:56 <badger> make it clear that giving back to the network improves your experience 21:23:07 <unixfr3ak> yes 21:23:18 <unixfr3ak> and to run it when they are not using thier pc 21:23:36 <unixfr3ak> insted of just letting thier connection that they are paying for be idle 21:23:51 <dream> most people turn their computers off, it's really sad 21:24:09 <unixfr3ak> yes 21:24:12 <dream> paying their ISP per month, when they could instead for the price of 4 light bulbs... 21:24:15 <l00kns33> i think most people understand this - i even think most people who use i2p are geeks themself ;) 21:24:32 <badger> anyway moving on - anything else to add for 1) I2P 0.7? 21:24:55 <unixfr3ak> for now yes 21:25:16 -*- welterde waits for his signal.. 21:25:20 <unixfr3ak> but that may change in the future 21:25:25 <eche|on> badger: no 21:25:25 <badger> 2) Syndie 21:25:37 <welterde> ok then :) 21:25:37 -*- badger passes the 70s boom mike over to welterde 21:25:45 <badger> *mic 21:26:15 <welterde> as you may (or may not) i recently finished the effort to apply these patches from MOSFET 21:26:20 <welterde> +know 21:26:35 <unixfr3ak> leave e out on the forums i don't use them :P , brb cigarette 21:27:14 <welterde> which should fix some bugs and disable that (imho) b0rked default ui 21:27:26 <welterde> instead the swt one is used, which most users find easier 21:27:42 <badger> <jrandom>w0rd</jrandom> 21:28:11 <welterde> hmm? 21:28:30 <dream> it's nice to hear someone was working on getting failed synchronizations to retry. 21:28:40 <badger> welterde: sorry, old dev meeting joke 21:28:59 <badger> is there a new public syndie archive somwhere? 21:29:06 <welterde> anyway.. i hope i have time soon to replace that b0rked ;) index thingy 21:29:09 <welterde> badger: yup 21:29:25 <welterde> http://syndie.welterde.(i2p|de)/ 21:29:52 <dream> making it possible to run syndie using a remote database is important I'd say, to make it easier for people to run their own archives. 21:29:54 <welterde> but you can't post there (yet) as it is just a static archive 21:30:47 <welterde> have to that one to the default ones too 21:30:56 <welterde> will do that soonish 21:31:16 <eche|on> so syndie work goes on 21:31:32 <welterde> yup 21:31:54 <welterde> currently trying to profile syndie.. 21:32:29 <welterde> but wasn't able to spend much time in that area though.. 21:32:59 <eche|on> so much work to do... 21:33:14 <welterde> yes :/ 21:33:17 <dream> running syndie in text mode is tricky, since the interface seems to be slipping behind its current behavior 21:33:17 <dream> usually it works if you just leave it in --cli, but when it freezes there's no real indication. 21:33:41 <welterde> yeah.. the cli is b0rked too currently :/ 21:34:00 <welterde> imho we should seperate syndie into multiple parts, eg. libsyndie, gui, cli, ... 21:34:12 <badger> makes sense to me 21:34:19 <welterde> that should make writing custom extensions, etc. easier 21:34:29 <dream> What sort of stuff would libsyndie cover? 21:34:36 <badger> early v0.0.1 syndie's UI was just a top on the cli binary 21:34:48 <badger> but it seems that idea got lost enroute 21:34:55 <dream> it even has the text console today. 21:35:23 <welterde> dream: message decoding, archive syncing, etc. etc. 21:35:34 <welterde> most of the logic 21:36:06 <dream> so libsyndie is pretty much an interface over the database, and maybe the archive/ directory? 21:36:09 <badger> aye, gui, cli and webtop should just be a light wrapper 21:36:10 <welterde> imho we should keep gui/cli seperate from the program logic 21:36:42 <welterde> dream: the archive isn't used to store anything.. it's just used for serving the archive 21:37:02 <dream> I know that. 21:37:14 <welterde> but as cli/webtop use it we should put it into the libsyndie as well 21:37:15 <dream> So I guess only the web server would need to deal with that directory. 21:37:35 <dream> filling it and synching from it, sort of like a postfix mail queue. 21:38:00 <welterde> but we should only generate/sync it, when we are actually using it.. not like now.. 21:38:08 <welterde> where it is always generated/synced... 21:39:18 <dream> I don't see a problem with only using the archive/ directory for the webserver. It's really just a convenience so you can use existing static file serving functionality. 21:40:07 <welterde> there should be a cli command like generate_archive or something like that imho 21:40:57 <welterde> and we should bring that import.cgi back, so we can run a mostly static archive, while still being able to post 21:41:04 <welterde> or... hmmm... 21:41:04 <dream> what would you do with that archive using the client interface? 21:41:15 <welterde> rsync with a remote site? 21:41:26 <welterde> that's how syndie.welterde.(i2p|de) works ;) 21:41:43 <dream> trouble with a static archive is that keeping the filesystem up to date with the database is a task that is similar to designing a database. 21:41:59 <welterde> hmm.. not really 21:42:05 <welterde> as it's one-way only 21:43:17 <unixfr3ak> this may be a little off-topic but has anyone considered a datastore function? 21:43:20 <dream> so using a hypothetical --cli someone creates a message. They then generate_archive after creating it? Sounds suspiciously similar to commiting a transaction after inserting. 21:43:52 <unixfr3ak> also in i2phex as i told Complication previously the bitzi lookup in i2phex inst anonymous 21:43:55 <dream> magicbutton() 21:44:04 <welterde> dream: uhm.. no 21:44:17 <dream> ...i2phex checks bitzi.com? that's nuts 21:44:37 <unixfr3ak> yes 21:44:39 <welterde> unixfr3ak: there was some work in direction of freenet afair 21:44:43 <dream> welterde, so then their message never goes into the archive/ directory and can't get synchronized... 21:45:20 <welterde> dream: no.. just mean that a transaction is a bit different 21:45:27 <welterde> for example: you don't edit anything 21:45:33 <welterde> (except for the index maybe) 21:46:02 <welterde> generate_archive just dumps the db and updates the indexes while doing that 21:46:41 <unixfr3ak> right click a file 21:47:20 <unixfr3ak> and view bitzi ticket takes you to the non-anon site 21:47:20 <unixfr3ak> lucky my browser is proxyd by i2p, and my alternate one tor 21:47:31 <dream> so how do you get your new database content into the archive? What if syndie dies after inserting a message, but before you save it to the archive/ directory? 21:47:39 <unixfr3ak> 0_0 looks like spongebob missed the meeting 21:47:57 <welterde> dream: nothing.. it's just not archive/ 21:48:16 <welterde> but it will be on the next successful run of generate_archive 21:49:01 <dream> what I'd do is let the client run the web server, and the web server checks archive/ and pulls out all the messages in the db not already there. Or just serve the db messages directly. 21:49:23 <dream> generate_archive doesn't seem like the sort of thing you'd want the client to have to keep track of. 21:49:50 <welterde> problem is.. you can't run syndie on every machine 21:50:18 <welterde> for example this server (i2p2.de/welterde.de) has reached it's limited 21:50:36 <welterde> it will heavily swap when i run syndie on it.. 21:50:41 <welterde> so i have to run it locally 21:50:46 <eche|on> yeah 21:51:06 <welterde> no problem if i had reasonable upload... which i don't have 21:51:19 <welterde> which most adsl-users don't have.. 21:51:45 <badger> anyway - good work with the all the patches welterde - can we expect a release in the not-too-distant-future? 21:51:47 <welterde> so it's either a static archive or one that is slow as hell 21:52:08 <welterde> badger: i think i'll switch from a to b (alpha to beta) soonish 21:52:16 <badger> great 21:52:40 <badger> anything else to add about future dev? 21:52:56 <badger> (syndie) 21:53:10 <welterde> n0pe 21:53:19 <welterde> ;) 21:53:24 <badger> righty in that case 21:53:30 <badger> 3) Donations 21:53:49 -*- badger swings the mic over to eche|on 21:54:00 <eche|on> it's open again! 21:54:18 <eche|on> I created a paypal account and linked it on i2p website 21:54:42 <hottuna_> :D 21:54:47 <badger> coolio 21:54:50 <hottuna_> wicked 21:54:52 <eche|on> but the buttons links to https:// sites of paypal, works not for eepsite yet 21:55:01 <dream> yeah I guess that's an advantage welterde 21:55:08 <eche|on> til yet no entry on that front 21:55:20 <welterde> eche|on: maybe you should add some notes on how to tell you what you should do with it 21:55:29 <eche|on> and undecided about a acc for 2ndlive 21:55:31 <zzz> can you add a link from the donate page to the halloffame page, and/or provide more info on what donations will be used for 21:55:39 <dream> I still think whatever creates the archive should synchronize more than just dump. 21:55:48 <badger> yup 21:56:02 <badger> are you planning to support bounties too? 21:56:10 <eche|on> welterde: acked 21:56:13 <unixfr3ak> you could just use apache 21:56:17 <welterde> dream: premature optimization ;) 21:56:19 <eche|on> zzz: acked 21:56:24 <dream> oops 3) 21:56:24 <dream> I don't have any money sorry T_T 21:56:28 <eche|on> we need a list of stuff to buy/not to buy with donations 21:56:37 <zzz> and shouldnt echelon and welterde subscriptions really be listed as expenses instead? 21:56:40 <unixfr3ak> what web server does i2p include? 21:56:51 <eche|on> badger: yeah, donations are "for all funds" or dedicated for a bounty 21:57:04 <badger> grand 21:57:19 <eche|on> and in paypal there should be a textfield in which you can enter the goal of the money :-) 21:57:33 <zzz> you could also put a news link on the front page that donations are open 21:57:36 <badger> If I donate 1000 EUR do I get a Hot Tuna i2P t-shirt? 21:57:51 <eche|on> but I cannot donate to myself ;-) 21:58:02 <welterde> hottuna_: say yes! ;) 21:58:16 <eche|on> no prob so far, I wait for the first one and announce it ;-) 21:58:35 <zzz> you had your chance to come to 25c3 and get a shirt 21:58:47 <welterde> there is still a 26c3 ;) 21:58:59 <eche|on> acked, zzz - nice idea 22:00:32 <eche|on> so no more from my site to topic donations 22:00:51 -*- welterde waits for paste to load.. 22:01:16 <badger> in that case: 22:01:22 <badger> 4) ???? 22:01:33 <badger> anyone else have anything to bring to the meeting? 22:01:37 <welterde> yup.. 22:01:46 <welterde> but you have to wait until paste loads :/ 22:01:52 <eche|on> lets have a piece of cake for everyone! 22:02:31 <welterde> yay! :) 22:02:32 -*- unixfr3ak takes it and runs 22:02:38 <welterde> nooooo 22:03:03 -*- badger *bafs* unifr3ak on the head 22:03:08 <unixfr3ak> yessss 22:03:12 <eche|on> ;-) 22:03:46 <unixfr3ak> i wonder if that part will go in the meting log 22:03:50 <unixfr3ak> :P 22:03:57 <welterde> I hereby announce *drum roll* thmoo: inbljam6y6mynwz2474hk655w2jtv7trofxbqzng4re26ga6rg4a.b32.i2p 22:03:58 <welterde> ;) 22:04:04 <welterde> unixfr3ak: of course it will! 22:04:15 <welterde> everyone get a telnet client and connect ;) 22:04:37 <badger> not a MUD?! 22:04:40 <unixfr3ak> the base 32 key? 22:04:49 <welterde> badger: of course! 22:05:06 <welterde> unixfr3ak: you have to open a client tunnel and connect to that with a telnet/mud client 22:05:08 <welterde> (or use socks) 22:05:38 <unixfr3ak> i dont want to get my socks dirty ill make a tunnel :p 22:05:43 <unixfr3ak> hmm 22:05:47 <unixfr3ak> but for destination 22:05:50 <badger> muddy socks 22:05:59 <unixfr3ak> does that include the .i2p ? 22:06:05 <welterde> unixfr3ak: yup 22:06:11 <welterde> worked for me at least ;) 22:06:56 <dream> you can also look up the dest of a b32 if you want a local copy. zzz showed me how using i2ptunnel's secret cli interface. 22:07:13 <unixfr3ak> Delay Connect: (for request/response connections) 22:07:18 <unixfr3ak> i take it yes for that 22:07:21 <dream> that reminds me I should get these room descriptions off paper and into the darn thing 22:07:24 <badger> welterde: maybe post a short howto somewhere ;-) 22:07:35 <welterde> dream: yay :) 22:07:46 <welterde> badger: heh.. will do 22:07:58 <unixfr3ak> Trying 127.0.0.1... 22:07:58 <unixfr3ak> Connected to localhost. 22:07:58 <unixfr3ak> Escape character is '^]'. 22:08:02 <unixfr3ak> impressive :P 22:08:02 <welterde> `http://paste.i2p2.i2p/show/11/` <- the b64 22:08:08 <l00kns33> one comment about i2p in general: 22:08:08 <l00kns33> i think it is too much "from geeks for geeks" - you need to know what non-geek users need and want 22:08:16 <unixfr3ak> wonder whats on the other side of the tunnel 22:08:20 <dream> unixfr3ak, if you're extra paranoid yes, otherwise timing attacks may be possible to test if you're online or not. :> 22:08:21 <welterde> l00kns33: they want games! :D 22:08:46 <dream> l00kns33, what could be less geeky than a text based online adventure game! 22:09:01 <welterde> unixfr3ak: works? you should see a menu of some kind 22:09:02 <dream> I put on my robe and wizard hat! 22:09:19 <unixfr3ak> of coarse 22:09:28 <l00kns33> that's one thing - and a good idea :) 22:09:31 <unixfr3ak> Welcome to thmoo-cmd 2.1... 22:09:38 <welterde> ha :) 22:09:47 <welterde> you then need to type connect guest afair 22:09:52 <unixfr3ak> whats so impressive about telnet over i2p? 22:10:30 <zzz> we'll have a connect client soon so you won't need to set up a tunnel 22:10:46 <l00kns33> cool :) 22:10:50 <welterde> unixfr3ak: nothing? 22:11:20 -*- welterde writes up a howto.. 22:11:26 <unixfr3ak> has a weird chat feature :P 22:11:45 <badger> well on that note - anything else anyone wants to add? 22:11:46 <welterde> unixfr3ak: you have to "say something" 22:11:50 <dream> I wonder how that would work zzz? You mean like a VPN? 22:12:01 <welterde> dream: more like socks i think 22:12:05 <dream> Or a specially designed telnet client? ._. 22:12:19 <dream> Oh well I did hear about SOCKs. 22:12:29 <unixfr3ak> foo siad hi 22:12:31 <zzz> more like socks 22:12:39 <zzz> telnet localhost 1234 22:13:00 <zzz> connect inbljam6y6mynwz2474hk655w2jtv7trofxbqzng4re26ga6rg4a.b32.i2p 22:13:00 <welterde> unixfr3ak: and to answer you to "say something" ;) 22:13:06 <zzz> thats it 22:13:15 <dream> socks is tricky, since it's like i2ptunnel except just about anyone can make new tunnels to different places. 22:13:37 <unixfr3ak> yes i know...no need to point out the painfully obvious 22:13:50 <welterde> dream: no.. i just uses the shared one 22:14:06 <welterde> at least.. that's how it should work ;) 22:14:34 <welterde> afk for a bit 22:14:36 <badger> well I think we've reached a good point to... 22:14:44 -*- badger winds up 22:14:54 -*- badger *baf*s the meeting closed 22:15:10 <eche|on> :-) 22:15:13 <badger> good job everyone 22:16:12 <dream> you can't make a server tunnel with the SOCKS thing? hmm... 22:16:34 <dream> I guess that would be a pretty nice thing for non HTTP protocols. :) 22:16:49 <dream> Either that or implementing CONNECT in the eeproxy. 22:16:52 <unixfr3ak> now you guys are going to dissapear again lol 22:18:38 <dream> poofda 22:19:40 <zzz> I'm still here 22:19:49 <zzz> our socks is client-only now 22:20:51 <zzz> I have CONNECT implemented, that's what I was talking about above 22:23:20 <dream> Neat I can't think of any reason why not to do that, and it'd be lots more convenient since SOCKS is so goddamn popular many apps come with it.

I2P 0.7 Release

Sun, 25 Jan 2009 00:00:00 +0000

I2P release 0.7

The 0.7 release adds stability and flexibility to I2PSnark, which can hopefully be used to distribute I2P updates in future.

The I2P router gets fixes and optimizations to various transport-level and streaming issues, network exploration, NetDB performance and the UDP introducer system. Among other features, the new release offers better connection limiting, higher tolerance to “out of memory” exceptions in helper applications, and an experimental new address system using Base32 hashes of destination keys (".b32.i2p" URLs).

I2P 0.6.5 Release

Mon, 01 Dec 2008 00:00:00 +0000

I2P release 0.6.5

The 0.6.5 release introduces new components, drops some old ones (like the old TCP transport) and has been optimized to perform better.

The BOB (Basic Open Bridge) protocol is introduced, for use by client applications which cannot import I2CP libraries directly. This deprecates the old SAM protocol which was previously used in such cases. For now however, BOB is not started automatically yet on new installations, and SAM remains active on old installations.

I2P 0.6.4 Release

Mon, 06 Oct 2008 00:00:00 +0000

I2P release 0.6.4

The 0.6.4 release adds performance and stability improvements. Floodfill peers which are already connected, are preferred for RouterInfo stores, and references to new floodfill peers obtained from ordinary peers in case of shortage.

Preference for already connected peers is generally increased by considering them active. Timeouts during tunnel joins are now counted against peer profiles.

Improvements to the shutdown handler, tunnel builder, router throttling, collection of tunnel pool statistics, as well as router console and I2PSnark improvements (and texts to explain reachability issues) are also included.

I2P 0.6.3 Release

Tue, 26 Aug 2008 00:00:00 +0000

I2P release 0.6.3

The 0.6.3 release introduces multiple bugfixes, optimizations and security improvements. Routers will start monitoring the number of well-behaved NetDB peers, volunteering as one if a shortage develops and they can. Well-behaved NetDB nodes are preferred stronger, and ill-behaved nodes blacklisted more effectively.

LeaseSets are handled more efficiently, new fixes should enable the correct operation of UDP introducers. I2P also gains preliminary support for permanent IP blocklists, and a new peer connection limiter. Improvements to the Router Console should make configuring client applications easier and I2PSnark will now resist corrupt data better.

I2P 0.6.2 Release

Sat, 07 Jun 2008 00:00:00 +0000

I2P release 0.6.2

The 0.6.2 release delivers performance and anonymity improvements. LeaseSet data is no longer added to every end-to-end message, reducing protocol overhead.

Unreachable peers are avoided as inbound tunnel gateways, which helps reliability and makes it possible to use persistent Lease selection, which in turn helps performance by reducing out-of-order message delivery.

The sequence of peers in a tunnel is now kept in a strict order according to XOR distance from a random value, to make it harder for an adversary to gather statistics for a predecessor attack. Improvements to applications like I2PSnark and the Router Console are also introduced.

I2P 0.6.1.33 Release

Sat, 26 Apr 2008 00:00:00 +0000

I2P release 0.6.1.33

The 0.6.1.33 release contains several important bug fixes and performance improvements in SSU reachability detection, floodfill peer selection, tunnel peer selection, tunnel testing, NTCP idle detection, the streaming lib, and news fetching. It also adds secondary tracker support to i2psnark, and verification of downloaded Jetty libraries when building from source.

Please upgrade as soon as you can, as these fixes should improve the reliability of the whole network. This release is backward compatible: if you already have 0.6.1.31 or greater installed, it will recognize the signature on the signed update file, and you can update automatically.

I2P 0.6.1.32 Release

Sun, 09 Mar 2008 00:00:00 +0000

I2P release 0.6.1.32

The 0.6.1.32 release contains several bugfixes, a new tunnel build algorithm from zzz which regulates the intensity of tunnel building according to previous levels of tunnel build success, and other performance improvements.

This release is backward compatible, and if you already have 0.6.1.31 installed, it will recognize the signature on the signed update file (so you can update automatically).

However, to ensure better distribution of load between our 3 signed update servers, I recommend that you perform the following optional check:

I2P 0.6.1.31 Release

Sun, 10 Feb 2008 00:00:00 +0000

Hi, there’s a new I2P release available for your enjoyment at http://www.i2p2.de/downloads/.

The 0.6.1.31 release will make the I2P release process independent of jrandom and *.i2p.net servers. Our new primary mirror is www.i2p2.de , accessible in I2P at www.i2p2.i 2p.

Automatic updates will hosted on several eepsites(I2P Sites), signed by Complication, for which purpose 0.6.1.31 includes two new release verification keys.

Also included are multiple bugfixes and improvements to the automatic update mechanism, address book, I2PSnark and IRC proxy. Support will appear for the SAM protocol version 2.

I2P Status Notes for 2008-02-01

Fri, 01 Feb 2008 00:00:00 +0000

Welcome!

Status Update 01/2008

Due to a server breakdown of i2p.net beginning of 2008 the I2P project page wasn’t reachable. The only person who’s got access (jrandom) to reactivate that server is offline and NOT reachable for us at least for 10 more month. It wasn’t even possible to get the installer or the seednodes to start a fresh router.

In the last few weeks we got 2 webserver by friendly helpers as donations and setup a complete redundant solution for the vital parts of I2P.

I2P 0.6.1.30 Release

Sun, 07 Oct 2007 00:00:00 +0000

Hi y’all, there’s a new I2P release available for your enjoyment at http://www.i2p.net/download

This release includes some experimental tunnel throughput enhancements, eepget fixes, network backlog handling, i2psnark fixes, among other changes. As always, a full list of changes can be found at http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/history.txt?rev=HEAD

Tue, 10 Oct 2006 00:00:00 +0000

Hi y’all, brief status notes this week

Index

0.6.1.26 and network status
Syndie development status
Distributed version control revisited
???

1. 0.6.1.26 and network status

The other day we pushed out a new 0.6.1.26 release, including lots of i2psnark improvements from zzz and some new NTP safety checks from Complication, and reports have been positive. The network seems to be growing slightly with no new odd effects, though some people still have trouble building their tunnels (as has always been the case).

I2P Status Notes for 2006-10-03

Tue, 03 Oct 2006 00:00:00 +0000

Hi y’all, a belated status notes this week

Index

Net status
Router dev status
Syndie rationale continued
Syndie dev status
Distributed version control
???

1. Net status

The past week or two have been fairly stable on irc and other services, though dev.i2p/squid.i2p/www.i2p/cvs.i2p had a few bumps (due to temporary OS-related issues). Things seem to be at a steady state at the moment.

1. Router dev status

The flip side to the Syndie discussion is “so, what does that mean for the router?”, and to answer that, let me explain a bit where the router development stands right now.

I2P Dev Meeting - September 12, 2006

Tue, 12 Sep 2006 00:00:00 +0000

Quick recap

Present: cervantes, jrandom, kostya213, modulus, tethra, vulpine

Meeting Log

16:06 <jrandom> 0) hi 16:06 <jrandom> 1) 0.6.1.25 and net status 16:06 <jrandom> 2) I2PSnark 16:06 <jrandom> 3) Syndie (what/why/when) 16:06 <jrandom> 4) Syndie crypto questions 16:06 <jrandom> 5) ??? 16:06 <jrandom> 0) hi 16:06 * jrandom waves 16:06 <jrandom> weekly status notes posted up at http://dev.i2p.net/pipermail/i2p/2006-September/001307.html 16:07 <jrandom> since those notes came up hours and hours ago, y'all should have already read them and have notes ready, right? ;) 16:07 <jrandom> jumping forward to 1) 0.6.1.25 and net status 16:08 <vulpine> <Complication> Regarding 0.6.1.25 seems to have worked fine over here, only one previously unseen error 16:08 <jrandom> cool, whats the prob? 16:08 <vulpine> * Complication searches logs 16:09 <jrandom> the net size seems larger than before, though still same orer of magnitude 16:09 <vulpine> <Complication> "Unknown error reading the net.i2p.data.i2np.GarlicMessage: wtf, fromLong got a negative? -840" 16:10 <vulpine> <Complication> Started with "ERROR [NTCP read 1 ] .router.tunnel.FragmentHandler: Error receiving fragmented message (corrupt?)" 16:10 <jrandom> ah ok cool, that one has been around for a long time, safe to ignore 16:11 <vulpine> <Complication> Single occurrence 16:11 <vulpine> <frosk> i've gotten several of that last one 16:11 <vulpine> * jrandom pokes fox 16:12 <vulpine> <Complication> Oh, and one more: "router.tunnel.TunnelDispatcher: wtf, took 1121 to dispatch net.i2p.data.i2np.TunnelBuildMessage@XXXX out YYYYY in net.i2p.router.tunnel.PumpedTunnelGateway@ZZZZ" 16:12 <vulpine> <Complication> (seems non-significant too, maybe simple congestion) 16:12 <jrandom> aye, likely 16:13 <jrandom> irc is, obviously, a bit rough at the moment still 16:13 <jrandom> (but, for once, its not i2p's fault :) 16:14 <jrandom> ok, anyone have anything else for 1) Net status and 0.6.1.25? 16:15 <kostya213> just want to add that .25 fixed all my problems i've been having the past few months 16:15 <jrandom> wikked! 16:16 <vulpine> <green> please, change status calcul when only using NTCP 16:16 <jrandom> 'k, but its not recommended to disable udp (i believe i've explicitly said that i won't tell people how to disable udp too) 16:17 <jrandom> but the status should be updated to take into consideration that udp is not the only transport 16:17 <jrandom> i'll get that fixed in the next rev, thanks 16:17 <vulpine> <green> jrandom : sure you don't tell, but i'm able to read code ;) 16:18 <jrandom> right, though when i don't recommend something, and tell people not even to try, don't be suprised if a display message comes up confusing ;) 16:19 <vulpine> <green> sure, i could also juste display "OK" in console :) 16:19 <jrandom> true 'nuff 16:21 <jrandom> ok, lets jump on over to 2) I2PSnark 16:21 <jrandom> zzz doesn't seem to be over there atm 16:22 <jrandom> there are some changes zzz is working on to improve the scheduling in i2psnark 16:23 <jrandom> (its a bit.. simplistic atm iirc, though i'm not entirely certain of the mods zzz is hacking on) 16:23 <jrandom> ((but i look forward to the progress!)) 16:25 <jrandom> ok, if there's nothing else on 2) I2PSnark, lets move forward to 3.*) Syndie stuff 16:26 <jrandom> lets jump in to 3.1) what is syndie first, since there's so much to cover 16:27 <jrandom> i got a few questions before the meeting regarding the encryption for posts 16:27 <jrandom> basically, posts are *symmetrically* encrypted - anyone with the symmetric key can read the post, as they're authorized 16:28 <jrandom> channel replies are asymmetrically encrypted to the public key associated with the channel/forum 16:28 <jrandom> some posts can use passphrase based encryption to generate the symmetric key for reading 16:29 <jrandom> and some posts can include the symmetric key in the post's readable headers (so that anyone can read it) 16:29 <modulus> what's the point of that last one? 16:29 <jrandom> and some forums themselves can include the symmetric key in the forum metadata, so that anyone can read the post but only if they have the channel metadata 16:29 <jrandom> modulus: so that everything is always encrypted, even publicly readable stuff 16:29 <jrandom> (so that trivial wiretapping is useless) 16:30 <modulus> right, i see. 16:31 <jrandom> ok, i think that covers the encryption questions that were asked before the meeting 16:31 <jrandom> does anyone have any questions on 3.1) what is syndie? 16:31 <jrandom> (I mean, more will be clarified as it is pushed out there, of course) 16:32 <vulpine> <void> hmm 16:33 <jrandom> que tal void? 16:33 <vulpine> <void> <void> i guess that the message (.zip) archive can also include other messages, possibly from other people, such as the messages being quoted? 16:34 <jrandom> well, yes, you can include .snd files as attachments, but there is an explicit namespace, so you can do standard References: style links to previous messages 16:34 <jrandom> (aka you don't have to do frost-style "threading") 16:35 <vulpine> <void> ok, right 16:37 <vulpine> <Complication> About Syndie, I wondered how people would go about solving the problem of granting people access to some multiple-poster forum (like accounts on an ordinary message board) but not granting this irrevocably, and avoiding undesired mess when need to revoke access (for whatever reasons) occurs 16:38 <vulpine> <Complication> One solution, of course, seemed for the author to specify a recommendation of whose replies clients should display 16:38 <jrandom> Complication: create a new pub/private keypair, give the private key to (temporarily) authorized people, and include the public key as the list of "keys allowed to post" 16:38 <vulpine> <Complication> ..and for clients, unless they desire to research history, to follow this recommendation (or more specifically its latest version) 16:38 <jrandom> (and when they are no longer authorized, remove that key from the list of "keys allowed to post") 16:39 <kostya213> jrandom: you might want to use a different extension than .snd since it's a widely used extension for audio applications, mime will confuse it 16:39 <jrandom> ah, right - all forums have an "owner" (a signing private key) who can manage the list of who is allowed to post, etc 16:39 <vulpine> <Complication> "keys allowed to post" would be metadata attached to the author's latest post, or some other message, right? 16:39 <jrandom> good point kostya213, though we may be stuck with .dat then ;) 16:40 <jrandom> Complication: ah sorry, no, its like the current/old syndie- separate signed metadata posts for the forum/channel itself 16:40 <vulpine> * Complication believes that someone has even claimed .dat for something :) 16:40 <jrandom> yes, the application called "octet-stream" ;) 16:40 <vulpine> <void> it doesn't look like .syn is used for anything noteworthy 16:41 <vulpine> <Complication> Aha, special metadata posts... right, that could do it 16:41 <jrandom> oh neat, we get to syn! 16:41 <jrandom> (good eye void, thanks kostya213) 16:41 <vulpine> <void> hmm, " 16:41 <vulpine> <void> hmm, "Word Synonym File", Company: Microsoft 16:42 <jrandom> well, i'm sure we'll work 'er out 16:42 <kostya213> yes it's used by word 16:42 <vulpine> <void> but we might as well ignore that :) 16:42 <kostya213> don't lose hope, i think it's possible to find something that won't cause problems with widely used mimetypes 16:43 <jrandom> ok, anything else on 3.1) What is syndie? 16:43 <vulpine> <void> err, then again, why would we stick with three-letter extensions? it's a relic from the DOS ages 16:43 <kostya213> one thing that must be asked, why limit to a three-letter extension? nobody uses DOS anymore 16:44 <jrandom> heh 16:44 <kostya213> jinx on void 16:44 <kostya213> .syndie seems good to me 16:44 <vulpine> <void> .synd wouldn't conflict with any 16:44 <kostya213> good as well 16:45 <vulpine> <void> damn lag :( 16:48 <jrandom> ok, lets jump on over to 3.2) Why does Syndie matter? 16:48 <vulpine> <void> jrandom: wait 16:48 <cervantes> (because you say it does) 16:48 * jrandom waits 16:48 <jrandom> !thwap cervantes ;) 16:48 <vulpine> <void> the status notes post mentions that an avatar can be attached to a post, otherwise a default will be used 16:49 <vulpine> <void> but what if a person wants to have several predefined avatars instead of a single "default" one? 16:49 <jrandom> aye, the author can include a default avatar in their own channel's metadata 16:49 <vulpine> <void> attaching the other one every time isn't going to be efficient 16:49 <jrandom> good question void - lets jump to that script code in the notes 16:50 <jrandom> listauthkeys --authorizedOnly true 16:50 <jrandom> authenticate 0 16:50 <vulpine> <void> (?) 16:50 <jrandom> listauthkeys will display all of the identities you can sign the message saying that you are, while "authenticate 0" picks an identity to sign with 16:51 <jrandom> so, that identity has its own channel, and that channel has its own metadata, which may include an avatar 16:51 <vulpine> <void> hmm, a separate identity means a separate keypair? 16:51 <jrandom> yes 16:51 <vulpine> <void> what if a person wants to have several avatars on a single identity? 16:52 <jrandom> they have a default avatar on their channel metadata, and they can override it on a per-message basis 16:52 <kostya213> dubious value 16:52 <vulpine> <void> several "default" avatars he can choose from 16:52 <vulpine> <void> or am i splitting hair here? :) 16:53 <jrandom> ah, i understand what you're saying. nah, not supported at first 16:53 <jrandom> maybe later 16:53 <vulpine> <void> true kostya213, never mind then 16:53 <vulpine> <void> :) 16:53 <jrandom> (but the avatars will be very limited in size, so shouldn't be much trouble to include) 16:53 <vulpine> * Complication thinks the adding of per-message ones could be coded to be easy enough 16:53 <vulpine> <void> so, 3.1) What is syndie? 16:53 <vulpine> <Complication> (eventually) 16:54 <vulpine> * cervantes glues the irc servers together 16:54 <vulpine> <void> Complication: jrandom just said he is going to do that already :) 16:54 <jrandom> (per message ones will be in the baseline complication, its the idea of having many 'defaults' to choose from, picking it by saying "use avatar 1" in a message rather than including the avatar itself) 16:54 <vulpine> <Complication> latency, latency... 16:54 <jrandom> ok, anything else for 3.1? 16:54 <jrandom> if not, lets jump to 3.2 16:55 <vulpine> <void> i think that's all 16:55 <jrandom> wr0d. 16:56 <jrandom> other than cervantes' snark, anyone have any questions/comments/concernts re "why"? 16:56 <jrandom> (er, "concerns") 16:58 <vulpine> <Complication> cervantes: did you clean the surface with alcohol before applying glue on the ircd? ;) 16:58 <kostya213> imo syndie doesn't need justification, its value should be self-evident to anyone who's already interested in anonymizing networks 16:58 <kostya213> and aware of the dangers of centralization of information 16:59 <vulpine> <Complication> (repost, please ignore if reached server) 16:59 <vulpine> * Complication thinks that Syndie matters because Joe Sixpack running phpBB would suffer pwnage too quickly, and Joe Sixpack running $random_blogging_tool would suffer it too 16:59 <vulpine> <Complication> (even if probability might vary) 16:59 <vulpine> <void> indeed 16:59 <jrandom> aye, plus anyone facing actual hostile adversaries (not even necessarily state level) 17:00 <jrandom> ok, cool, just wanted to run things by y'all 17:00 <jrandom> anything else on 3.2, or shall we move over to 3.3) when can we use syndie? 17:01 <vulpine> <void> well, essentially it's a forum/blogging/e-mail/communication tool based on cryptographic primitives and independent from a transport layer 17:01 <vulpine> <Complication> ...and in the far-out scenario that Joe Sixpack's adversary would mount intersection attacks, anyone running an eepsite of any kind would suffer pwnage eventually (except in an enormous network) 17:01 <kostya213> it might be a harder sell to those who don't see immediate value in privacy/anonymity 17:01 <jrandom> kostya213: aye, though we may be able to pull some tricks, like being able to safely browse offline 17:02 <vulpine> <Complication> They might appreciate security regardless 17:02 <jrandom> (e.g. an offline rss reader that also pulls in the full set of pages referenced, not just the rss summary) 17:02 <vulpine> <void> so yeah, i can't see why it needs justification :) 17:02 <vulpine> <void> kostya213: they needn't be anonymous to use syndie 17:02 <cervantes> when can we use syndie or when will syndie be useable? 17:02 <jrandom> word void :) 17:03 <cervantes> for the text interface I imagine there needs to be a fairly hefty amount of usage documentation 17:03 <jrandom> cervantes: right now, syndie is functional (you can create posts, manage channels, read posts, reply to posts, etc) 17:03 <kostya213> jrandom: how does syndie handle redundancy? how resilient is it against content disappearing? 17:03 <cervantes> (before it's useable) 17:03 <jrandom> cervantes: there's inline menus with each command doc'ed (at least minimaly) 17:04 <cervantes> cool, any plans on some use case examples? 17:04 <jrandom> kostya213: syndie works at the content layer - redundancy is handled by something else. if you post to usenet, its replicated across usenet (for instance) 17:04 <cervantes> I think the trick will be learning how they all script together 17:04 <vulpine> <void> kostya213: that's out of the scope of syndie, it's dependant on the transport mechanism 17:04 <vulpine> <void> unfortunately 17:04 <jrandom> good idea cervantes 17:05 <jrandom> the first syndie release will include an http replication system like the old/existing syndie 17:05 <jrandom> cervantes: perhaps some of the beta users can put together their favorite scripts for us to distribute :) 17:05 <modulus> mmm, is this a console app? 17:05 <jrandom> modulus: yes, the first text based app 17:06 <modulus> excellent! 17:06 <cervantes> jrandom: provided the beta users can work out how to use it ;-) 17:06 <jrandom> hehe 17:06 * jrandom considered curses/etc, as well as cli-only, but an interactive scriptable text interface is probably the simplest and most useful 17:07 <jrandom> (sans gui, that is) 17:07 <cervantes> modulus: see, jrandom listened to your relentless feedback :) 17:07 <vulpine> <Complication> If people want, they can probably build more interactive textual interfaces on top of it 17:07 <jrandom> aye, certainly 17:08 <jrandom> (the code is built to support easy integration with an irc client, like pircbot) 17:08 <modulus> cervantes: hehe 17:09 <modulus> i guess you could put a gui on top of it too for that matter, if it works roughly as i imagine 17:09 <modulus> although that'd be lots more work. 17:09 * kostya213 waits for the emacs plugin 17:09 <modulus> hahaha 17:09 <jrandom> heh 17:09 <modulus> actually an emacs mode isn't such a bad idea, maybe would attract more crazies to it. 17:10 <cervantes> press ctrl-alt-shift-break-uparrow-num7-b to choose your identity 17:10 * jrandom will leave that to elipsers to hack through ;) 17:10 <kostya213> no offense, but i'm not sure this project needs to attract more crazies 17:10 <vulpine> <Complication> would those sort of crazies code, too? 17:11 <jrandom> hopefuly complication 17:11 <jrandom> ok, hopefully 3.3) explains a it of whats coming down the line 17:11 <jrandom> as for *when*, well, we'll see, but i'm hoping "soon" ;) 17:12 <jrandom> ok, anyone have anything else for 3.3)? 17:12 <vulpine> * Complication would welcome a few hordes of those crazies then :D 17:12 <cervantes> well there's coding and then there's writing obfuscated perl interpreted tcl 17:12 <kostya213> a plugin for FUSE might be useful too 17:13 <jrandom> aye 17:13 <jrandom> ok, lets jump on over to 4) crypto for syndie 17:13 <jrandom> anyone have any comments on those issues? 17:14 <vulpine> <Complication> I wish I had, but I'm not competent to estimate the strength of those ciphers/hashes/key lengths 17:15 <vulpine> <void> how long are elgamal/rsa signatures? 4kbit for a 2kbit key? 17:15 <vulpine> * Complication leaves that talk entirely for others 17:15 <jrandom> dunno offhand 17:15 <vulpine> <void> vs dsa? 17:16 <jrandom> (though ecc looks nice'n'tiny) 17:16 <modulus> ElGamal signatures are hard and long. as gnupg's team found out. 17:16 <jrandom> aye, though some of those tricks were related to key reuse 17:16 <vulpine> <void> ah, ok 17:16 <vulpine> <void> yeah, it does 17:16 <tethra> modulus: if they're hard and long, there's a fetish site for it 17:17 <jrandom> ok, that point was really just a heads up and call for comments whenever y'all have thoughts 17:17 <cervantes> could it not be possible to implement some kind of pluggable ciphers - when a better method of creating keys is standardised we can add that to syndie and new posts will begin using them, but can still use obsolete methods for older posts 17:17 <tethra> (sorry) 17:17 <jrandom> cervantes: it includes a DSA: prefix, so an Elg: prefix would work 17:17 <modulus> are you using 1024-limited dsa or not? 17:18 <modulus> also what has? sha1 or higher order revs? 17:18 <cervantes> so really you are just concerned with getting syndie off to a good start 17:18 <jrandom> dsa is only 1024bit (there are dsa2 proposals for longer, but they aren't standardized yet) 17:18 <jrandom> and yes, dsa requires sha1 17:18 <modulus> hmm, my understanding is that they were quite strong pre-standards. 17:18 <kostya213> cervantes has a good point, having syndie content in fixed ciphers offers poor forward-secrecy, you never know when an algo will go titsup 17:18 <modulus> but i don't follow the process closely enough so you are probably right 17:19 <jrandom> kostya213: but choice is bad for crypto, so we should have fixed values when we can 17:19 <jrandom> (bad because of anonymity) 17:19 <vulpine> <void> do you know why aren't more people/protocols using ecc, anyway? are they afraid of the lack of research, or just worried about compatibility? 17:19 <modulus> patents. 17:20 <jrandom> patents and fud, yet some concerns in implementation 17:20 <vulpine> <void> ah, right modulus 17:20 <modulus> btw, is there are a good reason to go dsa vs rsa-sha512 for instance? 17:20 <tethra> patents and fud and the state (oh my) 17:20 <modulus> not trying to be annoying, just considering that gpg for instance has gone this way, among others. 17:20 <jrandom> haven't reviewed that option in years modulus 17:21 <modulus> obviously dsa is a standard, which speaks for it, but the keys are small and the hashes are weak. not that i think it's likely to end up being the weakest link ;-) 17:23 <cervantes> I wouldn't propose "choice" - but new versions of syndie would package increasingly secure (mandatory) ciphers 17:23 <vulpine> <Complication> Leaving some leeway in the structures for future change, seems reasonable regardless of which current crypto proves best, I'd think 17:23 <jrandom> aye, though that implies the fallback to weaker/older versions to interoperate 17:23 <jrandom> but, ok, we'll work through it 17:24 <jrandom> ok, lets jump on over to 5) ??? 17:24 <jrandom> anyone have anything else to bring up for the meeting? 17:25 <cervantes> no being able to read the latest posts from your favourite source is a good incentive to make sure everyone stays upgraded 17:25 <jrandom> to a degree 17:26 <cervantes> no=not 17:26 <jrandom> (aye, its an incentive, but people are lazy/not interested in "upgrading software", etc) 17:27 <jrandom> s/people/some people/ 17:27 <cervantes> I guess that's their issue though 17:27 <jrandom> true that 17:27 <kostya213> the i2p implementation at least can have painless upgrading 17:28 <jrandom> certainly 17:28 <cervantes> as for ??? - apologies for the irc connectivity - the ISP should be restoring one if it's major network carriers "as soon as possible" 17:29 <jrandom> w3wt 17:29 <vulpine> <Complication> To the ??? topic, I could perhaps add that the second (more extensive) part of NTP modifications is close to working, and I hope to have it committed for testing soonish 17:29 * cervantes pinches salt 17:29 <kostya213> what's the near-term plans for router development? is the roadmap accurate? 17:29 <jrandom> wikked complication 17:29 <vulpine> <Complication> It's goal is to second-guess NTP servers basing on peer clock skews 17:29 <jrandom> kostya213: stabilization until syndie is out 17:30 <jrandom> (from my perspective) 17:30 <vulpine> <Complication> (and avoid taking potentially connectivity-damaging action) 17:31 <cervantes> grand 17:32 <jrandom> ok, anything else for the meeting? 17:34 * jrandom winds up 17:34 * jrandom *baf*s the meeting closed

I2P Status Notes for 2006-09-12

Tue, 12 Sep 2006 00:00:00 +0000

Hi y’all, here’s our cough weekly status notes

Index:

0.6.1.25 and net status
I2PSnark
Syndie (what/why/when)
Syndie crypto questions
???

1. 0.6.1.25 and net status

The other day we pushed out the 0.6.1.25 release, including the swarm of bugfixes accumulated over the past month, as well as zzz’s work on I2PSnark and Complication’s work trying to make our time synchronization code a bit more robust. Right now the network seems to be fairly stable, though IRC has been a bit rough in the last few days (due to reasons unrelated to I2P). With perhaps half of the network upgraded to the latest release, tunnel build success rates have not changed much, though overall throughput seems to have increased (likely due to an increase in the number of people using I2PSnark).

I2P Dev Meeting - August 01, 2006

Tue, 01 Aug 2006 00:00:00 +0000

Quick recap

Present: bar, cervantes, Complication, frosk, jrandom, polecat, tethra, void

Meeting Log

16:02 <jrandom> ok, might as well get this rolling 16:03 <jrandom> hi, pre-meeting notes posted up at http://dev.i2p.net/pipermail/i2p/2006-August/001304.html 16:03 <jrandom> rather than have me essentially reread that message to y'all here, lets just skip to our standard ??? section - 16:04 <jrandom> anyone have anything they want to bring up and discuss? 16:04 <@cervantes> eerm 16:04 * cervantes scurries to read the post 16:05 <+Complication> With regard to network status, all fine over here... 16:05 <+Complication> But one question (actually relaying from forum) about the NTCP transport, 16:06 <+Complication> namely, does it sound likely that activating it could cause someone CPU load issues (they were on XP)? 16:06 <@cervantes> I have to say I've actually been seeing lower CPU usage since switching over :) 16:07 <jrandom> well, you can't *deactivate* it (unless you've been reading the source code and know the magic incantation ;) 16:07 <+Complication> The person who spoke of this problem (can't easily repeat it, and no big CPU use here) mentioned that their experience of high CPU usage seemed to correlate with NTCP 16:07 <jrandom> so, i assume they mean not accepting inbound ntcp connections 16:07 <+polecat> NTCP causes my router to instantly clock the CPU, and I repeated it twice before manually having to alter the config file to get a working router again. 16:07 <jrandom> (while still using outbound ntcp connections) 16:07 <+Complication> (over here it's only a tiny bit up from usual levels, and that's likely because of pumping *way* more data) 16:08 <+Complication> ( `http://forum.i2p/viewtopic.php?t=1815` ) 16:08 <jrandom> when you establish an ntcp connection, you do a heavyweight crypto calculation (or three) 16:08 <jrandom> if you are accepting inbound ntcp connections, you may get lots of inbound attempts at once, since there are hundreds of i2p routers out there 16:09 <jrandom> polecat: that wasn't ntcp's fault, it was the fault of a bad ntp server in the ntp pool 16:09 <+polecat> Yes. So I can't handle that myself, apparantly. 16:09 <jrandom> (thanks to cervantes for tracking down that ntp server and getting the pool folks to !thwap 'em :) 16:10 <jrandom> ((and Complication for making it so we avoid those crazy bastards in the future :)) 16:10 <@cervantes> heh I think their server watchdogs only work on weekdays ;-) 16:10 <+Complication> Well, the current avoidance is pretty limited 16:10 <@cervantes> http://www.pool.ntp.org/scores/216.52.237.153 16:11 <+Complication> I hope to get something more paranoid coded eventually 16:11 <+polecat> Oh, so enabling NTCP won't clock the CPU anymore? 16:11 <jrandom> (it never did polecat, 'twas a coincidence ;) 16:12 <+Complication> "clock" in which particular sense? 16:12 <jrandom> (see cervantes' link) 16:12 * polecat clocks Complication upside the head. 16:12 <@cervantes> whatcha smoking polecat 16:12 <+Complication> :P 16:12 <+polecat> Er, I mean, stole all clock cycles. :) 16:13 <+Complication> If it jumped 30 seconds forward or backward, it could have lost many, many sessions, and resorted to all kinds of heavy, heavy crypto 16:13 <+Complication> That could steal plenty of CPU cycles, I think 16:13 <+Complication> Indeed, perhaps the person in the forum actually saw the same, and mis-correlated it? Have to ask... 16:13 <jrandom> ah.. well, bursts of valid inbound ntcp connections will cause bursts of cpu, while outbound-only ntcp will only try to talk to so many new ntcp peers at a time 16:14 <jrandom> there is nothing wrong with not enabling inbound ntcp. 16:15 <@cervantes> Complication: the server was corrected mid-monday, so it might be worth seeing if they've had issues since then 16:15 <jrandom> ok, anyone else have something they want to discuss? 16:16 <+Complication> cervantes: indeed, could be worth a try 16:16 <@cervantes> I've had reports of some folk still losing leases periodically... is that a known problem? 16:16 <+void> how much does the ntcp implementation differ from ssu? 16:17 <+polecat> How do we tell if we lose leases? 16:18 <jrandom> void: there's a slightly higher per-message andwidth overhead in ntcp (though perhaps offset by the OS's likely-more-efficient reliable transmission implementation) 16:18 <+Complication> polecat: tunnels.jsp will show no tunnels for a particular tunnel pool (e.g. "shared clients") 16:18 <jrandom> cervantes: aye, our tunnel build success rates still aren't where they need to be 16:18 <+void> polecat: the router console says so 16:18 <+Complication> And like void says, the left sidebar of the console will tell so 16:19 <+polecat> I get those "No leases" messages a lot... that's what you mean, right? 16:19 <@cervantes> yup 16:20 <+polecat> That's usually what kills my IRC connection. Thought it was normal! 16:21 * jrandom cringes 16:24 <+tethra> lol ;) 16:25 <jrandom> ok, anyone have anything else for the meeting? 16:25 <@cervantes> jrandom: have you made any progress on syndie lately or have you had your hands full with ntcp/bug fixing/ISP hunting/bicycling ? 16:27 <+tethra> any news on feedspace, or should i just go to their eepsite? 16:28 <jrandom> when the live net hit the shitter i pushed syndie to the side. but with the net moving back on track again, syndie has been reclaiming my time, and I hope to have a small cli system out shortly (with focused guis coming after that, based on user feedback) 16:28 <jrandom> (the implemented swt gui is in pretty good shape, but its probably best to start off with the cli to adjust expectations) 16:29 * jrandom hasn't heard any news on feedspace 16:29 <@cervantes> cool 16:29 <jrandom> frosk: any word? :) 16:29 <+polecat> I'm glad you're working on syndie again. The new one does sound pretty promising. Any thoughts on ACL for stuff such as deleting blogs from a node, or doing administrative account-independant tasks? 16:30 <@cervantes> <jrandom> DELETE FROM messages WHERE postedOn <NOW()-14*24*60*60; 16:31 <jrandom> local archives will likely remain essentially trusted (since if you can access the local archive db, you can change the file however you want) 16:32 <jrandom> however, for shared blogs, yeah there's a whole set of crypto structures in place for authenticating and / or authorizing posts and changes 16:33 <jrandom> (but there'll be a way for people to view 'unauthorized' posts as well, but they'll be very much off to the side) 16:33 <+polecat> I'm sure once someone floods syndicates with thousands of giant blog posts, the technique to physically delete posts will be perfected. 16:34 <+tethra> heheh 16:35 <jrandom> physical deletion is trivial, its the question of what posts to accept in the first place ;) 16:36 <jrandom> (i have no interest in making syndie into a movie distriution platform, etc) 16:36 <+polecat> One cannot be sure of what one is accepting, until a sample has been accepted. I envision something like allowing only a whitelist of blogs, and allowing new IDs on a trial basis before adding them, insta-deleting on spam betrayal. 16:36 <jrandom> aye 16:37 <+polecat> I'm more interested in its application for colluding streams of conversation together: we could make a BBS that had no central server, just a tag in common! 16:37 <jrandom> (manually allowing new ids, manually kickbanning ids that flood, etc) 16:37 <jrandom> there's even inherent support for that in the crypto polecat :) 16:37 <+polecat> Possibly a moderator signing approved messages for the BBS, and people collecting those approval lists from the moderator's blog. 16:38 <+polecat> Ooh excellent. 16:38 <@frosk> jrandom: been working on gui stuff lately, but it's been hard to combine with starting a new job :( 16:39 * cervantes contacts Human Resources to get frosk fired 16:40 <jrandom> ah cool, hopefully once syndie is out there pushing kludged http syndication we'll tempt you on it again ;) 16:40 <@frosk> at least my boss follows i2p development now :) 16:40 * jrandom waves to frosk's boss 16:40 <@frosk> oh yes, i'm still determined (damn it!) :) 16:40 <jrandom> (gives frosk more time off, we need 'im!) 16:41 <@cervantes> hopefully he won't read about how you've been posting classified company information onto your syndie blog 16:41 <bar> gui is good, we like gui. you're forgiven. 16:41 <+Complication> Hehe :) 16:41 <@frosk> it's weird to walk into his office and catch him reading syndie :) 16:41 <jrandom> hah awesome 16:42 <+polecat> Congratulations frosk, even if you get fired in shame and infamy, at least you showed one more person how cool syndie can be. 16:43 <@frosk> hehe yeah 16:43 <+tethra> haha 16:44 <@frosk> the gui (in swt) is/will be a testbed for all things feedspace, to kickstart it 16:44 <jrandom> r0x0r 16:45 <+void> jrandom: perhaps you should cross-post everything that goes onto the mailing lists to syndie as well? 16:45 <jrandom> we should totally merge it in with the syndie swt gui (basic paradigm is a browser, though not displaying html pages in the tabs) 16:46 <+polecat> That'd be nice. I can't seem to get the mailing list anymore. 16:46 <jrandom> void: it'd be pretty easy for someone to write up a small shell script to pipe procmail into the syndie CLI 16:46 <@cervantes> are these fancy swt gui's tied into the applications? or are they tops for cli executables or use tcp etc etc 16:46 <@frosk> that makes sense 16:46 <jrandom> (iirc there's a post in my blog a while back explaining how to use the syndie cli to insert posts) 16:47 <+polecat> Currently one can make RSS feeds to feed into syndie, though it's kind of cludgy still. 16:47 <jrandom> cervantes: jdbc in event handlers, inline with jni and msvc callouts, of course ;) 16:47 * jrandom ducks 16:48 <+polecat> Microsoft Visual Classes? 16:49 <@cervantes> jrandom: so anything that can talk SQL can administer syndie then 16:49 <jrandom> (from syndie's perspective, all of the functionality is basically implemented in lots of tiny cli apps which just update the jdbc database, and there's an swt ui to browse around the db) 16:51 <+polecat> And since the database has two interfaces, JDBC, and SQL, a client communicating in either protocol can screw with syndie. 16:51 <jrandom> cervantes: well, yes and no - there's a good portion of the database thats encrypted, so not all fields are readable 16:51 <+void> will the current web interface still be there? 16:51 <jrandom> (jdbc == sql) 16:51 <jrandom> void: no 16:51 <+polecat> I thought you said that JDBC wasn't a stupid human readable protocol? 16:51 <+Complication> jdbc == java database interface, perhaps a bit similar to odbc 16:51 <jrandom> ((jdbc ~= sql)) 16:51 <+Complication> Something you talk SQL over 16:52 <+void> jrandom: what will happen to syndie.i2p/syndiemedia.i2p.net? 16:52 <+polecat> Oh. Well I never liked SQL anyway, for the record. 16:52 <@cervantes> jrandom: so it's best to create a top for syndieTools (tm) than to try and leech the data yourself 16:53 <jrandom> void: time will tell. likely they'll 1) serve as syndie's website/eepsite, 2) serve as a public archive of posts to syndicate with, and eventually, when a web interface is written, 3) serve up a web interface 16:53 <+polecat> Why not submit bytecode as database queries, instead of archaic COBOL statements? 16:53 <jrandom> aye cervantes 16:53 <jrandom> !lart polecat 16:54 <+void> hehehe 16:54 <+polecat> Ah, my secret weakness. 16:54 <@cervantes> * you have 6 larts left in your inventory, there is a door to the north and an unconsious polecat on the floor 16:54 <jrandom> cervantes: thats actually cli app #3 (extracting individual posts, which comes after app #2, listing individual posts (after #1, creating individual posts, and after #0, managing nyms))) 16:54 <jrandom> lol 16:54 <+tethra> haha 16:55 <+Complication> feature proposal: instead of bytecode, why not submit live $agency agents as database queries? ;P 16:56 <+Complication> Would be far easier to validate for safety :P 16:56 <@cervantes> jrandom: gotcha 16:56 <+tethra> do they act like carrier pigeons under the right climate, Complication? 16:56 <+Complication> tethra: only if you manage to push them through the TCP stack intact :P 16:56 <+polecat> Yes, database queries over CPP! 16:57 <+Complication> I imagine that getting wrinkled in TCP might corrupt them 16:58 <+Complication> (sorry, should really keep jokes to #i2p-chat, but sometimes can't help) 16:58 * cervantes senses a baff is soon approaching 16:58 <+Complication> database queries as shellcode? 16:59 <jrandom> ok, anyone have anything else for the meeting? 16:59 <+polecat> http://www.blug.linux.no/rfc1149/ <- we could tunnel i2p over this, really. 16:59 * Complication would rather stick with SQL 17:00 <+void> jrandom: do other langauges than java have libraries for hsqldb databases? 17:01 <+Complication> Oo would seem likely to, since they seem to use it 17:01 <+void> looks like a "no" to me 17:01 <+void> oh, hmm 17:01 <@cervantes> openoffice uses it so I would guess so 17:01 <+Complication> But I'm not sure what OpenOffice is written in 17:01 <jrandom> not that i know of. but someone could run syndie against another jdbc database (mysql, oracle, etc) 17:01 <jrandom> oo uses java 17:02 <+void> what exactly does openoffice use this database for? 17:02 <+Complication> But seems to only partially use it 17:02 <jrandom> void: for pdf generation and for their access-like database app 17:02 <jrandom> (among other things) 17:02 <+Complication> Given that it recommends an external JRE 17:02 <+void> okay 17:03 <+void> it's a pain in the ass to write portable sql though 17:03 <+Complication> if one doesn't do triggers or stored procedures, shouldn't be a big pain, though 17:04 <jrandom> eh, its not that bad, and easy to externalize 17:04 <+void> especially when aiming oracle ;) 17:05 <jrandom> actually, hsqldb supports pl/sql ;) 17:06 <bar> are there any other plans for this database, such as for stats, peer profiles, netdb..? 17:06 <jrandom> no, this is syndie only 17:06 <bar> ok 17:07 <jrandom> (though when we ship the hsqldb code, we can use it in i2p 'for free') 17:07 <@cervantes> since syndie is not an I2P application, just an application that can run over I2P correct? 17:07 <jrandom> aye cervantes, there is no dependency upon i2p 17:07 <+Complication> Good to keep Syndie portable, since it might have other transports besides I2P 17:07 <bar> right 17:08 <+Complication> However, I take it wouldn't be difficult to run many hsqldb instances on the same machine 17:08 <+Complication> So if other apps would need it, it seems they could just use it 17:08 <jrandom> trivial, and 0-cost if you just use the in-jvm dataase 17:08 <+Complication> (use their own instance, preferably) 17:10 <+void> there's no jdbc driver for sqlite? 17:11 <jrandom> dunno, never used it 17:11 <+void> ah, looks like there is *something* 17:13 <jrandom> ok, anything else for the meeting? 17:13 <jrandom> if not... 17:13 * jrandom dinws up 17:13 * jrandom steps back 17:13 * jrandom winds up 17:13 * jrandom *baf*s the meeting closed

I2P Status Notes for 2006-08-01

Tue, 01 Aug 2006 00:00:00 +0000

Hi y’all, time for a brief set of notes before tonight’s meeting. I realize that you may have a variety of questions or issues to bring up, so we’ll go in a more fluid format than usual. There are just a few things I want to mention first.

Network status

It seems the network is doing pretty well, with swarms of fairly large I2PSnark transfers completing, and with quite sustantial transfer rates achieved on individual routers - I’ve seen 650KBytes/sec and 17,000 participating tunnels without any fireworks. Routers on the low end of the spectrum seem to be doing fine too, browsing eepsites(I2P Sites) and irc with 2 hop tunnels using under 1KByte/sec average.

I2P Dev Meeting - June 13, 2006

Tue, 13 Jun 2006 00:00:00 +0000

Quick recap

Present: fedo, jrandom, modulus, NickyB, user-land

Meeting Log

16:05 <jrandom> 0) hi 16:05 <jrandom> 1) Net status 16:05 <jrandom> 2) 0.6.1.21 16:05 <jrandom> 3) ??? 16:05 <jrandom> 0) hi 16:05 * jrandom waves 16:05 <jrandom> weekly status notes posted up @ http://dev.i2p.net/pipermail/i2p/2006-June/001293.html 16:06 <jrandom> while y'all dig through that, lets jump on over to 1) Net status 16:07 <jrandom> the network's behavior isn't that great at the moment - it works pretty well for some people, but for others, it doesn't work at all 16:07 <modulus> .20 works pretty well for me, where .19 didn't work at all, but i guess that's just anecdote. 16:08 <jrandom> you say anecdote, i say data point :) 16:08 <jrandom> there'll be a new release tomorrow though which should improve things a bit 16:09 <jrandom> oh, i suppose thats 2)... anyone have anything else on 1) net status they'd like to discuss first? 16:10 <jrandom> if not, lets jump to 2) 0.6.1.21 16:11 <jrandom> 0.6.1.20-7 is cvs head, and will become 0.6.1.21 sometime tomorrow 16:12 <jrandom> it should improve the ability for fast peers to handle more tunnels, which in turn should improve everyone's success rates 16:13 * jrandom currently gets ~30-60% success rates (excluding expirations) - hopefully the expirations will be cut further 16:14 <jrandom> ok, I don't have much more to add on that front- the changes are listed in the history.txt, so keep an eye out tomorrow for the release 16:14 <jrandom> (also, remember that it may take up to 12 hours to push the release out, so its probably best to either build -7 or wait until the actual announcement on the mailing list/website) 16:15 <jrandom> ok, lets shimmy on over to 3) ??? 16:15 <jrandom> anyone have anything else they want to bring up? 16:15 <user-land> are there recommendations for routers that can take the load from i2p ? 16:15 <NickyB> yes 16:15 <NickyB> about the ircproxy 16:15 <user-land> and what holds up i2p 1.0 ? :-) 16:16 <jrandom> user-land: to the first question, no (other than "patience") 16:16 <jrandom> to the second question, see the first question 16:16 <NickyB> first, sorry for my poor english. My ircProxy is set to be reachable on my lan, like all others proxy (eeproxy too) but my 6668 is reachable on the Net.... 16:17 <jrandom> NickyB: when you say on your lan, what is the *interface* it is bound to (on `http://localhost:7657/i2ptunnel/index.jsp)` 16:18 <jrandom> NickyB: if the interface is "0.0.0.0", yes, it will accept connections from anywhere. if its "127.0.0.1" it will only accept connections from the localhost. if its "10.0.0.123" or "192.168.1.42", then it will accept connections from your LAN 16:19 <NickyB> err, for my console, i did a change in client.config 16:19 <NickyB> clientApp.0.args=7657 192.168.0.1 ./webapps/ 16:19 <NickyB> 192.168.0.1 is the adresse gived to all my proxy 16:19 <NickyB> Reachable by: 16:20 <NickyB> LAN Hosts 16:20 <NickyB> 192.168.0.1 16:20 <NickyB> and my 4444 is not reachable on the net, but my 6668 yes 16:20 <jrandom> NickyB: you need to stop and start that particular i2ptunnel proxy for the changes to take effect 16:21 <jrandom> though, perhaps we can continue debugging after the meeting (as this is all logged ;) 16:21 <NickyB> will try, thank you 16:21 <jrandom> np, thanks for your patience 16:21 <jrandom> ok, anyone have anything else for the meeting? 16:21 <fedo> why the .21 will not be a *mandatory* release ? i ask that because we have a lot of .12 .13 etc. routeurs. This may not help for the network health ... 16:23 <jrandom> the old routers don't hurt much, and there arent too many of them (something like 2-300 stay within 1 release of current) 16:23 <user-land> my hardware router crashed under i2p load. that is why i asked for hardware recommendations. 16:24 <jrandom> ah, sorry, misundertood your question user-land. i've been able to get by with cheap linksys and belkins, though i dont know what switches they have at the current colo 16:24 <user-land> thanks. 16:25 <jrandom> fedo: the real key of ...21 is that 1) fast routers upgrade (and they're the most likely to anyway) and 2) that users be on ...19 or higher 16:26 <fedo> ok Jr 16:26 <jrandom> ok, anyone have anything else for the meeting? 16:28 <user-land> thanks for your efforts :-) 16:28 * ashter2 seconds user-land 16:28 <user-land> and http://www.savetheinternet.com/ 16:29 <jrandom> (bah, never trust politics to defend us. use technology) 16:29 <jrandom> ok, if there's nothin' else... 16:30 * jrandom winds up 16:30 * jrandom *baf*s the meeting closed

I2P Status Notes for 2006-06-13

Tue, 13 Jun 2006 00:00:00 +0000

Hi gang, ’tis tuesday again,

Index

Net status
0.6.1.21
???

1. Net status

These days, things aren’t doing so great on the net, and unfortunately, there aren’t local tweaks you can do to improve it. Your patience is appreciated.

1. 0.6.1.21

Over the last few releases, we’ve been trimming down variables in the network’s behavior, and in the next day or so we should have a new 0.6.1.21 release to build upon the experiences we’ve found with 0.6.1.20. Among other things, tomorrow’s release should reduce the number of unnecessary tunnel rejections (though to a state thats a bit too free-wheeling), and as that is deployed, we’ll hopefully see some improvement. If not, we’ve still got one more subsystem to shred to get us back into good form, but I’d like to avoid that battle, if at all possible.

I2P Dev Meeting - May 30, 2006

Tue, 30 May 2006 00:00:00 +0000

Quick recap

Present: bar, cervantes, frosk, green, jrandom, tethrar

Meeting Log

16:00 <jrandom> 0) hi 16:00 <jrandom> 1) Net status 16:00 <jrandom> 2) Peer filtering 16:00 <jrandom> 3) Syndie status 16:00 <jrandom> 4) ??? 16:00 <jrandom> 0) hi 16:00 * jrandom waves 16:01 <jrandom> weekly status notes posted up @ http://dev.i2p.net/pipermail/i2p/2006-May/001291.html 16:01 <jrandom> (up an hour early, even [or a few weeks late, if you want to pick on me ;]) 16:02 <jrandom> ok, lets jump on in to 1) Net status 16:02 <jrandom> things arent in the shape they should be in. they're better than they were during the congestion collapse, but it should be better than it is now 16:03 <jrandom> i don't have much more to add on that though, unless anyone has any questions/concerns on 1)? 16:03 <@frosk> i get days of irc connection with .19, so no complaints here 16:04 <jrandom> nice 16:04 <jrandom> yeah, its good for some, just not good enough or consistent enough. stats in the db aren't looking that great either 16:06 <jrandom> ok, anyone have anything else on 1) Net status, or shall we move on over to 2)Peer filtering? 16:07 <jrandom> [insert moving sounds here] 16:09 <jrandom> as mentioned in the mail, the gist of things is to give our peer selection a bit of a boost. at first, it'll be a bit dangerous, allowing some active partitioning attacks, but if it works as I hope, we can avoid those 16:10 <jrandom> (but avoiding it requires essentially killing all router identities, which would essentially serve as a network reset, so i'd like to avoid that unless its worthwhile) 16:11 <bar> reset them once or repeatedly? 16:11 <bar> s/reset/killing 16:11 <jrandom> at least once, but also on all subsequent drastic config changes 16:12 <jrandom> (aka putting some criteria into the router identity's certificate, which in turn means changing the ident hash, so they can't pretend to push one setting to some people and others to others) 16:13 <bar> gotcha 16:14 <jrandom> ok, i dont think i have anything else on that topic atm, unless anyone has any questions/comments/concerns? 16:15 <jrandom> (hopefully there'll be a build out in the next day or two, release after it stabilizes) 16:17 <jrandom> ok, hitting 3) briefly.. 16:18 <jrandom> syndie is coming along, and although the amd64/amd32/x86/swt/gcj battle hasn't always been pretty, we'll have a build ready in june 16:19 <jrandom> (but still don't talk to me about mingw/gcj ;) 16:19 <jrandom> i don't have much more to add on there at the moment though, unless anyone has any questions/concerns re: the syndie revamp? 16:21 <@cervantes> how's mingw/gcj support coming along? 16:21 <@cervantes> *duck* 16:22 <@cervantes> do we get some screenies before the june release? :) 16:23 <jrandom> i'm sure i'll try to rope some eager volunteers into pre-release testing ;) 16:23 <tethrar> count me in ;) 16:23 <jrandom> w3wt 16:24 <jrandom> ok, lets swing over to the bullet point i know y'all have been waiting for: 4) ??? 16:24 <jrandom> wazaaaap? 16:24 <green> Is there any plan to have to have a "real" working I2P router with Via C7 ? jbigi give only 30% better than full java 16:25 <jrandom> is 30% still too cpu intensive? what makes it not "real"? 16:25 <jrandom> but no, i do not have the math or c7 asm skill to make a better libGMP for C7. 16:25 <green> sure too cpu intensive with 100% cpu load :P 16:26 <jrandom> 100% cpu load suggests that the problem isn't jbigi, but the fact that jbigi needs to be used too much 16:26 <jrandom> and for that, yes, there is lots we've got on the way. 16:26 <jrandom> (e.g. reducing the connection reestablishments, improving tunnel build success rates, etc) 16:27 <jrandom> ((and not getting as many tunnel requests if the router is not capable of handling them)) 16:29 <green> humm, this is with a dedicated box with 100Mb/s so It should be capable 16:30 <jrandom> no, bandwidth is not the only resource constrained here, cpu obviously is ;) 16:33 <jrandom> ok, anyone have anything else for the meeting? 16:36 <jrandom> *cough* 16:37 * jrandom winds up 16:37 * jrandom *baf*s the meeting closed

I2P Status Notes for 2006-05-30

Tue, 30 May 2006 00:00:00 +0000

Hi y’all, after a brief intermission, its time for our weekly status notes again (unsigned for system maintenance reasons)

Index

Net status
Peer filtering
Syndie status
???

1. Net status

Unfortunately, there isn’t anything new to report regarding the network’s status. The seas are still pretty rough out there, and as far as I can see, there’s no tweak or tunable parameter you can use to safely improve it locally. We’ll put out more information and releases to do so when its available, but in the meantime, your patience is appreciated.

I2P Dev Meeting - May 16, 2006

Tue, 16 May 2006 00:00:00 +0000

Quick recap

Present: bar, cervantes, Complication, Pi

Meeting Log

<cervantes> moo: http://dev.i2p.net/pipermail/i2p/2006-May/001289.html <cervantes> 0) hi <cervantes> 1) jrandom's not here <cervantes> 2) ??? <cervantes> 0) hi <cervantes> hi <cervantes> moving on to 1) <cervantes> jrandom isn't here today, but he'll give us a status update tomorrow <cervantes> 2) ??? <cervantes> does anyone have anything else to add to the meeting? <bar> i have a question <cervantes> in that case... * cervantes winds up * cervantes stops winding <Complication> Aha, a question... <bar> the PRNG fix in cvs, will that improve the general performace or is it related to something else? <cervantes> it's uncertain what consequences it might have in general <Complication> I'm personally not aware of its total impact, but it does involve at least two behaviours I'm aware of: <cervantes> but it specifically fixes a symptom with i2ptunnel * cervantes lets complication decomplicate <Complication> tunnel length randomization and IRC server choice (more generically, random selection from a list of I2PTunnel destinations) <Complication> Tunnel length randomization probably has a significant effect on overall network health, since it allows clients who are permitted to compromise on tunnel length to actually do that <Complication> So they won't be holding breath and building 2-hop tunnels, but also try some 1-hop tunnels <Complication> (which on hard times, are much easier to get) <cervantes> also irc connectivity might improve once it's rolled out. Basically freshcoffee was never getting any client connections because it was second in the list - so with the next release the load should be evenly distributed between both servers <bar> so the bug made people always go for the longer tunnel lengths if available? <Complication> If I understood right, every randomization with smallish integers (e.g. pick 0 or 1) was affected <Complication> I *think* randomizations with bigger integers (e.g. pick an integer between 0 and 100) were less affected <Complication> if you're interested, you should probably ask jranom for details when he's back <Complication> I may get the details wrong. <bar> i see, thanks. good catch <Complication> well, cervantes came here and started complaining about not getting any overload ;P <cervantes> that was my understanding of it too <cervantes> see...you don't get anything in life if you don't grumble :) <cervantes> do any folk have other questions or topics for the meeting? <fox> <duck> yes <Pi> a question about general net health : i see more and more clients get left behind i2p-version wise (2 still using 0.6.1.11 and so on). won't these clients make monitoring effects of changes to the core more and more harder? (as "fewer" seem to want to update) <fox> * duck repeats above * w423412323 suggests a topic change along that line. ;) <fox> <duck> I was wondering, I have seen some funky tuning commits on the cvs mailinglist. are those more experiments? are they based on observations? are they premature? <Complication> Pi: as long as they aren't present in big numbers, they shouldn't make a big difference <Pi> 70 of 300 clients using non-0.6.1.18-version according to my netdb now <Complication> It's a game of numbers and capacity - if either most routers, or additionally the highest-capacity routers are reasonably updated, some people forgetting that they installed I2P shouldn't matter :) <cervantes> Pi: if the older routers misbehave then the network _should_ adapt and reduce traffice being router via them <cervantes> *being routed <cervantes> Complication: did you see duck's question? <Pi> and a question about a stat on the i2p-console which appeared some time ago : what does handle backlog mean? <Complication> duck: would you mean the tunnel throttle adjustments? They're tuning in the sense that they won't bring much inherently new, but they should be fairly well-tested now (e.g. they probably won't byte) <Complication> But they might byte a little, if you run an exotic setup which is completely outside the parameters I could think of <fox> <duck> Complication: I was wondering if '2' instead of '3' thingies really mattered that much <fox> <duck> but it seemed that the random problem might have been a big baddy <fox> <duck> (though the relative impact of that towards network unhealth depends on when it was introduced) <cervantes> Pi: handle backlog is the number of pending inbound tunnel join requests (quoted from the changelog) <Complication> If you mean the random nextInteger() problem, and effect on tunnel length randomization, I feel it would have significant effect <Complication> The cost difference of building a 1-hop and 2-hop tunnel is pretty significant <Pi> thx, cervantes :) <fox> <duck> when was it introduced? <Complication> duck: I think it was introduced with some switchovers to the Fortuna generator, or some modification therein <fox> <duck> ok; thanks a lot for your input <Complication> Let me check the cvsweb for more detail... <cervantes> Pi: I believe there's code in place now that drops inbound tunnel requests if the queue fills up (to help reduce cpu load) <Complication> Pi: yes, that should be the visible indicator of another parameter used for deciding "do we have enough capacity to participate in another tunnel?" <cervantes> duck: I certainly experience a large change in router behaviour since the fix was introduced. - not all good I have to say :) <Complication> big handle backlog == congestion, no point in trying to join other people's tunnels <cervantes> had a load average of 14 and 12000 participating tunnels the other day <Complication> Handle backlog seems important particularly on high-capacity routers (referring to what cervantes saw) <Complication> Low capacity routers generally throttle their tunnel acceptance for bandwidth reasons <Complication> (or tunnel test time reasons, to be correct) <Complication> (or at least, to try that) <cervantes> wow we've managed half an hour.... <Complication> Indeed :D <cervantes> anyone want to bring anything else to the table? <cervantes> in that case... * cervantes winds up * cervantes *baffs* the meeting closed <fox> <duck> thx for taking care of the meeting <cervantes> heh I was expecting to baf it closed before anything said anything....but bar ruined that plan :)

I2P Status Notes for 2006-05-16

Tue, 16 May 2006 00:00:00 +0000

Hey y’all, quick meta-notes today. I’ve got to bolt for the evening and won’t be back in time for the meeting, but will write up a set of status notes tomorrow (with the meeting next week, of course). Complication has been churning away with some neat mods in cvs, and there is some promising stuff coming up, so hopefully we’ll have a release later this week. Not sure though.

In any case, if y’all meet up tonight, please keep logs of the meeting and commit ’em to the i2pwww cvs module and I’ll post those to the site tomorrow.

I2P Dev Meeting - May 09, 2006

Tue, 09 May 2006 00:00:00 +0000

Quick recap

Present: arse, cervantes, Complication, i, jrandom, roderick_spod1, tmp

Meeting Log

16:31 <jrandom> 0) hi 16:31 <jrandom> 1) Net status and 0.6.1.18 16:31 <jrandom> 2) baz 16:31 <jrandom> 3) ??? 16:31 <jrandom> 0) hi 16:31 * jrandom waves 16:32 <jrandom> weekly status notes posted up at http://dev.i2p.net/pipermail/i2p/2006-May/001288.html 16:32 <jrandom> while y'all read through that, lets jump on in to 1) Net status and 0.6.1.18 16:33 <jrandom> the past week has been pretty bumpy on irc & the net in general 16:33 <+Complication> Watching the graphs, but haven't noticed a perceivable change yet 16:33 <+Complication> Only the beginning too, of course 16:34 <jrandom> aye, its only been a few hours, with under 20% of the net upgraded 16:35 <jrandom> there are still a few big guns left to deploy on the net, but I'd like things to stabilize first before pushing out major changes 16:35 <+Complication> Indeed, it helps to see (as much as seeing is possible) what changes what, and in which direction 16:36 <+Complication> If one deploys everything at once, figuring out what worked may be very tough 16:38 <tmp> *sigh* 16:38 * tmp dreams of IRC stability. 16:39 <jrandom> aye, on all fronts ;) 16:39 <+fox> <roderick_spod1> Roderick dreams of big tits. 16:39 <jrandom> (this is why we can filter the meeting logs... ;) 16:40 <jrandom> ok, anyone have anything else for 1) Net status and 0.6.1.18? 16:41 <jrandom> if not, lets hop on over to 2) 16:42 <jrandom> not much more to add here, just giving a status update on some w32/w64 support 16:43 <jrandom> as mentioned in the mail, gcj doesn't really seem viable on mingw atm, though we might be able to pull some tricks 16:44 <jrandom> there is an older 3.4.4/3.4.5 gcj that works on mingw, but the classpath suport in there is pretty old. 16:45 <jrandom> (and even after stripping a bunch out of hsqldb, there are still some dependencies that 3.4.5 doesn't meet. but maybe we can hack those out too... if necessary) 16:47 <jrandom> ok, if there's nothing else, lets move on over to 3) ??? 16:47 <jrandom> anyone have anything else to bring up for the meeting? 16:48 <cervantes> just to say "nice one bar" for his cool donation 16:48 <+Complication> Well, there was a question in the forum about uptimes presented in NetDB... 16:48 * Complication seconds that 16:49 <+Complication> 'bout the uptimes, if you recall, I fuzzified them slightly in March... 16:49 <cervantes> must have missed that amongst the odci.gov rants 16:50 <tmp> What on earth are you doing on that side roderick_spod? 16:50 <jrandom> aye Complication 16:50 <+Complication> Well, since the question was raised, I wondered if they could be fuzzified further, or would it hurt ability to debug? 16:52 <jrandom> i'm not sure of the point - with careful analysis, all of the stat data can reveal a bunch of information 16:52 <arse> do you guys think the network periodicity is gonna subside 16:52 <jrandom> when its time, we will just turn off the stat publhshing whatsoever 16:52 <+Complication> We haven't recently had any router-restarting ones, but that's only recently... 16:52 <jrandom> arse: yes 16:52 <+Complication> (and partly because the watchdog lacks teeth) 16:54 <+Complication> True, it's pretty inevitable that during this phase, some info must be out there 16:55 <jrandom> also, the assumption they've made isn't correct, publishedTimeAgo is how long ago the router /received/ the netDb entry, not when it was signed 16:55 <jrandom> erm, wait, no, thats not true 16:56 <jrandom> never mind me. yeah, it just adds a small variation 16:56 <+Complication> Heh, I'm trying to post a reply, but get "no post mode specified" currently 16:57 <+Complication> Yeah, there's delay involved, and besides, how often was this info published? Not very frequently, IIRC? 16:57 <+Complication> Basically, if I offered to somewhat decrease the precision there, would you mind? 16:58 <jrandom> a new signed entry is published eery 5-15 minutes, but that is only published to the netDb, not all peers 16:58 <jrandom> peers only get the updated one when they either search for it or they reconnect 16:59 <jrandom> but yeah, adding more variation is fine. it'd affect stat.i2p's uptime plots, but as long as it keeps things reasonable, thats cool 17:01 <+Complication> I'll try to keep it reasonable, then :) 17:01 <jrandom> heh cool, thanks Complication 17:04 <jrandom> *cough* (and consistent ;) ok, anyone have anything else for the meeting? 17:04 <+Complication> sidenote: neat, the "post mode" bug yielded to persistence, and I could post a reply too :) 17:05 <jrandom> w3rd Complication offtopic messages snipped 17:08 <jrandom> ok, if there's nothing else... 17:08 * jrandom winds up 17:09 * jrandom *baf*s the meeting closed

I2P Status Notes for 2006-05-09

Tue, 09 May 2006 00:00:00 +0000

Hi y’all, tuesday rolls ‘round once again

Index

Net status and 0.6.1.18
baz
???

1. Net status and 0.6.1.18

After another week of testing and tweaking, we pushed out a new release earlier this afternoon which should get us into a more stable environment to make improvements from. We probably won’t see much effect until it gets widely deployed though, so we may have to wait a few days to see how it goes, but measurements will of course continue.

I2P Dev Meeting - May 02, 2006

Tue, 02 May 2006 00:00:00 +0000

Quick recap

Present: green, jrandom

Meeting Log

16:09 <jrandom> 0) hi 16:09 <jrandom> 1) Net status 16:09 <jrandom> 2) Syndie status 16:09 <jrandom> 3) ??? 16:09 <jrandom> 0) hi 16:09 * jrandom waves 16:10 <jrandom> weekly status notes posted up at http://dev.i2p.net/pipermail/i2p/2006-May/001285.html 16:11 <jrandom> ok, while y'all read through that exciting mail, lets jump on in to 1) Net status 16:13 <jrandom> so far, it seems the whole congestion collapse issue is fixed, yand tunnel creation rates are doing pretty well. still, there are issues left to be sorted out 16:14 <jrandom> the previously discussed cyclic behavior (often running on 10-12 minute intervals) is still in place,causing rejections inversely. there's a new fix to the code as of -1 that should get rid of that though 16:15 <jrandom> (namely, randomize the tunnel expirations /correctly/, unlike the broken randomization before) 16:16 <jrandom> that, plus the improved ssu and tunnel test scheduling should help, but to what dgree, i'm not entirely sure yet 16:17 <jrandom> ok, thats about all i have on that at the moment. anyone have any questions/comments/concerns on 1) Net status? 16:18 <green> humm, max bw limits are never reached and this is really far from previous 16:18 <green> like in 1-7 16:18 <green> s/1-7/.12-7 16:18 <jrandom> how is your bw share percentage set? thats now a very powerful control 16:19 <green> 80% 16:19 <green> but only about 40% of total bw is used 16:20 <green> this is just a "do nothing router" :P 16:20 <jrandom> hmm, how often does your bw spike up to 80%, and do you often reject tunnel requests (`http://localhost:7657/oldstats.jsp#tunnel.reject.30` and tunnel.reject.*) 16:21 <jrandom> the periodicity seen in tunnel requests often causes people to detect overload when it isn't really there 16:21 <jrandom> (because routers have excess capacity at other times, just not when they're being spiked) 16:22 <green> tunnel.reject.30 is very flat like 1,00 over 14 025,00 events 16:22 <jrandom> oh, sorry, its the event count theselves for that stat thats key - you've rejected more than 14,000 tunnel requests due to bandwidth overload 16:23 <jrandom> (the "value" for that stat is how many tunnels were rejected at the event, and thats always 1, since an event is caused by a message) 16:27 <jrandom> ok, if there's nothing else on 1) Net status, lets slide on over to 2) Syndie status 16:27 <jrandom> I don't have much more to add to whats in the email regarding syndie, just wanted to give an update 16:28 <jrandom> ok, as such, unless there's something someone wants to bring up wrt syndie, lets jump on to ol' faithful, 3) ??? 16:28 <jrandom> anyone have anything else they want to bring up for the meeting? 16:31 * tethra would like to say "thanks" (again) for .17, as it has been muchos improvement 16:33 <jrandom> glad to help, and there's more stuff on the way 16:33 <jrandom> ok, but if there's nothing else for toay's meeting... 16:33 * jrandom winds up 16:33 * jrandom *baf*s the meeting closed

I2P Status Notes for 2006-05-02

Tue, 02 May 2006 00:00:00 +0000

Hi y’all, tuesday rolls ‘round one more time

Index

Net status
Syndie status
???

1. Net status

With another week on 0.6.1.17 under our belt, several of the prime measurements of network health are staying in good shape. We are however seeing some of the remaining problems propogate up to the application layer, namely the recent rise in reconnections on the irc2p servers. Postman, cervantes, Complication, and myself have been digging through various aspects of the network’s behavior as it relates to the user-visible performance, and we’ve tracked down and implemented a few improvements (current CVS HEAD is 0.6.1.17-4). We’re still monitoring its behavior and experimenting with some tweaks before pushing it out as 0.6.1.18 though, but thats probably only a few days away.

I2P Status Notes for 2006-04-25

Tue, 25 Apr 2006 00:00:00 +0000

Hi gang, ’tis time for our pre-wednesday meeting

Index

Net status and 0.6.1.17
I2Phex
???

1. Net status and 0.6.1.17

After a few days of monitoring some patches, we pushed out a new 0.6.1.17 release, and so far, the improvement has been substantial. Tunnel build success rates have increased by one to two orders of magnitude, and throttled peers are now able to operate with reasonable bandwidth constraints again. A good 60%+ of the network has upgraded so far (thanks!), though getting the rest up to speed would be useful.

I2P Status Notes for 2006-04-18

Tue, 18 Apr 2006 00:00:00 +0000

Hi y’all, tuesday rolls around again for our weekly status notes

Index

Net status and 0.6.1.16
Tunnel creation and congestion
Feedspace
???

1. Net status and 0.6.1.16

With 70% of the network upgraded to 0.6.1.16, we seem to be seeing an improvement over earlier releases, and with the issues fixed in that release out of the way, we’ve got a clearer view of our next bottleneck. For those not yet on 0.6.1.16, please upgrade as soon as possible, since earlier releases will reject tunnel creation requests arbitrarily (even if the router has sufficient resources to participate in more tunnels).

I2P Dev Meeting - April 04, 2006

Tue, 04 Apr 2006 00:00:00 +0000

Quick recap

Present: BrianR\___, cervantes, Complication, frosk, jrandom, tethra

Meeting Log

16:21 <jrandom> 0) hi 16:21 <jrandom> 1) Net status and 0.6.1.14 16:21 <jrandom> 2) Syndie plotting 16:21 <jrandom> 3) Local jbigi optimizations 16:21 <jrandom> 4) ??? 16:21 <jrandom> 0) hi 16:21 * jrandom waves 16:21 <jrandom> weekly status notes posted up at http://dev.i2p.net/pipermail/i2p/2006-April/001275.html 16:21 * Complication reads 16:22 <jrandom> while y'all read that (briefly put together) post, lets jump on in to 1) Net status 16:23 <@cervantes> (forum back) 16:23 <jrandom> there are a few problems out there affecting use on 0.6.1.13, and most of tem have been tracked down and solved 16:24 <Complication> Over here, with the "fourth" CVS build, I noticed a change in my graphs 16:24 <jrandom> here are still a few kinks getting tested and revamped though, but a release should be out in the next few days 16:24 <Complication> In general, things moved towards more stability and less jumpyness 16:24 <jrandom> oh bugger, I forgot to increment it to -4 didn't I? 16:24 <jrandom> (ok, -5 will be out later this evening) 16:24 <jrandom> cool Complication 16:25 <Complication> But my perceptions could be influenced by jbigi too, as I didn't take steps to exclude that 16:25 <Complication> Now, after a while, retransmission has edged down to 15% too 16:28 <jrandom> hmm, i'm also seeing my average ssu rto approach the 3s ceiling as well 16:28 <jrandom> (though very low retransmission still, under 5%) 16:29 * Complication takes a second look at it 16:29 <Complication> Let's say the raw average is a little over 1500 16:29 <Complication> (over here) 16:30 <+fox> <BrianR___> jrandom: Is there a de-facto "MTU" for i2p packets? 16:30 <jrandom> ah ok, perhapsas that inches up, the retransmission rate will go down 16:30 <Complication> I noticed mine start out with smaller MTUs, now it's upped some to 1350 16:30 <jrandom> BrianR___: yes, either 1350 or 608 (as shown on `http://localhost:7657/peers.js)` 16:31 <jrandom> if the failure rate is too high at the larger MTU, it falls back to the smaller MTU (and if its too low at the smaller MTU, it jumps up to the higher MTU) 16:31 <+fox> <BrianR___> jrandom: Now is that for the inside payload or the visible IP packets? 16:31 <+fox> <BrianR___> Ie, if I were to send a block of data over an I2P stream, what would be the ideal size for the chunks to minimize overhead? 16:31 <jrandom> that is for the UDP payload 16:32 <jrandom> streams are two layers up 16:32 <jrandom> (there's fragmentation for tunnels, and then fragmentation at the stream/i2cp level) 16:32 <+fox> <BrianR___> Yes... Is there an ideal size to minimize fragmentation? 16:32 <jrandom> the ideal block size of an app using the streaming lib is "large", so that the streaming lib can use the appropriate size. 16:33 <jrandom> (aka ignore the man behind the curtain) 16:33 <+fox> <BrianR___> Aah.. Maybe I should think about pipelining or something then.. 16:34 <+fox> <BrianR___> I'm planning an app with lots of request/response traffic... 16:34 <jrandom> i'd recommend batching then to cut down on the chattyness 16:34 <Complication> Perhaps keeping traffic focused would help to some extent 16:37 <jrandom> ok, anyhing else on 1) Net status, or shall e shimmy on over to 2) Syndie plotting 16:38 * jrandom shimmies 16:39 <jrandom> this is largely a placeholder and cfp - there's going to be some substantial revamp to syndie, both in operaion and the ui, so if you've got some key features or use cases you think need to be addressed, get in touch 16:40 <jrandom> (more info will be of course forthcoming as things get fleshed out further) 16:42 <jrandom> thats all i've got to say on that for the moment, so, moving on over to 3) jbigi optimizations 16:42 <@frosk> and i had assumed "plotting" referred to some jrobin stuff in syndie :) 16:43 <jrandom> hehe 16:43 <jrandom> it'd be interesting to plot posts/day, posts/author, new authors/day, etc ;) 16:44 <Complication> Oh, on bit about Syndie (sorry, only now remembered) 16:44 <Complication> =one bit 16:44 <@frosk> which do you want, 0 or 1? :) 16:44 <Complication> Do you think it could be practical, or easy/difficult to separate favourite authors and blacklisted (spam)authors into two different lists? 16:45 <Complication> On addresses.jsp 16:45 <jrandom> oh, yeah without much trouble 16:46 <jrandom> thats a good idea for therevamp too, but perhaps we can get that into the 0.6.1.14 build 16:47 <Complication> Nah, it's not byting me, I just remembered something I noticed back then 16:47 <Complication> Anyway, jbigi gets faster on Linux/AMD64 when you compile locally and use GMP 4.2 16:48 <jrandom> cool 16:48 <jrandom> did you compare that w/ -O3 -m64 on GMP 4.1.2? 16:48 <Complication> And I'm a damn fool for going after way wrong compile flags :O 16:48 <@cervantes> the relevant link was `http://forum.i2p/viewtopic.php?t=1523&start=30` btw 16:48 <jrandom> ah thanks cervantes 16:48 <Complication> jrandom: I haven't compared yet, but will 16:49 <Complication> During next scheduled reboot 16:50 <jrandom> the jbigi build process is essentially "build GMP, then build jbigi.o, and link the two together", so any sort of optimizations people want to make on GMP can be made as the first step 16:50 <@cervantes> I've not seen much difference between -O3 and -O2 in any previous tests I've done, whether that's different under x86_64 ... *shrug* 16:50 <jrandom> aye, might be compiler rev dependent as well 16:50 <jrandom> (especially with all these 3.3/3.4/4.0/4.1 issues) 16:51 <@cervantes> just to re-iterate what I mentioned in that thread... we probably won't see windows64 optimised jbigi anytime soon 16:51 <+fox> <BrianR___> Does the i2p stream lib do payload compression? 16:52 <Complication> BrianR: yes 16:52 <@cervantes> unless someone has M$ VC 2005 w/64-bit SDK and fancies some heavy toil to get it to compile gmp 16:52 <Complication> At least to my knowledge 16:53 <@cervantes> (there was a project to port gmp into a vc project somewhere though) 16:53 <jrandom> cervantes: well, we've got one that /works/ for amd64/win, but it doesn't use the most out of the hardware ;) 16:53 <jrandom> (when my new box gets here though i may be able to tweak that, as its an amd64) 16:53 <+fox> <BrianR___> trying to figure if I should use a binary protocol to save bits or if zlib or something is going to smoosh up ascii protocol nice and small.. 16:54 <@cervantes> coolio - unfortunately Mingw64 or cygwin64 doesn't seem to be on the near horizon... 16:54 <jrandom> BrianR___: premature optimization being the root of all evil, and all that jazz... 16:55 <Complication> at least partly human readable protocols are generally easier to debug, but I guess it depends what one's doing 16:56 <Complication> ('cause some things like encryption don't like being human-readable, no matter what :) ) 16:57 <Complication> But if I2P does the encryption, and also compresses, good chances are that many things which occur on top of it, can be done with human-readable protos 16:58 <jrandom> aye 16:58 <jrandom> ok, anything else on 3) jbigi stuff? 16:58 <jrandom> if not, lets move to 4) ??? 16:59 <jrandom> anyone have anything else for the meeting? 17:01 <+tethra> i recall hearing something about anonymous collaboration tools recently 17:01 <+tethra> care to elaborate on what kind, and whether they'll be syndie-esque or not? 17:02 <@cervantes> irc and syndie is an anonymous collaboration tool :) 17:02 <jrandom> hmm, not sure of what you refer to - or maybe you mean the actual planned syndie revamps? :) 17:02 <+tethra> true. 17:02 * tethra isn't sure either, which is why he asked 17:02 <+tethra> there was talk of it on the forums - reasons for anonymity and stuff 17:03 <+tethra> i'll find the thread so i can get the quote 17:03 <jrandom> ah right 17:03 <+tethra> http://forum.i2p.net/viewtopic.php?t=1618 17:03 <jrandom> the use case thread 17:03 <+tethra> - anonymously hosted & publicly reachable forums/boards/wikis 17:03 <+tethra> yeah 17:04 <+tethra> is there going to be an i2wiki type project that is based around something like syndie or is it up to users? 17:04 <jrandom> there have been some good ideas in there, and some good feedback 17:05 <jrandom> the ability to edit syndie posts is an oft-requested feature, and with that, you could pull off a wiki w/ a rich editor 17:05 <jrandom> but, of course, nothing will exist in a vaccum - if someone believes that is necessary, someone should say "hey, a wiki is essential, and here's why" 17:06 <jrandom> there are an infinite number of apps that /can/ be built, but as we're aiming for strong anonymity and strong security, care must be taken in what is built 17:07 <+tethra> right 17:07 <+tethra> that said, some of the more difficult things to keep anonymous and secure might be better off being done by someone who is good at keeping things anonymous and secure, right? 17:08 <jrandom> likely so, though there is no cabal - anyone can learn 17:08 <+tethra> (key things, basically. not that i'm naming any, but hey.) 17:08 <+tethra> true 17:09 <+tethra> but learning at the cost of your own and other people's anonymity isn't the greatest way of doing it 17:10 <jrandom> everyone has to start somewhere, of course 17:10 <+tethra> (perhaps if someone made a sandbox type thing that allowed people to run $software and have people attack it and stuff that'd be good for someone who is new/inexperienced?) 17:10 <+tethra> yeah 17:14 <jrandom> ok, anyone else have anything for the meeting? 17:15 <jrandom> if not 17:15 * jrandom winds up 17:15 <@cervantes> *ahem* 17:15 * jrandom pauses 17:16 <jrandom> whats shakin' cerv? 17:16 <Complication> Neat, I found a baf ;P 17:17 <jrandom> baf-blocked ;) 17:17 <@cervantes> hups srry, continue baffing 17:17 * jrandom resumes winding 17:18 * jrandom *baf*s the meeting closed