Fair point, and thank you for putting it more neutrally.
I do agree that this thread has been heavily derailed by personal accusations and speculation. But the underlying issue is still real: inconsistent support handling, unresolved warranty/support obligations, GDPR-related requests, and what appears to be a pattern where users who challenge Bambu Lab formally are treated very differently.
This is not about attacking frontline support staff. I have said several times that ordinary employees should not be targeted personally. My criticism is aimed at company-level handling, escalation, documentation, and policy enforcement.
There are also public examples outside this thread where Bambu Lab’s conduct toward users, creators, open-source/community concerns and legal pressure has been discussed. One example is this video:
I am not saying that video proves my case. It is simply another example showing that concerns about Bambu Lab’s handling of users and community issues are not limited to me.
As for the 21 tickets: that number is being used against me without context. Bambu Lab’s own process expects separate issues to be handled in separate tickets. If tickets remain unanswered, unresolved, redirected or closed without proper resolution, they naturally stack up. I have had many separate hardware and support issues over time, including parts replaced, repeated mechanical issues, and a laser repair after roughly one week.
The original GDPR matter started because of unsupported accusations and account-level action. That is also why I react strongly when the same pattern appears again in this thread: people making claims without evidence, instead of sticking to documents, timelines and facts.
So yes, the thread got messy. But the subject is still valid: Bambu Lab’s support handling, settlement terms, GDPR requests, warranty/support obligations, and whether other users have experienced similar inconsistent communication.
That is the topic I want the thread to return to.