2024lctgmeetingchats
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
2024lctgmeetingchats [2024.11.06 08:49] – Steve Isenberg | 2024lctgmeetingchats [2024.11.20 09:36] (current) – Steve Isenberg | ||
---|---|---|---|
Line 4: | Line 4: | ||
These are a record of the chats that were passed during meetings in 2024. They have been edited to a small extent.\\ | These are a record of the chats that were passed during meetings in 2024. They have been edited to a small extent.\\ | ||
To find chats for a given day, for example January 10, 2024, search for datecode 20240110 (2024, month 01, day 10). | To find chats for a given day, for example January 10, 2024, search for datecode 20240110 (2024, month 01, day 10). | ||
+ | |||
+ | ====20241120==== | ||
+ | ===Potpourri=== | ||
+ | <WRAP prewrap> | ||
+ | < | ||
+ | 10:19:42 From Barry Kort to Everyone: | ||
+ | QC3.0 stands for Quick Charge 3.0. It's a fast-charging technology developed by Qualcomm that allows for rapid charging of compatible devices. It works by intelligently adjusting the voltage and current levels during the charging process to optimize charging speed and efficiency. | ||
+ | 10:20:14 From Barry Kort to Everyone: | ||
+ | Key features of QC3.0: | ||
+ | Faster charging: It can charge devices significantly faster than standard charging methods. | ||
+ | Intelligent charging: It adapts to the specific needs of the device being charged, ensuring optimal charging performance. | ||
+ | Improved efficiency: It reduces charging time while minimizing heat generation. | ||
+ | If your device supports QC3.0 and you use a compatible charger, you can expect faster charging times and a shorter wait between charges. | ||
+ | 10:21:21 From Rich M to Everyone: | ||
+ | For what it's worth, USB-C PD has pretty much overtaken Qualcomm QC. | ||
+ | 10:27:23 From Rich M to Everyone: | ||
+ | Maybe don't place a MagSafe phone on top of your old floppy disks :) | ||
+ | 10:48:13 From tedpk to Everyone: | ||
+ | https:// | ||
+ | 11:06:10 From Harry Forsdick to Everyone: | ||
+ | Here is a video of the Lex250 show from firefly.com: | ||
+ | </ | ||
+ | </ | ||
+ | [[lexingtoncomputergroup|return]] | ||
+ | |||
+ | |||
+ | ====20241113==== | ||
+ | ===Passwords and Passkeys=== | ||
+ | <WRAP prewrap> | ||
+ | < | ||
+ | 10:09:09 From Steve Isenberg to Everyone: | ||
+ | Secret questions work if answer is not related to the question | ||
+ | 10:10:01 From Bob Primak to Everyone: | ||
+ | I think the point is, we don't want to be using the same communication channel for a login and the password reset process. | ||
+ | 10:24:10 From Adam Broun to Everyone: | ||
+ | Replying to " | ||
+ | ..and as long as you don’t reuse the answers | ||
+ | 10:26:39 From Carl Lazarus to Everyone: | ||
+ | Replying to " | ||
+ | A prime number has no factors. | ||
+ | 10:37:28 From Barry Kort to Everyone: | ||
+ | For a while, LCC had an expired certificate, | ||
+ | 10:43:00 From Mitch Wolfe to Everyone: | ||
+ | Examples of bad certificates: | ||
+ | 11:09:20 From Steve Isenberg to Everyone: | ||
+ | There is no mathematical difference between a “Public” key and a “Private” key. Your system makes up two keys that work in a PKI system. Then it picks one as “Private” and the other as “Public” and shares the Public one. | ||
+ | 11:20:23 From Dan Silber to Everyone: | ||
+ | I don't understand. If a password manager generates a different password for each application/ | ||
+ | 11:25:03 From Steve Isenberg to Everyone: | ||
+ | In short, those password hint questions are also used as passwords (as they can bypass your secure password and reset it). Best to use a random response to the password hint questions (or generate another secure password for the answers). | ||
+ | </ | ||
+ | </ | ||
+ | [[lexingtoncomputergroup|return]] | ||
+ | |||
====20241106==== | ====20241106==== |
2024lctgmeetingchats.1730911764.txt.gz · Last modified: 2024.11.06 08:49 by Steve Isenberg