<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention">@<span>0xabad1dea</span></a></span> <br />* simplified model; the reality is typically more complex but the constraints and approaches remain roughly the same<br />** most devices expressly designed for type-C charging will at least tolerate 20 V on the input; but in any case, a (non-malicious) type-C cable cannot cause an overvoltage event, unlike e.g. QuickCharge, where a damaged cable can potentially make that happen</p>

@lain@lain.com @ff16e04363da999a0645281d7bcc8ae23131e5708e5e3c32631b97c8767df70b@mostr.pub @vaartis@pl.kotobank.ch assigned fag at girth

<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention">@<span>0xabad1dea</span></a></span> (the first step the majority of modern devices, certainly the more expensive ones like phones--the ones you&#39;d care about being fried--do with the power they receive is feed it into a DC-DC converter lowering whatever voltage it is to the 4.2V used to charge the battery*. as long as it&#39;s within the converter&#39;s maximum ratings, it&#39;s fine**.</p>

@lain@lain.com @ff16e04363da999a0645281d7bcc8ae23131e5708e5e3c32631b97c8767df70b@mostr.pub @vaartis@pl.kotobank.ch TL note: the G stands for Geburtstag

@ff16e04363da999a0645281d7bcc8ae23131e5708e5e3c32631b97c8767df70b@mostr.pub assigned male/female at birth, the last one is not an acronym

@vaartis@pl.kotobank.ch @ff16e04363da999a0645281d7bcc8ae23131e5708e5e3c32631b97c8767df70b@mostr.pub assigned fag at birth

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention">@<span>0xabad1dea</span></a></span> <a href="https://mastodon.social/@becomethewaifu@tech.lgbt/112201273153655478" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@becomethewaif</span><span class="invisible">u@tech.lgbt/112201273153655478</span></a> says that one particular very widespread device often used by children *did* fry itself in some circumstances, by acting very out of spec.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <br />Otoh:<br />Aa🄐🄰🅐🅰ɑ𝐀𝑎𝒜𝔞𝔄</p>

<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention">@<span>0xabad1dea</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@dascandy42" class="u-url mention">@<span>dascandy42</span></a></span> &quot;fast charging&quot; is largely enabled by type-C (not exclusively, but type-C made it pervasive). it&#39;s not the device that will be fried (it is exceptionally unlikely that anything will happen to the device and you can independently confirm that this doesn&#39;t happen a lot by going through reviews); it&#39;s the cable that may overheat and catch fire</p><p>the lack of standardization regarding data transfer is a separate, also acute problem</p>