Is your feature request related to a problem? Please describe.
This is not related to a defect.
Describe the solution you'd like
Currently, dbt Labs has telemetry in place that records dbt plugin initialization, and records the number of models injected via plugins. This is a privacy violation for dbt-loom users since dbt Labs has a competing proprietary approach, and since dbt Lab may use this as an extension of their surveillance of the open source community. Ideally, during the instantiation of dbt-loom, the telemetry associated with plugin use is deactivated via variable or dynamic patching.
Describe alternatives you've considered
We could leave it in place. This seems not ideal since we would then be maintaining the status quo.
We could provide erroneous or other garbage data to damage the quality of their telemetry. This would be actively hostile, and is likely not the "friendly" thing to do.
Is your feature request related to a problem? Please describe. This is not related to a defect.
Describe the solution you'd like Currently, dbt Labs has telemetry in place that records dbt plugin initialization, and records the number of models injected via plugins. This is a privacy violation for dbt-loom users since dbt Labs has a competing proprietary approach, and since dbt Lab may use this as an extension of their surveillance of the open source community. Ideally, during the instantiation of dbt-loom, the telemetry associated with plugin use is deactivated via variable or dynamic patching.
Describe alternatives you've considered
Additional context None.