Development discussions
0.9.38 Release Summary « Release Summaries « I2P Development
Thu, 04 Oct 2018, 11:40am #1

Long cycle due to holidays, CCC, and my schedule

Target release: Mid-late January 2019
Roadmap: http://i2p-projekt.i2p/en/get-involved/roadmap


open tickets with this milestone: http://trac.i2p2.i2p/query?status=!closed&m...


0.9.38 includes a new first-install wizard with a bandwidth tester. We've added support for the latest GeoIP database format. There's a new Firefox profile installer and a new, native Mac OSX installer on our website. Work continues on supporting the new "LS2" netdb format.

This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.


Big changes in by: early Dec.
Feature freeze: mid Dec.
IRC meeting to review requests for console home page changes: Dec. 4
Tag freeze: Wed. Jan. 9
Checkin deadline: Fri. Jan. 18
Review deadline: Sun. Jan. 20
Release: week of Jan. 21
Android/F-Droid/Maven: late Jan.



- New setup wizard with bandwidth testing
- New beta OSX installer
- New Firefox profile installer
- Preliminary floodfill support for LS2
- Sybil tool background analysis
- Add support for Maxmind GeoLite2 GeoIP format
- Switch JSON lib to json-simple, add Debian dependency

Bug Fixes

- Fix NPE in GeoIP
- Fix RouterInfo publishing for IPv6-only routers
- I2CP error propagation fixes
- Fix rare NetDb deadlock
- Fix several bugs with susimail attachments
- AppArmor fixes


- Refactoring to support LS2
- Preliminary LS2 support in I2CP
- ShellCommand and UrlLauncher refactoring for security
- Split /peers page into tabs
- New background for light theme
- Translation updates
- Update GeoIP data (new installs and PPA only)

Full list of fixed bugs: http://trac.i2p2.i2p/query?resolution=fixed&amp...

Last edited: Fri, 18 Jan 2019, 01:11pm by zzz

Wed, 14 Nov 2018, 08:27pm #2

Dear .i2p dev

Can you change the counter hardware agency ( resolution ) to 1024*786 (as same as The

onion router Brower)

some clean net (likes YouTube nerd stats ) or (( Whois )) can use resolution detect the

user special screen (likes 1080p / 4K or 720P or 480p etc )

The RGB accept code / The VA panel/ The VGA port / The Display port Version / The HDMI

port version can leak your real identify

Also , Can the dev accept Face recognition or Finger print reader (biometric) as

login method? likes Apple Id fingerprint or Iris scan ( samg sung mobile phone)

still finding how to use Pretty good privacy certificate generate by GPG4win

Tue, 18 Dec 2018, 01:01pm #3

pubcrawlhk@secmail.pro wrote:

Also , Can the dev accept Face recognition or Finger print reader (biometric) as

login method? likes Apple Id fingerprint or Iris scan ( samg sung mobile phone)

On the one hand you don't want to be identified by browser fingerprinting and on the other hand you accept the convenience of face recognition and finger print reader in an apple context. That sounds very schizophrenic to me.

Last edited: Tue, 18 Dec 2018, 01:16pm by newkidonthebloc

Sat, 22 Dec 2018, 11:26am #4

re: #2 above, we don't provide a browser and have no control over your browser.

Sun, 30 Dec 2018, 11:40am #5


Ubuntu DiscoDingo's deadline is Feb. 21. Negotiation might be possible after that if needed, but I guess we assume Disco will have .38.

Fri, 04 Jan 2019, 01:55pm #6

^^ OP updated with dates ^^