Linus Tech Tips

3526 readers

2 users here now

~~⚠️ De-clickbait-ify the youtube titles or your post will be removed!~~

~~Floatplane titles are perfectly fine.~~

~~LTT/LMG community. Brought to you by ******... Actually, no, not this time. This time it's brought to you by Lemmy, the open communities and free and open source software!~~

~~If you post videos from Youtube/LTT, please please un-clickbait the titles. (You can use the title from https://nitter.net/LTTtranslator/ but it doesn't seem to have been updated in quite some while...)~~

founded 1 year ago

MODERATORS

[email protected]

930

The Problem with Linus Tech Tips: Accuracy, Ethics, & Responsibility (www.youtube.com)

submitted 1 year ago by [email protected] to c/[email protected]

298 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago

Might be a bad example but that stuck to me: Under no circumstance, you should talk like this to customer service. Always remember that the other end is a human and being rude makes it hard to offer a solution.

How do I deal with support? Start nicely (with good companies that's all you need) and slowly provide hints they screwed up allowing them to keep face as well as being the one offering it instead of reacting to the demand. If they don't understand: tell them. The last resort is the blacklist (company, date, reason) paired with DNS blocking (in case I forget about it).

Want an example of a blacklisted company? Asus.

They don't have any technical support unless you are an influencer or some big shot buying frequently truckloads of products. I might be able to get somewhere by being a dick but do I always want to push hard to escalate it?

Just call it a day (aka. scrap those products) and buy Asrock. This was definitely a quality-of-life improvement.

Btw. Extracting firmware can be difficult. Nordic had a horrific bug in the NRF52, WCH has a bug in the CH552 allowing to out the firmware by software. For ST STM32F it's complicated. They have a design flaw but exploding it requires decapping the MCU and knowing in which area of the die the readout protection bit is located. Haven't checked if they fixed it with the newer G, U and MP series.