🚀 5–9: Solopreneur scaling my own company
💡Sharing daily insights to help you build faster → https://github.com/jlison
🍎 macOS: brew install exiftool
🪟 Windows: choco install exiftool
🐧 Ubuntu: sudo apt update && sudo apt install -y libimage-exiftool-perl
Verify: exiftool -ver
#DevTools #OpenSource
🍎 macOS: brew install exiftool
🪟 Windows: choco install exiftool
🐧 Ubuntu: sudo apt update && sudo apt install -y libimage-exiftool-perl
Verify: exiftool -ver
#DevTools #OpenSource
It may not work for everyone, but I still recommend giving it a try
It may not work for everyone, but I still recommend giving it a try
#encryption #diskencryption #privacy #privacytools #cryptography #cybersecurity #devsecops
github.com/veracrypt/Ve...
#encryption #diskencryption #privacy #privacytools #cryptography #cybersecurity #devsecops
github.com/veracrypt/Ve...
If agencies can't crack the crypto, your threat is keys & opsec:
1. Use a long passphrase (5–7 random words)
2. Dismount when idle; fully shut down, don't sleep (RAM/key attacks exist)
3. Ensure hiberfile is encrypted; consider VC's RAM-key protection setting
If agencies can't crack the crypto, your threat is keys & opsec:
1. Use a long passphrase (5–7 random words)
2. Dismount when idle; fully shut down, don't sleep (RAM/key attacks exist)
3. Ensure hiberfile is encrypted; consider VC's RAM-key protection setting
1. Download from the official repo (verify sigs)
2. Create an encrypted container or full-disk volume
3. Mount → work → dismount
4. Keep backups of unencrypted essentials like recovery info (securely stored)
1. Download from the official repo (verify sigs)
2. Create an encrypted container or full-disk volume
3. Mount → work → dismount
4. Keep backups of unencrypted essentials like recovery info (securely stored)
- Cross-platform (Win/Mac/Linux)
- CLI automation + scripting
- Hidden volumes (plausible deniability but use carefully; research has poked holes in some scenarios)
- Fast on modern CPUs, open source, no proprietary dependencies
- Cross-platform (Win/Mac/Linux)
- CLI automation + scripting
- Hidden volumes (plausible deniability but use carefully; research has poked holes in some scenarios)
- Fast on modern CPUs, open source, no proprietary dependencies
- 🇺🇸 2018: Court filing notes the FBI couldn't decrypt VeraCrypt protected devices and sought to compel unlocking instead
- 🇧🇷 2010: Brazilian banker case: after months of effort (incl. FBI help)
- No public evidence of a VeraCrypt backdoor
- 🇺🇸 2018: Court filing notes the FBI couldn't decrypt VeraCrypt protected devices and sought to compel unlocking instead
- 🇧🇷 2010: Brazilian banker case: after months of effort (incl. FBI help)
- No public evidence of a VeraCrypt backdoor
♻️ Bonus: cron it weekly + push to a private repo
♻️ Bonus: cron it weekly + push to a private repo
I also really liked your point about using actions. Forgot to highlight that one!
I also really liked your point about using actions. Forgot to highlight that one!
✅ API responses that change hourly/daily
✅ Computed data with short TTL
✅ Anything under 128MB
Don't use it for:
❌ User file uploads
❌ Data you need for months
❌ Cross-region consistency
✅ API responses that change hourly/daily
✅ Computed data with short TTL
✅ Anything under 128MB
Don't use it for:
❌ User file uploads
❌ Data you need for months
❌ Cross-region consistency
🚀 Cache API: <10ms response time (edge cache)
🚀 R2: 20-50ms (object storage)
Developer experience:
🎯 Cache API: 3 lines of code
🎯 R2: SDK setup, bucket management, error handling
🚀 Cache API: <10ms response time (edge cache)
🚀 R2: 20-50ms (object storage)
Developer experience:
🎯 Cache API: 3 lines of code
🎯 R2: SDK setup, bucket management, error handling
Each schedule triggers the same workflow, but conditional if statements run different jobs based on which cron fired.
Result? One file manages your entire automation schedule.
Each schedule triggers the same workflow, but conditional if statements run different jobs based on which cron fired.
Result? One file manages your entire automation schedule.
1. Create ".github/workflows/cron.yml"
2. add your cron schedule
3. push to main
That's literally it. GitHub handles provisioning, execution, scaling, monitoring.
#IndieHackers Stop overthinking automation. Just use #GitHubActions.
1. Create ".github/workflows/cron.yml"
2. add your cron schedule
3. push to main
That's literally it. GitHub handles provisioning, execution, scaling, monitoring.
#IndieHackers Stop overthinking automation. Just use #GitHubActions.
✍️ - Auto posting on BlueSky
🔄 - Daily backup scripts
📊 - Metrics collection
🐛 - Health checks
📨 - Notification systems
💾 - Database cleanup tasks
🔍 - API monitoring
All running in the cloud, tracked in git, completely free for public repos. #WebDev #TechTips