Wow, the best part being that the octopus “punched” opportunistic fish who don’t help in the hunt.

Spektr-R | Decommissioned, single array, 10 meter diameter

From your link: "The very high angular resolving power was achieved in conjunction with a ground-based system of radio-telescopes and interferometrical methods, "

HALCA | Decommissioned, single array, 8 meter diameter

From your link: This orbit allowed imaging of celestial radio sources by the satellite in conjunction with an array of ground-based radio telescopes" … “the project was eventually cancelled in 2011 due to increasing costs and the difficulties of achieving its science goals”

Orion | “It is believed that this refers to the diameter of the main antenna, which might be well in excess of 100 m”, potentially you’re correct! Oh. These are ground facing dishes that aren’t use for scientific purposes and are highly classified.

The same is done in space, you realize that…

No, it isn’t. The radio astronomy done in space is for Gamma rays, x-rays, UV and IR. Things the atmosphere blocks.

What’s done on the ground is for much larger wavelengths (+1m) which, again, requires massive equipment that is currently is not feasible to send up.

The fix isn’t to eliminate StarLink, I agree. The fix in my opinion is to have stricter controls from the ITU about how much interference a device can produce.

Put that shit in space like they always should have

So which is it? It’s already done in space, or that’s the direction we should go?

Even your explanation about your original comment being “extremely easy to comprehend” has two opposing statements.

We don’t do a majority in space because of the absolutely massive size of the equipment needed… The VLA, for example, is 28 different dishes/antennas that are over 200 tons of metal a piece.

The signals that are being measured are absolutely tiny, so much so (and to your point about interference in the ground), that A microwave can cause issues.

The issue with the StarLink v2 is that; they are in LEO (Low Earth Orbit), they emit a lot more than other satellites, and there are a shit-ton of them - which means it’s harder to schedule equipment time around the interference theyre causing. And the problem is only getting worse.

Your comment is very disjointed though, so I’m not entirely sure what your point is.

Woah, I learned something new today.

Neat!

Very interesting, especially how they’re executing unsigned code via the *.sys files to (presumably) get around waiting for MS to re-sign their driver.

Have you tried using:

flatpak repair

https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak-repair

There is a

--dry-run

Option to see if there are any issues before committing the changes.

Super cool, thanks for sharing

Red Panda!

Damn this photo goes hard

Very interesting, thanks for sharing

That’s a good take - and I do hope they continue to treat Siege the way they have been in the past.

That’s fair, I left that very open ended.

I didn’t mean it in a “This is bad, I think they need a sequel” way. I more meant it in a “This is Ubisoft and committing to 10 years on anything seems impossible” way.

I definitely like the Siege development team, they consistently have pretty solid updates and balancing choices to address issues in the game.

Last year they also said they’re committed to another 10 years of updates for the game - which is absolutely wild imo.

I still really enjoy the game, but another 10 years of updates…

Friends and I came up with some other names as it seems the discoverers needed help:

#1: archarc

#2: Arcus Giantus

#3: Cosmic Crescent

#4: Very Big Ring (aka VBA)

#5: The Giant Ring

Hahaha, thanks!

Vroom Vroom

Hmm, that’s good / reassuring - hopefully we don’t have to find out!

Wow, so many good parts in this…

Side note: I do not do any coding professionally, just self taught stuff to impressive my business coworkers - but this was really well explained.

My favorites: Default username and password for accessing the debugger on the trains computer (that apparently can’t be changed)

Hard coded geofenced coordinates that would disable a train if it was being serviced at a competitors location

Absolute favorite: the incorrectly programmed date lock that would only disable the train November & December on the 21st-30th

Hopefully the company is reprimanded for this - here in the US it would probably be a slap on the wrist and nothing else.