PieFed vs Lemmy. What say you? (lemmy.world)

submitted 2 weeks ago* (last edited 2 weeks ago) by LemmySlopSkimmer@hexbear.net to c/slop@hexbear.net

189 comments fedilink hide all child comments

So, it seems like PieFed is becoming a real alternative to lemmy.

What are the differences between these two? From a tech perspective, and also morality/ethics, if you want. Any differences in vision for these services?

Say whatever is on your mind. I want to know.

On which one should we put our weight?

PieFed all the way. It’s developing at lightning speed, while Lemmy lags behind as the transphobic genocide denying devs beg for donations with in built donation begging banners on all Lemmy instances front pages. Instances are apparently scared to defed from .ml for fear the devs wont support them with help.

Rimu has made some interesting choices, such as blocking 196 from default federating posts until a user subs first or a dislike for meme subs. But when spoken to has been receptive and removed such things or made them optional for admins.

Ethically and feature wise PieFed is in the lead, its not perfect but its open to change and receptive to ideas

you are viewing a single comment's thread
view the rest of the comments

[-] RedWizard@hexbear.net 7 points 2 weeks ago* (last edited 2 weeks ago)

Wait. The logic flow makes sense though. I've been double checking this. The proactively_delete_reply only proactively deleted if the parent user has the replying user blocked.

What this means, is that this function is attempting to mirror the host instance even closer. LocalUser (LU) blocks RemoteUser(RU). LU makes a comment that federates to RU's instance. RU replies and their comment is sent back to LU instance.

LUs community where the comment is received checks its inbox. It then validates the comment. It then checks to see if the comment is from a site banned user, it passes. It then checks if the RU is blocked by the parent comment user (LU), it fails.

In 1.5.X currently this returns None thus never storing the comment.

In the main branch however, a secondary task is fired off, calling proactively_delete_reply only if the community is local. proactively_delete_reply searches for a mod or admin account and sends a moderator action back to the remote server with the note "Automatic delete do to block".

This is because of a few reasons:

They prevent local users from leaving comments on posts and comments from users who block them using the UI.
They CANNOT do this for remote piefed instances (I think). They obviously can't do it for Lemmy instance. Thus the Return None.
Now this new code enforces the removal of the comment on the remote server because it is already stored in the DB.

They are effectively enforcing blocks at the DB level instead of the API level. Lemmy to my understanding will simply flag the user as blocked and it is on developers to prevent the content from being displayed to the user.

The implications seem to be that in the future if a Lemmy user replies to a post or comment from a piefed local community, and the author blocks them, a federated mod action will be sent to the Lemmy server to remove the comment.