Michael Schmidt

Auto-saving to the current save file is generally not a good idea. Users frequently make temporary changes that they don't want to save, so we shouldn't force them to make...

> This is protection against crash app/BSOD/loss of electricity. That's a good use case. I would probably do it like: Chainner constantly saves the current canvas to a temporary file....

Just a node that given 2 images A and B returns `(A - B + 1) / 2`.

I was mistaken over how the Overlay blend mode works. The actual result would be more complex than just `(A - B + 1) / 2`.

We have an overlay blend mode, so for 2 images O, B and `overlay(O, B) = C`, I wanted a node that does `createOverlay(B, C) = O`. So it's kind...

This could become difficult. What a valid directory is depends on the OS. Even simply joining two paths is non-trivial, since different operating systems have different separators. So it would...

I'm somewhat against going the paths-are-strings route so many programming languages go. While all paths are string, not all strings are paths. However, I also see that using strings is...

In the future (and even in the now), we want chains to be easy to share. We already plan on adding a feature that allows you to create custom nodes...

> I don't know how well this can be handled, especially considering interop between JS and Python. As long as we make all paths URLs, there won't any interop issues...

Don't worry, `../1.jpg` is a valid (relative) URI, no need for the `file:` prefix.