awesome-reMarkable VS readability

> As much as I love the hacker spirit of cracking open hardware and software and bending it to your will (whether or not it was designed towards that end), I enjoy my reMarkable precisely because I can get away from the ubiquity of computing and needing to constantly tinker with and repair software.

Personally I completely agree with you, and could have written almost exactly that paragraph - I too have a ReMarkable (the 2nd / current version), and love using it as it ships for both note taking and especially for reading ebooks/PDFs ("especially" just because it's what I use it for more, not because that's what it's better at - in fact, it's UI for reading documents is among its weaker points and I hope they improve it in future software updates).

However it's worth pointing out that you can SSH into it, and there are a fair few 3rd party tools and hacks for it - so far I've avoided trying any of them as there's nothing that I want enough to have even a 1% risk of bricking it to worry about. But I'm tempted to start playing around with it someday.

This is the best list of stuff for the ReMarkable that I'm aware of, though I don't know how complete it is / how many released tools or guides there might be that aren't included here:

https://github.com/reHackable/awesome-reMarkable

There are options for USB/wifi syncing and lots of other community mods if you're handy with a terminal: https://github.com/reHackable/awesome-reMarkable

If you follow the instructions and you are fine to turn automatic updates off, you may have a lool at awesome-remarkable https://github.com/reHackable/awesome-reMarkable

This sentence doesn't make sense. People apply hacks because they want to make full use of their device. reMarkable has shortcomings, yes, but they can be overcome with the software that others have written. The Awesome reMarkable link the sidebar was basically a founding document of this very subreddit.

More info can be found at awesome-ReMarkable: https://github.com/reHackable/awesome-reMarkable

Use a software to manage your templates automatically. See the Awesome reMarkable list, and Ctrl-F "templates".

You can also take backups using easy, convenient, community-written software, like RCU (which I'm the author of), reMy, reMarkable HyUtilities, rmExplorer, rmAPI, and many others found in the Awesome reMarkable list.

You could try reMy, which has its own renderer. There are more rendering programs in the Awesome reMarkable list, many of which will work with 2.15 and below--just avoid anything saying 'cloud' or 'web UI'.

I'm working with the Mozilla's readability library https://github.com/mozilla/readability to get the "readable" text from articles and now I want to style the extracted text in a readable way.

Do you remember the Firefox Reader View? It's a feature that removes all unnecessary components like buttons, menus, images, and so on, from a website, focusing on the readable content of the page. The library powering this feature is called Readability.js, which is open source.

I wonder if Firefox "reader mode as a utility" might be a viable alternative for Pinboard like "content oriented" archiving?

https://github.com/mozilla/readability

Depending upon the type of content, one might want to look into using the Readability (Browder's reader view) to parse the webpage. It will give you all the useful info without the junk. Then you can put it in the DB as needed.

https://github.com/mozilla/readability

Btw, readability, is also available in few other languages like Kotlin:

https://github.com/dankito/Readability4J

Use Mozilla's Readability to extract that sweet, sweet text content from webpages.

Same as above but the ability to grab the entire article text (you can use the Readability library for that: https://github.com/mozilla/readability)

// Original script // https://gist.github.com/kepano/90c05f162c37cf730abb8ff027987ca3 // Bookmarklet Converter // https://caiorss.github.io/bookmarklet-maker/ // Libraries // https://github.com/mixmark-io/turndown // https://github.com/mozilla/readability javascript: Promise.all([import('https://unpkg.com/[email protected]?module'), import('https://unpkg.com/@tehshrike/[email protected]'), ]).then(async ([{ default: Turndown }, { default: Readability }]) => { /* Optional vault name */ const vault = ""; /* Optional folder name such as "Clippings/" */ const folder = "Clippings/"; /* Optional tags */ const tags = ""; function getSelectionHtml() { var html = ""; if (typeof window.getSelection != "undefined") { var sel = window.getSelection(); if (sel.rangeCount) { var container = document.createElement("div"); for (var i = 0, len = sel.rangeCount; i < len; ++i) { container.appendChild(sel.getRangeAt(i).cloneContents()); } html = container.innerHTML; } } else if (typeof document.selection != "undefined") { if (document.selection.type == "Text") { html = document.selection.createRange().htmlText; } } return html; } const selection = getSelectionHtml(); const { title, byline, content } = new Readability(document.cloneNode(true)).parse(); function getFileName(fileName) { var userAgent = window.navigator.userAgent, platform = window.navigator.platform, windowsPlatforms = ['Win32', 'Win64', 'Windows', 'WinCE']; if (windowsPlatforms.indexOf(platform) !== -1) { fileName = fileName.replace(':', '').replace(/[/\\?%*|"<>]/g, '-'); } else { fileName = fileName.replace(':', '').replace(/\//g, '-').replace(/\\/g, '-'); } return fileName; } const fileName = getFileName(title); if (selection) { var markdownify = selection; } else { var markdownify = content; } if (vault) { var vaultName = '&vault=' + encodeURIComponent(`${vault}`); } else { var vaultName = ''; } const markdownBody = new Turndown({ headingStyle: 'atx', hr: '---', bulletListMarker: '-', codeBlockStyle: 'fenced', emDelimiter: '*', }).turndown(markdownify); var date = new Date(); function convertDate(date) { var yyyy = date.getFullYear().toString(); var mm = (date.getMonth()+1).toString(); var dd = date.getDate().toString(); var mmChars = mm.split(''); var ddChars = dd.split(''); return yyyy + '-' + (mmChars[1]?mm:"0"+mmChars[0]) + '-' + (ddChars[1]?dd:"0"+ddChars[0]); } const today = convertDate(date); // This is the output template // It is similar to an Obsidian core template // except to insert a value we use: ${value} instead of {{value}} const fileContent =`--- type: clipping date_added: ${today} aliases: [] tags: [${tags}] --- author:: ${byline.toString().split('\n')[0].trim()} source:: [${title}](${document.URL}) ${markdownBody} `; // This copies your text to the clipboard navigator.clipboard.writeText(fileContent); // This creates a new document in Obsidian containing your clipping // I commented it out as this isn't what you asked for /* document.location.href = "obsidian://new?" + "file=" + encodeURIComponent(folder + fileName) + "&content=" + encodeURIComponent(fileContent) + vaultName; */ })

So first part of the task is to "extract the text from URL", and that is achieved by using descendant of https://github.com/mozilla/readability library which can extract text of any URL.