<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Matt Senter</title>
    <description>The latest articles on DEV Community by Matt Senter (@mattsenter).</description>
    <link>https://dev.to/mattsenter</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3931606%2F17899b14-3035-4135-be09-fc925e0215c7.png</url>
      <title>DEV Community: Matt Senter</title>
      <link>https://dev.to/mattsenter</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mattsenter"/>
    <language>en</language>
    <item>
      <title>AI Is Making Hacking Easier. Here's How to Protect Yourself.</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Thu, 19 Nov 2026 14:37:31 +0000</pubDate>
      <link>https://dev.to/mattsenter/ai-is-making-hacking-easier-heres-how-to-protect-yourself-634</link>
      <guid>https://dev.to/mattsenter/ai-is-making-hacking-easier-heres-how-to-protect-yourself-634</guid>
      <description>&lt;p&gt;The short version&lt;/p&gt;

&lt;p&gt;AI-powered hacking makes established security habits more urgent because attackers can automate convincing scams and exploit unpatched software faster. Start with a reputable password manager that generates a unique password for every account, and keep its recovery information securely stored offline. Protect your primary email account with a passkey or strong multi-factor authentication, since your inbox often controls password resets elsewhere. Enable automatic updates, review application permissions, and independently verify unexpected requests using contact information you already trust. For financial accounts, enable transaction alerts, freeze your credit with all three major bureaus, and report unauthorized activity promptly. Keep encrypted copies of important records and a separate backup you can reach if your vault becomes unavailable. AI can help research purchases, but granting it payment credentials and unrestricted spending authority creates additional risks. These measures reduce exposure; they cannot guarantee protection, so prepare a recovery plan before an incident.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclaimer: This article offers general information, not professional cybersecurity, financial, or legal advice. You are responsible for your own security decisions, including actions you take or choose not to take. I accept no responsibility or liability for any resulting losses or damages.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Last night, my mother-in-law texted me after reading a &lt;a href="https://cloud.google.com/blog/topics/threat-intelligence/agentic-threat-activity-crosses-a-significant-threshold" rel="noopener noreferrer"&gt;new Google report about AI-powered cyberattacks&lt;/a&gt;. She had a pretty reasonable question:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"How do we ordinary peeps protect our sensitive personal info?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;My initial response was that the advice hasn't changed all that much. Don't install random applications, be suspicious of links in unexpected emails, use strong passwords, and enable two-factor authentication. What has changed is the scale and speed at which attackers can operate.&lt;/p&gt;

&lt;p&gt;Google's November 16, 2026 report describes hackers using autonomous AI systems to discover vulnerabilities, develop exploits, and conduct multi-stage attacks with significantly less human intervention. Some of these systems can examine software updates, identify the vulnerabilities being patched, and develop working attacks against systems that haven't been updated yet. Other tools help criminals automate phishing campaigns, create convincing fake identities, and scale their operations far beyond what would previously have been practical.&lt;/p&gt;

&lt;p&gt;Much of the report concerns attacks against businesses and their infrastructure rather than individual consumers. That's an important distinction, but it isn't particularly comforting when those businesses are holding our personal information.&lt;/p&gt;

&lt;p&gt;The good news is that protecting yourself doesn't require understanding how these attacks work. Most of the recommendations are things we've been telling people to do for years. The challenge has always been getting people to actually follow them.&lt;/p&gt;

&lt;p&gt;My exchange with my mother-in-law turned into a longer conversation about password managers, banking information, and the practical things an ordinary person can do to stay safe. I figured it was worth writing down.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stop trying to remember all your passwords
&lt;/h2&gt;

&lt;p&gt;The first thing I recommended was getting a password manager, specifically &lt;a href="https://1password.com/" rel="noopener noreferrer"&gt;1Password&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;My mother-in-law responded:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Thanks...never heard of 1Password. Will look it up. Long password? Good strategy. But how do I remember it with my aging brain?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That's actually the entire point of a password manager. &lt;strong&gt;You're not supposed to remember your passwords anymore.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A password manager is a secure, encrypted vault that remembers your usernames and passwords for you. When you create an account on a website, it can generate a long, completely random password. When you return to that website, it automatically fills in your login information.&lt;/p&gt;

&lt;p&gt;You don't need to know what that password is. It could be 30 random characters long, and you would never need to memorize or type it. In fact, I couldn't tell you what the passwords are for almost all of my own accounts.&lt;/p&gt;

&lt;p&gt;Instead, you remember one strong password that protects your password manager. Ideally, that's a long, unique passphrase made from several randomly chosen, unrelated words, rather than something predictable like your dog's name and birthday. On supported devices, you can usually unlock the manager with Face ID or your fingerprint, although you'll occasionally need your account password.&lt;/p&gt;

&lt;p&gt;1Password has another security feature called a Secret Key, which I'll explain shortly. You don't have to memorize that either.&lt;/p&gt;

&lt;p&gt;The important part is that every account gets a different password. If some random shopping website gets hacked and exposes its customer credentials, the password you used there is worthless to someone trying to log into your bank or email.&lt;/p&gt;

&lt;p&gt;You can also use a password manager on multiple devices. Your phone, laptop, and desktop can all have access to the same encrypted vault. You don't have to remember passwords when switching between them.&lt;/p&gt;

&lt;p&gt;1Password isn't the only good option. &lt;a href="https://support.apple.com/guide/passwords/welcome/mac" rel="noopener noreferrer"&gt;Apple Passwords&lt;/a&gt; is built into Apple's ecosystem and is free. &lt;a href="https://bitwarden.com/" rel="noopener noreferrer"&gt;Bitwarden&lt;/a&gt; is another well-established option with a free tier. I particularly like 1Password, but the important decision is to start using a reputable password manager rather than continuing to invent and reuse your own passwords.&lt;/p&gt;

&lt;p&gt;For someone new to this, I'd suggest starting with your email and financial accounts, then gradually updating other passwords. There's no reason to spend an entire afternoon changing hundreds of credentials.&lt;/p&gt;

&lt;h3&gt;
  
  
  Yes, you can write down your master password
&lt;/h3&gt;

&lt;p&gt;For years, we've been told never to write down passwords. That's generally sensible advice when we're talking about leaving passwords on sticky notes attached to monitors, but it ignores an important distinction between physical and digital security.&lt;/p&gt;

&lt;p&gt;The United Kingdom's &lt;a href="https://www.ncsc.gov.uk/collection/top-tips-for-staying-secure-online/password-managers" rel="noopener noreferrer"&gt;National Cyber Security Centre also says writing passwords down can be done safely&lt;/a&gt;. Its guidance specifically discusses journals and password books as an arrangement that can suit people who receive regular help from family members managing their online accounts. It emphasizes choosing strong passwords, considering who can physically access the record, and checking whether a service's terms permit writing passwords down. Simply hiding the book may not be enough, and paper still requires you to recognize fraudulent websites yourself.&lt;/p&gt;

&lt;p&gt;A criminal sitting halfway around the world can attempt to steal your online credentials using phishing, malware, compromised websites, or automated attacks. That same criminal cannot simply reach into a locked safe in your house and retrieve a piece of paper.&lt;/p&gt;

&lt;p&gt;Physical security and digital security involve different threats. A piece of paper stored in a secure location is not exposed to the same remote attacks as an online account or an unencrypted file sitting on your desktop.&lt;/p&gt;

&lt;p&gt;That doesn't make paper inherently safe. Someone with physical access could steal it. It could be lost, destroyed in a fire, or photographed by someone who shouldn't see it. The point is that those risks are different and can be managed with appropriate physical safeguards.&lt;/p&gt;

&lt;p&gt;This is also &lt;a href="https://support.1password.com/emergency-kit/" rel="noopener noreferrer"&gt;1Password's own recommendation&lt;/a&gt;: print your Emergency Kit, write your account password on at least one printed copy, and store it safely. The company specifically suggests a safe deposit box as one option. I recommend a similarly secure location, such as a locked home safe. The kit includes your Secret Key, which is an additional randomly generated secret used to protect your encrypted vault. Together, your account password and Secret Key are extremely sensitive, so don't leave that document in an unlocked drawer or email yourself a photograph of it.&lt;/p&gt;

&lt;p&gt;If you use two-factor authentication on your 1Password account, make sure you've also planned how to recover that access if your phone is lost. Follow the company's recovery instructions rather than assuming the Emergency Kit alone covers every situation.&lt;/p&gt;

&lt;p&gt;A securely stored recovery document isn't an embarrassing workaround for somebody who can't remember passwords. It's a deliberate backup mechanism. You may never need it, but if you lose your phone or forget your account password, you'll be grateful you prepared it.&lt;/p&gt;

&lt;p&gt;For couples and families, &lt;a href="https://support.1password.com/family-recovery-plan/" rel="noopener noreferrer"&gt;1Password Families&lt;/a&gt; also offers shared vaults and account-recovery capabilities. You can keep your personal passwords private while sharing things like household utility accounts. With the right setup, a designated family organizer can help another family member recover access.&lt;/p&gt;

&lt;p&gt;The goal is to make your digital life safer and easier, not give you another complicated system to worry about.&lt;/p&gt;

&lt;h2&gt;
  
  
  Isn't a password manager a single point of failure?
&lt;/h2&gt;

&lt;p&gt;A couple of months ago, I &lt;a href="https://www.reddit.com/r/askanything/comments/1wuc63g/why_are_some_people_so_averse_to_or_otherwise/" rel="noopener noreferrer"&gt;asked Reddit why so many people resist using password managers&lt;/a&gt;. I received a lot of responses, and one objection came up repeatedly: putting all your passwords in one place creates a single point of failure.&lt;/p&gt;

&lt;p&gt;It's a legitimate concern. If someone compromises your unlocked password vault, they could potentially access every account stored inside it. There's no reason to pretend otherwise. The question is whether that risk is greater than the risks introduced by whatever alternative you've devised for yourself.&lt;/p&gt;

&lt;p&gt;One commenter told me they refused to use a password manager because they kept their passwords in an encrypted file. Another kept a physical notebook locked in a wall safe. Others described personal formulas for generating passwords based on the websites they visited.&lt;/p&gt;

&lt;p&gt;I found the encrypted-file response particularly interesting. That person had effectively created their own password manager, only without the features and protections offered by dedicated software.&lt;/p&gt;

&lt;p&gt;The physical notebook deserves a little more consideration. Unlike a file stored on an internet-connected computer, a notebook sitting in a locked safe can't be directly accessed through a remote software vulnerability. For someone with very few accounts, it may be a perfectly reasonable system.&lt;/p&gt;

&lt;p&gt;The problem isn't that paper is inherently insecure. It's that paper becomes increasingly impractical as the number of accounts grows.&lt;/p&gt;

&lt;p&gt;If you have a hundred online accounts, are you going to write down a unique, randomly generated password for each one? What happens when you're traveling and need to sign in somewhere? Do you carry the notebook, potentially losing it or exposing it to theft? What happens when you need to update a password on your phone and the notebook is at home?&lt;/p&gt;

&lt;p&gt;The notebook also doesn't provide any protection against typing a password into a fraudulent website. A password manager can recognize which website a credential belongs to and generally won't offer to fill it into an unrelated domain.&lt;/p&gt;

&lt;p&gt;If a notebook works for your particular circumstances, I'm not going to tell you it's inherently unsafe. I am going to suggest that a properly configured password manager solves considerably more problems for anyone who regularly uses modern online services.&lt;/p&gt;

&lt;p&gt;Personal password formulas are especially problematic. Taking a familiar password and modifying it based on the website might produce different passwords, but different doesn't necessarily mean unpredictable. Once an attacker discovers the pattern, the security of every password generated using it may be compromised.&lt;/p&gt;

&lt;p&gt;Professional password managers approach the problem differently. They generate independent, random credentials and protect them inside an encrypted vault.&lt;/p&gt;

&lt;p&gt;With 1Password, your vault is encrypted on your device before being uploaded to its servers. The company doesn't possess the information necessary to decrypt it. Your account password and a separately generated Secret Key are combined to protect your vault. The Secret Key is generated locally and isn't available to 1Password, meaning someone who steals encrypted vault data from the company's servers doesn't automatically have what they need to decrypt it.&lt;/p&gt;

&lt;p&gt;This is a sophisticated security architecture, which you can read about in &lt;a href="https://1password.com/files/1Password-White-Paper.pdf" rel="noopener noreferrer"&gt;1Password's security design white paper [PDF]&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Of course, password managers aren't invulnerable. In 2022, &lt;a href="https://blog.lastpass.com/posts/notice-of-security-incident" rel="noopener noreferrer"&gt;LastPass suffered a major security breach&lt;/a&gt; in which attackers stole backups containing customers' encrypted vaults along with some unencrypted information, including website addresses. That created opportunities for attackers to attempt offline password cracking, particularly against vaults protected by weak master passwords.&lt;/p&gt;

&lt;p&gt;That's a serious incident, and I wouldn't dismiss anyone's concern about it. The lesson, however, isn't that we should abandon password managers. It's that the security architecture of the manager matters, along with how you configure and use it.&lt;/p&gt;

&lt;p&gt;There's also a difference between someone stealing an encrypted copy of your vault and someone compromising your computer while that vault is unlocked. Malware running on your computer may be able to steal credentials after they've been decrypted for use. A password manager isn't a substitute for securing your devices.&lt;/p&gt;

&lt;p&gt;Losing access to your vault is another legitimate concern. That's why I recommend having the manager installed on more than one trusted device, keeping recovery information safely stored offline, and configuring recovery options before you need them.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://pages.nist.gov/800-63-4/sp800-63b.html" rel="noopener noreferrer"&gt;National Institute of Standards and Technology (NIST)&lt;/a&gt; explicitly supports the use of password managers, noting that they encourage stronger, unique passwords and reduce the burden of remembering credentials.&lt;/p&gt;

&lt;p&gt;I think the supposed single point of failure is often misunderstood. A password manager does concentrate some risk, but it also dramatically reduces the number of places where your own password habits can create vulnerabilities.&lt;/p&gt;

&lt;p&gt;Instead of reusing the same password across 50 websites, you're using 50 independent passwords. A breach at one website no longer compromises your credentials everywhere else.&lt;/p&gt;

&lt;p&gt;I'm a software engineer, and I'm not going to pretend that a homegrown system I invented is automatically safer than one developed specifically to protect credentials. I could build a password manager, but then I'd also be responsible for maintaining its encryption, security updates, backup systems, synchronization, and recovery mechanisms.&lt;/p&gt;

&lt;p&gt;I'd rather spend my time doing something else.&lt;/p&gt;

&lt;p&gt;For the overwhelming majority of people, I suspect their personal password system is substantially less secure than they think. A professionally designed password manager isn't perfect, but it's likely a much better solution.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use passkeys and multi-factor authentication
&lt;/h2&gt;

&lt;p&gt;Password managers are excellent, but passwords themselves are slowly becoming less necessary.&lt;/p&gt;

&lt;p&gt;You may have noticed websites offering something called a &lt;em&gt;passkey&lt;/em&gt;. Rather than authenticating with a traditional password, a passkey uses cryptography to prove your identity. You generally approve the login using your phone, fingerprint, face, or device PIN.&lt;/p&gt;

&lt;p&gt;The advantage isn't just convenience. Passkeys are designed to be resistant to phishing. A fake banking website can't simply trick you into giving it a reusable passkey the way it might trick you into entering a password.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://fidoalliance.org/passkeys/" rel="noopener noreferrer"&gt;FIDO Alliance&lt;/a&gt;, which develops the standards behind passkeys, explains the technical details for anyone interested.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1Password can create, save, and manage passkeys for you, just like regular passwords.&lt;/strong&gt; More importantly, it can securely synchronize those passkeys across your supported devices, including Macs, Windows computers, iPhones, and Android devices. That means you aren't necessarily dependent on one phone or one manufacturer's ecosystem to use them. &lt;a href="https://1password.com/product/passkeys" rel="noopener noreferrer"&gt;1Password explains its passkey support here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This is one of my favorite developments in authentication. Instead of remembering passwords or worrying about which device holds a particular passkey, you let your password manager handle those details.&lt;/p&gt;

&lt;p&gt;For services that still require passwords, enable multi-factor authentication, commonly abbreviated as MFA.&lt;/p&gt;

&lt;h3&gt;
  
  
  What exactly is MFA?
&lt;/h3&gt;

&lt;p&gt;MFA means requiring more than one type of evidence to prove you're the person attempting to sign in.&lt;/p&gt;

&lt;p&gt;These factors generally fall into three categories: something you know, such as a password; something you have, such as your phone or a physical security key; and something you are, such as your fingerprint or face.&lt;/p&gt;

&lt;p&gt;When a website requires a password and a code generated by your phone, that's multi-factor authentication. Two-factor authentication, or 2FA, is a specific form of MFA that uses two factors.&lt;/p&gt;

&lt;p&gt;You may already be familiar with websites that text you a six-digit code after you've entered your password. That's better than requiring a password alone, but it's no longer the preferred approach when stronger alternatives are available.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;NIST's current digital identity guidelines classify authentication using SMS or voice calls over the telephone network as a "restricted authenticator."&lt;/strong&gt; This doesn't mean text-message verification has been prohibited, but it does mean NIST recognizes significant security weaknesses and places additional requirements on its use.&lt;/p&gt;

&lt;p&gt;You can read the guidance directly in &lt;a href="https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63B-4.pdf" rel="noopener noreferrer"&gt;NIST SP 800-63B-4 [PDF]&lt;/a&gt;, particularly the sections on authentication using the public telephone network and restricted authenticators.&lt;/p&gt;

&lt;p&gt;The problem is that phone numbers aren't particularly secure identities. Criminals can sometimes convince a mobile carrier to transfer your number to another device, an attack known as SIM swapping. There are also weaknesses in the telephone network that can permit interception of messages.&lt;/p&gt;

&lt;p&gt;A better alternative, when passkeys aren't available, is an authenticator application.&lt;/p&gt;

&lt;p&gt;An authenticator app, such as &lt;a href="https://support.google.com/accounts/answer/1066447" rel="noopener noreferrer"&gt;Google Authenticator&lt;/a&gt;, &lt;a href="https://www.microsoft.com/en-us/security/mobile-authenticator-app" rel="noopener noreferrer"&gt;Microsoft Authenticator&lt;/a&gt;, or &lt;a href="https://2fas.com/" rel="noopener noreferrer"&gt;2FAS&lt;/a&gt;, generates temporary verification codes directly on your device. Typically, you scan a QR code when configuring MFA for a website. After that, the app generates a new code approximately every 30 seconds.&lt;/p&gt;

&lt;p&gt;The important distinction is that these codes aren't delivered through your phone number. Someone who manages to hijack your phone number doesn't automatically gain access to the codes generated by your authenticator app.&lt;/p&gt;

&lt;p&gt;1Password can also store and generate these one-time codes, which is convenient because it can fill them automatically alongside your passwords. There is a tradeoff in keeping both your password and its verification code in the same vault, since someone who compromises that vault could obtain both. For especially sensitive accounts, a separate authenticator or physical security key can provide additional separation.&lt;/p&gt;

&lt;p&gt;Authenticator apps are still vulnerable to certain phishing attacks. A convincing fake website could trick you into entering a valid code and immediately relay it to the real service. Passkeys and properly configured physical security keys offer stronger phishing resistance because their authentication is tied to the legitimate service.&lt;/p&gt;

&lt;p&gt;If a website only supports SMS verification, use it rather than leaving MFA disabled. Just recognize that there are better options when they're available.&lt;/p&gt;

&lt;p&gt;One particularly important rule: never give someone a verification code they unexpectedly ask you to provide. If you receive a login approval notification you didn't initiate, reject it. Attackers sometimes already have the password and are simply trying to convince you to complete the login for them.&lt;/p&gt;

&lt;p&gt;Passkeys and MFA make account takeovers considerably harder, but they're only as strong as the recovery procedures surrounding them. If a website lets someone bypass these protections through an insecure account-recovery process, much of that protection can be undermined.&lt;/p&gt;

&lt;p&gt;I've &lt;a href="https://www.mattsenter.com/blog/microsoft-gave-my-sons-account-back-it-shouldnt-have-taken-60000-views" rel="noopener noreferrer"&gt;written about this problem before&lt;/a&gt;, after my son's Microsoft account was compromised and recovering it became a rather ridiculous ordeal. We eventually got it back, but the experience reinforced my belief that account recovery is every bit as important as account authentication.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your email account is the skeleton key to your digital life
&lt;/h2&gt;

&lt;p&gt;We've somehow decided that the email address we hand out to practically everyone should also be our universal username, our primary means of proving our identity, and the mechanism for recovering access to our most sensitive accounts.&lt;/p&gt;

&lt;p&gt;Think about how absurd that is. The same address that receives restaurant promotions and unsolicited sales pitches can also be used to initiate a password reset for your bank account.&lt;/p&gt;

&lt;p&gt;The address itself isn't supposed to be secret, and simply knowing someone's username doesn't authenticate you. The real design failure is that we've made an openly accessible communication channel a critical part of our identity and account-recovery infrastructure.&lt;/p&gt;

&lt;p&gt;It's an extraordinary amount of trust to place in a technology originally designed to deliver messages between computers.&lt;/p&gt;

&lt;p&gt;I've &lt;a href="https://www.mattsenter.com/blog/email-is-awful-ai-can-fix-it-if-we-protect-the-inbox" rel="noopener noreferrer"&gt;written before about how badly email needs to be replaced&lt;/a&gt;. It's one of the reasons I'm building &lt;a href="https://www.mattsenter.com/projects/premail" rel="noopener noreferrer"&gt;Premail&lt;/a&gt;, an AI-powered email assistant designed to make email more manageable while we remain stuck with it.&lt;/p&gt;

&lt;p&gt;Premail addresses part of this problem by using AI to identify spam and other unwanted messages, then applying the rules you choose to archive, quarantine, or trash them. Its Pro feature, Reputation Shield, also checks sender domains against the Spamhaus Domain Block List for known spam, phishing, and malware infrastructure. That adds a useful layer of protection, but it can't tell you that every message left in your inbox is safe. New scams and compromised legitimate accounts can still get through. You can run the AI classification locally with Ollama or Apple Intelligence, keeping that processing on your computer; if you choose a cloud AI provider, the content needed for classification goes to that provider. No Premail server processes your mail.&lt;/p&gt;

&lt;p&gt;Unfortunately, we're not getting rid of email tomorrow. For now, your primary email account deserves at least as much protection as your bank account.&lt;/p&gt;

&lt;p&gt;Use a passkey or strong MFA, review your account-recovery settings, and periodically check which devices are signed in. Make sure that an old phone number or forgotten recovery address can't be used to regain access to your account.&lt;/p&gt;

&lt;p&gt;You might also consider using a separate, private email address for financial accounts rather than the address you give out publicly. Email aliases can also help you avoid exposing the same address everywhere. Neither approach makes an account inherently secure, but they can reduce exposure to targeted phishing and make suspicious messages easier to recognize.&lt;/p&gt;

&lt;p&gt;If someone compromises your primary inbox, they may be able to reset passwords and take over other accounts. Protecting email is really about protecting everything connected to it.&lt;/p&gt;

&lt;p&gt;Someday, I hope we stop using email addresses as the foundation of digital identity. Until then, treat your inbox as one of your most valuable and vulnerable digital assets.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stop trusting unexpected messages
&lt;/h2&gt;

&lt;p&gt;For years, we've taught people to look for spelling mistakes, awkward grammar, and strange formatting in phishing emails. Those were useful warning signs when criminals were sending poorly written messages by the thousands.&lt;/p&gt;

&lt;p&gt;AI has made that advice considerably less reliable.&lt;/p&gt;

&lt;p&gt;A criminal can now generate polished messages in virtually any language, personalize them using information collected from data breaches or social media, and make them look remarkably convincing.&lt;/p&gt;

&lt;p&gt;The practical response is to change how you handle unexpected requests.&lt;/p&gt;

&lt;p&gt;If you receive an email claiming there's a problem with your bank account, don't click the link in the message to investigate. Open your banking app or independently navigate to the bank's website. If someone calls claiming to be from your bank, hang up and call the number on your card.&lt;/p&gt;

&lt;p&gt;That doesn't mean every link in every email is malicious. It's perfectly normal to receive legitimate links. The point is that you shouldn't rely on the very message making an alarming claim to tell you how to verify it.&lt;/p&gt;

&lt;p&gt;This applies to text messages, phone calls, social media messages, and even video calls.&lt;/p&gt;

&lt;p&gt;AI voice cloning has made it possible to impersonate someone's voice using samples of recorded audio. Someone calling and claiming to be your grandchild in an emergency may sound remarkably convincing. The &lt;a href="https://consumer.ftc.gov/consumer-alerts/2026/11/grandpa-i-need-your-help-how-spot-and-avoid-grandkid-scams" rel="noopener noreferrer"&gt;FTC specifically warns about these scams&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If someone unexpectedly asks for money, sensitive information, or urgent action, independently verify their identity using contact information you already trust. Calling them back or reaching another family member is far more reliable than trying to determine whether their voice sounds real.&lt;/p&gt;

&lt;p&gt;You could even establish a family verification phrase for unusual emergencies, although it should supplement rather than replace independently contacting the person. Don't put that phrase on social media or share it broadly.&lt;/p&gt;

&lt;p&gt;The goal isn't to become an expert at recognizing AI-generated deception. It's to develop habits that still work when the deception is convincing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep your software updated, and be careful what you install
&lt;/h2&gt;

&lt;p&gt;This is probably the least exciting recommendation, but Google's report makes it especially relevant.&lt;/p&gt;

&lt;p&gt;Attackers are increasingly using AI to examine security patches and develop exploits for vulnerabilities that have already been identified. That shortens the time available for organizations and individuals to install updates before criminals start exploiting those flaws.&lt;/p&gt;

&lt;p&gt;Turn on automatic updates for your operating system, web browser, and applications. Don't ignore updates for weeks because they seem inconvenient. Keep your home router updated as well, replacing it if its manufacturer no longer provides security patches.&lt;/p&gt;

&lt;p&gt;Be selective about what you install. Random browser extensions, unfamiliar utilities, pirated software, and applications downloaded from questionable websites can introduce security risks. Even legitimate-looking applications can request access to sensitive information they don't need.&lt;/p&gt;

&lt;p&gt;There's another concern that's growing alongside AI-powered hacking: AI-powered software development.&lt;/p&gt;

&lt;p&gt;AI has made it remarkably easy for people with little or no programming experience to produce applications. Someone can describe an app in natural language, have an AI generate thousands of lines of code, and publish something that appears to work without necessarily understanding how any of it works internally.&lt;/p&gt;

&lt;p&gt;I think that's a potentially enormous security problem.&lt;/p&gt;

&lt;p&gt;A functioning application isn't necessarily a secure application. Code that compiles and passes a few basic tests can still contain serious vulnerabilities, expose private information, mishandle authentication, or grant itself unnecessary permissions.&lt;/p&gt;

&lt;p&gt;Developers who don't understand these risks may not even know what questions to ask their AI coding assistants. They may see a working interface and assume the underlying software is production-ready.&lt;/p&gt;

&lt;p&gt;This isn't just speculation. In its &lt;a href="https://www.veracode.com/blog/genai-code-security-report/" rel="noopener noreferrer"&gt;2025 GenAI Code Security Report&lt;/a&gt;, Veracode tested AI-generated code across a variety of programming languages and security-sensitive tasks. In that evaluation, 45% of generated solutions contained a known security flaw. That's not a measurement of every AI-generated application, but it's a useful reminder that code which appears to work can still be dangerously insecure.&lt;/p&gt;

&lt;p&gt;Researchers at Georgia Tech have also been &lt;a href="https://news.research.gatech.edu/2026/04/13/bad-vibes-ai-generated-code-vulnerable-researchers-warn" rel="noopener noreferrer"&gt;tracking security vulnerabilities associated with AI-generated software&lt;/a&gt;, examining how these problems reach real-world applications.&lt;/p&gt;

&lt;p&gt;I've spent nearly 30 years developing software, and I use AI coding tools extensively. I think they're extraordinary productivity tools. They don't eliminate the need to understand software architecture, cryptography, authentication, privacy, memory safety, input validation, or the countless other considerations involved in producing reliable software.&lt;/p&gt;

&lt;p&gt;When I release an application, I'm responsible for the design decisions behind it. That includes what information it can access, which permissions it requests, how it handles sensitive data, and what happens when something goes wrong. AI can help implement those decisions, but I don't expect it to make them correctly without informed direction and review.&lt;/p&gt;

&lt;p&gt;Not everyone publishing an attractive AI-generated application has that experience, and consumers generally have no way to determine whether the person behind a particular product understands the security implications of what they've built.&lt;/p&gt;

&lt;p&gt;I expect this to become an increasingly important distinction as AI makes it possible to produce and distribute software at unprecedented speed.&lt;/p&gt;

&lt;p&gt;None of this means every AI-generated application is unsafe, or that every traditionally developed application is secure. Experienced developers make mistakes, too. The concern is that AI has dramatically reduced the effort required to create software without equivalently reducing the expertise required to make it secure.&lt;/p&gt;

&lt;p&gt;I also don't believe every application outside an official app store is automatically dangerous. I develop software that sometimes requires powerful system permissions, and there are perfectly legitimate reasons to distribute software independently. You should, however, know who developed the application, understand why it needs the permissions it requests, and obtain it from a trustworthy source.&lt;/p&gt;

&lt;p&gt;Browser extensions deserve particular scrutiny because some can access information on the websites you visit. You probably don't need every extension you've installed over the past five years. Review them occasionally and remove anything you no longer use or trust.&lt;/p&gt;

&lt;p&gt;Most people don't need a complicated collection of security utilities. Modern operating systems already include substantial protections. Keeping those protections enabled, installing updates, and avoiding questionable software will get you a long way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Protect your financial accounts, not just your passwords
&lt;/h2&gt;

&lt;p&gt;Securing your banking credentials is important, but there are additional precautions worth taking.&lt;/p&gt;

&lt;p&gt;First, enable transaction notifications. Most banks and credit card issuers allow you to receive alerts when money moves, purchases occur, or unusual activity is detected. I recommend using those features rather than relying solely on monthly statements to discover problems.&lt;/p&gt;

&lt;p&gt;Second, freeze your credit with &lt;a href="https://www.equifax.com/" rel="noopener noreferrer"&gt;Equifax&lt;/a&gt;, &lt;a href="https://www.experian.com/" rel="noopener noreferrer"&gt;Experian&lt;/a&gt;, and &lt;a href="https://www.transunion.com/" rel="noopener noreferrer"&gt;TransUnion&lt;/a&gt;. Credit freezes are free, don't affect your credit score, and make it much harder for someone to open new credit accounts in your name. You can temporarily lift the freezes when you need to apply for credit. The &lt;a href="https://consumer.ftc.gov/articles/credit-freezes-and-fraud-alerts" rel="noopener noreferrer"&gt;FTC explains the process here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A credit freeze won't stop someone from stealing money from an existing bank account, so don't confuse credit protection with account security.&lt;/p&gt;

&lt;p&gt;Third, secure your phone number. Many websites still use SMS messages for authentication and account recovery. Criminals sometimes attempt to transfer a victim's phone number to a device they control, allowing them to intercept verification messages. Your mobile carrier may offer an account PIN, port-out protection, or both. The &lt;a href="https://consumer.ftc.gov/consumer-alerts/2019/10/sim-swap-scams-how-protect-yourself" rel="noopener noreferrer"&gt;FTC has advice on SIM-swapping attacks&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Finally, maintain some independent financial records.&lt;/p&gt;

&lt;p&gt;My mother-in-law's question got me thinking about whether people should print bank statements or maintain offline copies of their financial information. I think there's value in doing so, although not necessarily in printing hundreds of pages every year.&lt;/p&gt;

&lt;p&gt;Consider periodically downloading statements from your bank, brokerage, retirement accounts, and other important financial institutions. Keep them in encrypted storage separate from the institutions themselves. A physically secured paper copy of selected important records is also reasonable.&lt;/p&gt;

&lt;p&gt;Here's another reason I like 1Password: &lt;strong&gt;it's not just a password manager. It's a general-purpose encrypted vault for sensitive information.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;1Password has dedicated entries for things like bank accounts, credit cards, identification documents, and other sensitive records. You can securely store account and routing numbers, important financial details, and notes associated with particular institutions.&lt;/p&gt;

&lt;p&gt;You can also &lt;a href="https://support.1password.com/files/" rel="noopener noreferrer"&gt;store documents directly in 1Password&lt;/a&gt;, including PDF copies of bank statements, insurance policies, and other important records, subject to your plan's storage limits.&lt;/p&gt;

&lt;p&gt;That means you don't necessarily need to invent another system for organizing and protecting sensitive financial information. You can keep important records alongside the credentials you use to access the institutions that issued them.&lt;/p&gt;

&lt;p&gt;For example, you might create a bank account entry containing the institution's name, account number, routing number, customer service telephone number, and other details. You could then attach a recent statement or maintain separate document entries for important records.&lt;/p&gt;

&lt;p&gt;If you use a family account, you can also selectively share access to certain information with trusted family members while keeping other entries private.&lt;/p&gt;

&lt;p&gt;There's a tradeoff here, of course. Storing financial documents in your password manager means those documents share the security and availability characteristics of the vault. That's generally a reasonable choice for convenience and encryption, but I wouldn't make it the only place those records exist. Keep a separate, securely maintained backup for situations where you can't access the vault.&lt;/p&gt;

&lt;p&gt;There's also an important limitation: &lt;strong&gt;a printed or downloaded bank statement isn't definitive proof of your account history.&lt;/strong&gt; Paper statements and PDFs are easily fabricated or altered. They can help you identify discrepancies and reconstruct what happened, but a dispute may ultimately require the financial institution's own transaction records and other independently verifiable evidence.&lt;/p&gt;

&lt;p&gt;Keeping copies of records is about preserving information, not guaranteeing that the records will be accepted as proof.&lt;/p&gt;

&lt;p&gt;There's also a security tradeoff. Those downloaded statements may contain sensitive account information, addresses, and transaction details. Don't leave them sitting in an unencrypted folder or a publicly accessible cloud drive. Physical copies belong somewhere secure, and old records containing sensitive information should be shredded when you no longer need them.&lt;/p&gt;

&lt;p&gt;More importantly, don't assume that discovering unauthorized transactions months later will provide the same protections as reporting them immediately. Under federal rules governing many electronic fund transfers, your liability can depend on how quickly you notify your bank. The &lt;a href="https://www.consumerfinance.gov/ask-cfpb/how-do-i-get-my-money-back-after-i-discover-an-unauthorized-transaction-or-money-missing-from-my-bank-account-en-1017/" rel="noopener noreferrer"&gt;Consumer Financial Protection Bureau&lt;/a&gt; explains these protections, including a commonly applicable 60-day reporting deadline after a statement showing an unauthorized transaction is sent. Other deadlines can be shorter, particularly when a debit card is lost or stolen.&lt;/p&gt;

&lt;p&gt;Don't wait until tax season to find out that somebody has been stealing from you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Please stop taking financial security advice from billionaires (and trillionaires, for that matter) selling you AI agents
&lt;/h2&gt;

&lt;p&gt;There's another side to this AI security discussion that I find particularly troubling.&lt;/p&gt;

&lt;p&gt;While Google is warning about criminals using autonomous AI systems to compromise infrastructure and steal information, technology companies are simultaneously encouraging consumers to give increasingly autonomous AI systems access to their personal information, accounts, and money.&lt;/p&gt;

&lt;p&gt;In October 2026, &lt;a href="https://www.thepoke.com/2026/10/13/elon-musk-encouraged-people-to-share-photos-of-their-credit-cards-with-his-ai-bot/" rel="noopener noreferrer"&gt;Elon Musk encouraged people to photograph their credit cards and upload the images to Grok&lt;/a&gt;, explaining that the AI agent could search the internet for the best deal and complete the purchase.&lt;/p&gt;

&lt;p&gt;He subsequently suggested that providing a screenshot of a credit card was the easiest way to enable shopping through Grok. He compared the practice to handing your card to a restaurant employee.&lt;/p&gt;

&lt;p&gt;On October 15, he also &lt;a href="https://www.businessinsider.com/elon-musk-spacex-will-pay-users-back-grok-purchase-mistakes-2026-10" rel="noopener noreferrer"&gt;promised that SpaceX would make customers whole&lt;/a&gt; if Grok made a purchasing mistake or leaked their card information. The promise came without clearly defined terms explaining what kinds of losses would actually be covered or how customers could obtain reimbursement.&lt;/p&gt;

&lt;p&gt;I'm going to be very clear about this: &lt;strong&gt;Do not upload a photograph of your credit card to a chatbot and give it unrestricted authority to spend your money.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We have spent decades trying to protect sensitive financial information from unnecessary exposure. Now we're being encouraged to hand that information to experimental autonomous systems for the convenience of not having to complete our own purchases.&lt;/p&gt;

&lt;p&gt;The restaurant comparison is particularly ridiculous because it ignores the most important difference between a human waiter and an autonomous AI agent: scale.&lt;/p&gt;

&lt;p&gt;When I hand my credit card to a waiter, I'm handing it to one person in one physical location to complete one particular transaction. There's certainly some risk involved, but the scope of that interaction is relatively limited.&lt;/p&gt;

&lt;p&gt;An AI agent doesn't necessarily operate under those same constraints.&lt;/p&gt;

&lt;p&gt;Depending on how it's designed, an autonomous agent can execute operations at machine speed, communicate with other systems, delegate work to additional agents, and potentially replicate its operations across enormous numbers of concurrent processes.&lt;/p&gt;

&lt;p&gt;This doesn't mean Grok itself is literally a self-replicating system with unlimited purchasing authority. It means the technology we're being encouraged to trust is capable of operating at a scale completely unlike a human restaurant employee.&lt;/p&gt;

&lt;p&gt;Handing a credit card to an unrestricted autonomous system could, in principle, become the equivalent of handing that same card to a million waiters simultaneously, each capable of taking actions without waiting for your explicit approval.&lt;/p&gt;

&lt;p&gt;That's not remotely the same security proposition.&lt;/p&gt;

&lt;p&gt;I have no objection to using AI to research products, compare prices, or recommend purchases. I use AI extensively myself, both personally and professionally. There is, however, a substantial difference between allowing an agent to find a product and giving it the authority and credentials to purchase that product on your behalf.&lt;/p&gt;

&lt;p&gt;There are safer ways to build this technology. Single-use payment credentials, restricted payment tokens, transaction limits, merchant restrictions, and explicit approval before purchases can reduce risk. Those protections are not equivalent to photographing your everyday credit card and dropping it into a conversation with an AI.&lt;/p&gt;

&lt;p&gt;The larger problem is the advice coming from people who have an enormous financial incentive to convince us to adopt their products.&lt;/p&gt;

&lt;p&gt;Please stop treating billionaires and trillionaires as authorities on personal security simply because they're wealthy and involved in technology. Their companies stand to benefit when consumers trust these systems with more information and more authority. That conflict of interest should be obvious.&lt;/p&gt;

&lt;p&gt;Their view of financial risk can also be astonishingly detached from the experiences of ordinary people. A financial mistake that barely registers for someone worth billions of dollars can be devastating to a household living paycheck to paycheck. Even when a bank eventually reverses an unauthorized transaction, the resulting disruption can be substantial.&lt;/p&gt;

&lt;p&gt;I'm not suggesting that wealthy technology founders have nothing valuable to say. I'm suggesting that their enthusiasm for their own products should not be mistaken for an independent assessment of the risks those products impose on everyone else.&lt;/p&gt;

&lt;p&gt;Billionaire optimism is not a security model, and the ability to build or finance a technology doesn't automatically confer good judgment about how ordinary people should use it.&lt;/p&gt;

&lt;p&gt;I also find something deeply contradictory about encouraging consumers to surrender control over their financial decisions at the same time we're learning how easily autonomous AI systems can be manipulated or exploited.&lt;/p&gt;

&lt;p&gt;AI agents can make mistakes. They can misunderstand instructions. They can encounter malicious content designed to redirect their behavior, including prompt-injection attacks embedded in websites or other material the agent processes. These aren't merely theoretical concerns for anyone building systems that allow AI to interact with the outside world.&lt;/p&gt;

&lt;p&gt;When an AI agent is only summarizing an article, a mistake might produce a bad summary. When it has permission to move money or make purchases, the consequences can be considerably more serious.&lt;/p&gt;

&lt;p&gt;Use AI where it helps you. Be much more cautious about granting it access to sensitive information or the authority to perform consequential actions without your approval.&lt;/p&gt;

&lt;p&gt;For now, I'd let an AI help me decide what to buy. I'd still make the purchase myself.&lt;/p&gt;

&lt;h2&gt;
  
  
  Have a recovery plan before something goes wrong
&lt;/h2&gt;

&lt;p&gt;Most security advice focuses on preventing attacks, but it's also worth considering what happens if somebody succeeds.&lt;/p&gt;

&lt;p&gt;What would you do if your email account were compromised tomorrow? Could you still access your password manager? Would you know how to contact your bank without relying on information stored in your email? Do you have backup copies of important documents and photos?&lt;/p&gt;

&lt;p&gt;A small amount of preparation makes these situations considerably easier to manage.&lt;/p&gt;

&lt;p&gt;Keep important recovery codes and emergency account information somewhere secure and independent of the accounts they protect. Back up important files, preferably with at least one copy that malware or a compromised cloud account can't easily delete. Make sure a trusted family member knows where essential emergency information is kept.&lt;/p&gt;

&lt;p&gt;For people using a password manager, this is particularly important. Your password manager should make your life easier, but you should also know how to recover access if your phone is lost, your computer dies, or you forget your account password.&lt;/p&gt;

&lt;p&gt;If you discover an account compromise, use a trusted device to change the affected credentials, terminate unfamiliar sessions, and review recovery settings. If financial information may have been exposed, contact your financial institution immediately.&lt;/p&gt;

&lt;p&gt;For identity theft, the FTC maintains &lt;a href="https://www.identitytheft.gov/" rel="noopener noreferrer"&gt;IdentityTheft.gov&lt;/a&gt;, which provides recovery instructions based on what happened.&lt;/p&gt;

&lt;p&gt;A password manager, passkeys, and MFA can substantially reduce the likelihood of an account takeover. They cannot guarantee you'll never become a victim, especially when criminals exploit weaknesses in the companies holding your information.&lt;/p&gt;

&lt;p&gt;A recovery plan is what prevents one incident from turning into a prolonged disaster.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where I'd start
&lt;/h2&gt;

&lt;p&gt;If all of this sounds overwhelming, work through these steps one at a time:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Get a password manager.&lt;/strong&gt; Set it up on your phone and computer, then start replacing reused passwords with unique, randomly generated ones. Start with your email and financial accounts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Protect the vault itself.&lt;/strong&gt; Choose a reputable manager with a documented security design, use a strong, unique account passphrase, and enable its MFA. Keep your devices secure, and store your Emergency Kit or other recovery information somewhere physically safe.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use passkeys and MFA wherever available.&lt;/strong&gt; Choose passkeys when offered. Otherwise, enable MFA, preferably with an authenticator app or physical security key. Use SMS if that is the only option, and never approve an unexpected login request or give someone a verification code they ask for.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Secure your primary email account.&lt;/strong&gt; Review its recovery settings and signed-in devices. Remove unfamiliar sessions and outdated recovery details so your inbox cannot become an easy route into your other accounts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Install an email defender like Premail.&lt;/strong&gt; Use an email filtering tool such as &lt;a href="https://www.mattsenter.com/projects/premail" rel="noopener noreferrer"&gt;Premail&lt;/a&gt; to help handle spam and unwanted messages. Start in Learning mode to review its decisions before enabling automatic actions, and consider Pro's Reputation Shield for known phishing and spam domains. Keep independently verifying suspicious messages; no filter catches everything.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Independently verify unexpected requests.&lt;/strong&gt; If somebody contacts you demanding money, personal information, or urgent action, reach the person or organization through a channel you already trust. A familiar voice or polished message is not proof of identity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enable automatic updates and review what you install.&lt;/strong&gt; Keep your phone, computer, browser, applications, and router current. Remove unused browser extensions, check application permissions, and obtain software from trustworthy sources.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Protect your financial accounts.&lt;/strong&gt; Turn on transaction alerts, freeze your credit with all three major bureaus, and enable your mobile carrier's account PIN or port-out protection. Keep securely stored copies of important financial records, and report unauthorized activity immediately.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep control over AI purchases and sensitive information.&lt;/strong&gt; Use AI to research products, but do not upload your everyday credit card to a chatbot or give it unrestricted spending authority. Make the purchase yourself, and evaluate security claims independently of the people selling the system.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prepare a recovery plan.&lt;/strong&gt; Keep recovery codes and emergency contact information somewhere secure and independent of the accounts they protect. Back up important files, including a copy that a compromised account cannot easily delete, and make sure a trusted family member knows where essential information is kept.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;None of these requires a technical background, and most of them don't require much ongoing effort once they're configured.&lt;/p&gt;

&lt;p&gt;I've spent much of my career building software, and one thing I've learned is that security systems shouldn't depend on people behaving perfectly all the time. Humans forget passwords, click the wrong links, overlook notifications, and occasionally make terrible decisions. I'm certainly not immune to any of those things.&lt;/p&gt;

&lt;p&gt;The better approach is to use technology to eliminate as many opportunities for human error as possible. Let a password manager remember your credentials. Let passkeys handle authentication. Let your devices update themselves. Configure alerts so you don't have to constantly check whether something has gone wrong.&lt;/p&gt;

&lt;p&gt;At the same time, retain control over decisions that can have serious consequences, especially when money and sensitive personal information are involved.&lt;/p&gt;

&lt;p&gt;AI is giving criminals faster and more sophisticated tools. We don't necessarily need an entirely new set of personal security practices to respond. We need to get much better at using the protections that already exist.&lt;/p&gt;

&lt;p&gt;My mother-in-law shouldn't have to become a cybersecurity expert to use the internet safely. Neither should anyone else.&lt;/p&gt;

&lt;h2&gt;
  
  
  Disclaimer
&lt;/h2&gt;

&lt;p&gt;This article is provided for general informational and educational purposes only. It does not constitute personalized cybersecurity, financial, legal, or other professional advice.&lt;/p&gt;

&lt;p&gt;While I've made reasonable efforts to ensure the information is accurate and supported by credible sources, security threats, technologies, laws, and recommended practices change over time. No security measure or combination of measures can guarantee protection against hacking, fraud, identity theft, financial loss, or other harm.&lt;/p&gt;

&lt;p&gt;Any products, services, techniques, or practices discussed are presented for informational purposes. References to particular companies or products do not constitute guarantees of their security, reliability, or suitability for your individual circumstances.&lt;/p&gt;

&lt;p&gt;You are solely responsible for evaluating the information presented and determining which actions to take or not take. I assume no responsibility or liability for any decisions, actions, omissions, losses, damages, security incidents, or other consequences arising from your use of or reliance upon this article.&lt;/p&gt;

&lt;p&gt;For advice specific to your circumstances, consult an appropriately qualified professional.&lt;/p&gt;

</description>
      <category>aisecurity</category>
      <category>passwordmanagers</category>
      <category>passkeys</category>
      <category>phishing</category>
    </item>
    <item>
      <title>CalendarPA: Scheduling That Leaves Room for Your Day</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Mon, 16 Nov 2026 18:31:29 +0000</pubDate>
      <link>https://dev.to/mattsenter/calendarpa-scheduling-that-leaves-room-for-your-day-32hf</link>
      <guid>https://dev.to/mattsenter/calendarpa-scheduling-that-leaves-room-for-your-day-32hf</guid>
      <description>&lt;p&gt;Disclosure: Alan is a friend, and my CalendarPA links are referral links. I may earn a commission if you sign up through them.&lt;/p&gt;

&lt;p&gt;My friend Alan Seales built &lt;a href="https://calendarpa.com/?via=matt-8625ead2" rel="noopener noreferrer"&gt;CalendarPA&lt;/a&gt;, and it deserves more than a spot on my tools page. I use it myself. You can see my booking page at &lt;a href="https://calendarpa.com/@matt?via=matt-8625ead2" rel="noopener noreferrer"&gt;calendarpa.com/@matt&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The short version&lt;/p&gt;

&lt;p&gt;CalendarPA connects Google, Microsoft, and Apple calendars so availability can account for life across accounts. AdaPA, its AI scheduling assistant, handles scheduling through email, text, and chat. The free plan includes unlimited bookings, two booking types, two connected accounts, email reminders, and payment collection with one active provider. Pro adds recurring sessions, prepaid packages, automated email and SMS sequences, and burnout protection: meeting limits, protected lunch, breaks, and focus time. I want a booking tool that leaves me time to do the work between the calls. CalendarPA’s emphasis on protecting the day is what makes it stand out to me. Seeing commitments across calendars matters for the same reason: a personal commitment still takes time, even if it lives outside the work calendar. Disclosure: Alan is a friend, and my CalendarPA links are referral links. I may earn a commission if you sign up through them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://calendarpa.com/features?via=matt-8625ead2" rel="noopener noreferrer"&gt;CalendarPA&lt;/a&gt; connects Google, Microsoft, and Apple calendars so availability can account for life across accounts. AdaPA, its AI scheduling assistant, handles scheduling through email, text, and chat.&lt;/p&gt;

&lt;p&gt;The free plan includes unlimited bookings, two booking types, two connected accounts, email reminders, and payment collection with one active provider. Pro adds recurring sessions, prepaid packages, automated email and SMS sequences, and burnout protection: meeting limits, protected lunch, breaks, and focus time.&lt;/p&gt;

&lt;h2&gt;
  
  
  One builder. Plenty of judgment.
&lt;/h2&gt;

&lt;p&gt;Alan is building CalendarPA as a team of one, using AI tools alongside his experience in enterprise security and infrastructure. AI expands what he can build alone; his experience informs how it should work.&lt;/p&gt;

&lt;p&gt;To me, the difference between useful AI-assisted software and AI slop is the judgment behind it. Connecting calendars is useful. Recognizing that an available hour is not always an hour you should give away is a product decision. CalendarPA puts that judgment into features I actually want. AI can keep generating code around the clock; the builder still has to decide what deserves to ship.&lt;/p&gt;

&lt;h2&gt;
  
  
  Growth built into the product
&lt;/h2&gt;

&lt;p&gt;CalendarPA bootstrapped its first users through a lifetime referral program, and that program is still running. Booking pages introduce the product to the next person who needs to schedule something. Rewarding the people making those introductions gives customers a stake in its growth.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://calendarpa.com/get-paid?via=matt-8625ead2" rel="noopener noreferrer"&gt;current program&lt;/a&gt; offers 20% of referred subscription payments for as long as the customer stays subscribed. “Lifetime” means the life of that subscription. Payout eligibility starts after 60 active days, with commissions credited retroactively from day one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Familiar workflows, a different way to build
&lt;/h2&gt;

&lt;p&gt;CalendarPA connects familiar scheduling workflows with AI tools. CalendarPA keeps the booking page and existing calendars, adds conversational scheduling through AdaPA, and offers imports from tools such as Calendly and TidyCal. The infrastructure can evolve while the user still starts with a familiar problem: finding a time that works.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I prefer it
&lt;/h2&gt;

&lt;p&gt;I want a booking tool that leaves me time to do the work between the calls. CalendarPA’s emphasis on protecting the day is what makes it stand out to me. Seeing commitments across calendars matters for the same reason: a personal commitment still takes time, even if it lives outside the work calendar.&lt;/p&gt;

&lt;p&gt;There is also a practical advantage over &lt;a href="https://calendly.com/pricing" rel="noopener noreferrer"&gt;Calendly&lt;/a&gt;’s free plan, which currently lists one event type and one calendar connection. Calendly puts payment integrations on Standard. CalendarPA gives you more flexibility before you need a subscription.&lt;/p&gt;

&lt;p&gt;That makes it a better starting point for someone juggling work and personal calendars, or trying paid appointments. Calendly Standard does offer unlimited event types; CalendarPA Pro lists ten. The right choice depends on what you need, but for my priorities, Alan has built something worth trying.&lt;/p&gt;

&lt;p&gt;Feature and plan details checked November 2, 2026.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://calendarpa.com/?via=matt-8625ead2" rel="noopener noreferrer"&gt;Try CalendarPA (referral link)&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.mattsenter.com/tools" rel="noopener noreferrer"&gt;More tools I recommend&lt;/a&gt;&lt;/p&gt;

</description>
      <category>calendarpa</category>
      <category>alanseales</category>
      <category>scheduling</category>
      <category>calendlyalternative</category>
    </item>
    <item>
      <title>How to Authenticate a Time Traveler</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Fri, 13 Nov 2026 00:55:08 +0000</pubDate>
      <link>https://dev.to/mattsenter/how-to-authenticate-a-time-traveler-5d7f</link>
      <guid>https://dev.to/mattsenter/how-to-authenticate-a-time-traveler-5d7f</guid>
      <description>&lt;p&gt;I've come up with a secret phrase that I intend to use to authenticate anyone who claims to be a time traveler. I've never written it down, typed it, or told anyone what it is. It exists exclusively in my head, and I intend to keep it that way until the day someone in the future can demonstrate that they're connected to a message I've already received from a time traveler.&lt;/p&gt;

&lt;p&gt;I realize that sounds ridiculous, but I've been thinking about this for a while. With advances in artificial intelligence, quantum computing, and our understanding of physics, I wonder whether we'll eventually discover some means of communicating backward through time. I'm skeptical that we'll ever physically transport human beings into the past, but transmitting information seems more plausible to me. Perhaps we'll find a way to send data, or even project thoughts backward through time. I have no idea how that would work, but I'm not willing to rule out what future generations might discover, and if it ever happens, I want to be prepared.&lt;/p&gt;

&lt;h2&gt;
  
  
  Time Travel Isn't Entirely Science Fiction
&lt;/h2&gt;

&lt;p&gt;Before dismissing this as nonsense, it's worth looking at some of the actual scientific research into time travel. This isn't exclusively the domain of science fiction writers and conspiracy theorists. Some of the most respected physicists and mathematicians in history have seriously studied the possibility.&lt;/p&gt;

&lt;p&gt;In 1949, mathematician &lt;a href="https://journals.aps.org/rmp/pdf/10.1103/RevModPhys.21.447" rel="noopener noreferrer"&gt;Kurt Gödel published a solution to Einstein's field equations [PDF]&lt;/a&gt; describing a rotating universe in which spacetime could contain closed timelike curves. Essentially, these are paths through spacetime that loop back into the past. Gödel's model doesn't describe the universe we actually observe, but it demonstrated that Einstein's equations don't universally prohibit such paths.&lt;/p&gt;

&lt;p&gt;In 1988, Michael Morris, future Nobel Prize winner Kip Thorne, and Ulvi Yurtsever published &lt;em&gt;&lt;a href="https://physics.uwyo.edu/~mbrother/acs/p1446_1.pdf" rel="noopener noreferrer"&gt;Wormholes, Time Machines, and the Weak Energy Condition [PDF]&lt;/a&gt;&lt;/em&gt;, examining whether traversable wormholes could theoretically be converted into time machines. Then, in 1991, quantum computing pioneer David Deutsch published &lt;em&gt;&lt;a href="https://gwern.net/doc/science/physics/1991-deutsch.pdf" rel="noopener noreferrer"&gt;Quantum Mechanics Near Closed Timelike Lines [PDF]&lt;/a&gt;&lt;/em&gt;, exploring what happens when quantum systems interact with their own past.&lt;/p&gt;

&lt;p&gt;Researchers at the University of Queensland even published an &lt;a href="https://quantum.technology/andrew/publications/2014/ncomms5145.pdf" rel="noopener noreferrer"&gt;experimental simulation of closed timelike curves [PDF]&lt;/a&gt; in 2014. They simulated a quantum system interacting with an older version of itself. To be clear, they didn't actually send anything backward through time, but they were able to experimentally study some of the behavior predicted by these theoretical models.&lt;/p&gt;

&lt;p&gt;Of course, there's substantial scientific skepticism about whether any of this could actually work. Stephen Hawking proposed his &lt;a href="https://lweb.cfa.harvard.edu/~loeb/Hawking_C.pdf" rel="noopener noreferrer"&gt;chronology protection conjecture [PDF]&lt;/a&gt; in 1992, arguing that the laws of physics might prevent the formation of closed timelike curves and thereby prohibit travel into the past.&lt;/p&gt;

&lt;p&gt;None of these theories or experiments demonstrates that backward time communication is achievable, and AI or quantum computing doesn't necessarily bring us any closer to it. Still, this is legitimate scientific research conducted by highly regarded scientists. I think it's reasonable to wonder what might become possible with sufficiently advanced technology and a better understanding of physics.&lt;/p&gt;

&lt;p&gt;More importantly, preparing for the possibility costs me practically nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem With Authenticating a Time Traveler
&lt;/h2&gt;

&lt;p&gt;Imagine someone approaches me tomorrow and tells me they're from the future. They have important information that I need to know, and they insist that I believe them. How am I supposed to know they're telling the truth?&lt;/p&gt;

&lt;p&gt;They could predict something that's going to happen, and that might actually be useful evidence. If they correctly predict tomorrow's lottery numbers or a stock's closing price an hour from now, I'd certainly be interested. I'd still have to wait for the prediction to come true, and predicting an event doesn't necessarily establish who they are or how they acquired the information.&lt;/p&gt;

&lt;p&gt;What I really need is a piece of information that only I could know. Something I establish now that my future self can share with a time traveler, who can then bring that information back to me. That would give me a way to authenticate the message immediately, even if the communication only travels in one direction and never allows me to ask a follow-up question.&lt;/p&gt;

&lt;p&gt;This is essentially how shared-secret authentication works in computer security. Two parties who possess the same secret can use that information to establish trust. In this case, however, the two parties are separated by time rather than distance, and the secret needs to exist before anyone contacts me.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Secret Has to Come First
&lt;/h2&gt;

&lt;p&gt;The main reason to establish the phrase now is security. If someone contacts me tomorrow and I invent a password in response, that password does nothing to authenticate the encounter I've already experienced. I can't use a secret I haven't invented yet to verify information someone has already given me.&lt;/p&gt;

&lt;p&gt;There's also a time travel problem worth considering, which is where things get a little weird.&lt;/p&gt;

&lt;p&gt;Suppose someone travels back in time and tells me a secret phrase. Years later, I encounter that same person before their trip into the past, and I tell them the phrase so they'll know what to say when they meet my younger self.&lt;/p&gt;

&lt;p&gt;Where did that phrase originate?&lt;/p&gt;

&lt;p&gt;I learned it from the time traveler, who learned it from me, who learned it from the time traveler. Nobody ever actually invented it. The information exists in a loop without an identifiable origin.&lt;/p&gt;

&lt;p&gt;This is called the &lt;a href="https://plato.stanford.edu/entries/causation-backwards/#BooPar" rel="noopener noreferrer"&gt;bootstrap paradox&lt;/a&gt;, also known as an ontological paradox. Philosophers and physicists have debated whether such causal loops are possible, but I'd rather avoid creating one with my password.&lt;/p&gt;

&lt;p&gt;There's another scenario that's less obvious. Suppose someone approaches me claiming to be from the future, but doesn't tell me a secret phrase. Instead, I immediately decide that I need to invent one so I can authenticate them. I come up with a phrase right then and plan to tell that person when we meet again in the future, before they make their trip into the past.&lt;/p&gt;

&lt;p&gt;The phrase itself has an identifiable origin because I invented it, so this isn't necessarily a bootstrap paradox in the strict sense. What prompted me to invent it, though? Someone claiming to be from the future approached me and gave me a reason to create it. The decision to create my authentication mechanism was already influenced by an event that may have originated in the future.&lt;/p&gt;

&lt;p&gt;That doesn't make the phrase invalid, but it means the decision to create it wasn't independent of the alleged time travel encounter. More importantly, it still wouldn't authenticate the contact that prompted me to invent it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What I want is a secret with an independent origin, established before any alleged time traveler gives me a reason to invent it.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That doesn't mean I've eliminated every causal loop. In fact, if this scheme ever works, the events surrounding it will necessarily form one under the single-timeline model I'm assuming. I might reveal the phrase in 2055 because I received it in 2027, while the only reason I received it in 2027 is that I revealed it in 2055. The information itself still has an independent origin because I invented it in 2026, even though the events involving that information are causally connected across time.&lt;/p&gt;

&lt;p&gt;How do I know I'm not already part of some larger causal loop? For all I know, a time traveler is planning to contact me tomorrow, and something about my life has already been influenced by backward time communication. Perhaps even my decision to think about this problem was somehow influenced by events that haven't happened yet.&lt;/p&gt;

&lt;p&gt;I can't completely eliminate that possibility, nor can I prove that my decision to invent the phrase is causally independent of every possible future event. I can at least establish the phrase before any encounter I'm aware of, and that seems like a reasonable precaution.&lt;/p&gt;

&lt;p&gt;This is also why I think everyone should do this sooner rather than later. If you wait until someone claims to be from the future, you've already missed the opportunity to authenticate that initial encounter using a secret established in advance.&lt;/p&gt;

&lt;p&gt;I've already invented mine, and as of November 12, 2026, nobody claiming to be a time traveler has contacted me.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to Prepare Your Own Time Travel Password
&lt;/h2&gt;

&lt;p&gt;First, invent a phrase that would be extremely difficult for someone else to guess. Don't use a famous quotation, a common expression, or something easily associated with you. Make it unusual enough that someone independently coming up with the same sequence of words would be extraordinarily unlikely.&lt;/p&gt;

&lt;p&gt;Next, and this is important, &lt;strong&gt;don't write it down anywhere&lt;/strong&gt;. Don't type it into your phone, save it in a password manager, put it in an encrypted document, or tell ChatGPT about it. Don't even tell your spouse. The entire point is that you're the only person in the world who knows this phrase, and that the information has never been stored anywhere outside your brain.&lt;/p&gt;

&lt;p&gt;Of course, this introduces a practical problem. How are you supposed to remember an arbitrary phrase for the next twenty, thirty, or fifty years?&lt;/p&gt;

&lt;p&gt;I recommend repeating it silently to yourself every morning while brushing your teeth. You're already doing that every day, so associate your phrase with the routine. Eventually, remembering the phrase should become part of the habit. There's no guarantee that you'll never forget it, and over enough years you could even begin to misremember part of it without realizing it. Repeated rehearsal should help, and recognizing the correct phrase when someone tells it to you may be easier than recalling it perfectly from memory.&lt;/p&gt;

&lt;p&gt;There's a limitation to keeping the phrase exclusively in my head, too. If future technology can somehow reconstruct memories or read information directly from my brain, the phrase might not be as private as I think it is. I'm already speculating about technology that could project thoughts backward through time, so it's fair to consider the possibility that future technology might also be able to extract them. Those aren't necessarily the same capability, but either way, my approach assumes that nobody has obtained the phrase through some other means.&lt;/p&gt;

&lt;p&gt;A technical reader might also suggest publishing a cryptographic hash of the phrase today, giving me a timestamped commitment that anyone could verify later. That's a legitimate approach, and it would allow other people to confirm that I'd committed to the phrase before the alleged encounter. I'd need to use a sufficiently unpredictable phrase, since publishing a hash would also give attackers a way to test guesses. Personally, I'd rather avoid entering my phrase into a computer at all, even one operating offline.&lt;/p&gt;

&lt;p&gt;That does mean this experiment is primarily for my own benefit. Someone else might believe my account, but without independently verifiable evidence, they couldn't establish that I actually knew the phrase before the alleged time traveler appeared.&lt;/p&gt;

&lt;p&gt;I'm fine with that. I'm preparing to convince myself, not the rest of the world.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Happens When You Meet a Time Traveler?
&lt;/h2&gt;

&lt;p&gt;Let's imagine it's 2027, and someone approaches me with an extraordinary claim. They've come from the future, or they've found a way to transmit information backward through time, and they have something to tell me.&lt;/p&gt;

&lt;p&gt;It might involve some advanced computer system that can transmit data into the past. Maybe they've found a way to project information directly into someone's consciousness. They might even have built a physical time machine. I suspect transmitting information will be more feasible than transporting people, but that's just my intuition.&lt;/p&gt;

&lt;p&gt;Whatever the mechanism, they tell me my exact secret phrase.&lt;/p&gt;

&lt;p&gt;How the hell would someone know it? I've never disclosed it, and as far as I know, nobody has ever had access to that information except me. The fact that someone knows it doesn't automatically prove time travel, but it would be pretty damn compelling evidence that something extraordinary had happened.&lt;/p&gt;

&lt;p&gt;Now, I realize that knowing my phrase isn't absolute proof of time travel. Maybe someone has developed technology capable of reading my mind, or perhaps I've accidentally revealed the phrase without realizing it. There are conceivable explanations other than backward time communication, but receiving that exact phrase without having previously disclosed it would certainly get my attention.&lt;/p&gt;

&lt;p&gt;At this point, though, the phrase has served its purpose. Someone else knows it, which means it can no longer function as a secret exclusively known to me. If that person tells me the phrase again tomorrow, it doesn't prove anything new.&lt;/p&gt;

&lt;p&gt;That raises another question: how do I authenticate subsequent messages, or verify whoever eventually claims responsibility for sending the original one?&lt;/p&gt;

&lt;h2&gt;
  
  
  What If the Traveler and the Organizer Are Different People?
&lt;/h2&gt;

&lt;p&gt;Suppose that in 2027, Person A approaches me and tells me my secret phrase. I have no idea who this person is, but the fact that they know my phrase makes me take them seriously.&lt;/p&gt;

&lt;p&gt;Then, in 2055, I meet Person B, who explains that they've developed the technology and are planning to send someone back to 2027 to contact me. The person they're sending isn't Person B. It's Person A, who might not even be alive or available to speak with me in 2055.&lt;/p&gt;

&lt;p&gt;How do I authenticate Person B?&lt;/p&gt;

&lt;p&gt;In the single, self-consistent timeline I'm assuming, the phrase has already been delivered successfully. I'm not worried about whether Person B will somehow fail to send it. I'm worried about trusting the wrong person, someone who claims responsibility for an event they didn't actually arrange.&lt;/p&gt;

&lt;p&gt;I've been thinking about this as a computer security problem, and public-key cryptography offers a way to address it.&lt;/p&gt;

&lt;p&gt;When Person A contacts me in 2027, they don't just provide my secret phrase. They also provide a public cryptographic key belonging to whoever arranged the trip. That public key can be stored without compromising the secret, because public keys are designed to be shared.&lt;/p&gt;

&lt;p&gt;I preserve that key along with the details of the encounter. Unlike my original phrase, there's no reason I can't write this information down or store it electronically.&lt;/p&gt;

&lt;p&gt;Fast-forward to 2055, when Person B claims responsibility for sending Person A back to meet me. I can challenge Person B to prove that they possess the private key corresponding to the public key I received in 2027.&lt;/p&gt;

&lt;p&gt;I generate a new, random challenge and ask Person B to digitally sign it. If the signature verifies against the public key I received decades earlier, I have evidence that Person B controls a cryptographic credential associated with that earlier encounter. I never have to learn their private key, and Person A doesn't need to be present.&lt;/p&gt;

&lt;p&gt;This is called challenge-response authentication using a digital signature. Since I'm already speculating about advanced quantum computers, I'd also want the cryptography to be resistant to quantum attacks. NIST has already standardized &lt;a href="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.204.pdf" rel="noopener noreferrer"&gt;post-quantum digital signature algorithms [PDF]&lt;/a&gt;, although I'd obviously want to use whatever remained secure in 2055.&lt;/p&gt;

&lt;p&gt;Once Person B passes the challenge, I can reveal my original phrase. Person B can then give it to Person A, along with their public key, before Person A makes the trip back to 2027. From my perspective, that's simply how the information I received in 2027 got there in the first place.&lt;/p&gt;

&lt;p&gt;The public key has another advantage. After the original encounter, my secret phrase is no longer exclusive, but the private key can continue to authenticate subsequent messages. Person B could sign additional communications, and I could verify them without needing another password or revealing any additional secrets. The phrase establishes the initial connection, and the cryptographic key maintains it.&lt;/p&gt;

&lt;p&gt;Of course, there's no cryptographic mechanism that can guarantee Person B is trustworthy, or that their private key hasn't been stolen or transferred. The proof establishes control of a key associated with the earlier message, not the person's motives or an independently verified identity. It would be considerably stronger than simply taking someone's word for it.&lt;/p&gt;

&lt;p&gt;There's also a fallback if Person A didn't bring a public key. The original encounter itself could contain information known only to me and the people responsible for arranging it. Perhaps Person A said something unusual, met me at a specific location, or described circumstances that I never disclosed afterward. If Person B can independently recount those details in 2055, that would provide additional evidence connecting them to the encounter.&lt;/p&gt;

&lt;p&gt;It wouldn't be as strong as a cryptographic challenge, since someone might have obtained those details through another means. Person B might not know them if Person A never reported back. It's another possible way to investigate their claim, particularly if the original traveler is unavailable.&lt;/p&gt;

&lt;p&gt;Ideally, though, I'd want the public key. It gives me a repeatable way to authenticate communications without requiring the original messenger to participate.&lt;/p&gt;

&lt;p&gt;If my future self is reading this, make sure whoever you send back includes the public key.&lt;/p&gt;

&lt;h2&gt;
  
  
  You Could Also Be the Time Traveler
&lt;/h2&gt;

&lt;p&gt;The more I think about this, the more I suspect that if backward time communication ever becomes possible, the person contacting me might actually be me.&lt;/p&gt;

&lt;p&gt;Suppose that in 2055 I discover some way to transmit information backward through time. I remember receiving an unexplained message containing my secret phrase back in 2027, and now I finally understand where it came from. I can send that same phrase to my younger self, along with whatever information I intended to convey.&lt;/p&gt;

&lt;p&gt;How do I convince younger me that the message is legitimate? Well, I already know the phrase, so I include it in the message. When younger me receives it, he'll immediately recognize the phrase as something he invented and never disclosed.&lt;/p&gt;

&lt;p&gt;This arrangement has an advantage over relying on another person. I don't have to give my secret to an intermediary in the future, and there's no ambiguity about whether the sender was supposed to have access to it. Future me already has the information because I've been carrying it around in my head since 2026.&lt;/p&gt;

&lt;p&gt;I also like the idea that I could send the phrase back simply as a test. I wouldn't necessarily need to transmit some earth-shattering revelation. Just receiving the phrase would tell me that something extraordinary had happened, and I could start investigating from there.&lt;/p&gt;

&lt;p&gt;There's a catch, though. In the single-timeline model I'm assuming, I can't reach 2055 having never received a message and then simply decide to add one to my past. If I eventually send myself a message in 2055, that message must already have been part of my experience in 2027. That's the causal loop I can't eliminate, even though the phrase itself originated independently in 2026.&lt;/p&gt;

&lt;p&gt;There's also the possibility that I never live long enough to make the transmission. If I die before anyone learns my phrase, there's no future version of me available to disclose it. Unless someone acquires the information through some other means, the entire protocol ends with me.&lt;/p&gt;

&lt;p&gt;I suppose that's another reason not to procrastinate if I ever invent a time machine.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why You Only Need One Password
&lt;/h2&gt;

&lt;p&gt;Initially, I thought it might be a good idea to establish a few backup passwords, just in case someone claiming to be a time traveler turned out to be lying. The more I thought about it, the more I realized that I was approaching the problem as though time were moving forward for everyone involved.&lt;/p&gt;

&lt;p&gt;Consider someone approaching me in 2055 and claiming they're going to travel back to 2027 to contact me. If they're telling the truth, and we're operating in a single, self-consistent timeline, that encounter in 2027 has already happened from my perspective. I would have received my secret phrase twenty-eight years earlier and spent the intervening years knowing that someone had communicated information to me from the future, or at least had somehow acquired my secret.&lt;/p&gt;

&lt;p&gt;If I reach 2055 and nobody has ever contacted me with that phrase, why would I give it to someone who claims they're going to travel back to 2027? Their claim doesn't match my experience. I would already know that the event they're describing wasn't part of my past, at least not in the timeline I've experienced.&lt;/p&gt;

&lt;p&gt;From the time traveler's perspective, receiving the phrase in 2055 and transmitting it to 2027 happens in that order. From my perspective, I receive the phrase in 2027 and only encounter the person who will eventually transmit it in 2055. By the time I meet them, I've already experienced the event we're discussing.&lt;/p&gt;

&lt;p&gt;Of course, there could be multiple timelines, or perhaps changing the past creates an alternate branch of reality. I have no idea how any of that would work, and neither does anyone else. My approach assumes that backward communication is possible within a single, consistent history. If changing the past creates an entirely different timeline, then all bets are off.&lt;/p&gt;

&lt;p&gt;Under the assumptions I'm making, I don't need to prepare for multiple failed attempts by giving my phrase to strangers who promise to use it someday. The evidence of a successful attempt should already exist in my past before I ever need to disclose it in the future.&lt;/p&gt;

&lt;p&gt;Once that first message arrives, I have other ways to authenticate subsequent communications. The public-key approach provides a means of maintaining that relationship without repeatedly relying on a secret that is no longer secret.&lt;/p&gt;

&lt;p&gt;That doesn't mean the same phrase can independently authenticate every unrelated traveler who might ever appear. It means I only need one phrase to establish this initial connection, after which I can rely on other credentials.&lt;/p&gt;

&lt;h3&gt;
  
  
  What About Keeping a Few Extra Phrases?
&lt;/h3&gt;

&lt;p&gt;There's another, more practical reason I'm not keeping a collection of secret phrases. I already think the chance of receiving even one authentic message from the future is extraordinarily low. Preparing for several unrelated first contacts, each requiring its own unused secret, feels like planning for an even more remote possibility.&lt;/p&gt;

&lt;p&gt;If those encounters were independent, multiple successes could be astronomically less likely than one. For a simple illustration, if each of two independent opportunities had a one-in-a-million chance of succeeding, the chance that both succeeded would be one in a trillion. Those aren't estimates of the odds of time travel. They're just an illustration of why I don't feel compelled to memorize a whole inventory of passwords for independent encounters.&lt;/p&gt;

&lt;p&gt;There's an important catch: the encounters might not be independent. If someone figures out how to send a message backward through time, sending a second one might be easy. Receiving that first message would also radically change my view of what's possible. I can't assume that a second message would remain extraordinarily unlikely after the first one arrives.&lt;/p&gt;

&lt;p&gt;That's why the distinction matters. More messages from an established connection can use the public key. A genuinely unrelated first contact might call for a fresh secret, but preparing for several of those in advance adds something else to remember for a possibility I already consider remote. One phrase seems like a reasonable amount of preparation.&lt;/p&gt;

&lt;p&gt;I'm sticking with one phrase. I just need to remember it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I'm Actually Doing This
&lt;/h2&gt;

&lt;p&gt;I recognize that there's an exceptionally good chance none of this will ever matter. We don't know whether backward time communication is possible, and there are serious scientific arguments suggesting that the laws of physics may prevent it entirely, but I'm also not convinced that we understand enough about the universe to categorically dismiss every conceivable method of communicating with the past. A century ago, the technology we have today would have seemed pretty extraordinary, and I don't pretend to know what another century of scientific discovery might bring.&lt;/p&gt;

&lt;p&gt;What interests me about this particular exercise is that there's practically no cost to preparing. I don't need to spend any money, learn anything new, or change my routine. I just need to memorize an unusual phrase and make sure I don't disclose it prematurely.&lt;/p&gt;

&lt;p&gt;If time travel never happens, I've spent a few seconds every morning thinking about something that ultimately didn't matter. I can live with that, but if someone ever does figure out how to transmit information backward through time, I want to have already established a means of authenticating the first contact, and if it's my future self doing the transmitting, I want him to know that younger me is going to be skeptical and that simply claiming to be from the future isn't going to cut it.&lt;/p&gt;

&lt;p&gt;The important thing is that the phrase exists before anyone contacts me. That gives it an independent origin, allows me to recognize it immediately, and avoids having to invent an authentication method in response to someone I haven't authenticated yet.&lt;/p&gt;

&lt;p&gt;I've already done it. I have my phrase, and I haven't shared it with anyone. It's not even encoded in this blog post as an easter egg.&lt;/p&gt;

&lt;p&gt;If you're interested in preparing for the same possibility, I suggest coming up with yours today. Don't write it down, don't tell anyone, and repeat it to yourself every morning while brushing your teeth.&lt;/p&gt;

&lt;p&gt;For all you know, your future self is already trying to figure out how to contact you. Might as well be ready.&lt;/p&gt;

</description>
      <category>timetravel</category>
      <category>authentication</category>
      <category>sharedsecrets</category>
      <category>publickeycryptography</category>
    </item>
    <item>
      <title>Is the Waitlist Dead?</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Tue, 10 Nov 2026 23:12:46 +0000</pubDate>
      <link>https://dev.to/mattsenter/is-the-waitlist-dead-3i93</link>
      <guid>https://dev.to/mattsenter/is-the-waitlist-dead-3i93</guid>
      <description>&lt;p&gt;When apps ship faster, making customers wait needs a better reason.&lt;/p&gt;

&lt;p&gt;You announce an app. Put up a landing page. Collect emails. Tell people something exciting is coming.&lt;/p&gt;

&lt;p&gt;Meanwhile, someone else sees the same opportunity, opens a coding agent, and starts building.&lt;/p&gt;

&lt;p&gt;By the time you send your “We’re almost ready” email, your prospective customers might already be using something else.&lt;/p&gt;

&lt;p&gt;That’s the problem I have with the startup waitlist in the agentic building era. The time between having an idea and shipping a useful version has changed. I’m less convinced the launch advice has caught up.&lt;/p&gt;

&lt;p&gt;If you can give someone something useful today, why ask them to come back later?&lt;/p&gt;

&lt;h2&gt;
  
  
  The old playbook had a reason
&lt;/h2&gt;

&lt;p&gt;When building a product required months of engineering, a waitlist gave founders something to do with early interest. It could help test messaging, recruit beta users, and assemble an audience while the software took shape.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://review.firstround.com/linears-path-to-product-market-fit/" rel="noopener noreferrer"&gt;Linear&lt;/a&gt; and &lt;a href="https://review.firstround.com/superhuman-onboarding-playbook/" rel="noopener noreferrer"&gt;Superhuman&lt;/a&gt; are familiar examples. Linear selected early users from a waitlist and improved its product through small cohorts. Superhuman invested heavily in personal onboarding. Both approaches supported deliberate learning about customers.&lt;/p&gt;

&lt;p&gt;But those strategies originated before today’s coding agents. They explain how the playbook developed. They don’t establish that its tradeoffs still make sense.&lt;/p&gt;

&lt;p&gt;When the cost of delivering a working experiment falls, the case for collecting expressions of interest instead gets weaker.&lt;/p&gt;

&lt;p&gt;An email address tells you someone liked your promise enough to submit a form. A person using your app can tell you where that promise breaks.&lt;/p&gt;

&lt;h2&gt;
  
  
  You’re giving competitors time, too
&lt;/h2&gt;

&lt;p&gt;A public waitlist announces an opportunity before you’ve necessarily earned a customer.&lt;/p&gt;

&lt;p&gt;That matters most for products whose core functionality is relatively easy to reproduce. Your announcement describes the problem. Your demo outlines the solution. Your signup count advertises interest.&lt;/p&gt;

&lt;p&gt;A competitor doesn’t have to reproduce your whole roadmap. They only need to solve enough of the customer’s problem to become useful first.&lt;/p&gt;

&lt;p&gt;This is a competitive risk, not an established law. I haven’t found research showing that waitlists routinely cause startups to lose their markets. Shipping first doesn’t guarantee winning, either.&lt;/p&gt;

&lt;p&gt;Still, deliberately extending the interval between “I want this” and “I can use this” deserves scrutiny.&lt;/p&gt;

&lt;p&gt;Your customer’s problem is happening now. Your launch schedule is yours.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do the newer examples tell us?
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.linkedin.com/posts/lovable-dev_we-failed-2-launches-in-2024-the-third-time-activity-7278452566454120448-v343" rel="noopener noreferrer"&gt;Lovable’s own retrospective&lt;/a&gt; describes two unsuccessful launches in 2024, gradual onboarding from a waitlist, and an AI that still got stuck too often. The company attributes its eventual breakthrough to product improvements, a rebrand, and better communication. The list existed before the breakthrough; it wasn’t sufficient to produce one.&lt;/p&gt;

&lt;p&gt;Manus complicates any declaration that restricted launches are dead. It &lt;a href="https://www.axios.com/2025/03/10/manus-chinese-ai-agent-deepseek" rel="noopener noreferrer"&gt;entered invitation-only testing in March 2025&lt;/a&gt; and subsequently &lt;a href="https://manus.im/blog/manus-100m-arr" rel="noopener noreferrer"&gt;reported $100 million in annual recurring revenue&lt;/a&gt;. That demonstrates commercial success following a restricted launch. It doesn’t tell us whether restricting access caused that success, or whether opening sooner would have worked better.&lt;/p&gt;

&lt;p&gt;We should apply the same standard in both directions. A successful company that used a waitlist doesn’t prove the waitlist worked. A failed company that used one doesn’t prove it was the problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inviting someone into a product is different
&lt;/h2&gt;

&lt;p&gt;There’s an important distinction between collecting interest in an idea and controlling access to something people already use.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://instinct.com/" rel="noopener noreferrer"&gt;Instinct&lt;/a&gt; illustrates the invitation model: its public homepage includes an “Invite a friend” link. That alone doesn’t establish the company’s reasons for limiting access, but it points toward a different interaction. An existing user can bring someone else into the experience.&lt;/p&gt;

&lt;p&gt;That feels more credible to me when the invitation leads to a working product.&lt;/p&gt;

&lt;p&gt;There are reasonable constraints. You might only be able to support a few new customers each week. Agent usage might be expensive. You might need to observe failures before admitting more people.&lt;/p&gt;

&lt;p&gt;Invitations can manufacture scarcity, too. The mechanism doesn’t settle the question. The reason for the restriction does.&lt;/p&gt;

&lt;h2&gt;
  
  
  The strongest defense: finding customers still takes work
&lt;/h2&gt;

&lt;p&gt;Faster development doesn’t automatically create distribution.&lt;/p&gt;

&lt;p&gt;One contemporary founder account makes this point well. &lt;a href="https://www.reddit.com/r/lovable/comments/1qgo3lj/how_i_went_from_0_to_1137mo_in_45_days_with_a/" rel="noopener noreferrer"&gt;Hado SEO’s founder reported&lt;/a&gt; collecting 80 waitlist emails and converting five into paying customers during launch week. Before launch, the founder spent time helping prospective customers in communities and refining the offer. These are self-reported results, but they describe customer conversion rather than a large signup number.&lt;/p&gt;

&lt;p&gt;That’s a legitimate argument for a short prelaunch period. You can learn where customers gather, how they describe their problem, and whether you can reach them.&lt;/p&gt;

&lt;p&gt;But it leaves a question: could you learn more by giving those same people a small, working product?&lt;/p&gt;

&lt;p&gt;As building gets faster, that becomes a more practical alternative.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make the wait justify itself
&lt;/h2&gt;

&lt;p&gt;I’m skeptical of waitlists whose primary purpose is to make an unreleased app seem desirable.&lt;/p&gt;

&lt;p&gt;A useful waitlist should correspond to something concrete: a capacity limit, a customer experiment, a dependency, or a product limitation you’re actively resolving. There should be a reason people are waiting and a condition under which they get in.&lt;/p&gt;

&lt;p&gt;“Building hype” is a much weaker answer.&lt;/p&gt;

&lt;p&gt;Before adding that email form, ask what you could ship to those people instead. One workflow. One useful capability. A limited version that does something well.&lt;/p&gt;

&lt;p&gt;Then you can measure whether they use it, whether they return, and whether they care when it improves.&lt;/p&gt;

&lt;p&gt;If someone else can ship a useful version of your idea before you finish building anticipation, what exactly are you waiting for?&lt;/p&gt;

</description>
      <category>startupwaitlists</category>
      <category>agenticdevelopment</category>
      <category>aicodingagents</category>
      <category>productlaunches</category>
    </item>
    <item>
      <title>Weatherling 1.7: AI, UX, and Accessibility</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Tue, 03 Nov 2026 15:18:36 +0000</pubDate>
      <link>https://dev.to/mattsenter/weatherling-17-ai-ux-and-accessibility-33km</link>
      <guid>https://dev.to/mattsenter/weatherling-17-ai-ux-and-accessibility-33km</guid>
      <description>&lt;p&gt;&lt;a href="https://www.weatherling.app" rel="noopener noreferrer"&gt;Weatherling&lt;/a&gt; 1.7, the latest update to my Mac desktop weather app, is out, with shareable weather templates, grass growing along your windows, custom colors, more Lings, and optional Game Center. Building it has also given me more time to work on the parts of a product that are easy to put off: how a control behaves, what a default assumes, and whether someone can use it with VoiceOver.&lt;/p&gt;

&lt;p&gt;AI coding tools free up a lot of my time. I can spend more of it thinking through what happens before and after someone clicks a button, trying the app in different situations, and refining the experience. With &lt;a href="https://www.weatherling.app" rel="noopener noreferrer"&gt;Weatherling&lt;/a&gt;, that means paying attention to how a playful app fits into a computer someone is using to get work done.&lt;/p&gt;

&lt;h2&gt;
  
  
  Shareable templates that preserve your settings
&lt;/h2&gt;

&lt;p&gt;A feature description often ends too early. “Share a weather template” sounds complete until you follow the link on the receiving end. Should opening it immediately change your weather? Which settings should come along? How do you get back to what you had?&lt;/p&gt;

&lt;p&gt;In 1.7, templates save a scene’s weather, colors, and Random settings. You can start with Rainy Day, Snow Drift, Autumn Day, or Techno, make your own, and share it as a link or file. Opening one adds it to your collection while leaving your current scene, location, and device settings alone.&lt;/p&gt;

&lt;p&gt;That gives someone room to look before they commit. A friend can send you their weather without rearranging yours. Defining that behavior is product work, and faster implementation gives me more room to do it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Custom colors with a way back
&lt;/h2&gt;

&lt;p&gt;Each effect now has controls for color, intensity, and brightness. Natural restores the original appearance. Templates let you keep a scene you like before trying something else. Custom Sync lets you decide how much individual elements follow the weather outside, including leaving one unsynced.&lt;/p&gt;

&lt;p&gt;I want people to try strange colors and combinations without worrying about losing a setup they liked. The recovery path needs as much attention as the new control. If someone has to remember six slider positions to undo an experiment, I have left them with work the app should help them avoid.&lt;/p&gt;

&lt;h2&gt;
  
  
  Improving VoiceOver accessibility
&lt;/h2&gt;

&lt;p&gt;Accessibility is one of the best uses of the time these tools give me. There is more room to consider how someone reaches a control, how its purpose is announced, and whether a change of state makes sense without seeing the screen.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.weatherling.app" rel="noopener noreferrer"&gt;Weatherling&lt;/a&gt; already supported VoiceOver. Version 1.7 improves that experience: with VoiceOver running, the menu bar cloud opens the tray as a popover VoiceOver can follow, and more controls have clear labels. Those details determine whether someone can actually operate the app.&lt;/p&gt;

&lt;p&gt;Generated code still needs to be checked through the interaction it creates. A label can exist in the code and still be vague when spoken. A panel can look right while being awkward to navigate. Having time to follow those paths is valuable, especially for a solo developer responsible for the whole product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Optional Game Center and controls for daily use
&lt;/h2&gt;

&lt;p&gt;The new Lings come with optional Game Center leaderboards and achievements, including lifetime and weekly scores. You can also share a single Ling or achievement card. Game Center starts off, and weather, collecting, and your local score work without it.&lt;/p&gt;

&lt;p&gt;Some people want a collection to compete over. Others want rain while they write. Both should be comfortable using the same app. An optional feature needs to remain optional throughout the experience, including when someone chooses never to set it up.&lt;/p&gt;

&lt;p&gt;Version 1.7 also adds choices for battery power and hiding effects over selected apps. Polish, Dutch, and Traditional Chinese join the supported languages. These are different ways of giving people more control over how &lt;a href="https://www.weatherling.app" rel="noopener noreferrer"&gt;Weatherling&lt;/a&gt; fits their day.&lt;/p&gt;

&lt;h2&gt;
  
  
  Grass that responds to rain and wind
&lt;/h2&gt;

&lt;p&gt;Grass grows along window tops, with moss and soil beneath it. Rain helps it grow, wind bends the blades, and a slider controls its height. Weather now plays along the tray, too, and you can push settled leaves with the cursor.&lt;/p&gt;

&lt;p&gt;These interactions are why I enjoy building &lt;a href="https://www.weatherling.app" rel="noopener noreferrer"&gt;Weatherling&lt;/a&gt;. The effects share a little world, so they should respond to each other. Making grass appear is one step; making it feel at home alongside the rain and wind takes more decisions.&lt;/p&gt;

&lt;p&gt;The same care applies when the desktop changes around it. This release includes fixes for Stage Manager, Mission Control, dragging, browser menus, and shutting down. &lt;a href="https://www.weatherling.app" rel="noopener noreferrer"&gt;Weatherling&lt;/a&gt; needs to behave predictably through the ordinary things people do with their computers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where I spend the time saved by AI coding tools
&lt;/h2&gt;

&lt;p&gt;It is easy to fill every hour saved by AI with another feature. I want to spend some of that time returning to what is already there: trying another path through a panel, improving a label, reconsidering a default, or making it easier to recover from a change.&lt;/p&gt;

&lt;p&gt;I have written about &lt;a href="https://www.mattsenter.com/blog/scope-creep-in-the-age-of-ai" rel="noopener noreferrer"&gt;scope creep when AI makes features cheap&lt;/a&gt; and &lt;a href="https://www.mattsenter.com/blog/taste-is-the-bottleneck" rel="noopener noreferrer"&gt;the product judgment that still goes into shipping software&lt;/a&gt;. This release gives me a concrete way to act on both: spend some of the saved time improving the features people already use.&lt;/p&gt;

&lt;p&gt;The tools make more of that work practical for me. I still have to decide what a good experience should be and check whether the app delivers it. &lt;a href="https://www.weatherling.app" rel="noopener noreferrer"&gt;Weatherling&lt;/a&gt; 1.7 is how I am putting that extra time to use.&lt;/p&gt;

&lt;p&gt;Version 1.7 is included for existing customers. You can update through the &lt;a href="https://apps.apple.com/app/apple-store/id6813641198?pt=14608&amp;amp;ct=mattsenter&amp;amp;mt=8" rel="noopener noreferrer"&gt;App Store&lt;/a&gt;, read the &lt;a href="https://www.weatherling.app/blog/weatherling-1-7-templates-grass-and-color?utm_source=mattsenter.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=weatherling-1-7&amp;amp;utm_content=article" rel="noopener noreferrer"&gt;feature announcement&lt;/a&gt; or the &lt;a href="https://www.weatherling.app/release-notes?utm_source=mattsenter.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=weatherling-1-7&amp;amp;utm_content=article" rel="noopener noreferrer"&gt;full release notes&lt;/a&gt;, and &lt;a href="https://www.weatherling.app" rel="noopener noreferrer"&gt;see Weatherling in action&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>weatherling17</category>
      <category>indiedevelopment</category>
      <category>desktopweather</category>
      <category>templates</category>
    </item>
    <item>
      <title>Introducing Despacer: Copy. Paste. In One Piece.</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Fri, 23 Oct 2026 16:43:03 +0000</pubDate>
      <link>https://dev.to/mattsenter/introducing-despacer-copy-paste-in-one-piece-1f6i</link>
      <guid>https://dev.to/mattsenter/introducing-despacer-copy-paste-in-one-piece-1f6i</guid>
      <description>&lt;p&gt;I got tired of copying a command from Claude Code or Codex, pasting it into my terminal, and watching it fall apart. Those line breaks aren’t just visual wrapping. They come along for the ride.&lt;/p&gt;

&lt;p&gt;So I built Despacer: a tiny Mac menu bar app that puts wrapped commands back together. Copy and paste the way you already do. It repairs the breaks and can recover the original text from your local agent session history.&lt;/p&gt;

&lt;p&gt;It’s free and open source under the MIT license. No network access, no analytics, no data collected. And if a repair misses the mark, Undo Last Fix brings your original copy back.&lt;/p&gt;

&lt;p&gt;Despacer runs on macOS 14 Sonoma or later. For now, you install it by building from source; the README has the steps.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/MattSenter/despacer" rel="noopener noreferrer"&gt;Get Despacer on GitHub&lt;/a&gt;&lt;/p&gt;

</description>
      <category>despacer</category>
      <category>claudecode</category>
      <category>codex</category>
      <category>opensource</category>
    </item>
    <item>
      <title>CommandH ist da: Auch die letzte App ausblenden</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Thu, 22 Oct 2026 14:18:20 +0000</pubDate>
      <link>https://dev.to/mattsenter/commandh-ist-da-auch-die-letzte-app-ausblenden-47ln</link>
      <guid>https://dev.to/mattsenter/commandh-ist-da-auch-die-letzte-app-ausblenden-47ln</guid>
      <description>&lt;p&gt;Ich nutze Cmd+H, um meinen Bildschirm freizuräumen. Aber unter macOS lässt sich die letzte sichtbare App nicht ausblenden. Ein Fenster übrig, noch ein Tastendruck und… nichts.&lt;/p&gt;

&lt;p&gt;Also habe ich CommandH gebaut. Die kleine Menüleisten-App sorgt dafür, dass Cmd+H auch bei der letzten App funktioniert. Du kannst sie vollständig ausblenden oder Show Desktop wählen: Die Fenster gleiten an den Bildschirmrand und kommen mit einem weiteren Cmd+H zurück.&lt;/p&gt;

&lt;p&gt;Die App ist kostenlos und unter der MIT-Lizenz quelloffen. Keine Berechtigungen für Bedienungshilfen oder Bildschirmaufnahme, keine Netzwerkanfragen, keine Datensammlung. Nur eine kleine Korrektur, damit ich meinen Schreibtisch erreiche.&lt;/p&gt;

&lt;p&gt;CommandH läuft ab macOS 14 Sonoma. Vorerst wird die App aus dem Quellcode gebaut; die README auf GitHub erklärt das Installationsskript.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.mattsenter.com/de/projects/commandh" rel="noopener noreferrer"&gt;CommandH kennenlernen&lt;/a&gt; · &lt;a href="https://github.com/MattSenter/commandh" rel="noopener noreferrer"&gt;Quellcode und Installationsanleitung&lt;/a&gt;&lt;/p&gt;

</description>
      <category>commandh</category>
      <category>cmdh</category>
      <category>opensource</category>
      <category>macmenubarapp</category>
    </item>
    <item>
      <title>Apresentando CommandH: oculte aquele último app</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Thu, 22 Oct 2026 14:17:43 +0000</pubDate>
      <link>https://dev.to/mattsenter/apresentando-commandh-oculte-aquele-ultimo-app-4k19</link>
      <guid>https://dev.to/mattsenter/apresentando-commandh-oculte-aquele-ultimo-app-4k19</guid>
      <description>&lt;p&gt;Uso Cmd+H para limpar a tela. Mas, no macOS, o último app visível se recusa a se ocultar. Uma janela restante, mais um toque e… nada.&lt;/p&gt;

&lt;p&gt;Então criei o CommandH. É um pequeno app da barra de menus que faz Cmd+H funcionar também naquele último app. Você pode ocultá-lo completamente ou escolher Show Desktop, que afasta as janelas e as traz de volta com outro Cmd+H.&lt;/p&gt;

&lt;p&gt;É gratuito e de código aberto, sob a licença MIT. Sem permissões de Acessibilidade ou Gravação de Tela, sem requisições de rede e sem coletar dados. Só uma pequena correção para chegar à mesa.&lt;/p&gt;

&lt;p&gt;O CommandH funciona no macOS 14 Sonoma ou posterior. Por enquanto, a instalação exige compilar o código-fonte; o README no GitHub explica como usar o script.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.mattsenter.com/pt/projects/commandh" rel="noopener noreferrer"&gt;Conheça o CommandH&lt;/a&gt; · &lt;a href="https://github.com/MattSenter/commandh" rel="noopener noreferrer"&gt;Código e instruções de instalação&lt;/a&gt;&lt;/p&gt;

</description>
      <category>commandh</category>
      <category>cmdh</category>
      <category>opensource</category>
      <category>macmenubarapp</category>
    </item>
    <item>
      <title>CommandH の紹介：最後のアプリも隠せるように</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Thu, 22 Oct 2026 14:17:05 +0000</pubDate>
      <link>https://dev.to/mattsenter/commandh-noshao-jie-zui-hou-noapurimoyin-seruyouni-53cd</link>
      <guid>https://dev.to/mattsenter/commandh-noshao-jie-zui-hou-noapurimoyin-seruyouni-53cd</guid>
      <description>&lt;p&gt;私は Cmd+H で画面を片づけています。でも macOS では、最後に表示されているアプリだけは隠せません。残り一つのウィンドウでもう一度押しても……何も起きません。&lt;/p&gt;

&lt;p&gt;そこで CommandH をつくりました。最後のアプリでも Cmd+H が効くようにする、小さなメニューバーアプリです。アプリを完全に隠すか、Show Desktop を選んでウィンドウを画面の端へ移動できます。後者では、もう一度 Cmd+H を押すと元に戻ります。&lt;/p&gt;

&lt;p&gt;MIT ライセンスで公開している、無料のオープンソースです。アクセシビリティや画面収録の権限は不要。ネットワーク通信もデータ収集もありません。デスクトップに戻るための、小さな修正です。&lt;/p&gt;

&lt;p&gt;CommandH は macOS 14 Sonoma 以降に対応しています。現在はソースからビルドしてインストールします。スクリプトの使い方は GitHub の README にあります。&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.mattsenter.com/ja/projects/commandh" rel="noopener noreferrer"&gt;CommandH について&lt;/a&gt; · &lt;a href="https://github.com/MattSenter/commandh" rel="noopener noreferrer"&gt;ソースコードとインストール手順&lt;/a&gt;&lt;/p&gt;

</description>
      <category>commandh</category>
      <category>cmdh</category>
      <category>opensource</category>
      <category>macmenubarapp</category>
    </item>
    <item>
      <title>Voici CommandH : masquez cette dernière app</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Thu, 22 Oct 2026 14:16:30 +0000</pubDate>
      <link>https://dev.to/mattsenter/voici-commandh-masquez-cette-derniere-app-501l</link>
      <guid>https://dev.to/mattsenter/voici-commandh-masquez-cette-derniere-app-501l</guid>
      <description>&lt;p&gt;J’utilise Cmd+H pour dégager mon écran. Mais sur macOS, la dernière app visible refuse de se masquer. Une fenêtre restante, une pression de plus et… rien.&lt;/p&gt;

&lt;p&gt;J’ai donc créé CommandH. Cette petite app de la barre des menus permet à Cmd+H de fonctionner aussi sur cette dernière app. Vous pouvez la masquer complètement ou choisir Show Desktop, qui écarte les fenêtres et les ramène avec un autre Cmd+H.&lt;/p&gt;

&lt;p&gt;Elle est gratuite et open source, sous licence MIT. Aucune autorisation d’accessibilité ou d’enregistrement de l’écran, aucune requête réseau, aucune donnée collectée. Juste un petit correctif pour retrouver mon bureau.&lt;/p&gt;

&lt;p&gt;CommandH fonctionne sur macOS 14 Sonoma ou version ultérieure. Pour le moment, l’installation passe par une compilation du code source ; le README sur GitHub explique comment utiliser le script.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.mattsenter.com/fr/projects/commandh" rel="noopener noreferrer"&gt;Découvrir CommandH&lt;/a&gt; · &lt;a href="https://github.com/MattSenter/commandh" rel="noopener noreferrer"&gt;Code et instructions d’installation&lt;/a&gt;&lt;/p&gt;

</description>
      <category>commandh</category>
      <category>cmdh</category>
      <category>opensource</category>
      <category>macmenubarapp</category>
    </item>
    <item>
      <title>介绍 CommandH：把最后一个应用也隐藏起来</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Thu, 22 Oct 2026 14:15:54 +0000</pubDate>
      <link>https://dev.to/mattsenter/jie-shao-commandhba-zui-hou-ge-ying-yong-ye-yin-cang-qi-lai-5328</link>
      <guid>https://dev.to/mattsenter/jie-shao-commandhba-zui-hou-ge-ying-yong-ye-yin-cang-qi-lai-5328</guid>
      <description>&lt;p&gt;我习惯用 Cmd+H 清空屏幕。但在 macOS 上，最后一个可见应用就是不肯隐藏。只剩一个窗口，再按一次……毫无反应。&lt;/p&gt;

&lt;p&gt;所以我做了 CommandH。这款小巧的菜单栏应用让 Cmd+H 对最后一个应用也有效。你可以彻底隐藏应用，也可以选择 Show Desktop，将窗口滑到屏幕边缘，再按 Cmd+H 就能恢复。&lt;/p&gt;

&lt;p&gt;它免费开源，采用 MIT 许可证。不需要辅助功能或屏幕录制权限，不发出网络请求，也不收集数据。只是一个让我顺利回到桌面的小修复。&lt;/p&gt;

&lt;p&gt;CommandH 支持 macOS 14 Sonoma 及更新版本。目前需要从源码构建安装；GitHub README 提供了脚本使用说明。&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.mattsenter.com/zh/projects/commandh" rel="noopener noreferrer"&gt;了解 CommandH&lt;/a&gt; · &lt;a href="https://github.com/MattSenter/commandh" rel="noopener noreferrer"&gt;获取源码和安装说明&lt;/a&gt;&lt;/p&gt;

</description>
      <category>commandh</category>
      <category>cmdh</category>
      <category>opensource</category>
      <category>macmenubarapp</category>
    </item>
    <item>
      <title>Presento CommandH: oculta esa última app</title>
      <dc:creator>Matt Senter</dc:creator>
      <pubDate>Thu, 22 Oct 2026 14:15:17 +0000</pubDate>
      <link>https://dev.to/mattsenter/presento-commandh-oculta-esa-ultima-app-25c8</link>
      <guid>https://dev.to/mattsenter/presento-commandh-oculta-esa-ultima-app-25c8</guid>
      <description>&lt;p&gt;Uso Cmd+H para despejar la pantalla. Pero en macOS, la última app visible se niega a ocultarse. Queda una ventana, pulso una vez más y… nada.&lt;/p&gt;

&lt;p&gt;Así que creé CommandH. Es una pequeña app de la barra de menús que hace que Cmd+H funcione también con esa última app. Puedes ocultarla por completo o elegir Show Desktop, que aparta las ventanas y las devuelve con otro Cmd+H.&lt;/p&gt;

&lt;p&gt;Es gratuita y de código abierto, con licencia MIT. Sin permisos de Accesibilidad ni de Grabación de pantalla, sin conexiones de red y sin recopilar datos. Solo una pequeña solución para llegar al escritorio.&lt;/p&gt;

&lt;p&gt;CommandH funciona en macOS 14 Sonoma o posterior. Por ahora se instala compilando el código fuente; el README de GitHub explica cómo ejecutar el script.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.mattsenter.com/es/projects/commandh" rel="noopener noreferrer"&gt;Conoce CommandH&lt;/a&gt; · &lt;a href="https://github.com/MattSenter/commandh" rel="noopener noreferrer"&gt;Código e instrucciones de instalación&lt;/a&gt;&lt;/p&gt;

</description>
      <category>commandh</category>
      <category>cmdh</category>
      <category>opensource</category>
      <category>macmenubarapp</category>
    </item>
  </channel>
</rss>
