Our great sponsors
-
external-application-button
Communicate with external applications of your OS through a toolbar button or context menu item.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
The code references stochastic modeling[1] for predicting the users next command. There may be other places too.
https://github.com/atlas-engineer/nyxt/pull/2593
This probably wouldn't be possible due to browser sandboxing.
You could however, use a tool like External Application Button [0] in order to send the URL of the page to a script/program, which in turn can make the body of the page parsable by downloading the URL it gets, automating some action on it. I use it pretty often to automate downloads with yt-dlp or opening a picture directly in GIMP from the browser, but since you're invoking a bash/python/whatever script, the possibilities are basically endless.
[0]: https://github.com/andy-portmen/external-application-button
You can do that with vimium: https://github.com/philc/vimium/issues/367#issuecomment-3535...
git clone https://github.com/MY_USERNAME/vim.git
Not exactly what I'd call a difficult or time consuming setup method.
There are always going to be limitations to extension-based approaches but Firefox with tridactyl is most of the way there capability-wise IMO (https://github.com/tridactyl/tridactyl). I use that plus tree-style tabs and find it excellent. There's always some extensibility limitations that break the integration though, like extensions getting disabled on mozilla domains.
I love projects like nyxt and respect their priorities, but without big-player extension support it's usually a no-go for me. Still, I'll be interested to see the ideas they develop trickle out into the rest of the power-browser ecosystem. I especially like that lossless tree history – history management is a very under-explored UX area IMO