Appending an item should avoid bringing in unwanted/irrelevant data

Artists have struggled for more than a decade (see 1 , 2 ) with figuring out what datablocks the appended item uses.

This commonly manifests in an appended object bringing in a ton of other unnecessary and irrelevant objects, sometimes to massive confusion as to how the appended object depends on these other objects.

This request comes after a particularly heinous instance where an object contained a Geometry Nodes nodegroup that didn't visibly contain a reference to another object, but did deep inside the Data API. For more information on that please see this now-closed bug report.

To fix the issue stated in the bug report, it would be best to prevent the append operation from acknowledging these hidden datablock users.

In the long term, there needs to be more clarity as to what object uses what datablocks, and how it does so. Right now, the only information an artist gets is the number of users for a datablock, which is simply not enough. This can easily lead to a wild goose chase for a datablock user that almost seems to not exist.

Improving datablock visibility would do much to improve the ergonomics of Blender and make the Append/Link/etc. operation usable in complex environments.