<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>konschubert</author><text>To (maybe?) add to your list:  The e-paper smart display that I am making and selling does also allow users to build their own content. There are two different ways:&lt;p&gt;1. You can either just serve an image on a URL and the device will display it, refreshing whenever the image changes:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.invisible-computers.com&amp;#x2F;invisible-calendar&amp;#x2F;image-url-manual.html&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.invisible-computers.com&amp;#x2F;invisible-calendar&amp;#x2F;image...&lt;/a&gt;&lt;p&gt;2. Or you go one step further and wrap it into an API with a settings page, which will also allow others to install and use your app:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Invisible-Computers&amp;#x2F;image-gallery&amp;#x2F;blob&amp;#x2F;main&amp;#x2F;HowToBuildAnApp.md&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Invisible-Computers&amp;#x2F;image-gallery&amp;#x2F;blob&amp;#x2F;ma...&lt;/a&gt;&lt;p&gt;To be fully transparent: I know that many people are using the first approach to display their own designs, but I haven&amp;#x27;t had much uptake yet on the second option to build a public, installable app. So if anyone is interested in trying this out, please contact me! I am willing to cooperate closely and iterate on the API where necessary.&lt;p&gt;(I hope that this is sufficiently relevant, even though I am tooting my own horn here.)</text><parent_chain><item><author>raisjn</author><text>OP here. thanks for all the comments. some more info:&lt;p&gt;rmkit is a library (and group of devs) for creating apps on the rM (and now Kobo). outside of rmkit, people typically use Qt to write apps, but there&amp;#x27;s many routes[0], including SAS[1]: a solution that uses unix pipes. the rM2 requires a bit more hacking to get working than the rM1 because their framebuffer driver[2] is embedded in their software for rM2 and requires updating rm2fb every time remarkable releases a new update. there&amp;#x27;s alternative drivers[3] to drive the display in development.&lt;p&gt;i will keep updating the article based on feedback, thank you and keep hacking&lt;p&gt;[0]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;remarkable.guide&amp;#x2F;devel&amp;#x2F;index.html&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;remarkable.guide&amp;#x2F;devel&amp;#x2F;index.html&lt;/a&gt;&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;rmkit.dev&amp;#x2F;apps&amp;#x2F;sas&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;rmkit.dev&amp;#x2F;apps&amp;#x2F;sas&lt;/a&gt;&lt;p&gt;[2]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ddvk&amp;#x2F;remarkable2-framebuffer&amp;#x2F;&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ddvk&amp;#x2F;remarkable2-framebuffer&amp;#x2F;&lt;/a&gt;&lt;p&gt;[3]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;matteodelabre&amp;#x2F;waved&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;matteodelabre&amp;#x2F;waved&lt;/a&gt;</text></item></parent_chain></comment><story><title>E-ink is so Retropunk</title><url>https://rmkit.dev/eink-is-so-retropunk/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>yoavm</author><text>I don&amp;#x27;t know about the rM, but for Kobo - why not just run Linux? it literally runs Debian (and others). I&amp;#x27;ve written so apps for it (e.g. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;bjesus&amp;#x2F;pidif&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;bjesus&amp;#x2F;pidif&lt;/a&gt;) using GTK. It would have been great if we had a more unified eco-system for e-ink supported apps.</text><parent_chain><item><author>raisjn</author><text>OP here. thanks for all the comments. some more info:&lt;p&gt;rmkit is a library (and group of devs) for creating apps on the rM (and now Kobo). outside of rmkit, people typically use Qt to write apps, but there&amp;#x27;s many routes[0], including SAS[1]: a solution that uses unix pipes. the rM2 requires a bit more hacking to get working than the rM1 because their framebuffer driver[2] is embedded in their software for rM2 and requires updating rm2fb every time remarkable releases a new update. there&amp;#x27;s alternative drivers[3] to drive the display in development.&lt;p&gt;i will keep updating the article based on feedback, thank you and keep hacking&lt;p&gt;[0]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;remarkable.guide&amp;#x2F;devel&amp;#x2F;index.html&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;remarkable.guide&amp;#x2F;devel&amp;#x2F;index.html&lt;/a&gt;&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;rmkit.dev&amp;#x2F;apps&amp;#x2F;sas&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;rmkit.dev&amp;#x2F;apps&amp;#x2F;sas&lt;/a&gt;&lt;p&gt;[2]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ddvk&amp;#x2F;remarkable2-framebuffer&amp;#x2F;&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ddvk&amp;#x2F;remarkable2-framebuffer&amp;#x2F;&lt;/a&gt;&lt;p&gt;[3]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;matteodelabre&amp;#x2F;waved&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;matteodelabre&amp;#x2F;waved&lt;/a&gt;</text></item></parent_chain></comment><story><title>E-ink is so Retropunk</title><url>https://rmkit.dev/eink-is-so-retropunk/</url></story>