Following the breach, NXP reportedly took measures to boost its network security. The company enhanced its monitoring systems and imposed stricter controls on data accessibility and transfer within the company.

This is the real damage. China is establishing a surveillance culture in the west. By threatening to hack our computers, they hacked our culture instead.

I work at a company that is doing more and more security controls and it’s sad to see the culture of openness get chipped away little by little by this.

To allow the cable to work as a delay line memory, be sure to plug both ends into the router.

and GNOME 3 too

It’s 9 inches!

Even if they have the source, they may not have all the build tools anymore.

Or they have the build tools but the wizard that set up the build system back in the day no longer works there.

Or they have the build system archived and documented but it doesn’t run because some license expired, and the tool vender doesn’t sell that version anymore.

In the near future, there will be another possibility - SaaS cloud tools that are impossible to preserve so they are forever lost.

Don’t have a problem with them

nay

Wasn’t facebook also found to store images that were uploaded but not posted? This is just a resource leak . I can’t believe no one has mentioned this phrase yet. I’m more concerned about DoS attacks that fill up the instance’s storage with unused images. I think the issue of illegal content is being blown out of proportion. As long as it’s removed promptly (I believe the standard is 1 hour) when the mods/admins learn about it, there should be no liabilities. Otherwise every site that allows users to post media would be dead by now.

I’m fine with this. Instances shouldn’t proxy or cache images because it opens instance owners to a lot more liability than text. A client side setting to not load images in comments by default is better.

I should clarify. When the skinheads from the Nazi house down the street come over to visit, they must follow our instance-wide and community rules. This should be a basic fediquette for everyone. If they repeatedly fail to do that then we will have to defederate them. But if they check the swastika at the door and keep the Nazism to themselves while they’re here, I don’t see why not. Most of the calls for defederation so far have been about people not wanting to see activities happening on remote communities on certain instances.

Nay for now. While there’s a few communities on lemmygrad that I want to see like Late Stage Capitalism, lemmygrad has been defederated since day one, and all of us (should) have known this when we joined, so there’s no hurry to refederate with them.

The real solution is for Lemmy to let users block instances from their own view, then all the defederation discussions will be moot. When that happens, we should do as you proposed - federate as much as permitted by law.

Let’s wait for per-user instance filters to be implemented, then everyone can block instances to taste. As long as their users don’t cause trouble in our communities, there’s no need for our instance to act as a moral guardians and decide what our users can and cannot see. Defederation is a nuclear option that should only be done if their instance is disrupting our instance’s operation (spamming and breaking rules while in our communities).

I like that sh.itjust.works currently federates with almost everyone, and I can see a big part of the fediverse from here. It would suck having to visit multiple instance to see the whole fediverse.