|
| 1 | +# Reddit Post Template for SecureGen |
| 2 | + |
| 3 | +## 📋 Recommended Subreddits (in order of priority): |
| 4 | + |
| 5 | +1. **r/esp32** - Main ESP32 community (most relevant) |
| 6 | +2. **r/arduino** - Arduino/embedded projects |
| 7 | +3. **r/embedded** - Embedded systems |
| 8 | +4. **r/cybersecurity** - Security focus |
| 9 | +5. **r/privacy** - Privacy-focused audience |
| 10 | +6. **r/selfhosted** - Self-hosted solutions |
| 11 | +7. **r/opensource** - Open source projects |
| 12 | +8. **r/LILYGO** - LILYGO hardware specific |
| 13 | +9. **r/maker** - Maker community |
| 14 | +10. **r/electronics** - Electronics enthusiasts |
| 15 | + |
| 16 | +--- |
| 17 | + |
| 18 | +## 📝 Post Title Options: |
| 19 | + |
| 20 | +**Option 1 (Technical):** |
| 21 | +``` |
| 22 | +[Project] SecureGen - Open-source Hardware TOTP Authenticator & Password Manager on ESP32 T-Display |
| 23 | +``` |
| 24 | + |
| 25 | +**Option 2 (Feature-focused):** |
| 26 | +``` |
| 27 | +I built a hardware 2FA authenticator with password manager using ESP32 T-Display (Open Source) |
| 28 | +``` |
| 29 | + |
| 30 | +**Option 3 (Problem-solving):** |
| 31 | +``` |
| 32 | +Tired of phone-based authenticators? Built an offline hardware TOTP device with ESP32 |
| 33 | +``` |
| 34 | + |
| 35 | +--- |
| 36 | + |
| 37 | +## 📄 Post Content (Markdown format for Reddit): |
| 38 | + |
| 39 | +```markdown |
| 40 | +# SecureGen - Hardware TOTP Authenticator & Password Manager |
| 41 | + |
| 42 | +Hi r/esp32! I've been working on an open-source security device and just released v1.0.0. Thought you might find it interesting! |
| 43 | + |
| 44 | +## 🔐 What is it? |
| 45 | + |
| 46 | +SecureGen is a hardware-based TOTP authenticator (like Google Authenticator) combined with a password manager, built on the LILYGO ESP32 T-Display. It's completely offline and air-gapped for maximum security. |
| 47 | + |
| 48 | +## ✨ Key Features |
| 49 | + |
| 50 | +- **TOTP Authenticator** - RFC 6238 compliant, 30/60 second codes |
| 51 | +- **Password Manager** - Encrypted vault with 256-bit AES |
| 52 | +- **BLE Keyboard** - Types passwords directly into your computer |
| 53 | +- **7+ Security Layers** - PBKDF2, traffic obfuscation, anti-timing attacks |
| 54 | +- **Web Interface** - Easy management via WiFi |
| 55 | +- **Battery Powered** - Portable with JST battery connector |
| 56 | +- **Dual Themes** - Light/Dark mode support |
| 57 | +- **Offline First** - No cloud, no internet required for operation |
| 58 | + |
| 59 | +## 🎯 Why I Built This |
| 60 | + |
| 61 | +I wanted a physical 2FA device that: |
| 62 | +- Doesn't rely on my phone |
| 63 | +- Works completely offline |
| 64 | +- Stores passwords securely |
| 65 | +- Is open source and auditable |
| 66 | +- Can type passwords via BLE keyboard |
| 67 | + |
| 68 | +## 📦 What's Included |
| 69 | + |
| 70 | +The v1.0.0 release includes: |
| 71 | +- Pre-compiled firmware binaries (ready to flash) |
| 72 | +- Full source code |
| 73 | +- Documentation and setup guides |
| 74 | +- Web interface for management |
| 75 | + |
| 76 | +## 🛠️ Hardware Requirements |
| 77 | + |
| 78 | +- LILYGO T-Display ESP32 (~$15 on AliExpress) |
| 79 | +- USB-C cable for programming |
| 80 | +- Optional: 3.7V LiPo battery with JST connector |
| 81 | + |
| 82 | +## 🚀 Installation |
| 83 | + |
| 84 | +Three options: |
| 85 | +1. **Flash pre-built binaries** (easiest - just download and flash) |
| 86 | +2. **Build from source** with PlatformIO |
| 87 | +3. **Use Arduino IDE** |
| 88 | + |
| 89 | +Full instructions in the repo! |
| 90 | + |
| 91 | +## 📸 Screenshots |
| 92 | + |
| 93 | +[Add your screenshots here when you have them] |
| 94 | + |
| 95 | +## 🔗 Links |
| 96 | + |
| 97 | +- **GitHub Repository:** https://github.com/makepkg/SecureGen |
| 98 | +- **Latest Release:** https://github.com/makepkg/SecureGen/releases/tag/v1.0.0 |
| 99 | +- **Documentation:** https://github.com/makepkg/SecureGen/blob/master/README.md |
| 100 | + |
| 101 | +## 🤝 Contributing |
| 102 | + |
| 103 | +This is fully open source (MIT License). Contributions, bug reports, and feature requests are welcome! |
| 104 | + |
| 105 | +## 💭 Questions? |
| 106 | + |
| 107 | +Happy to answer any questions about the project, security architecture, or implementation details! |
| 108 | + |
| 109 | +--- |
| 110 | + |
| 111 | +**Tech Stack:** ESP32, Arduino Framework, TFT_eSPI, BLE, AES-256, PBKDF2, ECDH |
| 112 | + |
| 113 | +**License:** MIT |
| 114 | + |
| 115 | +If you find this useful, a ⭐ on GitHub would be appreciated! |
| 116 | +``` |
| 117 | + |
| 118 | +--- |
| 119 | + |
| 120 | +## 🎨 Post with Images (Alternative format): |
| 121 | + |
| 122 | +If you have screenshots ready, use this format: |
| 123 | + |
| 124 | +```markdown |
| 125 | +# [Project] SecureGen - Hardware TOTP + Password Manager on ESP32 |
| 126 | + |
| 127 | +[Image 1: Device showing TOTP code] |
| 128 | + |
| 129 | +Just released v1.0.0 of my open-source hardware authenticator project! |
| 130 | + |
| 131 | +**What it does:** |
| 132 | +- Generates TOTP codes (like Google Authenticator) |
| 133 | +- Stores passwords in encrypted vault |
| 134 | +- Types passwords via BLE keyboard |
| 135 | +- Completely offline and air-gapped |
| 136 | + |
| 137 | +[Image 2: Web interface] |
| 138 | + |
| 139 | +**Hardware:** LILYGO T-Display ESP32 (~$15) |
| 140 | + |
| 141 | +**Security:** 7+ layers including AES-256, PBKDF2, traffic obfuscation |
| 142 | + |
| 143 | +[Image 3: Different screens/modes] |
| 144 | + |
| 145 | +**Features:** |
| 146 | +✅ Battery powered & portable |
| 147 | +✅ Web-based management |
| 148 | +✅ Light/Dark themes |
| 149 | +✅ Factory reset protection |
| 150 | +✅ PIN code lock |
| 151 | + |
| 152 | +**Download:** Pre-built firmware ready to flash! |
| 153 | + |
| 154 | +🔗 GitHub: https://github.com/makepkg/SecureGen |
| 155 | +📦 Release: https://github.com/makepkg/SecureGen/releases/tag/v1.0.0 |
| 156 | + |
| 157 | +Open source (MIT) - contributions welcome! |
| 158 | + |
| 159 | +AMA about the project! 🚀 |
| 160 | +``` |
| 161 | + |
| 162 | +--- |
| 163 | + |
| 164 | +## 📊 Posting Strategy: |
| 165 | + |
| 166 | +### Timing: |
| 167 | +- **Best days:** Tuesday-Thursday |
| 168 | +- **Best time:** 8-10 AM EST or 2-4 PM EST |
| 169 | +- Avoid weekends for technical subs |
| 170 | + |
| 171 | +### Engagement Tips: |
| 172 | +1. **Respond quickly** to comments in first 2 hours |
| 173 | +2. **Be helpful** - answer technical questions |
| 174 | +3. **Share details** about challenges you faced |
| 175 | +4. **Add flair** if subreddit requires it |
| 176 | +5. **Cross-post** after 24 hours to other relevant subs |
| 177 | + |
| 178 | +### What to Prepare: |
| 179 | +- [ ] High-quality photos of device |
| 180 | +- [ ] GIF/video of it in action (optional but great) |
| 181 | +- [ ] Screenshots of web interface |
| 182 | +- [ ] Be ready to answer questions about: |
| 183 | + - Security implementation |
| 184 | + - Why not use phone apps |
| 185 | + - Hardware cost |
| 186 | + - Battery life |
| 187 | + - Comparison to YubiKey/other devices |
| 188 | + |
| 189 | +### Follow Reddit Rules: |
| 190 | +- Check each subreddit's rules before posting |
| 191 | +- Some require [Project] or [OC] tags |
| 192 | +- Some have specific days for project posts |
| 193 | +- Don't spam multiple subs at once (space out by 24h) |
| 194 | + |
| 195 | +--- |
| 196 | + |
| 197 | +## 🎯 Expected Questions & Answers: |
| 198 | + |
| 199 | +**Q: Why not just use Google Authenticator on phone?** |
| 200 | +A: This is for people who want a dedicated, offline device. Phone can be lost, hacked, or out of battery. This is air-gapped and purpose-built. |
| 201 | + |
| 202 | +**Q: How is this different from YubiKey?** |
| 203 | +A: YubiKey is hardware-only (no screen). This has a display showing codes, stores passwords, and can type them via BLE. Also it's open source and $15 vs $50+. |
| 204 | + |
| 205 | +**Q: Is it secure to have WiFi on a security device?** |
| 206 | +A: WiFi is only for initial setup and management. During normal operation, you can disable WiFi completely. TOTP generation works 100% offline. |
| 207 | + |
| 208 | +**Q: Battery life?** |
| 209 | +A: Several days of active use, weeks on standby. Depends on usage patterns and battery capacity. |
| 210 | + |
| 211 | +**Q: Can I audit the security?** |
| 212 | +A: Yes! Full source code is available. Security documentation explains all layers. That's the point of open source. |
| 213 | + |
| 214 | +--- |
| 215 | + |
| 216 | +## 📈 Success Metrics: |
| 217 | + |
| 218 | +Good post performance: |
| 219 | +- 50+ upvotes in first 24h |
| 220 | +- 10+ comments with questions |
| 221 | +- 5+ GitHub stars from Reddit traffic |
| 222 | + |
| 223 | +Great post performance: |
| 224 | +- 200+ upvotes |
| 225 | +- 30+ comments |
| 226 | +- 20+ GitHub stars |
| 227 | +- Cross-posts to other subs |
| 228 | + |
| 229 | +--- |
| 230 | + |
| 231 | +## 🔄 Follow-up Posts (Future): |
| 232 | + |
| 233 | +After initial release, you can post updates: |
| 234 | +- "v1.1.0 released with [new features]" |
| 235 | +- "Tutorial: How I implemented [specific feature]" |
| 236 | +- "Lessons learned building a hardware security device" |
| 237 | +- "Community requested features now live" |
| 238 | + |
| 239 | +--- |
| 240 | + |
| 241 | +**Ready to post? Start with r/esp32 - it's the most relevant community!** |
| 242 | + |
| 243 | +Good luck! 🚀 |
0 commit comments