Skip to content
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.

Hard fork the I2P network, or design/implement a new system, or implement another existing system #1000

Closed
anonimal opened this issue Aug 1, 2018 · 3 comments
Closed

Hard fork the I2P network, or design/implement a new system, or implement another existing system #1000

anonimal opened this issue Aug 1, 2018 · 3 comments

Comments

@anonimal
Copy link
Collaborator

anonimal commented Aug 1, 2018

By submitting this issue, I confirm the following:

  • I have read and understood the developer guide in kovri-docs.
  • I have checked that the issue I am reporting can be replicated or that the feature I am suggesting is not present.
  • I have checked opened or recently closed pull requests for existing solutions/implementations to my issue/suggestion.

We have gathered enough evidence over the years to finally propose this issue. Not to be taken lightly, I will present a very clear proposal and finish writing this issue after defcon.

The most recent of many poor decisions made by Java I2P project have proven to be the straw that broke the camel's back.

Details to come.
@janowitz
Copy link

Any updates? Can't wait to read some details...

@Hueristic
Copy link

Have been waiting on this, what is going on?

@anonimal
Copy link
Collaborator Author

anonimal commented Sep 7, 2018

NOTICE: THIS ISSUE HAS BEEN MOVED TO GitLab. Please continue the discussion there. See #1013 for details.

@anonimal anonimal closed this as completed Sep 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Hueristic @anonimal @janowitz