To allow the cable to work as a delay line memory, be sure to plug both ends into the router.
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.
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.
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.
I gave the bill a quick read.
It depends on the contents of the link. Is it a bare URL? Is it a text “click here”? Is it the title of the linked page? Is it a snippet of the linked page? You can quickly see how linking can incorporate copying depending on how it’s done.
I consider snippets copying, not linking, but let's agree to disagree on the terminology, because the bill covers anything from URLs to snippets anyway.
significant bargaining power imbalance
This is what the bill actually says, so we're small fish and get a free ride.
Combined toilet-sinks are a thing. It saves water by reusing the water you used to wash your hands to flush the toilet.
Nay. Banning the defederationists makes you as authoritarian as them. We should instead constantly remind them that much of the social progress they take for granted today were made possible by free speech.
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.
Nay. You're gonna encounter these people IRL. It's better to prepare yourself in a low stake environment like an internet forum.
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.
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.