#typescript#agent#ai#ai_agents#ai_tools#automation#browser#browser_automation#browser_use#chrome_extension#comet#dia#extension#manus#mariner#multi_agent#n8n#nano#opensource#playwright#web_automation
Nanobrowser is a free, open-source Chrome extension that uses multiple AI agents to automate complex web tasks directly in your browser, keeping your data private since everything runs locally. It supports many AI language models, lets you customize which models handle different tasks, and offers an easy chat interface to control and track automation. You can automate repetitive tasks, ask follow-up questions, and review past interactions without coding. It works best on Chrome and Edge and is a cost-effective alternative to expensive AI automation tools, giving you powerful, flexible web automation with full control and privacy.
https://github.com/nanobrowser/nanobrowser
https://pypi.python.org/pypi/oauthlib
A generic, spec-compliant, thorough implementation of the #OAuth request-signing logic for python
OAuth often seems complicated and difficult-to-implement. There are several prominent libraries for handling OAuth requests, but they all suffer from one or both of the following:
They predate the OAuth 1.0 spec, AKA RFC 5849.
They predate the OAuth 2.0 spec, AKA RFC 6749.
They assume the usage of a specific HTTP request library.
OAuthLib is a generic utility which implements the logic of OAuth without assuming a specific HTTP request object or web framework. Use it to graft OAuth client support onto your favorite HTTP library, or provide support onto your favourite web framework. If you’re a maintainer of such a library, write a thin veneer on top of OAuthLib and get OAuth support for very little effort.
https://aaronparecki.com/2012/07/29/2/oauth2-simplified#others
OAuth 2 Simplified
Sun, Jul 29, 2012 9:30am -07:00
Many services such as #Facebook, #Github, and #Google have already deployed OAuth 2 servers, and deployed implementations win.
The #OAuth 2 spec itself leaves many decisions up to the implementor. Instead of describing all possible decisions that need to be made to successfully implement OAuth 2, this post makes decisions that are appropriate for most implementations.
This post is an attempt to describe OAuth 2 in a simplified format to help developers and service providers implement the protocol.