jtchang

Long term this is good for the software ecosystem as a whole. Especially open source options like proxmox. I think Broadcom is making a strategic business mistake not willing to negotiate in good faith. However this is the true cost of using closed source solutions. The more this happens the more it gets factored into business decisions.

> The July 2022 outage was not the result of a design flaw in the Rogers core network architecture.

Talk about some grade A gaslighting here. Reading the post mortem they first tell you it wasn't a design flaw then say they routed all their data through one core router ( including a lack of a management network). Then they say they are going to fix things by separating out the wireless and wired traffic.

Why would you fix things if it wasn't a design flaw?

Out of band access is like resilient architecture 101. Hell even homelabs generally have some way to do it. It's appalling that Rogers didn't have a way to access the core IP routers out of band. Yes it might mean having to use a competitors infrastructure but they ended up having to do it anyway. And with the failure of the service now all the infrastructure providers are under additional scrutiny. Rogers should be striking some agreements with other providers to carry core traffic in case of an outage such as in this DR situation. For example Visa, MC, Amex all have agreements in place to process each others auth data in case the other party goes down. The thinking here being an outage for credit cards makes everyone look bad.

If you take a look here you can see how this type of tiering system works out:

https://usa.visa.com/content/dam/VCOM/download/merchants/vis...

Some of the tiers for Visa cards:

Visa Infinite Spend Qualified Visa Infinite Spend Not Qualified Visa Signature Preferred Visa Signature Traditional Rewards All Other Products

So this basically means to scan for this exploit remotely we'd need the private key of the attacker which we don't have. Only other option is to run detection scripts locally. Yikes.

“Any sufficiently advanced technology is indistinguishable from magic.”

Absolutely insane the level of wizardry being applied here to turn a lump of blackened, charred scrolls into readable text.

Having only cursory knowledge with machine learning are some of the techniques used in the article only recently discovered or have they been around for a while?

Is it due to us having reached an inflection point with these types of algorithms that they have become more popular and thus we are seeing new ways to apply them to old problems?

For me it's basically summed up as "we didn't test turning the power off" and making sure things worked the way we planned.

Yes it is hard and very expensive to do these types of tests. And doing it regularly is even more $$$ and time.

As most customers we seem to be okay with a cheap price hidden behind a facade of "high availability" since I don't really want to pay for true HA. Because if I knew the real cost it would be too expensive.

I don't think the issue is bad accounting. I think it comes down to software being uniquely different than a factory or piece of equipment. Amortization schedules that are even don't make any sense. Neither does anything measure in years. It's because we make improvement to software on a day by day basis. We don't necessarily add on to a factory every day.

> we broke up 2 months ago

Let's talk how that actually works in a business sense. Did you leave the company? Relinquish all control? Did you boot the cofounder out or did you buy out their portion?

What type of arrangement is this? Partnership? LLC? How did you register the entity?

"Broke up" doesn't really say anything.

Assuming you were in a partnership and you both have authority to make decisions on behalf of the company then you are free to just pay the contractors. So is your cofounder. Unless your governance documents indicate otherwise this is 100% valid.

Don't underestimate lobbying costs in dense urban areas. Whenever you have to deal with people the alternative is often easier.

If you have source mapping you can do basically what C compilers perform which is symbol mapping. If you are trying to map the HTML content to source you have to "tag" each of the steps in the process so you can figure out where the content came from.

Instead of transferring the cluster can you transfer the application(s)?

This is a very clever move by Microsoft. In essence they are painting a giant bullseye on their back to any lawsuits that may arise. The idea being that they have the resources to challenge them (they aren't wrong).

The way AI is going I'm sure we'll see some landmark cases very soon. It is very much in Microsoft's interest to grow this market as fast as possible and be at the center of it. This removes one of the key impediments to adopting generated code for smaller orgs: "Will I get sued if this product generates code that is copyrighted?".

Does Discord charge or have some type of contractual agreement with you? It does seem odd -- they must have some checking on addresses and personal information and what you posted just happens to match that regex.

> Although we use Typescript to mitigate these types of bugs, when we're working with external systems, it's easy to find yourself in a situation where the types are lying to you.

What does this mean? If you use typescript doesn't it prevent these types of bugs?

The ramifications of the inflection point we are currently at is mind boggling. I had a hard time explaining this last night but we may very well be witnessing the beginnings of a technological transformation era much like when the p-n junction was invented. From the 1940s standpoint it would be hard to envision all we had today.

- Lossless transport of energy - Batteries that don't take any time to recharge - Faster CPUs. Much faster with no heat to burn your lap.

Can I have my flying car now?

There is some really good advice here. I've been on both sides of this: pricing new enterprise service as well as negotiating them.

$49 per seat. Is that per month or per year?

Concretely look at the market and the value you are providing. Split up the user count to occasional users and permanent ones.

From the other side of the table I am expecting some type of volume discount because I am not spending 250k a year if the tech is not core to my business. I'd expect discounts for multi-year deals. You need to come in at a price point that makes sense to them depending on the market.

For cases like this email is not enough. You need to do trial shutdowns where you disable access to the db unless someone acknowledges via web. Do it for maybe 24 hours so you know you catch everyone.

What problem specifically is the away team solving? It sounds like DLL dependency hell except at a higher scope.

The fact you can cancel online is a good thing though. Some places have you send an email which is terrible. Honestly a unified API endpoint for all this would be a godsend.

These are fantastic!

Why don't I hear about these incidents with AWS? Is it just less common or different business takes on quotas and rate limits?

> disincentivizes the desperate from becoming innovative

People who are desperate are generally quite incentivized. They want to get out of their current situation. Being innovative does not require someone to be desperate.

Only circumstance? How about when people are looking to live a basic human existence but are unable to find a job?

One thing you should get out of your head is that there is zero risk. Even keeping it all in cash in a checking account has risk.

CD ladder isn't a bad choice. A treasury bill ladder could also work and might actually fit as well. The risk is in a rising interest rate environment the t-bills you buy now will be worth less in the future. You'll still get the dollars in absolute terms but it might buy less. Too bad you can't buy I-bonds past 10k a year.

Also the biggest risk in your plan is the "leave alone and not manage". There is manage a little, manage a lot, or pay someone to manage it for me. Leaving it alone and not managing it has its own risks.

I wonder what game this was for.

To me this is validation that going the SQL route in almost 99% of new apps is the right way to go. It will be a rare case that you won't be able to scale out given how mature some of these technologies are.

I can't believe I am alive to witness this.

I can imagine 100 years from now a SpaceX plaque will be in some museum timeline with this very event being one of many "failures". It's so hard to put that into perspective when you are actually living these events. I think partly because society has been conditioned to expect success out of all things when in reality true technological progress is rarely a straight line.

Wow -- something I didn't know I wanted but actually not too bad an idea. At least it is a starting point for conversation. Have to keep in mind that not everyone understands the technical lingo associated with shopping for broadband so it makes sense.

At its core the business fundamentals aren't great. However 130MM in revenue annually could mean there is something there.

I agree the number one thing to figure out is strategy. 24 to 36 months is a non starter in this environment. The company will die before you manage to pivot.

Figure out how to make the company sustainable and pitch that vision.

What state?

How many bits are in a gameboy rom? How do you even take a picture of a rom?

I see. But still after the initial TLS handshake. So clients can still connect over and over and force your server to do TLS handshakes all day long.