Cursor projects is hands down the best way to build, especially when working collaboratively.
Cursor Projects are *insane*, but they're still only at ~40% of where I think they should and will be in the future.
You should start using them right away (they're such a big improvement over Agents/Chats), but please give us some time to iron out the edges and perfect them.
2
249
Network effect has been, and always will be the most durable moat.
.@levelsio no longer believes in SaaS. Here are the six moats he says actually matter in the AI era.
1
4
191
Tailscale and Cloudflare’s free tiers are too good to be true. I know I’ll one day get rug pulled and be in too deep to switch.
Until that day comes I’m grateful for your services 🙏
what's the best macOS tiling/window manager right now? any recs?
Been using aerospace but looking to switch it up to something with better screen sharing support.
3
130
A cool @X feature would be "communities." Filtering your feed to people in your geographic proximity, with further filtering based upon interests.
1
5
329
have any of the @OmarchyMac folks attempted to get iPhone continuity camera working?
I've got a jerry rigged version up and running but I'm hoping someone smarter than me has produced a more seamless/native feeling solution
52
What is it about videos from this era that invoke so much nostalgia?
I think a lot of it is the warm glow of pre-LED lightbulbs.
1
87
the most plausible explanation I’ve seen
Lots of hot takes on the Microsoft 365 outage. Here's an engineering one.
To be clear: this is speculation. Microsoft hasn't confirmed a root cause. It's my read of their own updates, from 35 years of building and breaking systems.
What Microsoft has actually said:
• Traffic isn't up. Capacity is down. Servers are failing health checks and dropping out.
• A process that establishes secure connections gets overwhelmed, and servers stop processing requests.
• Servers they bring back fall over again as soon as traffic hits them.
• They're reverting a network config change that lines up with when it started. But changes aren't syncing, and some machines are stuck in a bad state.
• No indication of an attack.
My hypothesis: a metastable failure.
Whatever triggered it may be long gone. The outage is now keeping itself alive.
1. Reconnect storm. Every Outlook, Teams and mobile client on the planet is hammering for a fresh secure connection.
Full TLS handshakes are CPU-heavy, and a freshly rebooted server has a cold session cache.
A server comes up, eats a wall of handshakes, CPU pegs, it fails its health check and gets pulled, and its load lands on the next one. Dominoes.
2. The fix shares fate with the failure. If the rollback travels over the same secure channel that's melting, the cure can't reach the patient.
That's exactly what "changes aren't syncing" sounds like to me.
That's why they're throttling traffic types and rebuilding servers from an older config instead of flipping a switch.
You don't get out of this by finding the bug.
You get out by shedding load, restoring capacity in isolated cells, and letting traffic back in slowly.
Where AI fits (also speculation): not "an AI wrote the bad line". It's velocity. Microsoft flagged several recent config changes as suspects and took hours to find one that correlated.
When the volume of change outpaces the humans who understand each change, finding the culprit gets slow and rollbacks get messy. Automate the shipping faster than you automate the understanding, and this is the bill.
The takeaway for every business: your email, chat, files, identity and security tooling now share one failure domain. Today proved it. Have a way to talk to your team that doesn't live in the same tenant.
Happy to be proven wrong by the post-incident review. And I hope this post ages terribly.
57
Huge improvements to grok @bot’s end to end task completion.
Hand off something complicated, you will notice a difference!
1
4
219





















