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.

did you see an orange/white cloudflare error page or something else? i tried searching for it in our server logs but i don’t find it.

you may however have hit an outage we had for several minutes around an hour before your comment due to running out of memory on the host.

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.

what kind of error did you see and what did you click on? a link to a post?

pretty much, yeah. different people, different programming languages, some feature differences, etc. but still the same content.

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.

not that i know of. old.lemmy.world is a whole separate user interface, but a similar look can probably be achieved with themes alone.

no, accounts are completely separate.

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.

that’s because it’s a spam bot

sorry about the late response, got a lot of stuff going on currently and it seemed like you got useful replies here already anyway when i checked before.

we currently have a rule in place that blocks traffic with too high of a threat score. this rule was implemented before i joined, i’ll have to check with the team about the original reason for this and if we want to relax this.

at least the error message should be improved if we can do that, i think that’s just returning a static message currently.

you’re probably looking for the !perchance@lemmy.world community