Yes, good idea.

The main challenge is that we’d need to run the ‘get posts’ database query twice - once with no filters and once with the filters. These are big queries so they’re slow and hard to optimize. You really really don’t want to run them more than once per page load.

If you wanted a breakdown of which filter caused how many posts then you’d need to run one query per filter and compare it with the no-filter version to see the difference. So, about 6x. Impractical.

If all the filtering was done in the app logic (rather than on the DB server, using SQL) then it would be trivial to count up which filter did what, as the code looped through the posts. But I’m very sceptical about the performance potential of this, there’s a reason why we do as much filtering as possible on the DB… It’d be an interesting experiment to try.

Excellent news.

No doubt the struggle is not over but this is something to celebrate anyway 😁

The label doesn’t do anything until individuals opt in to filtering based on it.

We can’t leave it to the reposters to self-identify because

1. Lemmy does not have the functionality to do that and

2. reposters are deceptive and sneaky

Individuals, yeah. Instance admins are going to need to designate reposters if they refuse to self-designate (and Lemmy doesn’t have functionality for them to do that, except as a bot) and then it’s up to individuals to decide whether they filter out reposters or not.

It’s manually-applied and reversible. I can’t reliably code an automatic reposter detection system because they’re all different. It’s going to have to be a human judgement.

Similar to labelling things as AI-generated or NSFW - being a reposter isn’t necessarily bad. It just means that people who don’t mind whether they see it can do so and those who don’t want to can avoid it, without the conflict that ensues when people with different needs and tastes are forced to share space.

Not yet, this functionality isn’t running on a live server.

Yes the screenshot is just the user settings. Admins are going to have to manually designate accounts as reposters because I haven’t even tried to make an automated detection. That would be very hard to get right.

Working on it!

No, but every PieFed post you make will be sent to your Mastodon followers. And you can follow people on Mastodon and have their posts appear in your home feed.

Mastodon integration like this still very new and experimental for PieFed but is a high priority for future development.

The NoGoogleAi firefox extension solves this.

The last post from you was 8 months ago, lol

It’s a bot

Yeah that’s pretty crazy but this bit is crazier - https://www.anthropic.com/threat-intelligence-report-september-2026#cyber-operations-sep-26

AI is a useful tool, for all its flaws and negative externalities.

“If you ignore the negatives for everyone else and just focus on the positives for me, it’s pretty great”

Mhmm. Right, ok.

People who want to believe Anthropics AI is powerful.

https://deadsimpletech.com/blog/no-such-thing-as-just-a-tool

lemmy.ml and dbzer0 are silenced on piefed.social, which makes their communities hard to find.

But if you go to their url directly you can join them like normal:

https://piefed.social/c/asklemmy@lemmy.ml

https://piefed.social/c/piracy@lemmy.dbzer0.com

There is no hardcoded instance block list. There are some instances that are defederated from initially when an instance is first created but the instance admin is told about this when it happens and they can change it by clicking around in the admin area. More info at https://join.piefed.social/2026/08/13/what-piefed-blocks-out-of-the-box-and-how-to-unblock-it/

https://piefed.social/c/fediverse@piefed.social/p/2190040/who-decides-what-you-see-on-the-fediverse-a-look-at-voting-patterns

PieFed instance admins can set a limit to how many votes each account can cast each day. I set the default value for this at a level that 99% of us will never reach.

This pissed off some of the 1% (or people who thought they were the 1% but weren’t) so they spent weeks spreading FUD about it.

2-3 times a week is nothing. 2-3 per day is completely fine.

It would only be used for the most flagrant accounts, ones with some level of automation - dozens of posts per day with almost no comments. That sort of thing.

I too find content on other networks (mostly Mastodon, occasional YouTube) and post them here. Often a few per day. But it’s all completely manual and I usually rewrite the description, add hashtags, etc. And I’ll interact with people who comment on the posts. Cross-pollination of content is normal and good.

There’s a point though, usually enabled by using some extra software tools like the one above, where someone ends up flooding their target communities, not responding to comments on the posts, looking inauthentic when they repost OC which plainly isn’t theirs and causing extra moderation work because their content is in the wrong places. Sanitation is the most obvious example of this but there are others.

Despite this, a lot of people upvote and comment on their posts. I don’t know if

1. they’re even aware of who the author is. Most apps do not emphasise this strongly so it’s easy to miss.
2. if they are aware then are they aware that the author is ignoring them and won’t learn from the feedback they’re getting?

… Or if they don’t care. Maybe they’re just content with the conversation in the comments without the OPs involvement. That’s valid (although not the kind of conversation I personally want to be a part of).

It’s probably a combination of don’t know and don’t care. For those people, labelling sanitation et al as a bot would seem heavy-handed. That’s why I’m leaning towards creating an in-between state, for these kinds of centaur accounts.