muddybulldog

Problem is, it IS hosted here. That's the nature of the Fediverse. It doesn't just create links to other instances, it creates distinct copies of content on each instance. I am neither viewing this post on lemmy.world nor responding to it via lemmy.world. I am interacting with a distinct copy hosted on a completely unaffiliated instance, in a completely different country.

Your analogy to Google is flawed. Google links to content on other sites. Lemmy sites host distinct copies of content on each instance. While the communities aren't @lemmy.world communities the content is 100% hosted on Lemmy.world by nature of federation.

• https://lemmy.ml/post/3375472
• https://lemmy.world/post/3234363
• https://lemmy.dbzer0.com/post/2148792

All this post. Hosted on three completely different instances, with different admins. "It's not actually my community" doesn't work in the Fediverse.

The risk, however, is that you're going to be potentially liable for things that you DON'T see but are hosting due to federation.

That's your prerogative and the upside of the fediverse, as a whole.

The downside is that you may be held legally liable for something you completely had no part, or even knowledge, of simply because your federation has caused content to propagate to your instance. Now it's on your instance, you're hosting it and you're potentially liable.

They’re trying to avoid law enforcement and lawyers at their doors.

Even if you prevail, either can be a very expensive and/or destructive process.

Make no mistake, Reddit’s recent refusal to provide details surrounding users that were discussing piracy is highly unlikely to happen in the fediverse. Admins are going to get hit with a subpoena and comply because they can’t afford not to.

Federation is enabled by default. Defedersting takes explicit action..

It’s not a component aware system. The last phase is generally the spin cycle. The controller knows to trigger the spin cycle, it knows to stop the spin cycle after a period of time. What it doesn’t know is whether those things actually happened. Particularly, it doesn’t know that the drum has actually stopped spinning. So, it just wait a predetermined amount of time before unlocking the door.

In the case of my own device the door actuator uses a wax motor. Put simply, current is changed to heat which melts the wax, pushing a pin the locks the door. To open the door, current is removed, the wax cools, hardens and shrinks and the pin slides back. Now the door can open. So, even if I remove power during a cycle the door will eventually unlock as the wax cools.

Are you using a VPS or self-hosting?

What do you want to hear?

None (by Lemmy), as Lemmy doesn't actually request the image (that would be proxying). Your browser requests the image directly by URL. Lemmy, technically, doesn't even know an image exists. It just provides the HTML and lets your browser do the work.

Senior management made the case that my unit didn’t have the appropriately documented KPIs to work from home. I made the point that we’d been operating under the existing KPIs for the last 15+ years in the office without issue so the only obvious metric missing was “butts in seats”.

While nobody clapped I’m still employed and the team does have WFH agreements in place.

Take a bow.