Hello everybody, we have something new for you to test: a new version of Bear’s web clipper!
TL;DR
The new Web Clipper doesn’t use a remote server like the old version. Instead, it extracts content right in your browser, making it faster, more private, and more reliable with password-protected or local sites. You’ll find instructions for testing in the last section.
(The old) Web clipper 1.0
The web clipper 1.0 relies on Postlight Parser, a Node.js
library that extracts meaningful content from web pages (no navigations, footers, menus, ads…). The Parser lives on an Amazon S3 Lambda server, so right now, when you click the browser extension, this is what’s happening:
- The URL is fetched from the browser and transferred to Bear.
- Bear passes the URL to the Parser and waits for the cleaned content version of the page.
- Bear receives the content, downloads the images, converts everything to Markdown, and generates a note.
The web clipper 1.0 has some downsides: - Websites protected by passwords or on local networks can’t be reached by the Parser.
- Some websites use redirects or load portions of the page after its first loading, making it impossible to reach the desired content from the Lambda.
- Other websites use JavaScript libraries to load images asynchronously, and it is not possible to reach their URLs.
- The entire process feels less safe because a remote server is involved.
(The new) Web Clipper 2.0
With the new web clipper, the meaningful content extraction happens in the browser using Mozilla’s readability lib with the HTML code currently displayed. Then the HTML code is transferred to Bear, which fetches the images and converts them into Markdown. This means:
- Websites protected by passwords or on local networks can be transferred to Bear.
- Redirects have already happened at the moment the web clipper is invoked.
- Images and text loaded asynchronously are already there (with some exceptions, see below).
- Last but not least, everything is done on the device.
Limitations
- Some websites load images and texts on scroll. Those remain a problem unless the page is scrolled to the bottom before invoking the extension.
- Both the old and the new clipper have some custom behavior for some specific URLs. Adding/modifying those behaviors now requires an extension update.
How to test
We have prepared a beta version for you to test. If you have version 1.x installed, we suggest you unselect or disinstall it first.
Safari
- Download and uncompress this archive
- Open Safari’s settings
- Select the Developer tab. If it’s not visible, see Configure Safari in macOS to run unsigned extensions to enable it
- Click
Add Temporary Extension…
and select the archive
Chrome
- Download and uncompress this archive.
- Open chrome://extensions/ in Chrome
- Click
Load Unpacked
and select the uncompressed folder
Firefox
- Download this archive
about:debugging
in Firefox- Click
This Firefox
- Click
Load Temporary Add-on...
and select the archive
Give it a try and let us know how it works for you. Feel free to share your feedback here with us!
The Bear Team