3 ms·

yes and no. It's easy if you just want to display your own content: https://www.invisible-computers.com/invisible-calendar/image-url-manual.html https://www.i

yes and no. It's easy if you just want to display your own content: https://www.invisible-computers.com/invisible-calendar/image-url-manual.html https://www.invisible-computers.com/invisible-calendar/image... or, if you want to share your app with others, there is: https://github.com/Invisible-Computers/image-gallery/blob/main/HowToBuildAnApp.md https://github.com/Invisible-Computers/image-gallery/blob/ma... It's hard if you want to run your own embedded code. I just haven't written the documentation for it and you would need your own UART flasher board.

mschuster91 3y ago
> I just haven't written the documentation for it and you would need your own UART flasher board. That would not be an issue. However, I'm based in Germany as well... do you have some sort of newsletter?
- konschubert 3y ago
  No newsletter, but I just created a google form I you want to get notified if/when it is available in Europe: https://forms.gle/96sGBWFsxgAomG3Q9 https://forms.gle/96sGBWFsxgAomG3Q9
mulmen 3y ago
Wow, very clever, just display an image! Does the image server really have to be on the Internet? Can I just enter a locally-resolvable hostname or IP address?
- konschubert 3y ago
  Has to be online since it is proxied via an online backend which does the actual black-and-white conversion etc. I have some ideas for letting users point the device directly to a local URL, but I don't want to commit to any promises on that front. You could try using something like https://ngrok.com https://ngrok.com, that's what I sometimes use for testing.
  - mulmen 3y ago
    Hm, I see. I’m pretty sure I can figure out how to serve a greyscale image. I suggest making that proxy explicit in your docs. You suggest using HTTPS and an obscure URL to keep our data “secret” but then you’re literally processing our content and could be doing anything with it.
    - konschubert 3y ago
      That's a valid point. Image data is never stored, only hashes. But it passes though the server and I don't like that either. It's not quite greyscale, it has to be in a specific binary black-and-white representation, but definitely do-able if documented. Or I could publish a little python library. Just thinking out loud here.
      - mulmen 3y ago
        Yeah don’t mean to diminish the project, it’s very cool! I’m sure you already have a lot of work into it. This thing is almost exactly what I was looking for less than a week ago. It’s actually even simpler and more clever than I imagined. For me less is more. Just serve an image at a URL. EZPZ. If you want to make it hackable I suggest docs first because everyone is going to want to use their own preferred language. Maintaining a library is just more work and image processing libraries are already a dime a dozen.
        konschubert 3y ago
        That's a good point about documentation-first. Sometimes a little reference code can say more than 1000 words, though :)

mschuster91 3y ago

> I just haven't written the documentation for it and you would need your own UART flasher board. That would not be an issue. However, I'm based in Germany as well... do you have some sort of newsletter?

konschubert 3y ago
No newsletter, but I just created a google form I you want to get notified if/when it is available in Europe: https://forms.gle/96sGBWFsxgAomG3Q9 https://forms.gle/96sGBWFsxgAomG3Q9

mulmen 3y ago

Wow, very clever, just display an image! Does the image server really have to be on the Internet? Can I just enter a locally-resolvable hostname or IP address?

konschubert 3y ago
Has to be online since it is proxied via an online backend which does the actual black-and-white conversion etc. I have some ideas for letting users point the device directly to a local URL, but I don't want to commit to any promises on that front. You could try using something like https://ngrok.com https://ngrok.com, that's what I sometimes use for testing.
- mulmen 3y ago
  Hm, I see. I’m pretty sure I can figure out how to serve a greyscale image. I suggest making that proxy explicit in your docs. You suggest using HTTPS and an obscure URL to keep our data “secret” but then you’re literally processing our content and could be doing anything with it.
  - konschubert 3y ago
    That's a valid point. Image data is never stored, only hashes. But it passes though the server and I don't like that either. It's not quite greyscale, it has to be in a specific binary black-and-white representation, but definitely do-able if documented. Or I could publish a little python library. Just thinking out loud here.
    - mulmen 3y ago
      Yeah don’t mean to diminish the project, it’s very cool! I’m sure you already have a lot of work into it. This thing is almost exactly what I was looking for less than a week ago. It’s actually even simpler and more clever than I imagined. For me less is more. Just serve an image at a URL. EZPZ. If you want to make it hackable I suggest docs first because everyone is going to want to use their own preferred language. Maintaining a library is just more work and image processing libraries are already a dime a dozen.
      - konschubert 3y ago
        That's a good point about documentation-first. Sometimes a little reference code can say more than 1000 words, though :)