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

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.

Check Internet Archive. It was a torrent site.

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.

This must be BS or a regional thing. All the RCA ports I’ve seen in North America are labeled L and R, not L+R and L-R.

Combined toilet-sinks are a thing. It saves water by reusing the water you used to wash your hands to flush the toilet.

You can download everything in your account with google takeout

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.

I store my clothes in a stack, and I usually wear the same few pieces until the season changes.

I don’t like the idea of coalitions at all. To me it feels like the coalitions would become very “us vs them”, i.e. you must defederate all instances that allow any topic in this list or we will defederate you. It leaves no neutral ground, creates echo chambers, and deepens the political divide that plagues our society.

IMO it’s better if

1. Lemmy allows individual users to block all communities from an instance or all users from an instance, sort of like defederation but per-user.
2. Instances have the rule that “when you interact with other instances/communities, you must follow all their rules, or we will suspend your cross-instance posting rights for X days”.

Then instances can act like neutral infrastructure/identity providers and each user can decide exactly how they want to interact with the fediverse without causing fragmentation.

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.

What you’re describing is no longer federation but full P2P. From a purely technical point of view, it may work, but the biggest problem will be abuse (spam, excessive resource use, illegal content). When a new instance shows up, how do you know if it’s a spammer or not? And if an instance is blocked by another instance, whose side should you be on?

This is true. If you run the reddit-grab project directly without using the warrior (sudo docker run -d --name reddit --label=com.centurylinklabs.watchtower.enable=true --restart=unless-stopped atdr.meo.ws/archiveteam/reddit-grab --concurrent 6 yourname), you can set up to --concurrent 20, and some projects do work well with higher concurrent, but not reddit. 6 is already pushing the limit.

I’m running reddit-grab on 25 VMs on azure (trying to burn my $200 free credit that expires in 10 days) and I can only run --concurrent 4 safely on most of them. The only VMs that can run --concurrent 6 are the ones in India, which seem to be soft-ratelimited by their higher latency anyway.

I think the biggest cost will be image/video storage. The text takes very little space in today’s standards. The good thing is that symmetric fibre internet connections are becoming more common so it may be possible for members of the instance to contribute unused disk space to help with its image/video storage. This plus limiting the image/video sizes (and maybe forbidding video uploads altogether) will allow the instances to scale with user count.