Orbital AI datacentres come with latency issues.
-
@david_chisnall I hope that you would provide the AI-bros with parachutes so they can safely re-enter from LEO. Silk chutes would be the environmentally sensitive choice.
You would need to make sure that you can launch their Door Dash orders counter to their orbital direction for minimum delivery times.
@TallSimon @david_chisnall golden parachutes
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall I read your proposal and wish to fund it. Also I am not averse to gather a number of AiBros together, perhaps with a net or a NFT bait trap? But all to say I wholeheartedly endorse the idea of sending this essential latency mitigation into orbit.
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall @catsalad I’m giggling just imagining this … https://youtu.be/IBYS6VdRzyA
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall
LEO CEO
@catsalad -
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall I think @sundogplanets will approve
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
I keep hoping a massive asteroid will hit the Bay Area, hopefully down there at the south end with all those useless fucks in Santa Clara.
Wham. That asteroid would take out millions of people and wouldn't kill one honest person.
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
-
Yes...
The humor in the final clause of the final sentence gets too dark for me, though (in the context of actual space flight).
I merely express a reaction; this is not a veiled call for censorship.@vnikolov @david_chisnall is this darker than the current climate emergency trajectory?
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall still non-toxic even with all the ketamine and peptides?
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall GEO isn't far enough. Stick them at like Sun-Earth L4 or L5. I don't think we're using that for anything right now anyway.
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
this also solves the #ReflectOrbital issue
launch them into orbit, and a #techBro who wants to catch the Sun at odd times because "woah cool" vibing, they can catch the sun at 11 PM, 1 AM, 3AM... all sorts of unnatural times as they whizz around the Earth
rather than subjecting other people and the natural world to the stunt and messing with circadian rhythms
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall is that why they sent a car in space?
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall I’m not so sure, upon re-entry their boundless arrogance will be spread over a large area, potentially infecting millions
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall
Put them into a transfer or it to Pluto, but "accidentally" let them pass within gravity assist distance of Jupiter and Saturn. -
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall You can also save money on cooling - since AI-bros can not ever be cool, there's no point in even trying.
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall funny, I just read this paper last week https://arxiv.org/html/2607.14172v1 where I was slightly horrified to learn that "LEO satellites are designed for a lifetime of about 5 years. End-of-life implies reentry into earth’s atmosphere. The best possible outcome of such reentry is total vaporization."
And so they did not consider... "The costs related to the impact on the earth ozone layer resulting from the reentry of millions of tons of aluminium into earth’s atmosphere, each year"
-
@david_chisnall Also, if they're in LEO one side of them is being baked by the sun for half of each orbital period—and a big-ass reflector on the other side (the Earth). For decent cooling to be possible they really need to be out beyond GEO: see also Skylab, and why they installed the emergency sun shield (it hit 70°C inside after they lost one of the solar panels during the launch, if memory serves).
@cstross @david_chisnall but think about interference from other electromagnetic waves on earth and solar flares. Wouldn't it be much better to send them to orbit Jupiter?
-
@cstross @david_chisnall but think about interference from other electromagnetic waves on earth and solar flares. Wouldn't it be much better to send them to orbit Jupiter?
@qwazix @david_chisnall You're joking, right? You *do* know about Jupiter's radiation belts?
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall I worry sometimes about over-boosting but everybody needs to know about this innovative solution
-
Orbital AI datacentres come with latency issues. If they're in LEO, they will have moderately low latency to a moving point on Earth, but for a fixed client the latency will increase as more relays are needed to account for curvature, so the jitter is high. If you put them in geostationary orbit, the latency is fixed, but large.
The solution to this is to put not just the AI datacentres, but also the AI bros in orbit. If you put an AI bro and a small radio in LEO, in the same orbital trajectory as an AI datacenter, they will have very low latency - indeed, significantly lower latency than ground-based routing if both they and the datacentre are on the ground.
Importantly, AI bros have a lot less mass than datacentres. As such, they are much cheaper to launch. As a pilot programme, to assess feasibility, I recommend launching a test constellation of AI bros into LEO. Note that, unlike datacentres, AI bros are made out of non-toxic (at least, in the chemical sense) substances. The environmental impact of uncontrolled atmospheric reentry is significantly lower, making the risk from the failure of a pilot deployment significantly lower.
@david_chisnall @simon_brooke we could have many experiments into the Minimum Viable Propulsion (MVP) to get a tech bro into LEO
