aeden

Orkut is back? Almost fell out of my chair.

Thank you for posting. I am the founder and CEO of DNSimple and am happy to answer questions about this anyone has any. The blog post does a pretty good job of laying out the reasons why we ended up moving to our own edge infrastructure as well as some of the challenges, but if there is something we left out please let me know. Thanks!

I love seeing this pop up again. Our customer support team has been steadily moving all of our docs over to Diátaxis for a while and it's been a really nice improvement.

Devs don't do it because we are a lazy bunch, which is the same reason we like using LLMs so much, because it taps into our laziness.

Beyond the stated changes the author believes are necessary for citizens to make: stop externalizing responsibility, stop going along with social norms that perpetuate surveillance capitalism, and indulging in anger as a substitue for action; the other actionable takeaway to me is: "Unless we have real representation in our government. Companies don’t have vested interest in protecting privacy."

I interpret this as meaning citizens need to support advocacy groups that lobby elected officials to create/improve regulations that would limit the ability to implement surveillance capitalism. This aligns with the author's own words: "Responding to National or Regional calls for safety: Calls to support initiatives, or bills to increase security at the expense of freedom, make us less safe. Trading security for freedom reduces our ability to act."

Interesting, this is the first time I've seen this project. One thing I saw that concerns me a bit is that they provide command-line options for passing your user credentials and multi-factor code. I'm not a fan of giving anything that level of access when a resource-specific access token will do, but that's me.

Our current level of granularity allows you to give read or write access to a specific zone, but it does not go down to the level of giving read or write access to a specific RRset type yet, if that's what you're looking for.

I've put a comment on the parent thread, but unless I've misunderstood what the poster said, we addressed the limitation back in 2023 with scoped access tokens.

Thanks for recommending us, I (and the rest of the team) appreciate it.

At one point we were using Cloudflare's DNS Firewall product for our entire edge network. We have since moved half of our edge network to our own infrastructure and are currently in the process of expanding our edge network further, so at this point an outage at Cloudflare should be at least partially mitigated for our customers due to our separate edge network, and eventually it should be completely independent.

Sorry to hear that you're considering leaving. Is there a specific part of our pricing that you consider expensive? From the DNS side we've aligned pricing with what AWS, Google, and MSFT are charging, and for domains we've tried to stay competitive as well without completing removing our margins. Do you use specific features that are not available on our base plan?

I really hope they get manage to recover it. I grew up surfing in Central Florida and even I knew about it and had seen pictures of it. I finally went there a few years ago and it was a blast to see people surfing it.

I'd love to see an update of this for how things look in 2024.

We run a combination of managed hardware and virtual hardware. The prices for both have indeed gone up significantly since we launched some of our earliest plans. We don't have the luxury of using a cloud provider like AWS for our Anycast DNS infrastructure, thus we are limited to our choices. Furthermore the cost for network transit has gone up, as has the cost of ancillary services we use to operate our network (such as tooling for alerting, observability, etc).