It could send debris into a more elliptical orbit, but it wouldn’t be possible for it to raise the entire orbit above LEO. The point of impact will remain in the orbital path and since the entire orbit is currently in LEO, there will be, by extension, some part of the new orbit still in LEO and therefore subject any debris to atmospheric capture.

Media doesn’t care when SpaceX/Starlink fixes issues. They only care when problems are discovered, and act like it’s some malevolent act rather than an unforeseen issue. The albedo problem is fixed on all new launches for quite some time and the sats only have a 5 year service life before deorbit so the problem ones will be cleared out in short order. I expect this frequency issue to get ironed out in a similar fashion.

SpaceX and SL have a very good track record so far of working with scientists and authorities on minimizing impact of their sat constellations. Mind you, I don’t think this pure altruism, they just want to keep the government from locking down on them and jacking up costs.

I agree information shouldn’t be behind an invitation, but it does solve 3 important things:

• Keeps the law out of your hair
• Seed requirements ensure torrents stay alive
• Incentivizes strict quality control and uploading new content

I can’t tell you the number of times I’ve downloaded something from a public source and it’s been crap quality, or isn’t even the thing I wanted to download. Sometimes the file is fine but it takes 3 weeks to download because it has one seeder with a 10kbps upload rate. That’s a big “if” on if I can find it at all if it’s something more obscure.

Until someone solves those 3 issues in another way, I don’t see a better solution.

What did you switch to? I’ve tried to give rtorrent a go, but config is a pain and rutorrent craps itself when you have a lot of torrents. rtorrent + flood is the most promising I’ve tried other than the obnoxious setup but I’m pretty entrenched in deluge and flood was pretty early in development when I tried.

All the time. I deal with a lot C# code that makes and responds to HTTP API requests, and being able to check if requests and responses are properly formed without having to slap print statements everywhere is a godsend.