we got a team back to the moon, and still can't get teams or zoom to run correctly, and they're back on holy terra.
-
how in the fuck do we manage to get back to the moon and in that effort, enterprise software failed twice. Two different outlook clients, and meeting software.
In one hand we have the apex of humanity: traveling the furthest from our planet we ever have with the most complex hardware and guidance software there is, with the most well-trained space and ground crews. On the other hand, you can't send a fucking e-mail because slopware.
@da_667 just be thankful they didn't have to worry about any printers onboard Orion
-
how in the fuck do we manage to get back to the moon and in that effort, enterprise software failed twice. Two different outlook clients, and meeting software.
In one hand we have the apex of humanity: traveling the furthest from our planet we ever have with the most complex hardware and guidance software there is, with the most well-trained space and ground crews. On the other hand, you can't send a fucking e-mail because slopware.
@da_667 It just so happens that software made to be as resource intensive and inefficient as possible while gathering as much sensitive information as possible is goddamn terrible at doing anything useful.
There is a point where even the most brainwashed users and sysadmins are going to realize the software they are using has no utility, and that they are the guinea pig generating data for whatever nefarious fuckery the techbros cooked up.
-
@da_667 im suspecting moon wifi will work really fuckin great because theres no pesky air or rain to fuck with signal
-
@Viss THAT was a fucking miracle of science and absolutely amazing that it did work. We made TCP run on a laser link hundreds of thousands of miles into space.
-
@Viss @jpm @da_667 Eeehhh... Only if you configure your servers correctly!
https://web.mit.edu/jemorris/humor/500-miles -
@da_667 if there was a way for me to go work on that shit, i would close up shop at phobos overnight and run towards it.
that shit is so cool
-
@jpm @da_667 i guess a better way of saying it is:
it doesnt matter if the astronauts were INSIDE THE AZURE DATACENTER - they would have had the same problems.
because the problems had nothing to do with the lasers, groundstations, tranceivers, or protocol (tcp in this case).
the problem squarely rests at the feet of microsoft, azure, and "exchange".
the mistake was selecting microsoft to be the vendor to handle comms
-
@paul_ipv6 @Viss @da_667 moon cellular not WiFi; Nokia did a 4G tower test on the moon with Intuitive Machines to provide connectivity for robotic rovers.
-
@paul_ipv6 @Viss @da_667 moon cellular not WiFi; Nokia did a 4G tower test on the moon with Intuitive Machines to provide connectivity for robotic rovers.
"sign up for 2 years on the moon and we'll knock 40% off your recurring fees"
-
"sign up for 2 years on the moon and we'll knock 40% off your recurring fees"
@paul_ipv6 @Viss @da_667 I did a whole talk on this at Cloudflare Connect last fall; even people in tech don’t realize how much is going on up there.
-
@lispi314 fuck. foiled again.
-
@paul_ipv6 @Viss @da_667 I did a whole talk on this at Cloudflare Connect last fall; even people in tech don’t realize how much is going on up there.
"we see that you've been taking samples of the surface of mars. here are some reusable containers for your samples"
"we see that you've purchased a lunar orbit module. would you like to set up a monthly subscription for more lunar orbit modules?"
-
@da_667 their backhaul was fine. we were getting telemetry and fucking live highres video for 9 days of people who literally did a loop de loop around the moon.
then when they got out their nikons, and started machinegunning photos, they were able to then send those photos back to nasa via laser.
all that worked!
tcp was good, the link was good, 2500ms pingbut outlook didnt work.
meaning everything from "the moon" to "the groundstation" was 100% fine
-
"we see that you've been taking samples of the surface of mars. here are some reusable containers for your samples"
"we see that you've purchased a lunar orbit module. would you like to set up a monthly subscription for more lunar orbit modules?"
@paul_ipv6 @Viss @da_667 it’s a total land grab right now unfortunately ಠ_ಠ the US passed a law in 2015 giving American citizens the legal right to mine celestial bodies (the hubris here apparently went over the heads of legislators), and the race is already on. See https://www.theguardian.com/news/ng-interactive/2026/apr/01/lunar-prospectors-the-businesses-looking-to-mine-the-moon and https://nasaspacenews.com/2026/01/race-to-mine-the-moon/
At $20M/kg, there’s apparently enough money in it to be worth bringing it home and still making a profit (I remain skeptical but a Finnish company called Bluefors spent $300M with Interlune for rights to helium-3 from the moon)
-
-
@jpm @Viss @da_667 Reminds me of when I set up a fibre database on ArcGIS, the desktop was talking directly to Oracle for line segments and loading a map easily took 20k round trips to the DB to load all the layers. This took a few seconds on a wired connection, but on wifi it took like 30+s and was very noticibly laggy (which is why I loaded Wireshark to figure out what was going on) the only difference being the added latency, which just added up really fast. We ended up setting up a server with RDP so people who weren't on the LAN could have decent performance.
-
@da_667 their backhaul was fine. we were getting telemetry and fucking live highres video for 9 days of people who literally did a loop de loop around the moon.
then when they got out their nikons, and started machinegunning photos, they were able to then send those photos back to nasa via laser.
all that worked!
tcp was good, the link was good, 2500ms pingbut outlook didnt work.
meaning everything from "the moon" to "the groundstation" was 100% fine
-
R relay@relay.infosec.exchange shared this topic
at least, not yet.
