Building @SpondrApp 🦀 Also… Bitcoin. Marketing. AI. Email nerd. Doing it all in public.
Beaverton, OR
Joined October 2007
- Tweets9.8K
- Following1.1K
- Followers1.1K
- Likes12.1K
Pinned Tweet
Spondr is in alpha. 🦀
A native Linux email client for Gmail. Built in Rust. No browser tab, no middleman servers. Passed Google's CASA security audit.
Looking for Linux + Gmail users to help break it.
👉 spondr.co/#signup?ref=x-pinn…
4
155
Password manager extensions are one of those things you only notice when they're missing. Windows now, Mac on the way. Any plans for a Linux version?
DuckDuckGo for Windows is adding support for password manager extensions.
We're starting with Bitwarden and LastPass, with more on the way. Windows users, head to Settings to add the extensions now. (And Mac users, we're working on it!)
Learn more: duckduckgo.com/duckduckgo-he…
1
22
The 15-minute countdown where anyone can pause a release is such a good idea. Simple, and nobody needs a meeting to get a say.
We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work.
First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs.
Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue).
Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main.
Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown.
The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in.
Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way.").
This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours.
All of this works on mutual trust. It ONLY works with mutual trust.
Everyone at all times has to trust that they've got each others back:
1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts).
2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer.
3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly).
We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago.
In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.
1
55
The Linux desktop doesn't lose on tech. It loses because nobody is paid to make the whole thing feel finished.
What would actually accelerate Linux desktop share?
26
I keep coming back to this: distro fragmentation is great for invention, terrible for adoption.
Every distro can try something new. That same spread makes shipping one Linux app to everyone hard.
When you ship a Linux app, which packaging format do you start with?
30
Indie devs can't support every Linux distro, so we end up picking one or two targets.
Trying to cover everything usually ends badly.
If you could only support two distros, which would you pick?
2
1
43
Open-weight models will be good enough for most people. You don't need a PhD in your pocket to schedule pickleball.
Near-frontier models already run locally. Meta's Muse Spark Open runs on two M5 Ultra Mac Studios. That's a real threat to the consumer side of OpenAI and Anthropic, maybe Google too.
The future looks like local models, updated now and then, with privacy as a selling point.
68
Web UI is going to change a lot in the next few years. Agents are becoming the web's clients, and a polished interface doesn't matter to them.
The internet turns into a backend, and the agent builds the screen a person needs on the spot. Habit and old systems will slow it down. How fast it transforms, I'm not sure.
When did you last need a dashboard a human designed?
28
Discipline is when you do that thing you know is right but don't feel like doing, consistently, without reward, for a long time.
Both things are very hard.
3
7
259
Good reminder to run your updates today if you're on Ubuntu or Debian.
Fixes are available for CVE-2026-109518, a High severity vulnerability in APT, the package manager used in Debian, Ubuntu, and derivative Linux distributions. The CVE has a CVSS 4.0 score of 7.7.
Remediation details are available on our blog.
ubuntu.com/blog/apt-vulnerab…
23
The cost to build has collapsed. Linux desktop apps used to need a big company with a profit forecast, and the market rarely justified it.
With AI, solo devs can ship a high-quality native app that only needs to pay the bills, not become a unicorn.
More devs should build for Linux. Every Linux user benefits.
Would you pay for a great native Linux app?
1
23
