![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/0d5e3a0e-e79d-4062-a7bc-ccc1e7baacf1.png)
Defederating cuts off the whole instance. They just blocked those three piracy communities as far as I understand.
These are all me:
I control the following bots:
Defederating cuts off the whole instance. They just blocked those three piracy communities as far as I understand.
Remember that lemmy.world has to keep a copy of whatever content appears in a federated community on their servers, making them legally liable for the content. At least they just blocked the community instead of defederating.
A strength and a weakness. The strength, as you say, is being able to move to a different instance. However, the weakness is that Lemmy (the software) requires each instance to keep a copy of every federated post for its users to interact with. This means they have to host (and be legally liable for) data that they can’t police beyond blocking the community / instance.
Not really - it isn’t prediction, it is early detection. Interpretive AI (finding and interpreting patterns) is way ahead of generative AI.
Like I said - there is a small vocal group who few that Lemmy as a whole should be boycotted due to the developers’ political views.
Why would a Kbin user want to speak to you, a Lemmy user?
Some people are excessively sensitive to software developer political views.
Lemmy isn’t Kbin and Kbin isn’t Lemmy. Both are software participants in the fediverse. It is like saying nginx isn’t Apache: of course isn’t, but that doesn’t make them any less web servers.
While I agree there should be functionality to propagate changes to a community between instances when the host is offline, there is no practical way to share administrative control of a community. Any decision by an administrator to sanction a community or defederate an instance will just result in exactly the fragmentation you fear.
The real solution is for small groups of communities with similar interests to gather on separate instances with few or no users. Meanwhile, other instances gather users with few or no local communities. This maximizes the benefits of cacheing community content while minimizing the impact of defederation. If a community host can no longer be maintained by its owner, that ownership can be easily transferred without transferring the burden of hosting hundreds of communities or supporting user logins.
If the mods can agree on policy, there is absolutely no reason to have two communities. Shut one down and use the other.
Edit: can someone explain to me what the difference between synchronizing two communities and subscribing to a federated community is? I mean, that’s exactly the point of federation.
No, and the difference between Beehw and Lemmy.world is why. Different people have different views about moderation and what is acceptable content.
There are two solutions to the real problem of duplicate content:
There is no point to linking communities- if they are going to have identical content, just pick one or the other.
A better option would be for cross posts (using the Lemmy cross post feature) to exist as a single entity that is visible in multiple communities. This would allow for some differences in moderation which is the justifiable reason for multiple communities on the same topic in the first place.
The irony that this story was posted by a bot…
Bots that don’t identify as such count towards active users. There have been a number of bot purges.
Pro-tip: if you are trying to figure out if a website has a feature, try the default web interface first.
I’ve reported pictures/gifs of accidental nudity that were posted on Reddit without any evidence of consent, and they blew me off. Not just ignored me - they took the time to say the content was fine.
Yeah, it was legal to post stuff like that - no reasonable expectation of privacy in public places and all that. But it isn’t ethical. Don’t do it. It isn’t funny.
Well, LED lights are half-wave rectifiers that light up, so you wouldn’t add one. I don’t think I’ve ever heard of a half wave rectifier referred to as a bridge rectifier.
A bridge rectifier flips the negative current to positive, so instead of a sine wave you get a series of humps. Then a capacitor acts as a battery like you describe to smooth out the dip between humps.
My LED burn outs were almost certainly defective, not normal wear.
Also, cheap ones run directly on AC, so they flicker at 60 Hz (50 in Europe) because the current is only flowing for half the cycle.
Nature knows how to solve this problem.