[109 / 18]

/ntr/ - Netrunner official /g/ browser - NTR edition

No.61040927 View ViewReplyOriginalReport
We are making a web browser!
PREVIOUSLY >>61018259

In the face of recent changes in Firefox and Chrome some anons were asking for a /g/'s perfect web browser, we collected the most wanted here and plan on continuing with the creation.

To contribute follow the WORK PLAN and get to programming!

WEBSITE: https://retrotech.eu/netrunner/

>Main repo
https://git.teknik.io/eti/netrunner
>Github Mirror
https://github.com/5yph3r/Netrunner
>IRC
Web cient: https://qchat.rizon.net/?channels=/g/netrunner
Channel on Rizon: #/g/netrunner
IRC guide: https://pastebin.com/YDbEWRHV

>TODO:
- Host project at savannah.nongnu.org
- Set bug tracker, website, and mailing list in Savannah.

>WORK PLAN
1. Browse the links2 source code (you can use Ctags or GNU GLOBAL for tagging functions and files).
2. Open API to future javascript integration (by an independent engine?).
3. Dig the javascript enabled version 2.1pre28 of links2 if you are curious.
4. Expose API and give (scripting) access to just about everything (using executables).
5. Create a switch by profiles for incoming and outgoing connections (uBlock-like).
6. Create profiles generator for user-agent and canvas fingerprint, with manual option for the user-agent.
7. Give control over the DOM, use folders for each site to be manually edited (use a hierarchical structure to cover subsites).
8. Include cache/tmp/cookies/logs options like read only cache, local CDN emulation, and other security policies.
9. Implement a link grabber for every link available to be parsed by the scripting interface.
10. Work with the links2 ncurses interface to support simple tree style options for everything (adblocking and tabs in the future).
11. Implement tabs and add tree style tabs in ncurses.
12. Work in the tree style bookmark management with ncurses.
13. Work in the framebuffer graphics rendering.
14. Add a javascript engine.
15. Add the rest of the features.