4 ms·

Greetings HN community! I'm excited to share the latest iteration of my reMarkable streaming tool, designed to enhance remote work productivity. In 2021, I deve

Greetings HN community! I'm excited to share the latest iteration of my reMarkable streaming tool, designed to enhance remote work productivity. In 2021, I developed a tool that enabled me to stream content from my reMarkable tablet to my laptop, making it an invaluable asset during virtual meetings and presentations. My newly published article delves into the details of this revamped version, discussing its architecture, components, and the iterative journey of improving user experience. As a product manager, I gained unique insights into user perspectives, which drove me to simplify the tool's activation process. This article is a deep dive into the technical aspects of the tool, exploring how I eliminated the need for a local service and optimized network consumption. If you're curious about DIY tech solutions, optimizing remote work setups, or simply exploring innovative projects, I invite you to explore the article.

timoteostewart 3y ago
Engaging and informative write-up. Thanks!
- d__a__n___g 3y ago
  [flagged]
- j45 3y ago
  Agreed from the majority who is just upvoting and bordering on a comment to say thanks. To the flagged comment, HN isn’t littered with many thanks comments per article, a few ways to thank go a long way.
Knee_Pain 3y ago
Would it be possible to implement this via USB connection?
- owulveryck 3y ago
  It already works via USB if you activate the sharing option and connect via the 10.x.x.x address
danShumway 3y ago
Thanks for not only building the tool but also releasing such a great technical writeup. This is a wonderful blogpost.
natsucks 3y ago
As a reMarkable owner, I love it. I want it. gimme gimme gimme.
sireat 3y ago
Looks like awesome project! EDIT: Ctrl-C and restart with ./goMarkableStream got it working more or less. Saving the below message if it helps anyone else EDIT2: Awesome when it works - but getting quite a bit of spotty service. Still frequent `waiting for reMarkable screen` . SSH is showing everything normal, except for occasional: 2023/08/20 14:48:16 read /dev/input/event2: file already closed 2023/08/20 14:48:16 read /dev/input/event1: file already closed I upgraded my reMarkable2 to 3.5.2.1807 (from ancient 2 something version) Unfortunately I am getting waiting for reMarkable screen after installation. That is nothing is happening when I draw on reMarkable2 - in notebook, in sheets, on book. On inspection ReMarkable2 is certainly serving html with canvas element Both https://192.168.8.143:2001/ https://192.168.8.143:2001/ and https://10.11.99.1:2001/ https://10.11.99.1:2001/ work (after accepting unsafe SSH cert which is normal) and are serving html. Tried on Chrome, Firefox, Brave I installed it per github instructions. From Windows via PuTTY through 10.11.99.1 EDIT3: Looks like limitation is one browser (and one IP address) per stream - normal considering the usage :). Still sometimes no matter what address and browser I try I get `waiting for reMarkable screen` EDIT4: tried `nohup ./goMarkableStream &`, closed PuTTY and restarted client computer - all browsers giving `waiting for reMarkable screen` How would I restart the stream? Inspecting https://10.11.99.1:2001/stream https://10.11.99.1:2001/stream gives `too many requests` response.
- owulveryck 3y ago
  Regarding Edit 3: Yes it is a feature not a bug. I don’t want to stream to several browsers at once.
  - sireat 3y ago
    Agreed that is completely reasonable. One stream is sufficient. Unfortunately per EDIT4, it looks like it is not possible to leave this service running on reMarkable2 until the next time. Any way to reset without going into SSH again? EDIT: looks like enabling USB on reMarkable2 got the stream working. Curious though why did the web server work at all then (possibly sharing of common wi-fi?) FINAL_EDIT: I give up, there is no sense to this madness. Suddenly the stream starts working on same same https://10.11.99.1:2001/ https://10.11.99.1:2001/ where it was giving `waiting for reMarkable` canvas for last 15 minutes. Possibly there is some sort of timeout for the old stream?

timoteostewart 3y ago

Engaging and informative write-up. Thanks!

d__a__n___g 3y ago
[flagged]
j45 3y ago
Agreed from the majority who is just upvoting and bordering on a comment to say thanks. To the flagged comment, HN isn’t littered with many thanks comments per article, a few ways to thank go a long way.

Knee_Pain 3y ago

Would it be possible to implement this via USB connection?

owulveryck 3y ago
It already works via USB if you activate the sharing option and connect via the 10.x.x.x address

danShumway 3y ago

Thanks for not only building the tool but also releasing such a great technical writeup. This is a wonderful blogpost.

natsucks 3y ago

As a reMarkable owner, I love it. I want it. gimme gimme gimme.

sireat 3y ago

Looks like awesome project! EDIT: Ctrl-C and restart with ./goMarkableStream got it working more or less. Saving the below message if it helps anyone else EDIT2: Awesome when it works - but getting quite a bit of spotty service. Still frequent `waiting for reMarkable screen` . SSH is showing everything normal, except for occasional: 2023/08/20 14:48:16 read /dev/input/event2: file already closed 2023/08/20 14:48:16 read /dev/input/event1: file already closed I upgraded my reMarkable2 to 3.5.2.1807 (from ancient 2 something version) Unfortunately I am getting waiting for reMarkable screen after installation. That is nothing is happening when I draw on reMarkable2 - in notebook, in sheets, on book. On inspection ReMarkable2 is certainly serving html with canvas element Both https://192.168.8.143:2001/ https://192.168.8.143:2001/ and https://10.11.99.1:2001/ https://10.11.99.1:2001/ work (after accepting unsafe SSH cert which is normal) and are serving html. Tried on Chrome, Firefox, Brave I installed it per github instructions. From Windows via PuTTY through 10.11.99.1 EDIT3: Looks like limitation is one browser (and one IP address) per stream - normal considering the usage :). Still sometimes no matter what address and browser I try I get `waiting for reMarkable screen` EDIT4: tried `nohup ./goMarkableStream &`, closed PuTTY and restarted client computer - all browsers giving `waiting for reMarkable screen` How would I restart the stream? Inspecting https://10.11.99.1:2001/stream https://10.11.99.1:2001/stream gives `too many requests` response.

owulveryck 3y ago
Regarding Edit 3: Yes it is a feature not a bug. I don’t want to stream to several browsers at once.
- sireat 3y ago
  Agreed that is completely reasonable. One stream is sufficient. Unfortunately per EDIT4, it looks like it is not possible to leave this service running on reMarkable2 until the next time. Any way to reset without going into SSH again? EDIT: looks like enabling USB on reMarkable2 got the stream working. Curious though why did the web server work at all then (possibly sharing of common wi-fi?) FINAL_EDIT: I give up, there is no sense to this madness. Suddenly the stream starts working on same same https://10.11.99.1:2001/ https://10.11.99.1:2001/ where it was giving `waiting for reMarkable` canvas for last 15 minutes. Possibly there is some sort of timeout for the old stream?