We need more people like you.

It certainly wouldn’t be surprising.

You can limit liability by creating separate entities and this is absolutely the standard, at least in the US. You would have to be very ignorant, or have sought no outside counsel, if you have some kind of decently profitable business and haven’t done so. It’s the whole point of these legal structures, such as LLCs. I don’t know the particulars of the case, nor the particulars of Brazilian law, so I don’t really know if it the case here.

That being said, speaking from an only slightly informed US perspective, if they are suing Musk himself, then yes they can absolutely go after his assets, which would include ownership in Starlink and X. However, if they fined X, it wouldn’t even remotely be a stretch that they do not have the legal authority to lock down Starlink accounts, as they are two separate entities that are presumably linked only by common figurehead.

And my comment was in response to something different. You’re free to move along unless you can show that you’re authorized to police the comments in this thread.

It’s not supposed to be >.>

Its a joke. Literally.

Yes. There is. Orbit is a higher altitude than Brazil. Don’t play dumb.

Pretend?

Technically, I own a little piece of earth from the center of the core to space. I can’t control the skies above me, but I technically own them.

Brazil does not control the space in which the Starlink network operates. If Brazil wants to get in a pissing match over the operation of satellites that they can’t control, it will be about as effective as my efforts to stop 737s from overflying my house at 30,000 feet.

About all they can do is threaten the operations of other Musk properties operating within Brazil.

In a very real sense, Starlink is above the law. They can’t stop him from operating Starlink any more than we can stop foreign radio propaganda from being transmitted into our borders.

Edit: For the exact same reason that Starlink is above the law in North Korea, it is above the law in Brazil.

If I had to choose between global high speed internet access, and ground based astronomy, I’d pick the Internet every time. I’d completely blot out the sky forever if that’s what it took.

We don’t need ground-based astronomy to learn about the universe, I’d rather encourage more space-based astronomy. Or build some observatories on the moon if you really want to build on a solid space body.

However, Starlink is a for profit company run by Elon Musk. I don’t really want them doing it, because they’re not going to provide unlimited global Internet to everyone. So as the guy said, the idea is good, but Starlink is bad, although it is currently the only such option.

Wrecking is not really the right term.
It is causing work for astronomers, and wrecking very few older systems, but generally it is an issue you can work around. I.e. something temporary. What you usually see in my experience of the field is you have some of your work degraded by satellite streaks, which are about 2x more common since starlink, and you understandably complain at starlink. And then get around to coding up a solution to deal with the streaks, spend another few runs until it about works, and eventually forget this was ever a thing.

In more detail, the base issue is, that you are taking an image, with probably minutes or hours or days of exposure, and every satellite passing through that image is going to create a streak that does not represent a star. Naturally that is not good in most cases.
The classic approach here, because this issue has existed since before starlink satellites, is to - depending on frequency and exposure length and your methodology - either retake the entire shot, or throw out at least the frames with the satellite on it, manually.

The updated approach is to use info about satellite positions to automatically block out the very small angle of the sky around them that their light can be scattered to by the atmosphere, and remove this before summing that frame into your final exposure. Depending on methodology, it might also be feasible to automatically throw away frames with any satellite on them, or you can count up which parts of the image were blocked for how long in total and append a tiny bit of exposure only to them at the end.

To complicate this, I think more modern complaints are not about the permanent constellation satellites but those freshly deployed, that are still raising their orbits. Simply because their positions are not as easy to determine, since their orbits are changing. So you need to further adapt your system to specifically detect these chains of satellites and also block them out of your exposures.

The issue here is that you need to create this system that deals with satellite data. And then you need that control over the frames in your exposure, which naturally does not match how exposure used to work in the olden days of film, but to my knowledge does work on all “modern” telescopes.
My knowledge here is limited but I think this covers about 30-40 years of optical telescopes, which should largely be all optical ground based telescopes relevant today. Further, you probably do need to replace electronics in older telescopes, since they were not built to allow this selective blocking, only to interrupt the exposure.

In summary, not affected are narrow fov modern optical telescopes, and in general telescopes operating far from visual frequencies.
Affected with some extra work, would be some older narrow (but not very narrow) fov telescopes, as you now have to make them dodge satellites or turn off shortly, when previously you could have just thrown away the entire exposure in the rarer cases you caught a satellite. This would be software only (not that software is free).
Modern wide fov telescopes might need hardware upgrades or just software upgrades to recover frames with streaks on them.
Old wide fov telescopes may be taken out of commission or at least have their effective observation times cut shorter by needing to pass out on more and more exposure time over satellites in the frame.

It is a problem, yes, but in my understanding one that can be overcome, and is causing the main annoyance and majority of its issues while the number of satellites is increasing, not after they have been increased.
I don’t know of a single area of ground based astronomy that couldn’t be done with even a million satellites in leo.

Believe you mean far far lower than geosynchronous orbit. Which is not the ozone layer. Ozone is not particularly far. like… less than 20 miles. Geosync is like… 20k miles. While Low Earth Orbit is much closer to the ozone than to geosync, its still far past the ozone, around 300+ miles.

Where those vaporized materials end up kr the satellites themselves?

Starlink satelites are about 341 miles above earth, on average. https://uk.finance.yahoo.com/news/starlink-everything-know-network-satellites-151511672.html

Ozone layer is 9-18 miles above earth’s surface. https://www.epa.gov/ozone-layer-protection/basic-ozone-layer-science

you remember incorrectly.

That was indeed what I was thinking of. I didn’t realize it was rejected. My bad, and thanks for the letting me know!

The rockets that launch those satellites were developed using tax dollars.

When do you need faster ocean communication, besides luxury? Nobody is owned fast internet on an environment-destroying luxury cruiseship.

Starlink is a constellation of low-earth orbit (LEO) satellites, not geostationary satellites. That means that the ground station (i.e. subscriber equipment) talks to one satellite as it comes into view, and over time that satellite moves across the sky, and they switch to another satellite. This means the latency is highly variable as the distance changes, but at its lowest is much lower than a geostationary satellite since it is far closer.

So tell me, where does the government link the person to the coin? I do a cash trade to buy Bitcoin, who logs it’s me and puts my name on the wallet for the government to track me down?

Just because the dish exist doesn’t mean it’s still being used. You have to do a blanket ban on having the dish at all. And even then they’re kind of tiny and easy to camouflage. You’d probably have to make the enforcement penalty scary enough to dissuade them. Or pay neighbors to rat each other out

Literally on AWS ours does. Since 2014:

https://www.theatlantic.com/technology/archive/2014/07/the-details-about-the-cias-deal-with-amazon/374632/

That’s why it’s in West Virginia

You really are clueless.

Why don’t you go ask crowdstrike how easy it is to bring down enormous amounts of seemingly unconnected infrastructure .

With what weapon system is Brazil going to pose a debilitating threat to a constellation of 6000 satellites?

“Shoot them down” is well outside the scope of Brazil’s military capability.