fside

Sure thing, but essentially it would be another thing that we have to make sure that it is protected and performant. At the time of building a startup, that’s still an item we are leaving someone else to manage.

Should be easy enough. But, the problem is the scale. I work at a privacy conscious EU based startup and we used to use quad9 for our infra. Shortly after we started using, we started to hit scalability issues. When the whole eu traffic was hot, our DNS query latency would also go up. To be able to keep up, we had to switch back to CF and Google. Hope there is a really good alternative one day.

I’m with the author. DNS4EU is being sold as “sovereignty,” but it’s just another centralized resolver sitting on the same foreign-owned infrastructure we already depend on. Shuffling everyone’s queries through one EU-branded endpoint doesn’t fix privacy or resilience—it just adds another middleman. If the EU really wants independence, it should invest in making local ISP resolvers secure and trustworthy instead of outsourcing the job yet again.

The workflow here feels pretty natural, just using the AI to help with the boring parts and speed things up. I like the idea of treating it as a tool, not a replacement.

Well, we have realized the issue like 1 hr before they shared anything in their pages. That 1 hour feels forever. Essentially, I want my problem to be acknowledged from a service provider which they failed to do so in their status page.

I’m sure it’s related to the heroku outage.

probably related to https://news.ycombinator.com/item?id=44233923

It’s amazing. We cannot even submit a support ticket, because they require you to login and the incident is on the authentication path. You think such a company wouldn’t introduce a circular dependency at such a critical path…

I wonder if anyone has switched algorithms after hitting real-world scaling issues with one of those? Curious if there are any “gotchas” that only show up at scale. I only have experience with fixed window rate limiting

Amazing step towards saving tax payers money and avoiding foreign proprietary software. I hope to see more governments moving in this direction. The only problem is, certain systems may end up being a maintenance horror story.

Finally, a proof that’s less ‘universal truth’ and more ‘regional dialect’. Next up: the Schrödinger’s theorem—proven and unproven, depending on your timezone.

If our brains are energy misers, maybe the real supercomputers are the ones that can do more with less—not the ones with the most flops. This could reframe how we design efficient algorithms and even AI: sometimes, the best strategy isn’t processing power, but predictive efficiency.

Maybe the next breakthrough in cloud computing isn’t more cores or larger GPUs, but better energy allocation and anticipation, just like the brain.