R C-R

They are listed in the Privacy Policy statement, along with links to their privacy policies.

How would that help?

That info should always be immediately available, provided by the OS in the same way it is to Finder or Windows Explorer, both of which are applications. Agreed, but the question is how to do that without causing undesirable side effects, like degrading responsiveness or causing lots of disk thrashing.

All things considered, maybe the best solution, workaround, or whatever you want to call it for this is for the Affinity apps to pop up a warning if a user tries to open a file on a network drive, saying that there is a risk of data loss unless the file is copied to a local drive, with an option to do that?

Assuming I have understood how it works correctly, maybe they can make this work better, but one of the problems with trying to load the entire file into RAM is it is also used by every other process running on the computer, so there is no way to know how much of it the memory management system of the OS will allow an Affinity (or any other) app or its open documents to remain resident in memory at any particular time. That means paging to & from VM can occur at any time, so at best the app would have to spend a lot of time keeping track of that highly dynamic process instead of processing user input, updating the display, & so on; & that in itself could increase the amount of paging. Obviously, it also would adversely affect performance. Another potential problem is if the OS would even expose enough of this memory use info to the app for security reasons -- I do not pretend to understand the details but apparently if an app can get access to how memory is used by other processes than its own that increases the 'attack surface' malware can leverage to compromise data security ... or something like that. All I know for sure is it is all very complicated & the details probably vary considerably depending on the OS & the hardware everything runs on, so it is unlikely there is any simple obvious way to make it all work better than it does now.

From what I have read about this, all Nikon D8xx series camera sensors use the Bayer filter method of recording color information. As explained in the Raw Actually Spotlight article, a Bayer filter itself does not blur anything; it is just a matrix of tiny color filters that allow each of the sensor's photoreceptors to be sensitive to only one color of light. The image data from the sensor is basically just an ordered list of the brightness value of each photoreceptor, so without the demosaicing step, you would just get a greyscale image devoid of any color information.

I can see the text, if not clearly because it is so small. But there seems not to be a link to anything in it, not to the licensing terms or to anything else.

Do you mean this? If so, I am still not seeing anything in it that is a link to anything.

FWIW, my Mac is set to send crash reports to Apple & to share them with developers. I filled in the comment section with the steps to recreate the crash.

I am not seeing that on the Mac App Store versions, but maybe I am just overlooking where the link is on that screen.

Just to keep things interesting, the tool is named "Gradient" in Affinity Photo & "Fill Tool" in Affinity Designer. BTW, I just noticed that in Affinity Photo (Mac 1.6 version) if I select a pixel layer with the Gradient tool, set the context to "Stroke" & Type to "Bitmap" & then select a raster image file for the fill, Affinity Photo immediately crashes, so you might want to avoid doing that.

It could be improved but it probably should be mentioned here that if an Affinity app is purchased from the Mac, iOS, or Microsoft Store, the licensing & usage terms of those stores & their privacy policies also apply. Another complication is that the governing laws vary depending on the jurisdiction (often of both the seller & the buyer) & those boilerplate clauses that say all disputes will be settled according to the laws of a specific jurisdiction are themselves subject to legal disputes & may not be enforceable everywhere anyway. That's why these things are so long & full of legal jargon.

Maybe if you got to know me better you would think differently about that.

But very clearly you are using the web site, so what is your point?

But it explicitly states that all collected usage data is anonymous, why they collect that anonymous data, & that no personal data is collected. An exception is crash report data, which presumably collects some personal data, but only if a user opts to submit it. This, together with the rest of the policy, seems adequate for users to decide if this constitutes "spying," or is in any other way so unacceptable that it is reason enough not to buy & use the software. What more do you need to know than that?