url2epub VS is

Somewhat similarly, I wrote a web app to generate epub (instead of pdf) out of urls and send to eink reader(s) directly (via a telegram bot) so I can read them. Currently it supports sending epub by email (for kindle) or uploading epub to dropbox (for kobo, etc.). It originally also supports reMarkable cloud but we can no longer make reMarkable cloud actually work. There's also a REST api to generate epub to be downloaded directly: https://github.com/fishy/url2epub/blob/main/REST.md

For e-ink readers epubs are generally better than PDFs for urls anyways, as epubs are basically packed htmls, and also the flow text works better on smaller screens.

I wrote a service (Google Cloud Run as the backend, with Telegram bot as the frontend) to generate readable ePub from URLs and send directly to e-ink readers. It was originally wrote for reMarkable 2 (using reMarkable cloud), I recently added support for Kindle (by using the send-to-kindle emails). The code is at https://github.com/fishy/url2epub and I blogged about the recently added kindle support at https://b.yuxuan.org/url2epub-kindle.

I'm open to suggestions on what other e-ink platforms to add, as long as they have a reasonable cloud API. I'm also looking for a good e-ink platform to move to personally, as it becomes apparent that reMarkable really doesn't want third parties to use their proprietary cloud "API".

2. It's a relatively open system (compared to other e-ink readers), so it's pretty fun in terms of hackability.

I did get the forever free subscription which helps, but I also totally understand why they would want to charge for that, and I think the new $3/month is a pretty reasonable price for it.

Regarding instapaper use case and also hackability, shameless plug: I wrote https://github.com/fishy/url2epub for my own use case, so instead of relying on a third party service and manually sync stuff to reMarkable 2, I just send the link to the telegram bot (I picked telegram bot so that I can easily send links from my phone, not only desktops), and the epub will be auto synced to my reMarkable cloud account (they did made some changes to the cloud api causing I have to manually open their official mobile or desktop app to sync once before the reMarkable 2 itself would accept the new epub I uploaded through url2epub, haven't figured out how to avoid that yet, but it's still mostly automated).

For reMarkable, I also wrote a Telegram bot to convert http url into ePub and send to reMarkable directly: https://github.com/fishy/url2epub

(if you don't like telegram or don't use reMarkable, it also comes with a public rest API to generate epub out of urls)

Shameless plug and this is only loosely related: Over the last holiday season I wrote a backend (written in Go and running on App Engine) to convert http url into epub. The frontend is a telegram bot that sends the epub to your reMarkable account directly, but it also has rest api to download the epub file: https://github.com/fishy/url2epub/blob/main/REST.md

With the purchase of reMarkable 2, I have this need to easily send web articles to my reMarkable 2 from my phone, while officially they only provided a Chrome extension, which can only be used on desktops.

As a result I wrote some go code (https://github.com/fishy/url2epub) for the past 2 days, to generate ePub from URL. I also implemented reMarkable API to send them to reMarkable tablets directly.

The current UI for it is implemented as a Telegram bot (https://t.me/url2rM_bot?start=1), running on AppEngine (code: https://github.com/fishy/url2epub/tree/main/appengine). I initially considered making an Android app for the UI, but decided that Telegram bot is less work for me, and works good enough for this use case (sorry for people who don't use Telegram, but this also means that people on iOS, desktop, etc. will be able to use it).

For the future, I might do:

- Expand the URLs supported (currently it only supports URLs with an AMP version provided, and the AMP version does have article tag inside)

Not quite half-baked, but fairly fresh out of the oven:

https://github.com/oalders/is

It's a tool to make shell scripting read a little more like English.

https://github.com/oalders/is

I wrote a tool to make shell scripting just a little bit easier. It has a syntax that reads just a little bit like English, so that you can ask questions of your environment. That means you can do things like:

Check the version of a CLI tool:

$ is cli version tmux gt 3.2 && echo || echo

Check an OS version by its code name:

$ is os version-codename in ventura,monterey

Do things only if a dependency is installed:

$ is there go && go install golang.org/x/tools/cmd/goimports@latest

Query a CLI version:

$ is known cli version bash

5.2.15

Check if today is Wednesday using a case insensitive regex:

$ is cli output stdout date like "(?i)wed"

Update a binary if it's older than 7 days:

$ is cli age goimports gt 7 days && go install golang.org/x/tools/cmd/goimports@latest

Check the major (or minor, or patch) version of your OS:

$ is os version --major eq 13

Install if you have passwordless sudo:

$ is user sudoer && sudo apt-get install ripgrep

Check the output of STDERR for an arbitrary command:

$ is cli output stderr ssh --arg="-V" like 9.0p1

The idea is to make some scripting tasks less tedious. I mostly wrote this because I could and because I enjoyed doing it.

I recently wrote "is" so that I would have a tool to make shell scripting just a little bit easier: https://github.com/oalders/is

Olaf Alders recently shared his cool creation, is: an inspector for your environment. I am sure for all System Administrators out there, it would be very handy.

I'm working on "is". https://github.com/oalders/is

It allows me to install various things in various environments without getting too deep in to bash scripting.

For example:

$ is cli version tmux gt 3.2 && echo || echo

$ is there go && is there nvim && nvim +:GoUpdateBinaries +qa

$ is known cli version bash