I've always been intrigued by the whole "decentralized and fixed supply" argument around Bitcoin and similar cryptocurrencies.
But the more I look into it, the more I wonder: if one Bitcoin can be split into 0.1, 0.01, 0.001 or even smaller fractions for transactions, doesn't that kind of undermine the whole “fixed total supply” idea?
Also, sure, cryptocurrencies are decentralized in theory and the transactions are hard to trace. But at the end of the day, anyone holding crypt is still very much under the control of governments. You can't magically escape regulations or enforcement just because the currency is "decentralized." It's an interesting tension between theory and reality that I don't think enough people talk about.
Maybe we could try asking Claude to generate code using <table>, <tr>, <td> for layout instead of relying on div + CSS. Feels like it could simplify things a lot.
Would this actually work, or am I missing something?
If the goal is to fix the behavior instead of just documenting it, the penalties need to escalate with repeat violations. The first mismatch can be treated as an honest mistake. But when the third or fourth inspection still shows the same pattern, the fine shouldn't be the same $5k: it should jump sharply. At some point the cost of ignoring the problem has to exceed the profit from letting it continue.
Right now the incentive structure is backwards. As long as the downside is fixed and small, large retailers will keep treating it as business-as-usual. A tiered system tied to repeated violations would at least push them toward actually fixing the issue, instead of just shrugging it off every time they get caught.
Thanks for the heads-up! I actually wrote this based on my own thoughts about the incident, but I understand the concern. I'll make sure to keep my posts in line with the community guidelines.
What this incident really shows is the growing gap between how easy it is to create a convincing warning and how costly it is to verify what's actually happening. Hoaxes aren't new, but generative tools make fabrication almost free and massively increase the volume.
The rail operator didn't do anything wrong. After an earthquake and a realistic-looking image, the only responsible action is to treat it as potentially real and inspect the track.
This wasn't catastrophic, but it's a preview of a world where a single person can cheaply trigger high-cost responses. The systems we build will have to adapt, not by ignoring social media reports, but by developing faster, more resilient ways to distinguish signal from noise.
Your approach looks promising. One question: how do you handle conflict resolution at scale? ProseMirror's steps model helps, but once you mix in multiple cursors, mobile clients, and permission controls, things get complicated fast. If you've built extra abstractions or a custom syncing layer on top of ProseMirror, I'd be very interested in how you approached it.
Overall, impressive work - it’s refreshing to see an editor that aims for minimalism without sacrificing collaboration features. Bookmarking this to test on a few writing workflows.
You're absolutely right, ending up in spam is a real pain. I've run into the same issue myself with custom domains; even when everything is set up correctly, delivery can still be unreliable.
If I'm remembering correctly, there was another outage around 10 days ago.
It still surprises me that there are basically no free alternatives comparable to Cloudflare. Putting everything on CF creates a pretty serious single point of failure.
It's strange that in most industries you have at least two major players, like Coke vs. Pepsi or Nike vs. Adidas. But in the CDN/edge space, there doesn't seem to be a real free competitor that matches Cloudflare's feature set.
It feels very unhealthy for the ecosystem. Does anyone know why this is the case?
Absolutely — leaders must learn to delegate. Without delegation, you end up doing everything yourself, which isn’t sustainable and will burn you out. Effective leaders trust their team and distribute responsibilities wisely.
I'm not really sure I understand this. How is the new if() conditional function different from using @media (width ...) when adapting layouts to browser width?