eeems-org / remarkable.guide Goto Github PK

Are the bootloaders of reMarkable 1 and 2 locked or not?

So, can I e.g. flash Debian to them if I develop drivers for the Linux kernel?

https://github.com/irth/go-simple

In the 3.11.1.6 beta, the current update engine mechanism is removed and appears to be replaced with https://sbabic.github.io/swupdate/swupdate.html

https://github.com/wpilibsuite/sphinxext-opengraph

This makes embedded content and search results have more context.

https://github.com/bkirwi/armrest
rust library built on libremarkable the provides the following:

• Elm-inspired UI library
• Handwriting recognition

https://github.com/Eeems-Org/remarkable-template-qt-app/blob/6db5b639b94e11c2423f16fd87d837d85ee55cf7/.github/workflows/build.yml#L30-L51

• Some sort of "click/tap to expand" option to hide anything past the first row? Perhaps a horizontal scrolling gallery with buttons to navigate for mobile?
  Right now, it takes up too much of the page and pushes remux way too far down on the launcher page
• Adjust widths to make sure that at least two screenshots show up per row regardless of the width (on mobile/tablet it only shows one per row)

https://gist.github.com/Eeems/77f6161ad7f33d121bb1071814225f2c

It would be useful for users to know what types of splashscreens there are in the guide portion.

In the development portion, we should document the formats of the files.

In the tech articles, we should have an article about creating your own splashscreens.

https://www.sphinx-doc.org/en/master/usage/extensions/doctest.html#module-sphinx.ext.doctest

This should both talk about the requirements for a template, and creating a toltec package for the template.

would help newcomers understand why toltec or "hacking" is valuable in the first place, not "just" a risk

I submitted #49 after user confirmation, but upon configuring tailscale myself I have found that tailscale can only share services running on localhost.

I have proposed a package in toltec that will allow the web interface to be accessed over tailscale. Upon that package being merged, the guide can be updated to include/point to the new instructions.

In the meantime it may be advisable to revert #49.

https://giscus.app/

https://github.com/executablebooks/sphinx-tabs

Some pens have buttons and stuff, so they are not fully compatible out of the box. Would be nice to get some pointers on how to install hacks for those.

The tailscale guide should be updated to use the new tailscale-systemd package in toltec instead of having users manually create the systemd service.

It should also be updated to use code blocks for commands.

i.e. they are only on the device, the official apps don't see them, and third party tools may not support them either.

Ideally, toltec would start including some font packages as well by the time this is written.