OCLogs: 2026-02-03.log

Stuff goes here

L1[00:03:48] *** Joins: raptop (~Newpa_Has@ip98-169-31-148.dc.dc.cox.net) UmbralRaptor

L2[00:03:48] ChanServ sets mode: +o on raptop

L3[00:25:23] <FLHerne> .outcome add In the context of the previous mission this brings the competence of KSC's leadership distinctly into question.

L4[00:25:23] <LunchBot> Added outcome: In the context of the previous mission this brings the competence of KSC's leadership distinctly into question.

L5[00:25:26] <FLHerne> .mission

L6[00:25:26] <LunchBot> The top offside hydraulic paddle gear of lock 12 is jammed shut. You were curious to see what would happen. Now you know.

L7[01:09:04] <xxcoder> yep

L8[01:15:47] ⇦ Quits: darsie (~darsie@84-113-82-174.cable.dynamic.surfer.at) (Ping timeout: 198 seconds)

L9[01:59:02] *** Joins: [ (~test@139.94.159.176) [

L10[03:51:11] ⇦ Quits: JK (~JK@5586020d.adsl.multi.fi) (Ping timeout: 198 seconds)

L11[05:09:58] ⇨ Joins: JK (~JK@5586020d.adsl.multi.fi)

L12[05:28:10] *** Joins: Althego (~Althego@185.161.73.152) Althego

L13[05:28:10] ChanServ sets mode: +o on Althego

L14[07:07:18] ⇦ Quits: Ezriilc (~Ezriilc@47-199-0-108.fdr01.clwr.fl.ip.frontiernet.net) (Remote host closed the connection)

L15[07:30:29] ⇦ Quits: wallacer (~quassel@198.98.50.187) (Ping timeout: 201 seconds)

L16[08:10:40] *** Joins: darsie (~darsie@84-113-82-174.cable.dynamic.surfer.at) darsie

L17[08:59:53] <Mat2ch> What do you guys say about the merge of SpaceX and xAI? I fear when the AI bubble bursts it could take down SpaceX

L18[09:01:25] ⇨ Joins: sandbox (~sandbox@2a0a:ef40:6b2:3d01:e5f7:db70:aa24:7800)

L19[13:00:44] ⇦ Quits: JK (~JK@5586020d.adsl.multi.fi) (Ping timeout: 190 seconds)

L20[13:01:19] ⇦ Quits: Tank2333 (~Tank2333@p50853305.dip0.t-ipconnect.de) (Remote host closed the connection)

L21[14:27:04] ⇦ Quits: Althego (~Althego@185.161.73.152) (Quit: Leaving)

L22[15:34:47] *** Joins: Althego (~Althego@86FF4C27.dsl.pool.telekom.hu) Althego

L23[15:34:47] ChanServ sets mode: +o on Althego

L24[16:04:03] <xxcoder> Mat2ch: I had written off spacex, because of leadership

L25[16:04:24] <xxcoder> it's going to get worse if they merge x, xai and spacex together

L26[16:04:36] <Althego> heh i have just heard that

L27[16:04:39] <Althego> whatever xai is

L28[16:04:42] <Althego> but they merge

L29[16:04:48] <Althego> probably because of the datacenters in space idea

L30[16:04:52] <Althego> which seems to be stupid

L31[16:04:52] <xxcoder> its grok alt

L32[16:05:12] <Althego> of course, i think facebook is stupid too, yet people made billions with it

L33[16:05:59] <xxcoder> datacenters in space does, on surface, make sense. endless power, as long as theres enough radators to radate ir away from center, endless "cold"

L34[16:06:19] <Althego> yes heat is a problem here on earth, and in space more so

L35[16:06:26] <Althego> that is one big issue

L36[16:06:29] <Althego> other is maintenance

L37[16:06:42] <Althego> unless you have really cheap acces to space, or the technicians live there

L38[16:06:55] <xxcoder> yeah. on earth heat is easier to get rid of locally, harder long term. space its other way

L39[16:08:56] <Althego> with a working starship, access to space would be significantly cheaper, but proably still not on the level you want to go unless absolutely necessary

L40[16:09:15] <Mat2ch> The problem isn't just having cheap access to space. You need radiation hardned hardware or your satellites will all be dead in half a year

L41[16:09:35] <Althego> not that much, in leo you are under the magnetic field of earth

L42[16:09:42] <Althego> msotly it is protected

L43[16:09:48] <Mat2ch> You cannot pack leo with that many satellites

L44[16:09:56] <packbart> so, Grok is going to fly the Dragon? :)

L45[16:10:13] <xxcoder> grok undress crew

L46[16:10:14] <Mat2ch> and there is enough radiation in the upper atmosphere that planes flying there are radiation hardned

L47[16:10:20] <Althego> based on the blond goth chick it appears to be, it is going to ride the dragon :)

L48[16:10:37] <Mat2ch> So using modern CPUs and GPUs there with fast RAM will be almost impossible to get right

L49[16:11:06] <Mat2ch> Just because Musk got away with consumer hardware on F9 doesn't mean this hardware will work correctly for month in LEO

L50[16:11:21] <xxcoder> I guess if push it to much higher orbit, it could emit static field to deflect radation

L51[16:11:31] <Mat2ch> Yesterday I saw an article that we now have DDR4 for space, so radiation hardned. But that will be expensive

L52[16:11:46] <packbart> Mat2ch: the recent "bug" in Airbus software that could pitch the plane beyond safety margins if a bit was flipped by radiation

L53[16:11:52] <xxcoder> and ram is already expensive due to... ai bubble

L54[16:12:16] <Mat2ch> packbart: wasn't this also a "we cheaped out and didn't bring a backup" problem?

L55[16:12:33] <packbart> don't know. the fix was to roll back to an earlier version of the software

L56[16:12:54] <xxcoder> huh how would roll back fix it?

L57[16:12:55] <Althego> radiation hardened hardware lags behind by at least a decade. which means it is not on cutting edge node

L58[16:13:14] <packbart> xxcoder: I don't know but that is what they did to make the planes safe again

L59[16:13:32] <packbart> possibly the code wasn't comparing multiple results as it ought to?

L60[16:13:44] <xxcoder> I wonder if they had removed anti-corruption of bit stuff. like 3 copies using majority

L61[16:14:41] <Althego> fly by wire should be operating on 3 or even 5 computers in parallel

L62[16:14:57] <Mat2ch> F9 uses three consumer-grade boards for that

L63[16:15:09] <Mat2ch> for the short amount the F9 is in space this is enough

L64[16:15:24] <Althego> sometimes it goes up into at least medium orbit

L65[16:15:32] <Althego> maybe there are a few direct to geo launches

L66[16:15:57] <xxcoder> I wonder if they can just enclose sensive bits, and hardware outside that is hardened, like reciver/transmitter

L67[16:16:10] <xxcoder> and lots solar of course and their controllers

L68[16:16:42] <Mat2ch> "The software works by inducing "rapid refreshing of the corrupted parameter so it has no time to have effect on the flight controls", Airbus says."

L69[16:17:02] <Mat2ch> So they basically store the same parameters in different memory locations now?

L70[16:18:12] <Mat2ch> Althego: It's only the booster. I guess the second stage uses more sophisticated hardware

L71[16:19:23] <Mat2ch> and Airbus quietly changed the controller afterwards it seems

L72[16:22:01] <Althego> so where did the bit flip happen? ram?

L73[16:22:07] <Althego> on insidethe cpu?

L74[16:23:18] <Mat2ch> RAM it looks like

L75[16:23:37] <Althego> ecc ram should protect against this. full ecc including the bus

L76[16:23:53] <Althego> it doesnt even cost that much

L77[16:24:12] <Althego> peanuts compared to the price of the whole airplane

L78[16:24:29] <Althego> even if it is some special aerospace stuff

L79[16:26:19] <Mat2ch> I have never seen ECC ram for microcontrollers

L80[16:26:35] <Mat2ch> Not sure if they even had external ram

L81[16:27:00] <Althego> i have seen lpddr support but probably not ecc

L82[16:27:09] <Althego> although these dont need to be microcontrollers

L83[16:27:14] <Althego> but embedded somethings

L84[16:27:38] <Mat2ch> from the report I'd say this was just a small microcontroller which had something to do with the control inputs

L85[16:27:50] <Althego> wasnt apollo era stuff always carrying its own bit fault checking in some bits of a data word?

L86[16:28:00] <Mat2ch> but when the bit flipped it reported that the controller had been moved

L87[16:28:11] <Althego> then it is still possible to implement it in software

L88[16:28:28] <Mat2ch> I bet they did something like that

L89[16:28:32] <Mat2ch> as quickfix

L90[17:14:14] <Mat2ch> So you can get microcontrollers with ECC for the Flash and the internal SRAM

L91[17:19:57] ⇨ Joins: Ezriilc (~Ezriilc@47.199.0.108)

L92[22:07:15] ⇦ Quits: Althego (~Althego@86FF4C27.dsl.pool.telekom.hu) (Quit: HMI Module Alpha Humana on approach to Space Station Mercury)

L93[23:17:52] ⇦ Quits: sandbox (~sandbox@2a0a:ef40:6b2:3d01:e5f7:db70:aa24:7800) (Quit: Leaving)

L94[23:34:57] ⇨ Joins: Tank2333 (~Tank2333@p50853305.dip0.t-ipconnect.de)