this post was submitted on 22 Jan 2026
50 points (98.1% liked)

Slop.

771 readers
625 users here now

For posting all the anonymous reactionary bullshit that you can't post anywhere else.

Rule 1: All posts must include links to the subject matter, and no identifying information should be redacted.

Rule 2: If your source is a reactionary website, please use archive.is instead of linking directly.

Rule 3: No sectarianism.

Rule 4: TERF/SWERFs Not Welcome

Rule 5: No bigotry of any kind, including ironic bigotry.

Rule 6: Do not post fellow hexbears.

Rule 7: Do not individually target federated instances' admins or moderators.

founded 1 year ago
MODERATORS
 

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 6 points 5 days ago (1 children)

Ah yeah I see where I got mixed up. Sorry! Was the end of my day and doing to many things at once.

But do I have it correct that it seems as though individual users have some amount of control over how content federates on their instance through the blocking mechanism?

It's clamped to just the user's content, their comments and posts, but it still prevents federated content from being stored on the server or content being federated to other servers.

It's not a purely cosmetic block right? Because it changes what other users see relative to my own content. Unless I'm still confused about how this works.

If I make a post and I have a large block list of users from other instances, those users could be replying to my posts on their instance. But on my home instance, it wouldn't store those in the database because I've blocked them, which would result in users from my home instance never seeing them either, right?

[–] edie@lemmy.encryptionin.space 6 points 5 days ago* (last edited 5 days ago)

But do I have it correct that it seems as though individual users have some amount of control over how content federates on their instance through the blocking mechanism?

It’s clamped to just the user’s content, their comments and posts, but it still prevents federated content from being stored on the server or content being federated to other servers.

AFAIK, Correct.

It’s not a purely cosmetic block right?

It's not. See the two examples in your original comment (Cowbee, and me replying to my test accounts)

Because it changes what other users see relative to my own content.

Yes.

If I make a post and I have a large block list of users from other instances, those users could be replying to my posts on their instance. But on my home instance, it wouldn’t store those in the database because I’ve blocked them, which would result in users from my home instance never seeing them either, right?

Exactly.


This user is suspected of being a cat. Please report any suspicious behavior.