• 0 Posts
  • 40 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle


  • I totally get your point, but I don’t think SpaceX has any engineer problems. They’ve had a lot of issues with their test articles, but as far as it seems, that’s sort of by design using the move fast and break things philosophy, which obviously isn’t good in some ways. But it worked for the Falcon 9 landings, and it’s going to work for starship, and all the detractors and haters will say nothing in five years when Starship is an extremely successful program.

    I think a lot of people fail to see the extreme space fans and engineers who are super into space are willing to suffer through some of these things to work on what is actually the most incredible space program in our lifetime. I wouldn’t do it. I’m not an engineer though, and I really do fucking hate Elon Musk. But I say it again. Starship is awesome, and it’s going to be extremely successful, despite what you may believe now. SpaceX has a very long history of proving the haters wrong, in fact I can’t think of a single example when the haters and people saying “its impossible” ended up being right long term


  • You got them on a technicality. But multiple test articles have pretty much reached orbit, intentionally just missing orbit so they would re enter in a known location should something go wrong, and something has gone wrong most of the time.

    I’m excited for the staship program because it’s the most exciting spaceflight development in my lifetime, yes fuck Elon but that doesn’t change the facts of how exciting the program is for a space lover. The upcoming launches with v3 hardware are going to be very exciting, hopefully most of the kinks have been resolved.

    The more pressing issue IMO is that they haven’t really shown any of the moon landing hardware, which will be substantially different than the Starship articles they are using for testing now.


  • I don’t think you’re educated on the matter because landing on the moon with the mission plan that they set out requires the lunar gateway to be in place, it is not and likely won’t be for a long time. It was going to be impossible to land on the moon by the third mission (unless significantly delayed) no matter who was in charge. Like all ambitious space missions in history, it will be delayed, delayed, and delayed again. Sadly that’s how it has always been.

    You shouldn’t confidently spout incorrect information

    “The aerospace safety advisory panel recommended that Nasa rethink its objectives for Artemis III, … The panel said that the call for a revision was urgent, “given the demanding mission goals”.”

    The fucking safety advisory panel suggested the change moron dude, not Isaac. But yes fuck Elon cuck the pos ket head

    Edit: removed unnecessarily rude words, sorry I’m just an asshole
















  • The details on how it works from the website for those reading this chain.

    "how does this work

    k-id, the age verification provider discord uses doesn’t store or send your face to the server. instead, it sends a bunch of metadata about your face and general process details. while this is good for your privacy (well, considering some other providers send actual videos of your face to their servers), its also bad for them, because we can just send legitimate looking metadata to their servers and they have no way to tell its not legitimate. while this was easy in the past, k-id’s partner for face verification (faceassure) has made this significantly harder to achieve after amplitudes k-id verifier was released, (which doesn’t work anymore because of it.)

    with discord’s decision of making the age verification requirement global, we decided to look into it again to see if we can bypass the new checks. step 1: encrypted_payload and auth_tag

    the first thing we noticed that the old implementation doesn’t send when comparing a legitimate request payload with a generated one, is its missing encrypted_payload, auth_tag, timestamp and iv in the body.

    looking at the code, this appears to be a simple AES-GCM cipher with the key being nonce + timestamp + transaction_id, derived using HKDF (sha256). we can easily replicate this and also create the missing parameters in our generated output. step 2: prediction data

    heres where it kind of gets tricky, even after perfectly replicating the encryption, our verification attempt still doesn’t succeed, so they must also be doing checks on the actual payload.

    after some trial and error, we narrowed the checked part to the prediction arrays, which are outputs, primaryOutputs and raws.

    turns out, both outputs and primaryOutputs are generated from raws. basically, the raw numbers are mapped to age outputs, and then the outliers get removed with z-score (once for primaryOutputs and twice for outputs).

    there is also some other differences:

    XScaledShiftAmt and yScaledShiftAmt in predictions are not random but rather can be one of two values It is checked that the media name (camera) matches one of your media devices in the array of devices It is checked if the states completion times match the state timeline

    with all of that done, we can officially verify our age as an adult. all of this code is open source and available on github, so you can actually see how we do this exactly."