That works right up until the cell tower goes down too. Then the dongle is a fancy USB decoration, and Starlink Mini, clunky as it is, still has one big advantage: your backup path isn't sharing the same failure mode, which is the whole point even if the setup are uglier and the power draw is worse.
There are probably cheaper options, especially if you want to literally use your smartphone as the hotspot, but the Verizon home backup internet plan I looked at recently is $20 a month (and gives you 7 24-hour periods per month of unlimited data).
The Verizon home router is included when you sign up (you have to return it if you cancel). I bought it out of desperation when my home fiber internet was down all weekend due to a local tech screwing up and unplugging my house from the breakout box on the curb, but given the cost and the normal reliability of my home internet it’s really barely worth it.
Sure, but my reply was specific to the parent comment about Unifi though.
Most people who buy into the Ubiquiti/UniFi world want to keep within that ecosystem wherever possible, the integration between components is very good, it's just that some bits are vastly more expensive than they should really be.
A generic $20 4G dongle won't be as easy to integrate nor report as many shiny metrics as a UniFi component.
Right now I've got better things to spend the $480 difference on but if I had a lot more disposable income I wouldn't need to think twice about ordering the UniFi specific bit that's mostly fit and forget.
> Starlink only makes sense as a last resort if LTE coverage is not available in your area.
Again, the point is that LTE coverage can also disappear for exactly the same reasons why the primary FTTP/DOCSIS connection disappears. It's still reliant on local power and backhaul. Starlink has no local dependencies as long as you've got your own UPSes.
Many people who really want to be sure they have Internet will probably go FTTP/DOCSIS -> 4G/5G dongle -> Starlink.
My on-call plan is: FTTP Broadband -> 5G hotspot on mobile -> wifi in local cafe -> co-working space (24h access)
My off-call plan is: FTTP Broadband -> pick up a book
Again this is location specific. I have a mini ups on my router/ont. And I assume that my provider also has a UPS, because even when power is out my landline connection just works.
Cable and fiber providers typically have 24 hours of battery backup in their repeaters/concentrators but no more. Most 4g/5g stations have similar backup capacity, with only a few (that will be overwhelmed) located on big enough buildings to have standby generators.
So starlink backup is still interesting if your region occasionally has outages that last more than 24 hours.
There was a major storm that disrupted infrastructure across the west coast of Ireland last year. Turned out a lot of infrastructure couldn't survive multi-day grid power loss (water plants, cell tower repeaters, etc).
Starlink is a solid backup for mitigating the risk of such disruption by having no local dependencies other than ability to power the CPE.
Yup, OP is from the UK. In the UK I got a ThreeUK business SIM for £49 that lasted 2 years with 500GB data. It sits in wan failover and manages about 50mbps which is perfect to keep most services running.
Very much location dependent though. I lived less than a mile from Southampton city centre for a while and could never get anything close to dial-up standard download/upload speeds.
I've heard similar from London residents.
> “The companies three to five years from now that are going to be the most successful are those companies that doubled down on entry-level hiring in this environment,” Nickle LaMoreaux, IBM’s chief human resources officer, said this week.
Because several developers that work with docker also deploy to Kubernetes. So docker-desktop is a one-click method to get both on your workstation and deploy locally.
Doesn't this suffer from the opposite problem though? There is a very brief hiccup for Stripe and instance 7 triggers the circuitbreaker. Then all other services stop trying to contact Stripe even though Stripe has recovered in the mean time. Or am I missing something about how your platform works?
Good question, that's exactly why the trip decision isn't based on a single instance seeing a few errors. Openfuse aggregates failure metrics across the fleet before making a decision.
So instance 7 seeing a brief hiccup doesn't trip anything, the breaker only opens when the collective signal crosses your threshold (e.g., 40% failure rate across all instances in a 30s window). A momentary blip from one instance doesn't affect the others.
And when it does trip, the half-open state sends controlled probe requests to test recovery, so if Stripe bounces back quickly, the breaker closes again automatically.
It is answered in the FAQ at the bottom of the page
"The SDK is fail-open by design. If our service is unreachable, it falls back to the last known breaker state.
If no state has ever been cached (e.g., a cold start with no connectivity), it defaults to closed, meaning your protected calls keep executing normally. Your app is never blocked by Openfuse unavailability."
Yup, that is true for both Cloud and Self-hosted, it never blocks any executions by any external factors other than the breaker is KNOWN as open. The state sync and the hot path are 2 completely separated flows.
Any well-maintained project should already have a CONTRIBUTING.md that has good information for both humans and agents.
Sometimes I actually start my sessions like this "please read the contributing.md file to understand how to build/test this project before making any code changes"
>What more are we asking AI to do? And can a normal human do it?
1. Learn/Improve yourself with each action you take
2. Create better editions/versions of yourself
3. Solve problem in areas that you were not trained for simply by trial and error where you yourself decide if what you are doing is correct or wrong
reply