I will take this chance to discuss the license of your browser.

Did you write this yourself, or is it a spinoff of some existing free software license?

Why not go with a copyleft license, such as the GNU General Public License?

The License is the BSD license just copy pasted, not sure why github does not recognize it

Why didn’t I choose GPL? at the advice of some friends of mine who made a compelling argument. I also think there are some GPL compatibility issues if I choose to use BSD or MIT software- which I use right now

If you can make a compelling argument for GPL, I would be willing to switch for newer releases

Really nice seeing this progress. What browser is this based on? What JS vm are you using? Also you have a great project going on here with its own identity, have you considered changing the name and moving away from the franken-NeXT-Apple logo?

Hi! Thank you for the kind words and your help yesterday!!

It is based on Webkit. In terms of names I have thought about it for a long long time, and I eventually settled on nEXT-Browser. I am open to suggestions though!

From what I've seen it already looks promising. Can't wait for the linux release!

Thank you for the kind words!

Already looks usable, thanks for the effort!

No problem! :) Thanks for the support!

Any plans to allow the user to limit what web resources get loaded when visiting a web location?

I like the concept, but (similarly to Qutebrowser) I would not yet use this to browse the Internet, simply because it completely ignores the tracking issues with the vast majority of today's websites.

For reference, I use uMatrix in Firefox to achieve what I'm talking about (my only gripe with it being that it is mouse-controlled).

Hi yes! Absolutely an important feature and it is on the roadmap. This will be a little bit different than plugins in that the restriction of loading will be done way way before the assets are even requested. I'll be able to implement this in the resource handler (or whatever it is called) that actually loads URLs. I just need to come up with a simple, consistent way to allow people to hook into this mechanism and regulate the content they wish to load/not load.

Any plans to introduce self-documentation? I love what you’ve done so far and I would love to be able to access nEXT’s documentation in-browser with something like Emacs’s C-h.

there’s definitely a plan, just so much to do :D PRs always welcome!!

I'm a bot, bleep, bloop. Someone has linked to this thread from another place on reddit:

 If you follow any of the above links, please respect the rules of reddit and don't vote in the other threads.(Info/ ^Contact)

nEXT browser rock!

Thank you for your contribution to community.

Thank you for the kind words!!

Is it possible to select text input boxes without the mouse? can't figure that out.

Also, ironically, the links on reddit don't work for me at all.

That's very strange, the links work just fine for me on reddit: https://imgur.com/a/gQeJG

Which version of OSX are you running? Maybe I have some issues with anything below high Sierra or something :\

Input boxes, not yet, that's coming soon hopefully. Unlike vimperator, the javascript actually returns all of the anchors to the Lisp backend, which then calls set-url of the active-buffer. The reason the link hints are implemented this way is to avoid websites that hijack the keystrokes of the end user, i.e. GitHub, google, etc from preventing the user using link hints.

So in order to combat this, we need to make the function that receives the javascript in the lisp backend aware of text boxes/ other controls, and allow it to select them somehow.

Sorry about the issues!