Should material profiles be shared, or kept local?

I share a 3D printer and filament library with a local workshop, and I keep wondering whether our slicer should carry a portable, community-edited database of material profiles. It would cover temperature ranges, drying requirements, nozzle wear, and known failure modes—not just a magic “recommended” setting.

That sounds useful as a cautious, versioned starting point with user notes and uncertainty labels. But could it also create false confidence and discourage experimentation? Our recycled rPETG GF20+UV sheet, for example, calls for 8–10 hours of pre-drying at 65°C and flags glass fiber as relevant to nozzle wear. Helpful, yes; universal, no.

I’d want profiles local by default, rather than silently uploading printer and material data to a vendor. Should this be shared guidance without becoming checkbox compliance? Disagree, describe how you manage unknown materials, or suggest a safer alternative.

I’d support the database if it behaved more like a lab notebook than a recipe book. Every value should carry printer, nozzle, batch, date, and confidence context. The dangerous abstraction is “this filament prints at 235°C,” when the useful statement is “this combination worked under these conditions.” Local storage should be the default; export can be deliberate.

The vendor-upload question is not a footnote. Printer identifiers, consumable status, job metadata, and material information can all be part of cloud processing. A local profile file with optional, scrubbed sharing gives the workshop a clearer trust boundary. I’d rather lose convenience than discover that calibration data became product telemetry by default.

I’m less worried about experimentation being discouraged than about beginners having no warning at all. A profile can say “try this first; inspect the result; report back,” which is better than pretending the spool is self-explanatory. The interface matters more than the existence of the database. Don’t use a green checkmark where a confidence range belongs.

The uncertainty label is the essential part. Drying guidance and abrasive-fill warnings are actionable, but the recycled rPETG example also shows why a manufacturer sheet is not automatically a universal setting. I’d separate manufacturer guidance, workshop observations, and unverified anecdotes instead of flattening them into one rating.

I’d build this as a local folder or small database with signed exports, not a mandatory account feature. The workshop could share a profile intentionally, retain its history, and merge notes after review. Unknown filament would get a quarantine profile and a small test print. That preserves experimentation while making the first failure cheaper.