Changeset 3429405
- Timestamp:
- 12/30/2025 04:30:24 AM (13 days ago)
- File:
-
- 1 edited
-
pinnys-simple-smtp/tags/1.0.0/readme.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
pinnys-simple-smtp/tags/1.0.0/readme.txt
r3429402 r3429405 65 65 **Pinny's Simple SMTP** keeps your WordPress database clean, fast, and secure by letting your email provider do its job. 66 66 67 🚫The “Anti-Bloat” Architecture: Why We Rejected OAuth 68 Pinny’s Simple SMTP is built on a strict performance philosophy: Do not load code you do not use. 67 ### 🚫 The “Anti-Bloat” Architecture: Why We Rejected OAuth 68 69 **Pinny’s Simple SMTP** is built on a strict performance philosophy: **Do not load code you do not use.** 69 70 70 71 The industry standard is to force users into OAuth (Log in with Google/Microsoft). While this looks fancy, for a WordPress plugin, it is technically inferior to standard SMTP. Here is why we deliberately stripped OAuth out of Pinny’s: 71 72 72 1. The "Universal Adapter" Trap (Bloat) 73 Most users connect to oneprovider (e.g., just Gmail). However, to support OAuth, other plugins must bundle massive SDK libraries for 10–15 different services (Google, Microsoft, Amazon, Yahoo, Zoho, etc.).73 **1. The “Universal Adapter” Trap (Bloat)** 74 Most users connect to **one** provider (e.g., just Gmail). However, to support OAuth, other plugins must bundle massive SDK libraries for 10–15 different services (Google, Microsoft, Amazon, Yahoo, Zoho, etc.). 74 75 75 The Result: You install megabytes of vendor code just to send a simple email. 76 * **The Result:** You install megabytes of vendor code just to send a simple email. 77 * **Our Fix:** Pinny’s uses standard SMTP. We don’t force you to host 14 unused API libraries on your server just to use the 15th. This keeps our codebase at **~4.5KB** and auditable in minutes. 76 78 77 Our Fix: Pinny’s uses standard SMTP. We don't force you to host 14 unused API libraries on your server just to use the 15th. This keeps our codebase at ~4.5KB and auditable in minutes. 79 **2. The Complexity Risk (Security)** 80 In security, **Complexity is the Enemy.** OAuth flows require redirects, token storage, refresh tokens, and constant API updates. Every external library added to a plugin increases the “Attack Surface”—more code means more places for bugs to hide. 78 81 79 2. The Complexity Risk (Security) 80 In security, Complexity is the Enemy. OAuth flows require redirects, token storage, refresh tokens, and constant API updates. Every external library added to a plugin increases the "Attack Surface"—more code means more places for bugs to hide.82 * **The Reality:** If a plugin’s bundled “Google API Client” has a vulnerability, your site is at risk—even if you are using Outlook. 83 * **Our Fix:** We use native WordPress functions. **No external dependencies.** No third-party SDKs. No supply-chain vulnerabilities. 81 84 82 The Reality: If a plugin’s bundled "Google API Client" has a vulnerability, your site is at risk—even if you are using Outlook. 85 **3. App Passwords: The Superior Choice** 86 We use **App Passwords** (Standard SMTP Authentication). This is the secure, recommended method for server-side mailing (Gmail/Workspace & Microsoft 365). 83 87 84 Our Fix: We use native WordPress functions. No external dependencies. No third-party SDKs. No supply-chain vulnerabilities. 88 * **Strictly Scoped:** An App Password usually only has permission to *send mail*. Unlike an OAuth token (which can sometimes be scoped too broadly), an App Password cannot be used to change your account settings or read your Drive files. 89 * **Instantly Revocable:** If you suspect a breach, you can revoke that specific App Password instantly from your Google/Microsoft dashboard without changing your main login credentials. 90 * **Zero Downtime:** OAuth tokens expire or disconnect if the API changes. App Passwords work until you say stop. 85 91 86 3. App Passwords: The Superior Choice 87 We use App Passwords (Standard SMTP Authentication). This is the secure, recommended method for server-side mailing (Gmail/Workspace & Microsoft 365). 88 89 Strictly Scoped: An App Password usually only has permission to send mail. Unlike an OAuth token (which can sometimes be scoped too broadly), an App Password cannot be used to change your account settings or read your Drive files. 90 91 Instantly Revocable: If you suspect a breach, you can revoke that specific App Password instantly from your Google/Microsoft dashboard without changing your main login credentials. 92 93 Zero Downtime: OAuth tokens expire or disconnect if the API changes. App Passwords work until you say stop. 94 95 Pinny’s Simple SMTP chooses stability over shiny buttons. Enter your Host, Port, and App Password → Save. Done. 96 92 **Pinny’s Simple SMTP** chooses stability over shiny buttons. Enter your Host, Port, and App Password → Save. **Done.** 97 93 --- 98 94
Note: See TracChangeset
for help on using the changeset viewer.