it’s in the main settings area:

check if your piefed account has pms from other instances enabled. afaik piefed.social had this disabled by default for some time during the nicole spamwave.

fyi also @Bonus@lemmy.world

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.

seems to work for me

it’s the software, similar to how you’re using lemmy right now

no notification of a moderation event

lemmy.world has notifications for local users or users in local communities for removed content.

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.

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?

piefed doesn’t support animated media yet, iirc it doesn’t work in posts either

pixelfed supports signing in with mastodon, not sure about others

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.

see here: https://lemmy.world/post/11967676

i guess to put it in perspective i should have included other containers as well.

this is on a 32 physical core box with 96gb of memory:

NAME                    CPU %      MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O
lemmy-lemmy_ui_1-1      13.59%     1.864GiB / 94.15GiB   1.98%     198GB / 1.34TB    5.5GB / 4.45GB
lemmy-lemmy_ui_3-1      20.12%     2.764GiB / 94.15GiB   2.94%     312GB / 2.22TB    6.36GB / 4.24GB
lemmy-lemmy_ui_2-1      54.07%     2.042GiB / 94.15GiB   2.17%     222GB / 1.52TB    5.61GB / 4.61GB
lemmy-lemmy_api_3-1     10.16%     3.629GiB / 94.15GiB   3.85%     5.6TB / 1.71TB    290GB / 411GB
lemmy-lemmy_sched_1-1   0.01%      42.79MiB / 94.15GiB   0.04%     9.72GB / 1.23GB   1.38GB / 2.56GB
lemmy-lemmy_api_2-1     30.97%     4.049GiB / 94.15GiB   4.30%     5.07TB / 1.57TB   281GB / 401GB
lemmy-lemmy_api_1-1     27.39%     3.913GiB / 94.15GiB   4.16%     4.95TB / 1.54TB   286GB / 404GB
lemmy-postgres-1        1500.05%   49.99GiB / 78.12GiB   63.98%    1.84TB / 27TB     59.2TB / 67.7TB
lemmy-lemmy_fed_1-1     405.39%    802.1MiB / 94.15GiB   0.83%     3.67TB / 5.67TB   12.9GB / 19.4GB
lemmy-pictrs-1          514.29%    1.495GiB / 94.15GiB   1.59%     8.79TB / 5.36TB   511GB / 114TB
lemmy-pictrs_db-1       2.76%      2.956GiB / 68.36GiB   4.32%     531GB / 325GB     13.1TB / 9.25TB

with lemmy it’s a lot easier to separate frontend performance from backend performance, with piefed that’s harder to tell when not just using the APIs and requires more analysis. proper indexes and well crafted queries have a lot of impact though. most logic that you can move to the db side is probably better done there, but it can make queries a lot more complex.

NAME               CPU %      MEM USAGE / LIMIT    MEM %     NET I/O           BLOCK I/O      
lemmy-postgres-1   1717.01%   48.6GiB / 78.12GiB   62.21%    1.84TB / 26.9TB   59.2TB / 67.7TB

the container has been up for 3 weeks