lemmy currently doesn't have granular federation controls. the only option right now is to defederate from mbin instances, but other instances might still announce your users' votes to mbin instances. the more hacky way would be to also block federation related http requests from mbin instances to prevent them from retrieving user profiles, which is probably the most effective method that could be used.
piefeds non-federated votes are a user setting for the default value and users have the option for each vote whether it should be federated. see also https://piefed.social/post/982478
as explained in this post, the original implementation of "private voting" has already been replaced with non-federated voting, which addresses the abuse concerns, as it's then limited to just the instance the votes are cast on.
piefed is a fair bit younger, the first commitin the git repo was on Fri Jul 28 02:07:44 2023 +0000. it has only in recent months started really picking up some traction with several lemmy instances already creating piefed instances as well.
lemmy doesn't support subscribing to users, but you can subscribe to communities the same way you'd subscribe to other communities from other instances.
nobody needs to move to another platform. both lemmy and piefed show the same content, think of it more like using a different client that also has different features. both lemmy.world and piefed.world will continue to exist.
piefed does have some social auth support, which is currently also being worked on, but lemmy is not an auth provider that can be used with that. once social auth in piefed becomes more stable we will consider enabling it for supported providers.
i think the graph might not be fully accurate for the current hour? looking at it now it doesn't show that significant of a spike anymore. i don't see anything in our logs about federation issues from LW to p.d in the last 15 days.
My idea was to serve it in a way that would allow ActivityPub clients to resolve content still, while having a light static render for other clients for local content.
For content on other instances it would probably require some kind of lightweight redirection service towards the original item to be set up to prevent breaking those URLs.
This could probably be built just from scraping, without requiring database access.
I've considered setting up a static read-only copy of lemm.ee, but without being able to host this on the original domain i don't think it'll be of much use. i already reached out to @sunaurus@lemm.ee to see if he would be interested in something like this, doesn't seem like anything was planned from his end so far.
MrKaplan @ MrKaplan @lemmy.world Posts 0Comments 293Joined 1 yr. ago
lemmy currently doesn't have granular federation controls. the only option right now is to defederate from mbin instances, but other instances might still announce your users' votes to mbin instances. the more hacky way would be to also block federation related http requests from mbin instances to prevent them from retrieving user profiles, which is probably the most effective method that could be used.
piefeds non-federated votes are a user setting for the default value and users have the option for each vote whether it should be federated. see also https://piefed.social/post/982478