-
Cloud is the ideal place to build software while looking for product-market fit because the cost of failure is very low. Once you hit product-market fit and scale up past a certain point, you can save money by migrating to on-prem bare-metal.
-
I agree, a few years ago another company in town was suffering similar performance issues with AWS EBS (pre-performance options) they setup a VPN link to high performance storage in their data center and let the app run on AWS. It seemed to work out for them however I am unsure of how their infrastructure operates now.
-
-
gadams
2 years ago
|
link
| on:
Linode: "On June 27th, our DNS infrastructure will cease to answer DNS queries"
Talked with the founder of Linode Chris Aker (caker).
<gadams> anyone know about this ? https://lobste.rs/s/aepbqi/linode_on_june_27th_our_dns
<caker> yes, it’s total BS
<caker> gadams: –^
<gadams> thanks caker
<caker> this affects like 300 people. if you didn’t get a ticket about it, don’t worry about it
-
It’s total BS to make a major change like that, and sweep it under the carpet, without notifying all of your users.
As far “like 300 people” is concerned – http://bgp.he.net/ip/65.19.178.10 still reports, only a couple of days prior to the shutdown:
Address has 433 hosts associated with it.
Moreover, what about the rest of the people that now have to follow up on the reports about CloudFlare outages and IP hijacking? Before this change, 5 (five) separate and independent networks would have to be responsible for an outage. Now all it takes is a single third-party company, and a single BGP hijack of a single /22.
Your content could still be available via your Linode, but people won’t be able to reach it due to a third-party DNS outage (possibly only affecting users in Asia or Antarctica, so, you wouldn’t even know what’s going on). How nice. And Linode didn’t notify anyone why? Because CloudFlare’s too big to fail?
-
-
-
tedu
2 years ago
|
link
| on:
WhatsApp, Used by 100 Million Brazilians, Was Shut Down Nationwide Today by a Single Judge
A small nitpick (and mostly regarding the title, since the article is correct), but they weren’t shut down. They were blocked. The effect to the user may be the same, but as an interested observer, I’m very interested in the difference between a Brazilian judge blocking my website vs shutting it down.
This bugs me quite a bit, now that I’ve thought about it. A headline that says “blocked” would be correct, more informative, and shorter. You can do better, Intercept. You should do better.
-
I’m glad he updated his blog post to reflect that this wasn’t surreptitiously done. When recently helping a student we installed homebrew and we did receive the notification about usage analytics reporting and declined.
I wonder if the notification of this new feature was rolled in to a brew update and most people ignored the terminal scroll where it provides the commands to disable analytics.
Potentially. For what it’s worth I am fairly sure I saw the question and agreed.
It’s quite prominently displayed on installation and upgrade, along with the information how to disable it.
I believe I noticed it because there was a new file or folder in my home directory; I searched around until I could figure out how to disable it