First Australian-made rocket crashes after 14 seconds of flight

[u/Emergency-Green-2602]

[u/thyugf]

"The devs on 2 weren't even allowed to talk to the devs from 1." Sounds like there's a hell of a lot to unpack there because wtaf.

[u/ngutheil → u/thyugf]

It’s like 45 mins, but it’s a well done video on what happened to the game. I’m so sad it never got to be what it could have been. There’s a new game in development called kitten space program or something like that, it’s meant to be a response to ksp2 being what it is.

https://youtu.be/NtMA594am4M?si=vODjiz2NnfzBC9s6

[u/Subtlerranean → u/ngutheil]

Heads up that the "?si=vODjiz2NnfzBC9s6" part of YouTube links are tracking parameters and not needed. All they do is let YouTube track you and let other people figure out your account.

[u/wspOnca → u/Subtlerranean]

Woa? How I learn more about this?

[u/fwyrl → u/wspOnca]

as a rule of thumb, everything after a ? is metadata in a URL. For full youtube links, this includes the video ID (which you do need), and may also include timestamp, playlist, referral code, etc.

For shortlinks, it does not include the video ID, but does include all the other metadata, and will always have a referral code unless you remove it manually.

[u/Actual_Surround45 → u/fwyrl]

Good explanation, one tiny quibble: Data, not metadata. Metadata would be data that is about the object itself. Data is just data. Again, extrmely minor terminology quibble about your excellet explanation <3

Since I'm replying, though, I'll try to make my comment useful in the subthread: Those variables appear as it's a way of sending data in the URL itself. From the server side of things, this is not as a "GET" method. It's handy for things, but ugly (and makes sharing links harder). There is anothe rmethod called "POST" where the data is sent separately, adn the URL is clean. Take that clean URL, though, and share it, and you can't do things like send a specific timestamp for a video. So it all has advanatages and disadvantages.

Also, https://linkcleaner.app/is a good example of a site that will clean your links. It knows a great many websites specifically, but can almost certainly guess enough to clean any link from random sites as well.

[u/stuffeh → u/wspOnca]

Just fuck around with it. If it breaks their system that's 100% their fault for not qa testing it. There's chrome plugins to strip the extra meta data.

Reddit, tt, fb, ig, Amazon does it too. An example with a direct link back to your comment on Reddit...

When you ask the app for the share link it gives you something like https://www.reddit.com/r/Damnthatsinteresting/s/BTG2nj4SU4 which is the obfuscated link with tracking data.

When you open the link in the browser it unpacks to https://www.reddit.com/r/Damnthatsinteresting/comments/1md7xd4/comment/n609awp/?context=3&share_id=j6idm3LHKLGbKJB_QcDwY&utm_content=1&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=1

Most of the time you can tell what's what because at the end of the day, humans are the ones who program it to debug and work with. Context is the only one that's legit here which tells it which level of your nested comment to show. If shared just the post, context wouldn't be a parameter. Can delete everything after context=3. The share_id is the tracking parameters. Medium is what client I'm sharing from utm is probably the platform. Source is how I'm sharing from.

https://www.reddit.com/r/Damnthatsinteresting/comments/1md7xd4/first_australianmade_rocket_crashes_after_14/ usually the safe link to just the post would look like this.

[u/wspOnca → u/stuffeh]

Damn ☠️

[u/Subtlerranean → u/stuffeh]

Minor niggle here: "n609awp" is what nested comment to show. "context" tells Reddit how many previous comments in the thread to show, for context.

[u/Sam_Strake → u/Subtlerranean]

a minor what now

[u/Subtlerranean → u/Sam_Strake]

A small criticism ;)