Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adoption Plans: #2

Open
eyedeekay opened this issue Feb 27, 2020 · 0 comments
Open

Adoption Plans: #2

eyedeekay opened this issue Feb 27, 2020 · 0 comments

Comments

@eyedeekay
Copy link
Owner

I... do not realistically have time to maintain separate Chrome and Firefox plugins, and they can't share the same codebase in a productive way. But I do not wish to abandon this extension either. So finding somebody who wants to work with me to take it somewhere better becomes a pressing issue.

The bold, but logical choice would be to work with @brave and probably @PurpleI2P to integrate I2P into Brave in much the same way which Tor already has been. This would be great, but it's a lot of work and this is an issue because I'm strapped for time in the first place. Somebody who wants to take this path would have to be interested in spending significant time on C++ as well as Javascript. This is what I would do if I could live without sleep.

The less ambitious choice would be for a developer to continue working on features solely in the webextension itself. A Chrome webextension developer would be able to fill in the blanks between the Firefox and the Chrome build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant