Well, sure, they won't be thermally random, but they will be significantly perturbed from their nominal orbits, particularly at the lower orbital altitudes.
Solar flares cause atmospheric upwelling, so drag dramatically increases during a major solar flare. And the scenario envisioned in the paper is basically a Carrington-level event, so this effect would be extreme.
The cross section isn't actually all that outrageous, it corresponds to a hardbody radius of 4.5 meters. Hardbody radius is equal to the sum of the radii of the two colliding bodies, so 2.25 meters - which seems about right for Starlink.
I know it's against HN rules to ask if people have read the article, but you clearly didn't read the article.
The "non-sexual nudity" example is at the bottom of the article. It's a stylized cartoon drawing of a nude man and woman with arms around each others' waists viewed from the back as they walk along a path. There is a heart strategically placed around waist level so you can't even see their whole butts.
It's about the tamest artistic depiction of nudity you can imagine, certainly something that is totally fine anywhere else on Facebook. Very clear that this is a bullshit excuse being used by Meta.
> Fatma Ibrahim, the director of the Sex Talk Arabic, a UK-based platform which offers Arabic-language content on sexual and reproductive health, said that the organisation had received a message almost every week from Meta over the past year saying that its page “didn’t follow the rules” and would not be suggested to other people, based on posts related to sexuality and sexual health.
If you're getting a warning every week for a year, I would like to see the other 51 non cherry-picked examples that they didn't give to the guardian. Based on a quick look at some of their posts that are still publically available, I think Meta is completely justified in restricting visibility of some of these posts.
Indeed, how do we know they are nude if we can't see any of their parts? I mean, living in SF I've seen people walking around in public like that, wearing the most minimal covering possible.
I have Copilot at work, it feels so useless sometimes. As an example, I had a report which I needed to make some batch edits to. I figured why not let the robot take a crack at it, so I clicked the Copilot button and spent a couple minutes describing what I needed changed.
Copilot tells me it can't edit my current document, but it can create a new one. I figured okay, Microsoft doesn't want to set it loose on the original, guess it makes sense that it requires a copy. So I said yes.
Nope. Instead of creating a copy of my document and editing it, it created an entirely new document which excised basically everything in the original report and replaced it with a very short summary - I'm talking 5000 words down to 500. All my tables and figures were gone, as was the standard report template my employer uses.
What utter garbage. Office productivity is a major use case for LLMs, and here the largest vendor of productivity software on the planet is happy to fuck it up.
The chatbot doesn't see the document structure; it sees tokens. When it generates a response, it's not editing; it's rewriting from scratch. Without a mechanism capable of precise diff/patch operations (like Cursor attempts with code), an LLM will always be a destructive tool for complex documents. Microsoft marketed this as an editor, but in reality, it's a summary generator
Tailscale is a bit more than a VPN. It operates in a mesh configuration rather than a traditional VPN concentrator setup. Tailscale's control plane orchestrates NAT traversal for devices on the Tailnet (through techniques like UDP hole punching) and allows them to establish direct Wireguard tunnels between them. That way, there's no VPN concentrator bottleneck because there's no concentrator at all, every device establishes tunnels to every other device.
That's pretty cool, thanks for the info! I've been looking into Tailscale the past few days since it actually seems pretty convenient.
I've seen they offer to use Mullvad as an exit node for devices which is very cool. Sadly it seems like for this to work, you have to have them manage your Mullvad keys, which to me kind of defeats the purpose of Mullvad in some ways. But I can see how it makes sense to them from a business-perspective.
Even if you are self hosting in the cloud or on a rented box, Tailscale is still really nice from a security perspective. No need to expose anything to the internet, and you can easily mix and match remotely hosted and home servers since they all are on the same Tailnet.
