Dad working from home | Coffee ☕️ | Family, code & small ideas | https://xitter.gq/t.co/EWFebIIi5g https://xitter.gq/t.co/F3iGt6Iwct
Joined April 2009
- Tweets1K
- Following2.6K
- Followers173
- Likes1.4K
Been spending more time on marketing and distribution lately. There's actually a lot involved. SEO, content, social media, outreach, figuring out where your potential customers are...
And none of it happens overnight.
Been using Claude Code with Opus 5.5 (medium thinking) lately, and I'm quite impressed.
Sometimes it builds an entire feature with barely any changes needed.
Other times, one tiny issue takes longer to fix than the whole feature 😂
Felix Tj retweeted
Introducing OpenShip.
An open-source application platform for building, deploying, operating, and scaling applications on infrastructure you own.
Replace deployment tools, managed services, and infrastructure workflows with one open-source platform.
Available today:
- Mail Server (Built in. One click).
• Runs on your own VPS
• Unlimited domains
• Unlimited mailboxes
• Modern webmail included
• Connect with Gmail, Outlook, Apple Mail, Thunderbird, or any IMAP/SMTP client
• Send email directly from your applications using SMTP
• No mailbox subscriptions or API fees
• High email deliverability
- Deployment:
• Deploy any stack
• Git-based deployments
• Zero-downtime deployments
• One-click rollbacks
• Development, Staging, and Production environments
• Multi-branch deployments with isolated environments • Deploy to VPSs, dedicated servers, cloud VMs, or your homelab
- Services:
Provision the services your applications need in one click.
Replace multiple managed providers with services running on your own infrastructure.
• Supabase
• PostgreSQL
• MySQL
• MariaDB
• MongoDB
• Redis
• MinIO
• Meilisearch
• Qdrant
• RabbitMQ
• Kafka
• ClickHouse
• Elasticsearch
...and deploy any other service alongside your applications.
- Operate:
• Live deployment logs
• Live request logs
• Real-time traffic analytics
• Automated backups
• Monitoring
• Secrets management
• Domains
• Automatic SSL
• Environment variables
• Scheduled jobs
• Health checks
-Multi Environments:
• Separate Development, Staging, and Production environments
• Deploy every branch independently
• Test changes before production
• Isolated services, secrets, and configuration per environment
- Security & Teams:
• Team management
• Role-based access control
• IP allow/block rules
• Rate limiting
• Security rules
- Developer Experience:
• Web dashboard
• Native desktop application
• CLI
• REST API
• MCP support for AI agents, just add the mcp and your agent can do the work for you
• Manage your infrastructure without living in SSH
- Coming Soon:
• Multi-server clustering for applications and databases
• One-click load balancing
• Horizontal scaling across multiple servers
• Built-in high availability and failover
• Scale from a single VPS to a cluster with the same workflow
• Just add servers. OpenShip handles the rest.
Open source.
Felix Tj retweeted
‼️ Tailscale SSH Flaws Could Let Hackers Gain Root Access Across Servers
Details: cybersecuritynews.com/tailsc…
A new security report warns that Tailscale SSH has flaws that could let a hacker move from one compromised device to root access on other servers. Tailscale SSH lets approved devices log in to each other over a private network. The report lists 11 findings in five groups.
They cover Tailscale’s SSH server, its serve and app connector features, the DERP relay client, and headscale, an open-source server that manages Tailscale networks.
The researcher tested Tailscale 1.104.2 and headscale 0.29.5 between October 22 and October 24, 2026. The most serious group involves Tailscale SSH. Its SSH server runs inside tailscaled, a background program with full root privileges on the machine.
#cybersecuritynews
Readers added context they thought people might want to know
The flaws require an already-approved device in the Tailscale network with SSH rules permitting access/forwarding; they enable post-compromise lateral movement and escalation inside the tailnet, not unauthenticated remote access from outside.
tailworm.com
brandefense.io/security-news/…
tailscale.com/security-bulle…
x.com/mmaunder/statu…
Railway's outage has kept me from deploying for around 7 hours. I like Railway, but it's probably worth exploring other options too.
What are you using to host and deploy your apps these days? Any recommendations?
Today's reminder that shipping software depends on more than just writing code. Railway's outage has had builds paused for hours, and I haven't been able to deploy my updates.
Cloud platforms make development much easier, but you also depend on their availability.
AI makes it tempting to keep adding features.
Something that might have taken days can now be prototyped much faster.
I'm starting to think distribution deserves as much attention as development. It's relatively easy to spend another week improving a feature.
Much harder to spend that week finding out how to reach people who might actually need it. 😅
Before I put a workflow live, I test it with a request that doesn't fit. I want to see the request held at the defined stop, ready for a decision. If it keeps moving anyway, I haven't finished the workflow, no matter how well the automatic path works.
I don't choose the tool first. I write the stop condition first. Without one, an uncertain request keeps moving, gets processed by the next step, and creates work someone has to undo or revisit. The workflow needs a clear boundary before it needs more automation.
Still working on SodaDesk for small HVAC and field teams. Not trying to be another big platform. Just something that makes photo documentation and job accountability less painful for 5–20 team operations.
A timestamp won't answer who was at the property, what was checked, or what happened there. You need the technician tied to the job, time on site, photos, checklist items, and the record that shows the work. Otherwise, you're reconstructing the visit after it's closed.
Required proof belongs in the job before it can be closed. That might mean the after photo, a recorded reading, a completed checklist item, or a customer signature where it belongs. Missing details are easier to catch at the job than after you're chasing notes.